Opened 9 years ago
Last modified 9 years ago
#13517 new enhancement
Warn users if hw=path is a lone tag — at Version 5
| Reported by: | openstreetmap.org-user-d1g | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | |
| Keywords: | Cc: |
Description (last modified by )
If highway=path used without supplementary tags (access,sac_slace,surface,smoothness) it may mean up to 6 different things in OSM 1 2.
Similar to other unspecific values (barrier=yes and highway=road) users should be asked to enter more information about (sac_scale/surface/smoothness/access and other tags)
- http://wiki.openstreetmap.org/wiki/Key:access
- http://wiki.openstreetmap.org/wiki/Key:width#Estimated_values
- http://wiki.openstreetmap.org/wiki/Key:sac_scale
- http://wiki.openstreetmap.org/wiki/Key:surface
- http://wiki.openstreetmap.org/wiki/Key:smoothness
- http://wiki.openstreetmap.org/wiki/Key:trail_visibility
- http://wiki.openstreetmap.org/wiki/Key:obstacle#Specific_tagging - about physical barriers and practical (im)passibility per each vehicle/transportation mode
See also #11753.
Change History (5)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|
follow-ups: 4 5 comment:3 by , 9 years ago
comment:5 by , 9 years ago
| Description: | modified (diff) |
|---|
Replying to skyper:
I just did change a small unpaved hiking trail in the mountains from footway -> path, IMOH the opposite is much worser.
Still, it is not as good if was qualified with surface/visibility and other tags?
If this trail in the mountains (with rocks, cliffs and such), then it makes sense to tag it with sac_scale=* / mtb:scale=*, isn't?
What should I map if I have a source for paths but without any physical information (e.g. Maps4BW) ?
If you don't have any physical/surface information, you shouldn't enter fake/estimated values. Survey it over time and you will get complex parts of the tail (visibility, mtb:scale) or with complicated passibility (surface, smoothness).
highway=path is ambiguous without any (visibility, mtb:scale, surface, smoothness) tags.
hw=path users (myself including) trying to differentiate them from hw=footway, but exact reason "why are they different" is simply unknown if they only use single hw=path tag.



I just did change a small unpaved hiking trail in the mountains from footway -> path, IMOH the opposite is much worser.
People tend to use highway=footway/cycleway in many cases where there less stricter access restrictions.
What should I map if I have a source for paths but without any physical information (e.g. Maps4BW) ?