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: ChrisB [Submitted to the original trac issue database at 7.21pm, Saturday, 25th July 2009]
[http://osm.org/go/evfpn0Hb-- here] we have a rail line running next to a road - the rail line is rendered under the wide line for the road so it disappears at times.
[http://osm.org/go/evfFG7pT here] there is a cycleway running alongside the road - but the cycleway is invisible because the wide road line is rendered over the top of it.
The text was updated successfully, but these errors were encountered:
Author: osm[at]petschge.de [Added to the original trac issue at 11.19am, Monday, 27th July 2009]
The map has to show linear features with exaggerated width to be usable. Due to it's very nature osmarender can't move colliding linear feature laterally to avoid overpainting. To most people roads are more important so they go on top. Other maps (e.g. cyclemap) have different priorities and draw feature in a different order.
Reporter: ChrisB
[Submitted to the original trac issue database at 7.21pm, Saturday, 25th July 2009]
[http://osm.org/go/evfpn0Hb-- here] we have a rail line running next to a road - the rail line is rendered under the wide line for the road so it disappears at times.
[http://osm.org/go/evfFG7pT here] there is a cycleway running alongside the road - but the cycleway is invisible because the wide road line is rendered over the top of it.
The text was updated successfully, but these errors were encountered: