kopia lustrzana https://github.com/openmaptiles/openmaptiles
bc9bbd2e67
# Problem description #1128 introduced route relation concurrency information in OpenMapTiles via the `route_X` attributes. The original implementation assumed that there would be a single route relation for each `network` and `ref` pair. However, it is increasingly common practice to tag a separate route relation for each direction of a route in order to provide awareness to routers and other data consumers of the directionality of a route. This standard and growing practice is described on the [OSM wiki page on route directions](https://wiki.openstreetmap.org/wiki/Route_directions). Thus, the naïve implementation of #1128 caused duplicate entries to be added as `route_X` attributes in the case where separate route relations were used for directional routes. # Solution description This PR adds grouping when computing route concurrency information, such that duplicate entries are coalesced in a predictable way. Since this grouping is done only within a route membership join of a single member way, the computational complexity should be trivial. |
||
---|---|---|
.. | ||
100_import-large-park.osm | ||
200_import-aerodrome.osm | ||
300_import-landcover.osm | ||
400_import-boundary.osm | ||
500_import-highway.osm | ||
600_import-poi.osm |