Skip to content
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

OSRM table error with single-location instance #295

Closed
jcoupey opened this issue Feb 3, 2020 · 0 comments
Closed

OSRM table error with single-location instance #295

jcoupey opened this issue Feb 3, 2020 · 0 comments
Milestone

Comments

@jcoupey
Copy link
Collaborator

jcoupey commented Feb 3, 2020

This is an edge case somehow similar to #291. When solving a single-location instance (same location for vehicle and job) such as:

{
  "vehicles": [
    {
      "id": 1,
      "start": [2.35044, 48.71764]
    }
  ],
  "jobs": [
    {
      "id": 1,
      "location": [2.35044, 48.71764]
    }
  ]
}

then the OSRM table request contains only one location (input locations are deduplicated). Instead of the expected trivial one-step route, we get an error:

{"code":3,"error":"OSRM table: Number of coordinates needs to be at least two."}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant