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: a.t.chadwick[at]gmail.com [Submitted to the original trac issue database at 10.02am, Tuesday, 5th August 2008]
The mapnik layer renders some (maybe all) nodes and ways tagged with disused=yes normally. Essentially this bug is the Mapnik layer equivalent of #1079.
Both examples are physically present in the landscape (the canal rather dubiously), and so should be present in the OSM data. However they're useless for their stated purpose, and should not appear in a rendered map intended for the general public on the openstreetmap.org site.
The quickest fix for this would be to not render such nodes or ways at all on the OSM website: leave their rendering to more specialised sites.
The text was updated successfully, but these errors were encountered:
Author: !i! [Added to the original trac issue at 8.50pm, Saturday, 26th March 2011]
I would like to extend this suggestion in rendering disused=yes things with low opacity to make clear that they are out of order. Personaly I use disused=yes for abandoned buildings for example. Osmarender crosses the objects, but this might be depend on the interpretation, cause we don't have a reliable life cycle concept.
Reporter: a.t.chadwick[at]gmail.com
[Submitted to the original trac issue database at 10.02am, Tuesday, 5th August 2008]
The mapnik layer renders some (maybe all) nodes and ways tagged with
disused=yes
normally. Essentially this bug is the Mapnik layer equivalent of #1079.Examples:
http://www.openstreetmap.org/?mlat=51.7263&mlon=-1.35205&zoom=17&layers=B00FTT (node, pub)
http://www.openstreetmap.org/?mlat=51.66551&mlon=-1.29309&zoom=18&layers=B00FTTT (way, canal)
Both examples are physically present in the landscape (the canal rather dubiously), and so should be present in the OSM data. However they're useless for their stated purpose, and should not appear in a rendered map intended for the general public on the openstreetmap.org site.
The quickest fix for this would be to not render such nodes or ways at all on the OSM website: leave their rendering to more specialised sites.
The text was updated successfully, but these errors were encountered: