On Wed, Mar 11, 2020 at 01:46:19PM -0400, Greg Troxel wrote:
What I take away is
hc=1.2 does not ever result in any significant routing error (where
error is failure to match 1.0), of course in the cases you tried.
hc=1.3 is almost always non-erroneous, and the time saving from 1.5
to 1.3 is never important
I don't 100% follow the "need 1.2 to be safe for economic route".
Those routes don't necessarily look better than the 1.3, and you don't
have the "economic cost", because osmand doesn't expose it.
Just to add my 2-cents to the discussion. My use for OsmAnd's routing
(car) falls, primarially, into two major buckets:
1) to determine a route to get to a destination when I do not already
know how to navigate to that destination; and
2) to have an ETA indicator for long trips when I otherwise *do* know
how to navigate to the destination
For #2 I'm not so worried about the exact route OsmAnd picks, as I'm
not using it to navigate the route. And I've found the computed ETA to
be good enough (given that it will change quite considerably due to
food/restroom stops along the trip anyway).
For #1, I'm also not so concerned that OsmAnd find *the most perfect
route*. I do not know how to get to the destination, and as long as
OsmAnd will navigate me to that destination, I'm not so worried if an
'insider' might have known of a shortcut that might have saved 15
minutes. I don't know how to get there, therefore I don't know the
shortcuts, therefore any route (as long as it is not so far off as to
be silly) is fine.
Also, ten plus years ago when I first got a TomTom GPS unit, I
experimented with letting it compute some routes for routes I otherwise
knew (i.e., commute from home to workplace, etc.) just to see how it
did.
What I found was that while it would compute a path to the destination
just fine, the route it picked was not always the route I would have
choosen as an 'insider' for that route. Had I been unfamiliar with the
location, I would have never known that TomTom's route was less
optimal, and it still would have gotten me to my destination. One of
the routes it computed took about a 2 mile due west detour on a road
with a 45mph max-speed to avoid a 3.5 mile segment of the road it had
already picked that is posted at a max of 35mph and 30mph in two
different places. But, what I knew, that TomTom did not, is that the
road it picked to utilize after the 45mph detour was less optimal due
to traffic lights and generally denser (and slower moving) traffic than
simply remaining on the 35mph and 30mph road to the same final
destination. But without "real-time-traffic" info, no GPS unit will
know those little 'insider' details.
Which led me to my opinion I stated above for #1. Yes, the chosen
route might be less optimal than what an 'insider' will pick, but it
will get me to my destination, and if I'm not an 'insider' in that
area, I'll never know the difference. And if I'm 'routing' via OsmAnd
in a location where I do have 'insider' knowledge, I'm simply going to
ignore the GPS's chosen route anyway.
So my feelings are that trying to find the *perfect* route from an hc
of 1.0 is a bit much in that either I won't know enough to tell the
difference or I'll just ignore the navigators suggestions if I do know
enough to tell the difference. But having faster completion of route
computation might be a better benefit (esp. if there is a second
impatient person sitting in the passenger seat whining "come one, can
we get going already" while the lengthy computation is running).
--
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/20200311193249.GB18026%40d820.dp100.com.
