Brian Sperlongano bc9bbd2e67
Coalesce duplicate route concurrencies (#1361)
# 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.
2023-01-26 16:15:47 +01:00
..
2022-07-26 15:26:57 +02:00
2023-01-15 13:52:43 +01:00
2022-07-26 15:26:57 +02:00
2023-01-15 13:52:43 +01:00
2017-03-15 13:55:18 +01:00
2023-01-06 10:08:03 +01:00
2023-01-15 13:52:43 +01:00

transportation

Docs

Read the layer documentation at http://openmaptiles.org/schema#transportation

Mapping Diagram

Mapping diagram for transportation

ETL diagram

ETL diagram for transportation