[Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»

Dudley Ibbett dudleyibbett at hotmail.com
Fri Oct 12 19:18:18 BST 2012


In the UK local authorities are responsible for public rights of way.  Paths, bridleways etc.  There are so called Best Value Performance Indicators (BVPI) that require them to survey a certain % length of these each year to measure the ease of use of the network.

Documentation and forms for this are on the web.  http://www.iprow.co.uk/gpg/index.php/Performance_Indicators

In this they talk on terms of Obstruction.  These are either points or lengths.

Point Obstructions (i.e. a discrete obstruction, on or too close to the path)

Wall/fence/hedge/electric fence/ other barrier
Temporary Deposit (e.g. Straw bales)
Illegal or misleading sign
Muddy/Boggy hole
Upgrowth (localised)

Linear Obstruction (Surface)

Cross-field not reinstated
Headland ploughed
Surface path our of repair

Linear Obstruction (Other)

Standing water e.g. pond/lake
Barbed wire/electric fence adjacent
Intimidating beast/person
Encroachment (not ploughing) e.g. garden extension

It may be that this should be a different tag i.e. Obstruction as the objective of recording the above is to get the Obstruction removed and the right of way re-instated.



Date: Fri, 12 Oct 2012 09:47:32 +0200
From: lakonfrariadelavila at gmail.com
To: tagging at openstreetmap.org
Subject: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»


I'm reconsidering my proposal...
Before introduce in the wiki, I wanted to show you a scheme of the purpose... to see the viability of this.
I nedd help and comments ;)

I think that the name «Difficult Passability» could be changed for «Obstacle=*» (I see that this name is used in OSM: http://taginfo.openstreetmap.org/keys/obstacle#values especially in Germany).

For values, I want to propose:
- obstacle=yes
- obstacle=fallen_tree
- obstacle=dense_vegetation --> you could combined with seasonal=yes

- obstacle=unevenness ---> when you probably need hands, but not only in technical hiking also could be a small wall of 1,5 meters height that you should overcome to continue the route, for example. It could be combined with «Safety measures on hiking trail»

- obstacle=narrowness (like this: http://img534.imageshack.us/img534/4315/11passetdelarabosa.jpg )
- obstacle=water --> and you could combine with ford=yes, for example or natural=wetland

I'm not sure what to do with the value obstacle=with_precipe... ¿Rename it? ¿Omit it? ¿obstacle=precipice? ¿obstacle=cliff?

A «obstacle_description=*» key could be added for text (especially if only obstacle=yes you use).

The key refers to pedestrian and generalizes for bicycles or motor vehicles... perhaps a obstacle affects only to motor vehicles...
In this case, could be interesting to use especification like in the key access? obstacle:horse=yes , for example?

Thanks a lot!!
La Konfraria de la Vila del Pingüí de La Palma 
WEB:            http://www.konfraria.org

TWITTER:     http://twitter.com/La_Konfraria 
FACEBOOK: http://ca-es.facebook.com/people/Konfraria-Vila-Del-Pingui/100001918952076

Tagging mailing list
Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20121012/90e757f8/attachment.html>

More information about the Tagging mailing list