P.S.: OSMand algorithm obviously can be optimized wrt speed, I and Harry
would agree on that, but it was chosen by purpose
and will never have the speed of contraction hierarchy ( or like )
algorithm speed.
And contraction hierarchy definitely is not for BRouter, as it's high
priority is flexibility.
Those, who bought OSMand knew, or should know, what they bought.
There is enough fast car navigations, use them, if they suite your needs
better.
Not that I am just ordinary and rather just occasional OSMAnd user, not
speaking for developers.
I use mostly non car navigation of LocusMap+BRouter combo,
for car using Waze, MapsFactor Navigator of OSMAnd.
Dne 27. března 2020 16:11:18 Poutnik Fornntp <[email protected]> napsal:
..
In domain of routing, it sacrifices routing flexibility and puts on high
load the provider resources.
And that is why it is good to have both high and low speed routing
applications,
wher it is on the end user, what he/she prefers.
Those blindsided with high speed of contraction hierarchy do not see
the price to achieve that speed.
--
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/1711c9d0df8.2799.a291d67f9894f806060d35c996ca15e9%40gmail.com.
