highway=proposed should render under all other highway types

[matkoniecz]

It leads to misleading maps like at http://www.openstreetmap.org/?mlat=50.0380&mlon=20.0616#map=13/50.0380/20.0616 (it seems like S7 leads to nowhere - but it is connecting, see http://www.openstreetmap.org/?mlat=50.0380&mlon=20.0616#map=15/50.0380/20.0616 ).

see also #345

[matthijsmelissen]

Alternative phrasing: highway=proposed should render under all other highway types :) .

[Rovastar]

What a horrible example of the proposed roads.

Just to add some more details: the top bit of the green "trunk" road is actually a trunk link and the proposed are rendering over the trunk link. Not the secondary road that renders fine and the actual trunk road renders fine.

I suspect it is the confusing understanding of the ordering which lead "here be dragons" warning.
bea03ff
from
#23

Once there is a better understanding of the ordering we can fix this I suspect.

I might do a test to see what render over what and post a list.

Sort of related to
#462

[Rovastar]

Did a quick test and all proposed and construction are render above all link roads and tracks.
Also related any proposed (or construction) bridges are over all road classification on ground level.

[matthijsmelissen]

I suspect it is the confusing understanding of the ordering which lead "here be dragons" warning.

No, that warning has to do with the ordering of the instances within the construction road (i.e. the background versus the white dashes on top).

Sort of related to #462

Yes, #462 is a way to solve this problem.

[matthijsmelissen]

This has been resolved by #626.