Hiking profiles - poutnikl/Brouter-profiles GitHub Wiki

Hiking profiles

  • Walking.brf is the profile intended for easy paths, avoiding stoney terrains, as well as for general walks.(max SAC T1 in OSM SAC scale)

  • Hiking-SAC2 is intended for easy hiking, with some stones under feet.(SAC opt-max T1-T2). The old obsolete version of my Hiking profile Hiking-beta is included in standard profile set of Brouter-web, but not in the Brouter application.

  • Walking-wet and Hiking-SAC2-wet are intended to be used in rainy or wet weather, giving more priority to less problematic surfaces.

  • Mountain-hiking-SAC3 is intended for hiking in mountains below the alpine difficulty SAC scales T4-T6, with optimal-maximal SAC scales T1-T3.

  • See the full profile list to review Alpine hiking profiles (SAC opt-max T2-T4/T3-T5/T4-T6)

  • More end user profiles can be easily derived by tuning tunable parameters of the template, e.g. different SAC scale profiling.

  • My Hiking profiles are based on the release version of Hiking profile template

HikingComments

  • BRouter is primarily Bicycle Router, but its principles can be used for foot routes as well. The essential condition is the route generated by the BRouter always follows the OSM way network. It means it cannot be used for free terrain routing or for ways not mapped properly in the Openstreetmap.

  • Profiles for hiking are the long term experiment, triggered by a user demand to make SAC_scale alpine restrictions for trip planning/routing for seniors. The usage of Brouter in mountain or nature reserve areas can be advantage, it the marked ways are the only legal a/o safe ways to follow ,especially in emergency or bad trail visibility.

  • If the profiles are used with Locus Map application for direct navigation use, review the [[Locus glossary item|glossary#l]

  • The profiles evaluate road/track/path classes, quality of surface and and also SAC scale. If SAC scale rating is missing, then - if available - evaluation falls back to evaluation of MTB scale. There is done MTB to SAC mapping in such a case.

  • See also some OSM related pages like Hiking or [Safety measures] (http://wiki.openstreetmap.org/wiki/Safety measures_on_hiking_trails).

  • Hiking profiles implements SAC scale parameters.

    • The first value is "end of comfort zone", after which the path costfactor progressively grows.
    • The second one as "hard limit of the challenging zone".
      • IF this hard limit is crossed, the default behavior is the forbidden path will be routed through ONLY if it is the only option left to ever reach the destination.
      • This behavior can be changed by setting hard limit penalty to 10000 that totally forbids such routing, so the routing will fail. It may happen in the only path case, or if the start, destination or via-points lay on such forbidden path.

  • Some people may consider routing for the hiking as an IT excess, and they are partially right, for ideal conditions. But unexpected events like getting lost, injuries, bad weather or invisible trails can turn a pleasant trip into a run for the life. Imagine transportation of the friend with a broken leg or appendicitis, in fog or snowing, following the trail you can barely see in icy wind.... You can just select the destination and listen the voice guidance, carrying a body in the need.