#11503 closed defect (fixed)
Wrong validator ERROR: The 'from' way does not start or end at a 'via' node.
Reported by: | mdk | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 15.05 |
Component: | Core validator | Version: | tested |
Keywords: | oneway bicycle turn restriction from via to relation | Cc: |
Description
Download relation 5190111 and run validator. The validator shows an error. The problem in this special case is, that the 'from' way starts at the 'via' node, but is tagged with
highway=pedestrian oneway=yes oneway:bicycle=no
Without the oneway:bicycle=no
a turn restriction would not make sense here, because nobody could reach the 'via' node from the 'from' way. But in this case the turn restriction is only for bicycles, which can use the 'from' way to reach the 'via' node.
How to tag this situation without a validation ERROR? I would normally never upload a changeset, if a have an unfixed ERROR!
Attachments (0)
Change History (6)
comment:1 by , 10 years ago
Keywords: | oneway bicycle turn restriction from via to relation added |
---|---|
Milestone: | → 15.05 |
comment:2 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
follow-up: 4 comment:3 by , 10 years ago
What about other transport modes? The oneway:* keys are not exclusive to bicycle. You can have oneway:motor_car or e.g. oneway=no+oneway:bus=yes.
Please make the support universal.
comment:4 by , 10 years ago
Replying to aceman:
What about other transport modes? The oneway:* keys are not exclusive to bicycle. You can have oneway:motor_car or e.g. oneway=no+oneway:bus=yes.
This situation would not fail, because of oneway=no
, so we don't have the problem.
Please make the support universal.
Are there any other transport modes which make sense as:
oneway=yes & oneway:<x>:no
I think we can ignore the following, because they would never have their own turn restrictions:
oneway=yes & foot:oneway=no oneway=yes & ski:oneway=no oneway=yes & inline_skates:oneway=no oneway=yes & ice_skates:oneway=no oneway=yes & horse:oneway=no
This would never be tagged. You would use directly oneway=no
oneway=yes & vehicle:oneway=no oneway=yes & motor_vehicle:oneway=no
For this modes it make sense:
oneway=yes & bicycle:oneway=no (fixed)
Has anybody saw one of the following combinations for which a turn restriction for the ":oneway:no
exception is signposted?
oneway=yes & carriage:oneway=no oneway=yes & trailer:oneway=no oneway=yes & caravan:oneway=no oneway=yes & motorcycle:oneway=no oneway=yes & moped:oneway=no oneway=yes & mofa:oneway=no oneway=yes & motorcar:oneway=no oneway=yes & motorhome:oneway=no oneway=yes & tourist_bus:oneway=no oneway=yes & goods:oneway=no oneway=yes & hgv:oneway=no oneway=yes & agricultural:oneway=no oneway=yes & atv:oneway=no oneway=yes & snowmobile:oneway=no oneway=yes & psv:oneway=no oneway=yes & bus:oneway=no oneway=yes & taxi:oneway=no oneway=yes & hov:oneway=no oneway=yes & car_sharing:oneway=no oneway=yes & emergency:oneway=no oneway=yes & hazmat:oneway=no oneway=yes & disabled:oneway=no
I did'n see any other valid cases.
follow-up: 6 comment:5 by , 10 years ago
Writing that comment probably took longer than it would take to code the support universally ;) I do not like making lists of valid values just because the others are not used today. But they may be in the future.
And there is a ton of oneway=yes & oneway:moped=no e.g. in Netherlands.
comment:6 by , 10 years ago
Replying to aceman:
Writing that comment probably took longer than it would take to code the support universally ;)
No. And I won't add anything else until a real-world problem occurs.
In 8452/josm: