While editing a track, editor QA wants me to tag a ford:
How to proceed? I was thinking of adding barrier=rock …
While editing a track, editor QA wants me to tag a ford:
How to proceed? I was thinking of adding barrier=rock …
If your editor suggests a ford=yes here, there will obviously be a crossing with a waterway. Is there a waterway on the ground?
Obviously there is a waterway there on the ground. The photo shows that quite good. Obviously, it is an intermittent stream: Most always dry, can swell at times.
The track no longer passable by car. I think it is barrier=block instead.
iD automatically suggests adding a ford everywhere a path crosses a waterway, but that doesn’t mean it’s always correct (or even most of the time).
Dry gulches are often mapped as intermittent streams and the ford suggestion from the validator should be ignored.
Ideally QA tools would not suggest to add a ford when the waterway is tagged intermittent=yes.
I agree with not suggesting a ford when the waterway is intermittent.
Is there general agreement on this? (This wouldn’t prevent manually tagging a ford.)
Would this apply to all highway types? E.g. where a highway=primary crosses an intermittent waterway, does it make sense to still suggest a ford, or is that a valid combination without a ford as well?
iD’s design and UX pushes users quite strongly towards accepting its validator’s suggestions, so it might be better to change the validator rather than point out that the suggestions don’t have to be accepted.
I can make a request to iD for this change, but it might be good to get slightly more input or agreement. Please comment or thumbs-up!
In Bolivia between the mountains, there are a lot of rivers which are intermittent, often the river is used to drive to the next out, but that could be not directly opposite but further up- or downstream.
You get longer fords, with intermittent.
You can walk over it, it is more a hazard= thing.
I would say that any place where a highway=* crosses a usually dry river or stream bed is not a ford but rather a place that is flood prone (flood_prone=yes). However, if a waterway is wet perhaps 80% of the time and dry the other 20% perhaps calling it a ford still makes sense. Unfortunately since dry 80% of the time and dry 20% of the time are both tagged intermittent=yes this makes an absolute rule rather problematic.
As i tag thousands of dirt roads,i have noticed that as well.I would like like to ride the road in the picture !!
passable by off road motorcycle but i dont think there is a tag for that!
This seems good solid logic
We have loads of those here. Funnily my editor knew the flood_prone tag on a node
Ford is prominently rendered by lots of consumers. Yet I’d say, ford is not a good way to make users of maps aware of the hazard those places can pose. Certainly, map readers can add two plus two (a saying here for using common sense). Unfortunately, flood_prone is not in the hazard=* keyspace.
Mountainbikers just carry their bike there. From what I have seen BMX riders perform, with trial techniques should be easy peasy.
I guess I will go with barrier=block on either sides for vehicles and flood_prone for the shared node waterway and track and tag the stream an intermittent one.
Now whom to assign the “solved” badge?
All highway types. I’m sure there are edge cases, but they a very small proportion
Its what i do most weeks here in Greece on an off road motorcycle-yes it would be easy for me,just dont hit it too fast or you may have to tag”MEMORIAL”next to it ![]()
I’m late to the discussion, but I agree that this is not a ford and that validators are too aggressive in recommending ford=yes for where there is an intersection between a highway and a waterway tagged with intermittent=yes.
And I would suggest that more developed highways such as highway=primary likely have infrastructure to separate the highway from the waterway for the safety of motorists traveling at higher speeds.