I’m using the map API endpoints to query geographic features from OpenStreetMap data. Specifically, I’m working with the following endpoint: https://overpass.kumi.systems/api/map?bbox={{bbox}}.
Using this API, I’m able to retrieve features of various geometry types including nodes, ways, and simple polygons by providing a bounding box. However, I’ve noticed that multi-polygon features are not being returned in the responses, which limits the completeness of the data for certain use cases (e.g. administrative boundaries, parks, and complex building footprints).
Here are a few examples of queries I’ve used for reference:
- Berlin example
- Pittsburgh example
In contrast, when using the Overpass Interpreter API (e.g. via overpass-turbo.eu), I’m able to retrieve those missing multi-polygon features without issue.
I’m wondering whether this is expected behavior due to how this endpoint is optimized, or if there’s a way to include multipolygon data in the results. If not, would using a different endpoint (such as the Overpass QL interpreter) be the recommended approach for getting complete geometry data?
If the interpreter endpoint is recommended, please share documentation or examples for querying the API directly.
Any clarification or guidance would be greatly appreciated!