A bridge or tunnel should not suffice to stop warnings about crossing ways

[jleedev]

URL

No response

How to reproduce the issue?

1. Draw two crossing ways, one with highway=residential and bridge=yes, one with waterway=river.
2. Draw two crossing ways with different layer but neither bridge nor tunnel.

Actual:

Neither is caught by the validator.

Expected:

1 should be flagged: With the noted exceptions of indoor/corridor/building/etc, crossing ways (highway, waterway, railway) having the same layer is never correct: They should either intersect or have different layers.
2 should be flagged: If two highway/waterway/railway ways cross each other, it's a virtual certainty that one is a bridge or tunnel. Tagging just the layer is not enough.

Screenshot(s) or anything else?

Having a bridge at layer=0 cross a non-bridge at layer=0 may seem unambiguous, but it confuses rendering. Screenshots near https://www.openstreetmap.org/changeset/160586698 with Tracestrack Topo:

The sidewalk has layer=1; the highway has layer=0; the sidewalk casing obscures the roadway.

Which deployed environments do you see the issue in?

Released version at openstreetmap.org/edit, Development version at ideditor.netlify.app, RapiD version at mapwith.ai/rapid

What version numbers does this issue effect?

2.31.0

Which browsers are you seeing this problem on?

No response

[tyrasd]

for reference, this is from the wiki:

Bridges should have a layer=*, for simple crossings almost always layer=1 but other values may be appropriate for complex crossings.

(iD automatically adds layer=1 for newly tagged bridges using the field in the presets.)

It is however not that uncommon to see ways with bridge=* and no layer tag (about 7%), so making the validation more strict would potentially lead to many warnings that are not necessarily "problematic situations" (one could argue that a bridge could imply a layer=1 value). 🤔 Perhaps situations like this would be better accounted for in an external quality assurance tool?!