Proposed features/Difficult Passability
|Obsoleted by Proposed_features/Obstacle|
|Tagging:||dif_passability=no, dense_vegetation, fallen_tree, with_precipice, waterway_crossing, hands_needed|
|Definition:||Objective difficulties in a path (or highways) with verifiable situations|
|Rendered as:||no render|
I want that people can discern between trails without obstacles or objective difficulties (for example for people with less mobility, walks with children, etc.) and adventure trails. Also the key must be verifiable and for this motive I assigned values that I think that are concretes values.
The goal of this tag is that navigation applications can avoid trails with some difficulties when calculating routes. Some navigation applications like OsmAnd can avoid routes with bumps, tolls or ferries for calculating routes for vehicles, but not can personalize calculating routes for pedestrians. I proposed in OsmAnd's forum (see the discussion) that calculating routes could include options to avoid the tag trail_visibility=bad, because I was using this tag for trails with much vegetation that could be hard to cross in some cases with risk that suffer scratches for brambleberry (for example). This trails are historic rural trails abandoned. I understood quickly that trail_visibility=* was not the correct tag for my proposal. In discussion appeared some tags but none seemed useful (view Tagging content) I was very confused with the development of proposal, and a Proposed_features/Passability (Abandoned) expressed very different concept. A simple blog gave me an idea: «Objective difficulties». This approach allows trails with concrets impediments be tagged in a verifiable form for passability.
In the municipally term of La Palma de Cervelló (5,47Km², a very little municipally term in Catalonia, wikipedia), I calculate that there are approximately more than twenty highway=* (paths and tracks) that could be tagged with dif_passability=no, ten highway=path (or puntual part of this) that could be tagged with dif_passability=dense_vegetation, three dif_passability=fallen_tree that impede the passability could be added, two highway=path could be complemented with dif_passability=with_precipice, ten dif_passability=waterway_crossing could be localized in highway=path that cross streams and torrents, and two nodes with dif_passability=needed_hands could be added. There are much trails mapped and the pedestrian navigation experience improve with this key. I think therefore that this key could be very useful, and could be apply to a lot of places of the world, for example the key dif_passability=fallen_tree could be more used when a disaster occurs like a hurricane, earthquake... (La Palma de Cervelló was affected for extratropical Klaus cyclone in January 2009 and there were hundreds of trees fallen, a lot of them impeded the passability in trails). In Catalonia there are hard wind frequently, topcoat the Tramuntana wind (see the Wikipedia).
The key refers to highway=path and highway=footway for pedestrians, but these difficults in passability will be extensives to bicycles, road vehicles and horses. Therefore the key would be compatible for other highway=*.
|dif_passability=no||No static elements in the trail (in front or around) that difficult the passability for a pedestrian. You can walk erect and with stretched arms and in beeline, evidently following the path traced ;)|
|dif_passability=dense_vegetation||,||There are big shrubberies, brambleberry, very high and dense grass, big branches, lianas, etc that limited the personal space and force you to duck or to dodge, and you must walk careful. There are risk of scratches in arms and legs, and stumbles. If you can walk erect and with stretched arms and in beeline, in this case you never must not apply this value.|
|dif_passability=fallen_tree||There is a big fallen tree that completely hinders passability, and you only can continue the path if you cross the tree (cross it above or below). This key could be complemented with key abandoned=yes if the fallen tree takes a long time is there. If there is a fallen tree that permite the pass (in or around the trail) you never must not apply this value.|
|dif_passability=with_precipice||,||There is an important precipice alongside the trail (at least one side) that your eyes can't avoid see if you look forward (for example, because you can't move over away). When you are walking in the trail you can see the falling. There are a minimal risk of falling (major for people with a tendency to fall over, small children, etc.), but it's an important difficulty for people with dizziness. If you can move over away from the precipice and take out it of your visual field, you must not apply this value.|
|dif_passability=waterway_crossing||,||You must cross a river, stream or torrent and you only can do this if you jump, or if you walk stone by stone. If seasonally the waterway haven't water, you can combine with the intermittent=yes. If you can cross the waterway without changing the natural form of walking, you must not use this value.|
|dif_passability=needed_hands||,||In front of the trail you must use hands for continue the route. It can be because there is a big stone, a margin that must be crossed or simply the terrain begins to be very steep. This key could be complemented with the key incline=* in percentage or degrees. This difficulty can't be avoid in this trail for continue the route, in this case you must not use this value.|
Keys appeared in OsmAnd's forum (see the discussion) for my proposal were:
- trail_visibility=*: The key only refers to orientation problems, not to real impediments. People with less mobility perhaps could move without problems in a trail with bad visibility, but a felled tree will be surely an important problem in route, for example. This key has the problem of Verifiability.
- sac_scale=*: Is a general key (a good key!) for hiking trails, but it don't specify concrete impediments. This key has the problem of Verifiability.
- smoothness=*: Only refers to the quality of the road, not to elements around the road. This key has the problem of Verifiability.
- dangerous=*: Not created key. I think that key could be excessive because the proposal is to mark impediments, not the risk. These type of key (in relation with passability) could have values like minefield or hunting area that are dangers real.
- tracktype=grade5: Only refers to the quality of the road, not to elements around the road.
- abandoned=yes: Not always that a trail is abandoned we find difficulties on passability or impediments.
I think that the keys trail_visibility=*, sac_scale=*, smoothness=*, tracktype=grade5 and abandoned=yes are compatible with the key dif_passability=* proposed. If values are analized, we can see that:
- dif_passability=dense_vegetation: This key could be changed by landuse=dense_vegetation or similar, but I think that the most important factor is its relation with the passability, and this key not relates them. Also could be used the key natural=dense_vegetation, with this key happens the same that the key landuse=dense_vegetation. Other option could be use the key width=* or maxwidth=*, but a trail could have two meters of width=* and only a few centimeters be useful because the vegetation impedes it. maxwidth=* reffers to the legal restriction, not to the real maxim width useful in the trail.
- dif_passability=fallen_tree: This key could be replaced by the key natural=fallen_tree, but could be a madness to mark all the fallen trees and no provides rellevant information. The fallen tree also is important in relation with the highway=*. Other option could be use the key barrier=fallen_tree, I don't have arguments to discard this possibility.
- dif_passability=with_precipice: In the map we can detect the precipices with contour lines and with the key natural=cliff, but not the relation with the highway=*. Other option could be add the key natural=cliff to the highway=* for mark that the trail is very near of the precipice, but this information won't be certain, and besides the cliff will be rendered above the trail.
- dif_passability=waterway_crossing: We could consider that the best key for this element could be waterway=crossing, but could be much important that the node be in the highway=* (not in the waterway=*) for calculating routes proposals. This key is rellevant in relation with the highway=* and its transibility.
- dif_passability=needed_hands: The most similar key with this key, could be sac_scale=demanding_mountain_hiking and its superior values (T4,T5 and T6). I think that the major differences are: (1) sac_scale=* indicates a possibility and dif_passability=needed_hands indicates a fact, (2) sac_scale=* is a general characteristic of the trail and the dif_passability=needed_hands could be a puntual characteristic of the trail.
This key always must be in a way with the key highway=* (generally in highway=path, highway=footway, highway=cycleway or highway=bridleway). The key dif_passability=* could be a node in this way, or a key added to highway=* in the way or in a stretch of the way (if the difficulty is along five meters). The key dif_passability=no can't be a node because it would be absurd, and I consider that the key dif_passability=fallen_tree must be only a node because always is a puntual obstacle. If a long fallen tree obstaculizes two trails, I think that the best option would be add a node with dif_passability=fallen_tree in each trail. If we mark the fallen tree like a way that affects two trails, then we lose the calculating routes proposal for avoid obstacles.
I think that this key perhaps no needs to be rendered.
If this proposal is approved most of the highway=* pages must includes this key for add.
I'm not sure that this key could be the perfect solution for my proposal, but I'm very interested in the comments, and I desire that if is rejected perhaps this proposal helps somebody to find a best solution.