http://map.project-osrm.org/1r9 The obvious route is to follow I-80 all the way. But instead it gets off and follows surface roads across Indiana.
Could it be avoiding barrier=toll_booth? The exit where it gets off (SR 66) is missing this. But why would it avoid toll roads without the user telling it to do so, and why wouldn’t it be using the toll=* tag on the ways?
Discussion
Awennit n iandees di 2 October 2012 ɣef 01:35
Looks like it’s fixed now.
Awennit n NE2 di 2 October 2012 ɣef 02:44
Yep, it’s fixed. I don’t see any recent edits along I-80 here, so the OSRM guys may have changed something.
Awennit n dcp di 3 October 2012 ɣef 18:10
This is a very interesting development and it works! I tested it from Bonn, Germany to Croydon, England. It is very usable! What I noticed is that the were a number of purple overlays which seem to indicate that a OSM data error hinders the correct routing.
Is this so?
Should I, as a contributor, try to correct these “errors”?
Awennit n NE2 di 3 October 2012 ɣef 19:18
Where are you seeing purple overlays? The only purple I see is the admin boundaries and the alternate route when you hover over the B at the top right of the route description: http://osrm.at/1sb
Awennit n dcp di 4 October 2012 ɣef 05:51
To NE2
I recalculated the route once again just now. No purple overlays. Unfortunately I did not take a snapshot of these purple overlays yesterday. It is just like your original post. NE2 registered something odd, iandees check and found nothing. Very strange indeed.
Anyway it is a very good tool and it should be accessible from the OSM Home Page, don’t you think?
Awennit n butrus_butrus di 10 October 2012 ɣef 22:09
You need to check the “small components” checkbox (where you choose the map) to see the purple overlays.
Awennit n NE2 di 10 October 2012 ɣef 23:02
Huh? Whatever these ‘small components’ are supposed to be, they’re certainly not clustered around the routing.