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

Multivalued lcn_ref on ways rendered as 0;6;6a #3140

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Multivalued lcn_ref on ways rendered as 0;6;6a #3140

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

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

When you have multivalued lcn_ref on a way (e.g. 0;6;6a) it is rendered as "0;6;6a" instead of separate values "0 6 6a" as when a way belongs to multiple cycle route relations. This looks especially odd when you [http://www.openstreetmap.org/?lat=51.523202&lon=-0.131194&zoom=18&layers=C see both at the same time].

@openstreetmap-trac
Copy link
Author

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

There's no need to tag the way with a lcn_ref if that way is a member of the appropriate relations. Tagging the way is useful for situations where the way hasn't yet been added to the relation or where the relation does not yet exist. Doubly so when the way is part of multiple relations, the semi colon nonsense is unwanted when that's the whole point of having the relations.

I'm marking this as wontfix, the lcn_ref tag should be removed from the way.

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