-
Notifications
You must be signed in to change notification settings - Fork 69
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
Strange routing using contracted #196
Comments
Thanks for reporting, can you tell me:
|
I saw this strange route with the version 1.4.0pre something, just to be sure I updated to 1.4.0pre60. Tell me if you need more informations. Thanks in advance. |
Anything you can give me, source/destination coordinates for example. I'll try and have a look soon... |
AH sorry I thought you could have the source/destination coordinates from
geojson. I'll give you asap.
2018-06-06 22:29 GMT+02:00 Ben Abelshausen <notifications@github.com>:
… Anything you can give me, source/destination coordinates for example. I'll
try and have a look soon...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#196 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABtMQXrkrK0YnTAB1E-VeC7lZC40yLgQks5t6DuYgaJpZM4Uc3RA>
.
--
Alessandro Cavalieri
|
Ah no that's enough thanks, sorry... 👍 |
Hi Ben,
I'm reporting a strange routing using contracted classifications graph. See the following pictures and the corresponding attached geojson file.
Not contracted
![image](https://user-images.githubusercontent.com/1788993/41047932-ee9a60d8-69ad-11e8-8cab-8e0eeea3ecfd.png)
Contracted
![image](https://user-images.githubusercontent.com/1788993/41048008-198a15fe-69ae-11e8-9633-a10ea21120ab.png)
appo.zip
The text was updated successfully, but these errors were encountered: