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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: sebastien.aubry31[at]gmail.com [Submitted to the original trac issue database at 12.18pm, Tuesday, 9th November 2010]
Abandoned railways should not be rendered on the default OSM map using Mapnik. It should only be an option for some historical railway maps.
See the following links for discussion:
[http://chris-osm.blogspot.com/2009/07/abandoned-railways.html]
[http://help.openstreetmap.org/questions/361/why-render-abandoned-
railways]
[http://www.mail-archive.com/talk[at]openstreetmap.org/msg11895.html]
The text was updated successfully, but these errors were encountered:
Author: pnorman [Added to the original trac issue at 10.16pm, Monday, 7th April 2014]
The place to report issues with [https://github.com/gravitystorm/openstreetmap-carto openstreetmap-carto], the "standard" style on openstreetmap.org is on [https://github.com/gravitystorm/openstreetmap-carto/issues its issue tracker]. The old Mapnik XML based stylesheets have been retired.
The catch-alls that were the cause of many of these names have been removed. It also seems unlikely that this particular instance was mapped correctly - I'd normally expect the abandoned railway to be obliterated by an airport.
Reporter: sebastien.aubry31[at]gmail.com
[Submitted to the original trac issue database at 12.18pm, Tuesday, 9th November 2010]
Abandoned railways should not be rendered on the default OSM map using Mapnik. It should only be an option for some historical railway maps.
See the following links for discussion:
[http://chris-osm.blogspot.com/2009/07/abandoned-railways.html]
[http://help.openstreetmap.org/questions/361/why-render-abandoned-
railways]
[http://www.mail-archive.com/talk[at]openstreetmap.org/msg11895.html]
The text was updated successfully, but these errors were encountered: