Revision of Breeding-Bird-Survey-of-North-America from Sat, 2010-05-01 18:29

Revisions allow you to track differences between multiple versions of your content, and revert back to older versions.

Overview: 

 

About BBS

BBS Website

The North American Breeding Bird Survey (BBS) was formally launched in 1966 when approximately 600 surveys were conducted in the U.S. and Canada east of the Mississippi River. Today there are approximately 3700 active BBS routes across the continental U.S. and Canada, of which nearly 2900 are surveyed annually. Breeding Bird Surveys are conducted during the peak of the nesting season, primarily in June, although surveys in desert regions and some southern states, (where the breeding season begins earlier), are conducted in May. Each route is 24.5 miles long, with a total of fifty stops located at 0.5 mile intervals along the route. A three-minute point count is conducted at each stop, during which the observer records all birds heard or seen within 0.25 mile of the stop.


Aquiring BBS

BBS Raw Data

FTP site


Using BBS

BBS Survey Routes map layer available at: http://sagemap.wr.usgs.gov/FTP/unitedstates/NATLAS/birdm.htm

Last modified: 
2019
Taxonomic Group: 

Comments

I see there are some tags at the bottom, e.g. Aves and time series, but it would be useful to have a header that actually says "Tags", because right now it just looks like additional entries under About Using BBS or whatever it is.

This 2012 Ecological Archives dataset (http://esapubs.org/archive/ecol/E093/215/) contains landcover and landscape configuration data for 3,890 BBS routes. Add to EcologicalData and reference it on the BBS data page? (No organismal data, so I don't know how else one would discover it from the Find Data boxes.)

Also, this could be incorporated into the Retriever so it is automatically downloaded and integrated with the bird data!

Both excellent suggestions. Please add away.

We're in the process of planning for how to build integrated datasets into the Retriever and I'll go ahead and add a feature request for adding this one.