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

P2 'simple view' not show tags for node features in T-junctions #4133

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

Comments

@openstreetmap-trac
Copy link

Reporter: Harry Wood
[Submitted to the original trac issue database at 9.36am, Friday, 9th December 2011]

I noticed a problem while trying to select this node in P2 :
http://www.openstreetmap.org/browse/node/20694272
barrier=bollard is a recognised preset. After selecting the node I would expect the simple view to show 'bollard' in the drop-down, but it doesn't. I'm seeing an empty drop-down, as if it is an unrecognised tagging.

But by experimentation I seem to be seeing the same problem for any node feature tags whenever they're set on a node in the middle of junction of ways

So the bollard tag is recognised and displayed correctly in simple view if the node is free floating, or in the middle of one way, or on the end of one way. It's only a problem when the tag is set in the middle of a junction ...but it happens for any other tag actually. So if I set a supermarket in the middle of junction it also doesn't pick it up in simple view.

It doesn't crop up much and doesn't completely hamper anyone's ability to map (they can see the tag in advanced view fine) hence 'minor' I guess

@openstreetmap-trac
Copy link
Author

Author: stevage
[Added to the original trac issue at 11.05am, Thursday, 16th February 2012]

It's a limitation of the way turn restrictions are implemented: a turn restriction (or if you prefer, a junction node) is a type of entity, rather than being an inputset. So once the junction node has matched, there is no more matching: it can't also be a bollard.

This is a specific case of the general problem with feature matching being exclusive. There are a few solutions, none particularly simple:

  1. Show multiple simple editors
  2. Show one, combined simple editor (conceptually easy in this case, not always so).
  3. Show a simple editor and an advanced editor.
    ...

Specific cases like this one actually could be worked around, by creating hybrid "bollard with turn restriction" features, and making sure they get matched before either bollard or plain turn restriction. Probably not worth it yet.

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