search

drolbr / Overpass-API

A database engine to query the OpenStreetMap data.
http://overpass-api.de
GNU Affero General Public License v3.0
693 stars 90 forks source link

Overpass Boundaries / LEZ #595

Closed vshcherb closed 3 years ago

vshcherb commented 3 years ago

This is a feature request that might sound like a question.

Introduction: Since OSM-mappers decided to map LEZ https://wiki.openstreetmap.org/wiki/Tag:boundary%3Dlow_emission_zone as boundaries, it created some difficulties for routing engines. In contrast of maxspeed= tag which is mapped on each road and could be natively processed by routing, LEZ tag is a boundary and requires propagation from boundary to the road segment itself.

Feature request: Overpass supports boundaries natively and can query objects by certain boundaries and filters. Is it possible to process "data.osm" file containing osm ids (geometry if needed), so Overpass could filter out only ids that belongs to certain boundary. In case of this request the question is to detect which OSM ids belong to (boundary=low_emission_zone). OSM ids are provided by batch

mmd-osm commented 3 years ago

https://overpass-turbo.eu/s/Y08 would be an example query for one bbox. Note that ways will be included as a whole even if only a small part lies within the low emission zone.

You can also provide a list of way ids and check if those ids are still in the query result, in which case the way would be part of a low emission zone: https://overpass-turbo.eu/s/Y0b

Processing an data.osm would mean, that you run update_database to create an initial version of the database, followed by an area creation run via osm3s_query, and eventually execute your query via osm3s_query.

So after all, that's not really a feature request, you can achieve this already today by setting up some toolchain.

vshcherb commented 3 years ago

Thanks, I will need to catch up with features I was not aware of like map_to_area