railway not rendered correctly on highway=residental #1408
Comments
Author: smsm1 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. |
Author: landwirt[at]wilsen.de 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. |
Author: smsm1 Don't just think about the renderer, think about all the other data users, such as routing. |
Author: landwirt[at]wilsen.de Replying to [comment:3 smsm1]:
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? |
Author: osm[at]petschge.de 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. |
Author: smsm1 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. |
Author: osm[at]petschge.de 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 |
Author: landwirt[at]wilsen.de Note: even with separate ways using the same nodes, the level crossings are rendered on each node. |
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.
The text was updated successfully, but these errors were encountered: