New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Route alternatives for bicycle (OsmAnd + Brouter) #6112
Comments
We don't have alternative route UI as of today |
Is there something i can do, to have the posibility to choose the 4 alternative routes of Brouter in OSMAND UI? |
We are preparing new UI for Public Transport navigation where you will be able to select alternatives routes there it will be possible to change. |
Thank you for your answer. Yes, this is a request, it will be great to have alternative routes generated by Brouter in UI of OsmAnd. But at this time only Brouter0.gpx can be used in OsmAnd UI. You can read here:
|
Brouter already has implemented alternatives routes. In Osmand it is allready possible to configure Brouter as "routing engine" instead of the Osmand own routing engine. As you can read here, Osmand uses a Remote-Procedure-Call to get a route from Brouter: I do not know, if it is possible to get the alternative routes from Brouter with this Remote-Procedure-Call. Or if it only possible to get alternative routes with starting Brouter App again and again with the same start and finish points, to generate brouter0.gpx, brouter1.gpx, brouter2.gpx and brouter3.gpx |
Hello, it is still not possible to select all the 4 alternative routes that BRouter can generate. Will there be a solution? |
Hi, no news on this topic ? |
For bicycle i use OsmAnd and Brouter ( http://brouter.de/ ).
Brouter offers for each profile (e.g. trekking) 4 alternative routes:
http://brouter.de/brouter/alternatives.html
Live demo:
http://brouter.de/brouter-web/
But in OsmAnd you only have the first route of Brouter App, dont possible to choose the alternative ones.
Is it possible to implement alternative routes to OsmAnd?
Thank you.
The text was updated successfully, but these errors were encountered: