Closed mxxcon closed 1 month ago
If both are present then maybe adding one extra does not make sense.
I wonder how well it is supported in routers supporting maxheight
- but that is a separate question, I guess.
If both are present then maybe adding one extra does not make sense.
If maxheight:forward/backward=
are present I think adding plain maxheight=*
would be wrong..(and maybe there should be a validator for that too.)
What value would you put there? In my example the difference is just 2", but there can be more extreme situations where the difference is multiple feet/meters.
I think that putting either one would not be wrong, with maxheight:forward
maxheight:backward
overriding maxheight
value in own directions - while something processing maxheight
only would have at least some info (so probably put lower value?)
but not filling either should not be wrong...
The suggestion makes sense. If both are specified, not only is there no point in asking for the "general" height, but also if the height for the different lanes is different, it is often due to the tunnel's roof being an arc. Subsequently, a sign for the general height would not make sense and measuring it would also make sense.
I also encountered situation with different maxheight per lane in the same direction https://maps.app.goo.gl/P2kadGGVmtK9y6oRA but I'm not sure how to tag such situation and that's probably a different topic.
I also situation with different maxheight per lane in the same direction
That would be
maxheight:lanes=3.7|3.9|3.7
https://wiki.openstreetmap.org/wiki/Lanes
with a few hundred elements: https://taginfo.openstreetmap.org/keys/maxheight%3Alanes#overview
added this for the same reason as above.
How to Reproduce Look at way 1151405188.
Expected Behavior Maxheight quest should not come up.
Versions affected 57.3