Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#1408 closed defect (wontfix)

railway not rendered correctly on highway=residental

Reported by: Landwirt Owned by: osm@…
Priority: minor Milestone:
Component: osmarender Version:
Keywords: railway highway narrow_gauge Cc:

Description

There is a narrow gauge railway on a street in Doberan: http://www.openstreetmap.org/?lat=54.10834&lon=11.90267&zoom=16&layers=0B00FTF

highway=residental
railway=narrow_gauge

Except of rendering the railway, osmarender draws level_crossings at every node. This bug happens also with railway=preserved which I had used earlier for the track. It does not happen with railway=tram, this tag was used to circumvent the bug before I corrected the track.

Change History (9)

comment:1 Changed 10 years ago by Shaun McDonald

This is a data bug. You should be using 2 ways. One for the residential road, and one for the railway, both of which would share the nodes.

Having a way that is both a highway and a railway/waterway/whatever causes undefined results.

comment:2 Changed 10 years ago by Landwirt

Is this data bug documented anywhere? Why would it cause undefined results? It's clearly defined as a street with a railway.

A similar bug was fixed for Mapnik earlier this year in ticket #584

Nonetheless osmarender shouldn't draw level crossings on the nodes.

comment:3 Changed 10 years ago by Shaun McDonald

Don't just think about the renderer, think about all the other data users, such as routing. I do agree that osmarender shouldn't show level crossings unless there is a tag railway=crossing (for pedestrian crossings), or railway=level_crossing (for a level crossing that motor vehicles can use as well.

comment:4 in reply to:  3 Changed 10 years ago by Landwirt

Replying to smsm1:

Don't just think about the renderer, think about all the other data users, such as routing.

I absolutely don't map for the a renderer. Would that be the case I would just let it be railway=tram or make two ways with layer-tags. Speaking of two ways, why is it difficult to have one track with an highway/railway combination, but not with an highway/cycleway combination?

comment:5 Changed 10 years ago by osm@…

Priority: majorminor
Status: newassigned

comment:6 Changed 10 years ago by osm@…

Resolution: wontfix
Status: assignedclosed

Unless all the nodes where a highway=* way and a railway=* way intersect are explicitly tagged as level_crossing there isn't much I can do about this problem.

Judging from the stylesheets it doesn't matter if you use one way with both tags, or two ways which share nodes.

comment:7 Changed 10 years ago by Shaun McDonald

Um, but all level/pedestrian crossings should be tagged explicitly anyway. You cannot assume that they are a level crossing just because they share nodes.

comment:8 Changed 10 years ago by osm@…

In reality there are not (unfortunatly). So I guess I have to write an maplint test and we have to wait a year till that is fixed. *g*

comment:9 Changed 10 years ago by Landwirt

Note: even with separate ways using the same nodes, the level crossings are rendered on each node.

Note: See TracTickets for help on using tickets.