One of the as yet to be solved issues regarding eBird data is its lack of easily extractable data at resolutions finer than county. Oregon counties are large and unwieldy unlike East Coast counties where most birders (and apparently most eBird programers) live. Several of us have brought this up (once or twice) in previous eBird discussions.... I have mostly used brute-force methods to extract data. With Bean Goose data, I pulled up the map in "Explore Data > Species maps" and then clicked on every balloon and wrote the info I wanted on a legal pad. I then put it into a spreadsheet myself. You can probably get a close approximation species list by picking a common species (like Song Sparrow) for a species map and then zooming in to the Diamond Hill area. You'll still have to hand capture all the lists and you may need to pick more than one common species to get enough lists. You could also go to birdnotes.net and generate a checklist for Diamond Hill wetlands. But that looks like its mostly populated with data you put there, so it may not add anything... I am told that eBird will eventually have aggregate capacity a finer scales using polygons, but don't expect it any time in the next couple weeks... -- Mike Patterson Astoria, OR the CODE http://www.surfbirds.com/community-blogs/northcoastdiaries/?p=2702 OBOL archives: www.freelists.org/archive/obol Manage your account or unsubscribe: //www.freelists.org/list/obol Contact moderators: obol-moderators@xxxxxxxxxxxxx