You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder, if this validation is correct. What are your thoughts?
The way I read the short desc (wiki data) and the wiki, the railway=crossing already implicitly says highway=crossing, but for the specific case of railways. Or, to put it differently, there seem to be two keys to describe a crossing, one for non-railways, one for railways.
I wonder if this validation is by accident or by design (eg. "each crossing should have the same highway=crossing tag so we can treat them all the same").
In any case, is the goal to have both keys with the value of "crossing" on the same node, after the validation? Because after following the validation the node above will look like this:
@tordans Using both tags is not by design. iD doesn't intentionally recommend railway=crossing and highway=crossing on the same node, but if it's adding one of those due to a crossing ways fix it won't check to see if the other is already present.
@tordans Oh, now I see what's going on. iD doesn't expect crossing=unmarked on a node to be a subkey of railway=crossing, just highway=crossing. That's where the suggestion comes from. This is a bug if people actually tag rail crossings this way—I'm not sure how common that is. I'm okay with not suggesting the tag.
Location: https://www.openstreetmap.org/node/945141621
I wonder, if this validation is correct. What are your thoughts?
The way I read the short desc (wiki data) and the wiki, the railway=crossing already implicitly says highway=crossing, but for the specific case of railways. Or, to put it differently, there seem to be two keys to describe a crossing, one for non-railways, one for railways.
And on the highway=crossing-tag it say:
I wonder if this validation is by accident or by design (eg. "each crossing should have the same highway=crossing tag so we can treat them all the same").
In any case, is the goal to have both keys with the value of "crossing" on the same node, after the validation? Because after following the validation the node above will look like this:
The text was updated successfully, but these errors were encountered: