You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Network property is in Germany set to road even a network is available. The streets should always have a network so that the streets can be equipped with the national signs, as with mapbox street style.
Projects like openstreetmap-americana use the route_n tags instead to render highway shields since a road may belong to multiple networks. They publish the highway shield renderer as an npm package too.
The example from Germany is part of both an Autobahn and an E road. #1619 would’ve set the network to e-road, but #1648 backed out this change because it broke some clients.
From my point of view, it would make sense to include this as a shield property in transportation_name.
You can think of route_* as shield_*. As of #1620, the format has changed so that there are more properties. This should make it easier for you to pick out segments that are part of a network you’re interested in, even if you don’t intend to render a shield based on it.
Network property is in Germany set to
road
even a network is available. The streets should always have a network so that the streets can be equipped with the national signs, as with mapbox street style.US:
https://onthegomap.github.io/planetiler-demo/#14.14/43.67017/-92.86298
Germany:
https://onthegomap.github.io/planetiler-demo/#17.01/50.365394/11.785406
Credits to @msbarry
From my point of view, it would make sense to include this as a
shield
property intransportation_name
.initially posted at: openmaptiles/planetiler-openmaptiles#143
The text was updated successfully, but these errors were encountered: