dear harry, I followed your kind advice but am afraid to need more. I installed all smoothly and tested now with a few destinations of about 100 and 200 km distance. you are right: the only difference really is the time taken: with the standard profile you say to have HC1,0 it takes more time to calculate. which is most annoying when in need of a fast recalculation because of a deviation. I remember well sitting on the roadside for minutes after minutes sometimes (in former times) waiting for osmand to help me find my way (great when it's dark and raining!). that is over after I switched for your 1,2 or 1,5. what I do not understand: I would expect the 1,5 to give the fastest route also, due to smaller rates of choice. but although the differences are close to non-existence that is not the case.
when I drive by car I am mostly not in a hurry and would like to be lead to small unknown roads that even shorten my way - so I mostly choose gas saving (in fact, that is what I love osmand the most for!). one problem here still remains: the time calculations become completely wrong the moment I switch for gas saving. they are more than 50% to high (while without they are pretty much exact). a trip which takes about 3hours20 may be displayed with 5hours10. that shure helps not starting too late - but arriving way too early doesn't help either ;-) how can I change that without getting into even bigger problems? thank you! Am Freitag, 6. März 2020 15:25:39 UTC+1 schrieb Harry van der Wolf: > > > > Op vr 6 mrt. 2020 om 15:16 schreef Episteme PROMENEUR < > [email protected] <javascript:>>: > >> >> About long distance itinerary computing,for bike trekking what value for >> hc ? >> >> How to assign this value ? >> >> The heuristic coefficient is always 1.4 for bike trekking, unless you > make your own profile. > (So there the hc is not 1.0, like for car navigation. For pedestrian it is > 1.2) > I therefore do not know if it is interesting to play with this for cycling. > > See the blog post describing new features: https://osmand.net/blog > > You can easily play with the profiles. The original routing.xml can be > found on and downloaded from: > https://github.com/osmandapp/OsmAnd-resources/blob/master/routing/routing.xml > > Copy attached mycar15.xml to Android/data/net.osmand(.plus)/files/routing. > Same for mycar12.xml > > Make sure that they are saved as .xml. Some file managers save xml files > as .xml.txt > Simply open the xml in a text editor and you see that it is only a > subset for car navigation (but this can be done the same way for other like > the mentioned bike trekking). > The only changes are the name of the derived profile and the heuristic > coefficient which are added in the header of the routing profile. > You can also easily modify that yourself to play with other values. > > Open OsmAnd > - Settings -> Scroll down and create new profile > - Select Profile car > - Give it a name (mycar 1.5?) > - Select color and icons and save. > > You are now still in your freshly created profile. > - Got to navigation settings (2nd option) > - Select Navigation type (1op one) > - Now scroll down and select the mycar15 navigation type > - Go back until your are out of the profile and you can now use it. > - Adapt it further to your liking. > > > Attached also a mycar12.xml. I use this one in big towns. > -- You received this message because you are subscribed to the Google Groups "OsmAnd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/9cbde803-5880-40c2-b795-a401d07e0eed%40googlegroups.com.
