-
Notifications
You must be signed in to change notification settings - Fork 353
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
bad request #6
Comments
Hm, interesting. I'll check that out, but it sounds like a problem in OSRM. |
Thanks you for your quick response. Soon after posting, I realized my But now that it is working I find that the directions are not very helpful. I 80, I 80;I 58025 km, 28 minHead southwest250 mContinue southwest on I 80350 Continue northeast on I 8010 kmContinue north900 mContinue north on I 880100 This is confusing and not very specific. it seems to be describing a round anyway, thanks for your help michael shelman On Fri, Mar 21, 2014 at 7:19 AM, Per Liedman [email protected]:
|
The directions can hopefully be improved. There's of course some limits from what you can do with the data returned by OSRM, but I'm pretty certain that it can be turned into something more readable than today. |
Thanks for the reply, Per. Yes, it seems the data must be there but it must On Wed, Mar 26, 2014 at 12:38 AM, Per Liedman [email protected]:
|
I'm closing this issue since the original problem has been resolved, I opened #9 regarding your comments about improving the directions. |
For certain requests, I am getting '400 Bad Request' using the sample code. For example: http://router.project-osrm.org/viaroute?instructions=true&loc=-122.4,37.78&loc=-122.32,37.93&jsonp=_l_routing_machine_0. Any ideas? The latlngs in the samples display the routes correctly. Thanks
The text was updated successfully, but these errors were encountered: