Overpass API developpement

[Roland Olbricht <>]

Hi Brian,

I'm sorry for the late answer.

> We are transitioning off using http://overpass-api.de/api/map?bbox={bounding 
> box cords} and I am now using 
> http://my-ip/api/interpreter?node({bbox_coords});out body;
> We get different results but I haven't been able to pick apart the response 
> just yet to figure out whats different (only the end result). Do you know 
> what the different would be? Essentially we want to get all features within a 
> bounding box, would node({bbox_coords});out body; be the right query for that?

Most likely, it is the wrong query. It only fetches features mapped as
nodes. Features can be mapped as ways or relations as well.

Please note that http://my-ip/api/map?bbox={bounding box cords}
is highly likely to just work. If you want to use /api/interpreter
then I suggest using
http://my-ip/api/interpreter?nwr({bbox_coords});out center;

The documentation has more details:

https://dev.overpass-api.de/overpass-doc/en/full_data/map_apis.html#map
explains what the map API call actually does.

https://dev.overpass-api.de/overpass-doc/en/full_data/osm_types.html#full
lists various approaches to get the full data including geometry.

Please note also that the order of coordinates changes between the map
API call and the QL queries (the map API call has lon-lat for historic
reasons, the standard is lat-lon).

Best regards,
Roland