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 each combination of options.
Competitor maps.me suffers from a similar problem**. The use fast OSRM engine but can't offer routing options (avoid highways etc.). It should be investigated if THOR*** engine (Tiled Hierarchical Open Routing) which supports* multi-modal routing *can be implemented in OsmAnd to replace the current routing engine. * https://github.com/Project-OSRM/osrm-backend/issues/2377 ** https://github.com/mapsme/omim/issues/1888 *** https://github.com/valhalla/thor *** https://mapzen.com/blog/valhalla-intro/ -- 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]. For more options, visit https://groups.google.com/d/optout.
