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: malenki [Submitted to the original trac issue database at 12.07am, Friday, 2nd October 2009]
I consider this an not irrelevant issue since tracks which were rendered before construction works will disappear when the get mapped as under construction.
Since I don't know what kind of highway it will be after construction is finished (could be as mapped right now track grade 1 or foot/cycleway or unclassified) I stuck with the track since this was the pre-construction condition.
Author: Mateusz Konieczny [Added to the original trac issue at 8.37am, Thursday, 3rd July 2014]
I would propose that we don't render this tag, as rendering too many different tags will only cause a visual mess of which users don't understand the meaning. I will therefore close this issue. If someone disagrees, feel free to re-open this on the new CartoCSS issue tracker: https://github.com/gravitystorm/openstreetmap-carto
Author: math1985 [Added to the original trac issue at 9.53am, Wednesday, 20th August 2014]
I disagree, if we render highway=path under construction we should also render highway=track under construction. I created a new bug here: gravitystorm/openstreetmap-carto#898
Reporter: malenki
[Submitted to the original trac issue database at 12.07am, Friday, 2nd October 2009]
I consider this an not irrelevant issue since tracks which were rendered before construction works will disappear when the get mapped as under construction.
Since I don't know what kind of highway it will be after construction is finished (could be as mapped right now track grade 1 or foot/cycleway or unclassified) I stuck with the track since this was the pre-construction condition.
http://www.openstreetmap.org/browse/way/40584408
The text was updated successfully, but these errors were encountered: