-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Start point for round trip should be first coordinate #1939
Comments
@DEHWall omit the last location entry, all trips are planned as round-trips automatically. |
Still does not do as expected - am I misunderstanding the functionality here? Given that the starting point is 51.853842,-3.129779 SelectedStops: Nearest (replot points osrm/nearest) { |
/cc @chaupow |
@DEHWall yeah the lack of normalization here might be a problem. As a work around just start reading the permutation array at the position of 0 and read with wrap-around (yielding your array). You can feed the result again in |
Moving the required Start / End point to the end of the parameter list rather than the first gives a more desired result: Nearest |
The actual problem is not fixed: Trip should start at first coordinate. |
@DEHWall sorry for being late in the convo and thanks for flagging this :) working on it |
@DEHWall just to keep you updated, it was implemented in #3660 edit:
|
This landed by now in both the backend and in the node bindings. You can now request a roundtrip or not (return to the start or not) and fix start and end. |
Am I right in assuming that the first and last via_points should be the Start and End (being the same) points of a requested \trip url as follows.
Is there a known issue / fix available?
It also affects the order of the route_instructions.
http://osrm:5000/trip?loc=**51.853842,-3.129779**&loc=51.75983,-3.36673&loc=51.63623,-3.95339&loc=51.64771,-4.03711&loc=51.5827,-3.00176&loc=51.48148,-2.52805&loc=51.37876,-2.43739&loc=51.43524,-2.6002&loc=51.56916,-1.80141&loc=51.5523,-1.7864&loc=51.63753,-1.83719&loc=51.90335,-2.07979&loc=**51.853842,-3.129779**
{
"status_message": "Found trips",
"status": 200,
"trips": [
....
"via_points": [
[
51.636239,-3.953348],[
51.582627,-3.001746],[
51.481475,-2.528061],[
51.435281,-2.600249],[
51.37858,-2.437094],[
51.552301,-1.7864],[
51.569181,-1.801448],[
51.63735,-1.837459],[
51.903344,-2.079795],[
* 51.854382,-3.12917],[ <-------
51.854382,-3.12917],[ <-----*
51.759672,-3.366476],[
51.647716,-4.037114],[
51.636239,-3.953348]],
"permutation": [
2,4,5,7,6,9,8,10,11,0,12,1,3],
Many thanks
Dave
The text was updated successfully, but these errors were encountered: