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: lakeyboy [Submitted to the original trac issue database at 10.27pm, Tuesday, 26th May 2009]
If I am correct, the issue with highway=pedestrian used with area=yes ignoring layers and causing it to render over the top of buildings set on higher layers has been fixed. There looks to still be a bug where despite highway=pedestrian being set on a higher layer, other highway= and railway= ways are still rendered over the top of it when they should be rendered under, in the same fashion as the Osmarender does it. An example can be found here: http://www.openstreetmap.org/?lat=-37.81716&lon=144.9499&zoom=17&layers=B000FFTF Thanks.
The text was updated successfully, but these errors were encountered:
Author: javbw [Added to the original trac issue at 12.25am, Wednesday, 4th December 2013]
The pedestrian tag is ignoring layers when set as a way too - This isn't just for areas. I am making a park with gates over the pedestrian paths. Setting the way to highway=pedestrian layer=1 renders through the gate, building=roof layer=2.
Reporter: lakeyboy
[Submitted to the original trac issue database at 10.27pm, Tuesday, 26th May 2009]
If I am correct, the issue with highway=pedestrian used with area=yes ignoring layers and causing it to render over the top of buildings set on higher layers has been fixed. There looks to still be a bug where despite highway=pedestrian being set on a higher layer, other highway= and railway= ways are still rendered over the top of it when they should be rendered under, in the same fashion as the Osmarender does it. An example can be found here: http://www.openstreetmap.org/?lat=-37.81716&lon=144.9499&zoom=17&layers=B000FFTF Thanks.
The text was updated successfully, but these errors were encountered: