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
Possible solution: modify the lua script (setup/openstreetmap-carto.lua) to include railway = {turntable = true, traverser = true} inlocal polygon_values
Potential issues:
Does this mess up single nodes that are tagged as turntables?
While our repositories aren't linked, setup/openstreetmap-carto.lua is an exact copy of OpenStreetMap's file. Is it advantageous to be in sync? Should the change be proposed upstream?
The text was updated successfully, but these errors were encountered:
I guess this would also affect e.g. signal boxes, but those are usually also tagged as buildings. For none of them it makes IMHO sense to render them not as areas.
A closed way tagged as
railway=turntable
orrailway=traverser
is not automatically recognized as a polygon and the turntable rendering (shading) is not applied. If it's taggedarea=yes
or some other tag that indicates an area (ex.tourism=attraction
, https://www.openrailwaymap.org/?style=standard&lat=40.87484646450063&lon=-73.52816417813301&zoom=19) it will render.Possible solution: modify the lua script (setup/openstreetmap-carto.lua) to include
railway = {turntable = true, traverser = true}
inlocal polygon_values
Potential issues:
The text was updated successfully, but these errors were encountered: