I have file an issue on the OsmAnd bug tracker in order to reach the
developers:
https://github.com/osmandapp/Osmand/issues/3201
--
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
Thanks!
On Tuesday, October 4, 2016 at 5:21:05 PM UTC-4, Harry van der Wolf wrote:
>
>
> I add the value to the first (but that's not really necessary) and I set
> the car profile itself, like
> minDefaultSpeed="45.0" maxDefaultSpeed="130.0" leftTurn="5" rightTurn="5"
> roundaboutTurn="5"
I add the value to the first (but that's not really necessary) and I set
the car profile itself, like
I don't touch the outcommented value
Make sure that OsmAnd has really been closed otherwise the new value will
not be used. It will then use the already loaded in-memory value.
Rebooting the
Not trying to hijack this thread, but Harry, where exactly in routing.xml
do you change the heuristicCoefficient value? I see 2 possible places:
At the beginning, there's this section, with the value unset:
Then just a little below that is this section, with a value of 1.5
commented
THOR might be a good alternative, but the A* algorithm OsmAnd uses is just
fine.
I agree that OSRM is too limited due to its inflexibility.
It is the implementation of the A* algorithm in OsmAnd that is wrong (from
my point of view). OsmAnd is literally the only app that uses a heuristic
OsmAnd needs a new routing engine because of bad performance. Graphhopper
and OSRM do not fulfill the requirements because they don't support
conditional edge-weights at query-time*. THis is necessary to support
options like avoid highways and so on without the need for a separate
CH-graph for
