eBird and the BBS
This weekend I ran my Mini Breeding Bird Survey. Or, at least, I tried to (more on that in a bit). The MBBS is the brainchild of a former ornithology professor at UNC in which birders in Orange, Durham, and Chatham counties run smaller, shorter versions of the venerable, and effective, Breeding Bird Survey. The protocol for the MBBS is identical to that of BBSs, only the mini counts are 9.5 miles instead of 24.5, and can usually be ripped out in a morning before the rest of the world even has their coffee. The data isn’t warehoused in a USGS database, but kept for local use and mostly for personal interest, though lately the administrator has been interested in getting the data into eBird, which I think we can all agree is a very good thing.
The question of how to most effectively do this, however, is still up in the air. This is my first year participating, and I came into a system of data entry to eBird that seems unorthodox. Instead of entering data for the individual stops, the entire checklist is entered for the entire route, placed on a spot somewhere in the middle of the 9.5 miles. Because the magic of eBird relies of site specificity, this seems like it’s less than ideal.
Don’t get me wrong, having the data, especially good, complete data like this, is always better than not having the data. But on a lark, I decided to make a separate checklist for all 20 stops on my route to see how something like that would work. I ended up with a map like this:
It was mostly easy to get the checklists submitted. Fortunately, I like the monotony of entering data and the checklist for a 3 minute point count is hardly an imposition. I had between 5 and 14 species for every stop. The question now is how to best convince my fellow MBBSers, who may be older and certainly not as obsessive about properly entering data into eBird as I am, that this is the right way to go about it.
The answer is probably to create a spreadsheet that can be distributed to the counters, who can then fill in the species seen and the lat/long of the stops (easy enough to remind people to do) and use eBird’s fabulous bulk upload file importer. And the genius is, once the initial spots are entered one never has to worry about it again. Now, this doesn’t entirely apply to those who do the traditional BBS, which has a data entry system already in place, but there are, undoubtedly, serious eBirders out there who BBS, and I’d be curious to know how they put the data in for their own records. So let me know in the comments if you’re one of those people.
And I mentioned earlier that I had only “tried” to run my route. Turns out I got the start location wrong (I started at Hwy 86 instead of OLD Hwy 86 – thanks a lot NC Department of Transportation), cutting off the first 2 miles of my route and going two miles too far on the other end, so I’ll have to rerun the route next week. Fortunately, thanks to eBird, all my locations are ready to go (at least all but the last 3). So there’s that. Let’s just call this one a warm-up run.