Op ma 9 mrt. 2020 om 19:56 schreef Greg Troxel <[email protected]>: > "'Arndt' via OsmAnd" <[email protected]> writes: > > > So yes, if you know you "x" and are pretty sure the your hc stays well > > below, fine. > > We don't know x, it seems. > > I wonder if an algorithm that starts with hc sort of too high, but high > enough to be known to be adequately fast, perhaps 1.5, and then if the > computation finishes in a reasonable period of time, recompute with 1.4, > and so on. Perhaps this could be done more aggressively when on > external power, and less so on battery. (IMHO, navigating 500 km routes > on the phone's internal battery makes little sense anyway.) > > Also: As fas as I know (I read it somewhere), OsmAnd is using a 2-step approach. It first calculates the route with an hc=1.6 and then recomputes this route?? with hc=1.0. I have no idea how that should work, but this topic brings that part of my memory to life again. Unfortunately not good enough to remember where it was said and how it was explained.
Harry -- 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/CAGARPpuMoESx_5a8iaJejPmezYDWmik7cV-oAbve1E68_FpAwA%40mail.gmail.com.
