Good stuff Dian!
I don't know how widespread the problem is, but Garmin GPS navigation
devices see no road surface tag as sealed. This can create routing
stress for the driver and possibly safety issues. Might be worth
mentioning that it's far better to default tag new roads in non urban
areas as unpaved than no tag, if the surface is unknown.
I use surface:fine_gravel in places. Problem is that the gravel
eventually wears off and it becomes.. unpaved! Unpaved is also what one
would use if sourcing only from overhead imagery. This all for another
discussion though.
Cheers Bob
On 18/4/22 19:43, Dian Ågesson wrote:
We should discourage the vague surface values of "paved" and
"unpaved", instead using more specific tags like asphalt and
compacted. Can we replace the example with something more specific
than "surface=unpaved"?
surface=gravel has it's own problems given the common use in
Australia is different to the wiki description. I'm not sure the best
way to address this.
I agree with you that we would want to encourage a more accurate tag.
From what I could see on the wiki and in overpass queries, there is a
lot of confusion about the surface tag. I would definitely welcome
this list revisiting the discussion, but I didn't feel confident
changing what was already there.
_______________________________________________
Talk-au mailing list
Talk-au@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-au
