-
Notifications
You must be signed in to change notification settings - Fork 3
Home
-
This repository does not contain Hiking profiles, released for the end user usage. It focuses on the development of the Hiking profile template, used for the derivation of the above profiles ( from the Master branch). The Develop branch is usually ahead, containing some new or experimental features.
-
The very obsolete version of the profile based on this template is present on the Brouter-web as Hiking-beta profile ( but not in Brouter application ).
-
You can derive full list of generated profiles from this Template file according the guide Getting Profiles
-
General Walking/Hiking profiles slightly prefer marked routes and pleasant paths, but not too much, as the affordable relative detours decrease wit distance. 4 vs 3 km does not matter if nicer path is chosen. 40 vs 30 km does make the difference.
| Profile or purpose | What to change | Comment |
|---|---|---|
| Walking | assign SAC_scale_limit 1 | *) to safe space, for the following profiles |
| assign SAC_scale_preferred 0 | it is written like limit 1 / preferred 0 | |
| Walking-wet | assign iswet 1 | additionally to Walking, applicable to below as well |
| Hiking | limit 2 / preferred 1 | *) |
| "Unpaved" | assign Offroad_factor 0.5 .. 3 | See MTB profiles. It is port of the orignal MTB factor from bike profiles, using categories mainroad-paved-other-unpaved |
| "Paths" | assign path_preference 5 .. 20 | Progressively penalizes ways different to paths. It may better fit to foot profiles, as it is more focused on OSM way types. Both parameters may be merged in future, for now coexist for historical reasons |
| Nordic_Walkings | assign Offroad_factor 1.0 | Stronger preference of unpaved ways |
- Custom outdoor use It may not be possible to fit your priorities, so it is highly recommened to experiment with the below parameters and to upload profile to Brouter web client to be tested on the familiar routes.
| Parameter | Comment |
|---|---|
| SAC_scale_limit | Use optimal scale value for your purpose |
| SAC_scale_preferred | Use optimal scale value for your purpose |
| Offroad_factor | Use values 0.5 - 2.5 to prefer unpaved ways and to penalize paved ways /roads. It also decreases the effect of elevation evaluation |
| path_preference | Similar as Offroad factor, but focuses on OSM ways classes, Use values 2-20 |
| hiking_routes_preference | See marked route table below |
- Regarding preferences of the marked hiking routes, see the table. You can use either ready to use XXHRP profiles, or experiment with manual setting of "hiking_routes_preference".
| Profile or purpose | What to change | Comment |
|---|---|---|
| Marked route preference default | hiking_routes_preference 0.20 | all purpose mild preferring marked Hiking Routes, marked 6 km = unmarked 5 km |
| SHRP profiles | hiking_routes_preference 0.6 | Strong Hiking Routes Preference, 8 km marked=5 km unmarked |
| VSHRP profiles | hiking_routes_preference 2.0 | Very Strong Hiking Routes Preference, 15 km marked=5 km unmarked. |
| NHRP profiles | hiking_routes_preference 0.00 | Useful for non hiking cases |
- For the mountain hiking, the template uses alpine difficulty rating SAC T scale, if available. Otherwise it tries to imply SAC rating from eventually present MTB scale rating.
| Profile or purpose | What to change | Comment |
|---|---|---|
| Walking | assign SAC_scale_limit 1 | *) to safe space, for the following profiles |
| assign SAC_scale_preferred 0 | it is written like limit 1 / preferred 0 | |
| Hiking | limit 2 / preferred 1 | *) |
| Mountain-hiking | limit 3 / preferred 1 | *) |
| Alpine-Easy | limit 4 / preferred 2 | *) |
| Alpine-Demanding | limit 5 / preferred 3 | *) |
| Alpine-Difficult | limit 6 / preferred 4 | *) |
- See more at