Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

railway not rendered correctly on highway=residental #1408

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 8 comments
Closed

railway not rendered correctly on highway=residental #1408

openstreetmap-trac opened this issue Jul 23, 2021 · 8 comments

Comments

@openstreetmap-trac
Copy link

Reporter: landwirt[at]wilsen.de
[Submitted to the original trac issue database at 4.38pm, Sunday, 14th December 2008]

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[[BR]]
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.

@openstreetmap-trac
Copy link
Author

Author: smsm1
[Added to the original trac issue at 3.43pm, Tuesday, 16th December 2008]

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.

@openstreetmap-trac
Copy link
Author

Author: landwirt[at]wilsen.de
[Added to the original trac issue at 9.18am, Wednesday, 17th December 2008]

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.

@openstreetmap-trac
Copy link
Author

Author: smsm1
[Added to the original trac issue at 11.01am, Wednesday, 17th December 2008]

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.

@openstreetmap-trac
Copy link
Author

Author: landwirt[at]wilsen.de
[Added to the original trac issue at 12.14pm, Friday, 19th December 2008]

Replying to [comment:3 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?

@openstreetmap-trac
Copy link
Author

Author: osm[at]petschge.de
[Added to the original trac issue at 5.53pm, Saturday, 27th December 2008]

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.

@openstreetmap-trac
Copy link
Author

Author: smsm1
[Added to the original trac issue at 12.06pm, Sunday, 28th December 2008]

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.

@openstreetmap-trac
Copy link
Author

Author: osm[at]petschge.de
[Added to the original trac issue at 2.11pm, Sunday, 28th December 2008]

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

@openstreetmap-trac
Copy link
Author

Author: landwirt[at]wilsen.de
[Added to the original trac issue at 7.47am, Monday, 29th December 2008]

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant