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

lcn_ref=* on ways overrides lcn_ref=* on relation #3139

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

lcn_ref=* on ways overrides lcn_ref=* on relation #3139

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

Comments

@openstreetmap-trac
Copy link

Reporter: tko
[Submitted to the original trac issue database at 11.14am, Saturday, 24th July 2010]

LCN route 45 relation was incorrectly tagged as lcn_ref=15 while (some of) the ways still had the lcn_ref=45 tag on them. This resulted in the conflicting ways being rendered with '45' and ways only in relation as '15' making the route as a whole strangely broken. The effects can still be seen in the current rendering of the [http://www.openstreetmap.org/?lat=51.5048&lon=-0.191&zoom=14&layers=C&relation=10963 cycle map].

I'd think in case of conflicting lcn_ref tags cycle map should render both as if the way were part of multiple relations. Validation tool to check for such inconsistencies would probably be good too.

@openstreetmap-trac
Copy link
Author

Author: Andy Allan
[Added to the original trac issue at 10.17am, Monday, 26th July 2010]

There is no strict ordering as to which relation or way gets priority when rendering, instead as many labels as possible are shown on the map. It's perfectly possible to have a path shared between two routes, one as a relation and one still on the old tags, and - space permitting - both will be rendered.

Since I can't see anything that actually needs fixing, I'm resolving this as worksforme.

@openstreetmap-trac
Copy link
Author

Author: tko
[Added to the original trac issue at 12.07pm, Tuesday, 27th July 2010]

From what I can tell there's plenty of space in the southern part and yet that part of the route only shows "45" from the way, the "15" from relation is all missing.

This bug is still open, does that mean you agree there's something worth fixing?

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