OpenStreetMap User's Diaries
How a free bird-finder uses OSM data (and what we want to fix eventually)
I’m part of a small volunteer team that runs birding.live, a free site that helps people find birds and green spaces near them. Thought it made sense to introduce how the site leans on OSM data, and to say thanks.
What we do with OSM: geocoding and place search come through Nominatim with an identifying user agent, throttled through our own proxy. Nearby parks, woods and reserves are pla
I’m part of a small volunteer team that runs birding.live, a free site that helps people find birds and green spaces near them. Thought it made sense to introduce how the site leans on OSM data, and to say thanks.
What we do with OSM: geocoding and place search come through Nominatim with an identifying user agent, throttled through our own proxy. Nearby parks, woods and reserves are place queries framed from OSM data, mostly via Geoapify’s OSM-derived layer, and walking trails come from Overpass as named route relations for hiking, foot and walking. Plain paths only ever show up if their OSM tags carry a real signal like difficulty grading or waymarking, so road connectors and farm tracks don’t pretend to be trails.
Who it’s for: the site is a five minute route into birding for beginners. You type a place, see which birds have been reported around it recently from the eBird community, and get a map of parks, reserves and named trails to walk, all credited as OpenStreetMap contributors, ODbL.
Two things we want to improve, honestly: watching how the trail queries behave in areas with patchy tagging, and starting to give corrections back once we’re confident enough to do it properly. If you’ve got pointers on Overpass named-route queries, or you spot one of our pins naming something wrongly, that kind of eye is very welcome.
If you’re curious the site is birding.live and the code is at github.com/chocobar/birding. Thanks for the years of contributor effort behind every pin on our maps.
I’m part of a small volunteer team that runs birding.live, a free site that helps people find birds and green spaces near them. Thought it made sense to introduce how the site leans on OSM data, and to say thanks.
What we do with OSM: geocoding and place search come through Nominatim with an identifying user agent, throttled through our own proxy. Nearby parks, woods and reserves are pla
I’m part of a small volunteer team that runs birding.live, a free site that helps people find birds and green spaces near them. Thought it made sense to introduce how the site leans on OSM data, and to say thanks.
What we do with OSM: geocoding and place search come through Nominatim with an identifying user agent, throttled through our own proxy. Nearby parks, woods and reserves are place queries framed from OSM data, mostly via Geoapify’s OSM-derived layer, and walking trails come from Overpass as named route relations for hiking, foot and walking. Plain paths only ever show up if their OSM tags carry a real signal like difficulty grading or waymarking, so road connectors and farm tracks don’t pretend to be trails.
Who it’s for: the site is a five minute route into birding for beginners. You type a place, see which birds have been reported around it recently from the eBird community, and get a map of parks, reserves and named trails to walk, all credited as OpenStreetMap contributors, ODbL.
Two things we want to improve, honestly: watching how the trail queries behave in areas with patchy tagging, and starting to give corrections back once we’re confident enough to do it properly. If you’ve got pointers on Overpass named-route queries, or you spot one of our pins naming something wrongly, that kind of eye is very welcome.
If you’re curious the site is birding.live and the code is at github.com/chocobar/birding. Thanks for the years of contributor effort behind every pin on our maps.
OpenStreetMap Blogs

