Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
2012/10/12 Martin Koppenhoefer : > 2012/10/12 Eric SIBERT : >> No. It would indicate that it can't be used by vehicles. sorry, I got you wrong here, thought you wanted to exclude them (foot-bridge). cheers, Martin ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
2012/10/12 Eric SIBERT : > No. It would indicate that it can't be used by vehicles. if there are no legal restrictions one step or also 2 won't be an unsurmountable obstacle for most vehicles. cheers, Martin ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
you could use lanes=1 on the narrow parts. Agree. - a bridge or a raft with a bad link to the road/track i.e. a step at each end of the bridge/raft. obstacle=unevenness ? or obstacle=step? For me unevenness is to soft for what you describe. split the way and put a short highway=steps, step_count=1 No. It would indicate that it can't be used by vehicles. - a road on a dam or a bridge have been damaged : a bailey bridge (http://en.wikipedia.org/wiki/Bailey_bridge) have been temporary (for ten years ;-) ) added on it. is this an obstacle, or is it simply another type of bridge construction? If it is an obstacle the tagging should line out in what the obstacle consists (smoothness, width, maxweight, ...) It's first a lanes=1 and second short connecting slopes at each end. Something no so far from the steps I mentioned earlier i.e. you have to slow down at entrance and exit of the bridge. Éric ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
Hi 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 Tree/bough Temporary Deposit (e.g. Straw bales) Illegal or misleading sign Building Muddy/Boggy hole Upgrowth (localised) Linear Obstruction (Surface) Cross-field not reinstated Headland ploughed Surface path our of repair Flooded/muddy/boggy/rutted Upgrowth Linear Obstruction (Other) Overgrowth Standing water e.g. pond/lake Barbed wire/electric fence adjacent Intimidating beast/person Encroachment (not ploughing) e.g. garden extension Quarry Plantation 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. Regards Dudley Date: Fri, 12 Oct 2012 09:47:32 +0200 From: lakonfrariadelav...@gmail.com To: tagging@openstreetmap.org Subject: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle» Hi! 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!! -- KONFRARE ALBERT 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/11918952076 ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
2012/10/12 Eric Sibert : > - a narrow bridge i.e. you can't cross a vehicle in opposite direction. We > may use width=* but it is difficult to get it precisely. obstacle=narrowness you could use lanes=1 on the narrow parts. "narrowness" is a very relative concept and I wouldn't encourage you to use it, IMHO it is better to use width (or est_width) also with rough estimates it will still be more useful. > - a bridge or a raft with a bad link to the road/track i.e. a step at each > end of the bridge/raft. obstacle=unevenness ? or obstacle=step? For me > unevenness is to soft for what you describe. split the way and put a short highway=steps, step_count=1 > - a road on a dam or a bridge have been damaged : a bailey bridge > (http://en.wikipedia.org/wiki/Bailey_bridge) have been temporary (for ten > years ;-) ) added on it. is this an obstacle, or is it simply another type of bridge construction? If it is an obstacle the tagging should line out in what the obstacle consists (smoothness, width, maxweight, ...) In general the change to "obstacle" as key seems consistent with what you want to express. I would refrain from narrowness and water, as there are already other ways to express them. cheers, Martin ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
2012/10/12 Eric Sibert > - a narrow bridge i.e. you can't cross a vehicle in opposite direction. We > may use width=* but it is difficult to get it precisely. obstacle=narrowness > It's slightly offtopic, but wouldn't it be logical to use "car" as a non accurate unit of length? So you can have a tag like "width=1car" or "width=1.5car". I remember people using 1.5 for the lanes=* tag, but this looks better to me. And for the obstacle, I think it's a useful tag. I'll vote for it. Janko ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Reconstructing «Dificult passability» proposal to «Obstacle»
Hi, During my last travel in Africa, I was thinking on how to map obstacles on road. So I support your proposal but in a generalized way, not only for pedestrian or bicycle. And I take the opportunity to review what I observed: - a narrow bridge i.e. you can't cross a vehicle in opposite direction. We may use width=* but it is difficult to get it precisely. obstacle=narrowness - a bridge or a raft with a bad link to the road/track i.e. a step at each end of the bridge/raft. obstacle=unevenness ? or obstacle=step? For me unevenness is to soft for what you describe. - a hole in the road. * A small hole you can drive other at full speed but that may surprise you when driving during night. * A medium hole where you have to use the other side of the road at full speed if nobody is arriving in front * A big hole where you have to slow down and drive inside. (For full uneven sections, I use smoothness=*). - a road on a dam or a bridge have been damaged : a bailey bridge (http://en.wikipedia.org/wiki/Bailey_bridge) have been temporary (for ten years ;-) ) added on it. I would no use obstacle for thinks that are deliberate and/or in their initial state. For river and water. If there is water year around (or large fraction of the year) : ford=yes. Only flooded few days a year (after heavy rain), flood_prone=yes. Use surface=* to indicate whenever you are just driving in the river or if there is some raft build. Seasonal? Use seasonal=yes in conjunction with access:conditional=* to indicate approximative closing period (discussed recently on this mailing list. I will update the wiki according soon...). Same with traffic_calming, check points... HOT is also dealing with obstacle : http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Model#Obstacle Eric ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
