-
Notifications
You must be signed in to change notification settings - Fork 410
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
Lack of a manual/freehand route option #167
Comments
This is a frontend issue, please register it here: |
Frontend will consume this but it’s a feature that has to be implemented to the backend ultimately. The idea is: if a direct connection should be returned the backend simply doesn’t optimize between those two waypoints. We have the code for this in an older version (which was implemented), I might be able to find it. |
I agree that this would be really useful for hiking route planning, too. I used it earlier, and am missing it now. |
@TimMcCauley Did you find where the old code was for this? |
@rabidllama sorry, I checked and I can't find it (most likely on my old laptop which was stolen 👎). The idea is quite straightforward, every waypoint gets an additional attribute optimize which is either
|
OK, I don't think this will be too major a thing to add, so lets aim for getting it in there for v4.7 |
Moved to 4.7.2 |
Can it be done in the current front-end or this is coming ? |
@Martin868 yep, we will include this in the client as soon as it is released! |
On all the routing engines I know that allow the user to draw a route, there is on option to bypass routing for a section of the route and manually link two points. This option is handy when the route need to follow a missing way on the map, or that there is a routing error in the map database. I do a lot of cycling route planning and this happens all the time. For example the route planners in Strava, RideWithGPS, Garmin, all offer this. In ORS this should be a type of via point.
The text was updated successfully, but these errors were encountered: