access no rendered over junction without access = no

[matkoniecz]

see http://www.openstreetmap.org/?mlat=50.0710&mlon=19.8889#map=16/50.0710/19.8889 for an example

related to #177

[pnorman]

duplicate of #119

[matthijsmelissen]

No, this is not a duplicate, #119 has been solved while this one is still open (in some cases).

The particular example given in the report has been solved by the way, but the problem still occurs, for example here: http://www.openstreetmap.org/?mlat=50.0710&mlon=19.8889#map=19/50.06504/19.90714

[matthijsmelissen]

Could someone re-open this issue?

[matthijsmelissen]

I am not sure how to tackle this issue, does anyone have suggestions?

[matkoniecz]

new example: http://www.openstreetmap.org/?mlat=50.0788&mlon=19.8956#map=15/50.0788/19.8956

[matthijsmelissen]

Would there be a way to make the access casing a couple of pixels shorter than the road itself?

[matkoniecz]

new example: http://www.openstreetmap.org/?mlat=50.07877&mlon=19.89566#map=19/50.07877/19.89566 (geometry of the road slightly changed)

[matkoniecz]

second example: http://www.openstreetmap.org/?mlat=50.0787&mlon=19.8928#map=16/50.0787/19.8928

[pnorman]

Would there be a way to make the access casing a couple of pixels shorter than the road itself?

At the intersection of multiple (e.g. 2) access-restricted roads this would work badly

[matkoniecz]

and the next example:

http://www.openstreetmap.org/?mlat=50.07864&mlon=19.89302#map=17/50.07864/19.89302

[gravitystorm]

@mkoniecz Please stop posting more examples, everyone understands the problem but what is needed is a solution.

[matthijsmelissen]

A solution would probably to sort the roads in the query, so that access roads are rendered first.