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.
You expect that at least in it's own family that Mapnik would respect the layer tags when rendering trunk* bridges, because this looks really ugly. It looks like all the ways are intersecting each other which is obviously not the case here since it's an elevated interchange.
Heck, Mapnik respects motorway/motorway_link bridges when layer/bridge tags are used and they cross each other. Why not trunk/trunk_link as well?
So, please get this fixed asap. At least osmarender can do this correctly.
The text was updated successfully, but these errors were encountered:
Author: Ldp [Added to the original trac issue at 6.34pm, Thursday, 21st April 2011]
There are lots of tickets that point out these layering issues. Lots of duplicates too.
In short: we're well aware of these issues, but haven't moved entirely forward due to several reasons. Stylesheet complexity and server performance being the most prominent ones.
Reporter: rickmastfan67
[Submitted to the original trac issue database at 12.23pm, Tuesday, 12th April 2011]
Whenever there is a trunk bridge rendered over a trunk_link bridge (or vice versa), the layer tags are not respected at all. An example would be here: http://www.openstreetmap.org/?lat=41.887203&lon=-87.614107&zoom=18&layers=M
You expect that at least in it's own family that Mapnik would respect the layer tags when rendering trunk* bridges, because this looks really ugly. It looks like all the ways are intersecting each other which is obviously not the case here since it's an elevated interchange.
Heck, Mapnik respects motorway/motorway_link bridges when layer/bridge tags are used and they cross each other. Why not trunk/trunk_link as well?
So, please get this fixed asap. At least osmarender can do this correctly.
The text was updated successfully, but these errors were encountered: