What is the difference between Nominatim and Overpass-Api?
What can't I do with Nominatim that I can do with the overpass-api ?
-
4In your research so far what have you found to be any evident differences?– PolyGeo ♦Commented Nov 5, 2016 at 10:08
-
1What are you trying to do?– John PowellCommented Nov 5, 2016 at 13:58
-
Welcome to gis.stackexchange! Please note that a good question on this site is expected to show some degree of research on your part, i.e. what you have tried and - if applicable - code so far. For more info, you can check our faq.– underdarkCommented Nov 5, 2016 at 20:01
Add a comment
|
1 Answer
Nominatim is a geocoder and reverse-geocoder. You can search for an address and it will return the location. Likewise you can search for a location and it will return its full address hierarchy. Nominatim usually only returns address-related tags from OSM.
Overpass API instead can query for all tags in OSM. You can search for POIs, parking spaces, roads, rivers, speed cameras, traffic lights, ... However it just allows you to search for raw tags. It doesn't know about addresses (except for the raw address tags in OSM), especially it lacks the knowledge of address hierarchies.
For a better understanding of their differences and specific use-cases take a look at the Nominatim examples and Overpass API exmaples in the OSM wiki.
-
1Overpass API feature list looks somewhat incomplete, which is probably due to the language guide cited (it's a bit dated). For a better idea on what is possible, I'd recommend to take a look at the following wiki page: wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL -– mmdCommented Nov 5, 2016 at 20:21
-
-