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

Route calculation is dependant on route changes in unrelated area #1429

Closed
MaartenDeen opened this issue Apr 3, 2015 · 14 comments
Closed

Route calculation is dependant on route changes in unrelated area #1429

MaartenDeen opened this issue Apr 3, 2015 · 14 comments
Milestone

Comments

@MaartenDeen
Copy link

I apologise for the maybe cryptic subject. I am noticing a change in the route calculation in unrelated areas when you change the parameters of the route in other areas.
Consider these two routes (screenshots are also attached):

  1. http://www.osrm.at/bDs

  2. http://www.osrm.at/bDt

  3. is the route that osrm calculates without intermediate points and takes a shortest path in the village Lierop. For 2) I added an intermediate point in an area that is not related to the route in the village (it is not on a track that should be affected by the new point) and the new route calculates a different route in the village Lierop which is about 500 meter longer.
    Looking at the speed information from the point of change, 1) is about 340 meters @ 30 km/h, 2) is about 145 m @ 50 km/h and 680 m @ 30 km/h. This can never be a faster route.

Why does the route calculation change when I put an intermediate point in a non-related area?

route1
route2

@danpat
Copy link
Member

danpat commented Apr 14, 2015

Possibly related test case. Here, the intermediate marker is moved around a corner that is on the path in both cases. In the second case, the routing seems reasonable, in the first case, the routing does a complete lap of the block to arrive at the point.

screen shot 2015-04-13 at 5 20 57 pm

screen shot 2015-04-13 at 5 22 03 pm

@woodbri
Copy link

woodbri commented Apr 14, 2015

Please supply links from the [Generate Link] link so we can have a link example of these last two. Thanks.

@danpat
Copy link
Member

danpat commented Apr 14, 2015

Here you go:

http://osrm.at/bOG
http://osrm.at/bOF

@danpat
Copy link
Member

danpat commented Apr 14, 2015

Here's a minimal case from the original report. By moving the intermediate marker slightly, the route changes in unexpected ways.

I loaded a 10x10km OSM extract for this region of the Netherlands into a local OSRM install, and I can't reproduce the problem based on HEAD from master. If I place markers in the same spots, the routing does not jump around like it does on http://map.project-osrm.org/.

http://osrm.at/bPo
screen shot 2015-04-14 at 10 55 13 am

http://osrm.at/bPp
screen shot 2015-04-14 at 10 53 33 am

@danpat
Copy link
Member

danpat commented Apr 14, 2015

While I can't reproduce it in master, it is reproducable in develop as of 61dca4a

@danpat
Copy link
Member

danpat commented Apr 14, 2015

Looks like this behaviour appeared in 11c6713

@danpat
Copy link
Member

danpat commented Apr 14, 2015

Reversing the route often does not produce the same path, even when there are no one-way streets involved. Examples above demonstrate this behaviour.

@TheMarex TheMarex added this to the 4.7.0 milestone May 4, 2015
@TheMarex
Copy link
Member

Seems related to #1474 Can also reproduce this with develop.

@TheMarex
Copy link
Member

@danpat just double checked: Reverting that commit fixes this problem. Awesome work tracking that down! Going to cross verify with the other issues that have cropped up.

emiltin added a commit that referenced this issue May 17, 2015
@emiltin
Copy link
Contributor

emiltin commented May 17, 2015

TheMarex added a commit that referenced this issue May 17, 2015
…eet as destination but should have been reached before, closes #1424"

This reopens #1424 but potentially fixes #1429.

This reverts commit 11c6713.
@TheMarex
Copy link
Member

Just reverted 11c6713 on develop tomorrow we will see if that fixes the problems that have cropped up recently. Still this code has bugs that need to be fixed.

@woodbri
Copy link

woodbri commented May 17, 2015

I just built and tested develop and it fixed this case:
http://map.project-osrm.org/?hl=en&loc=-34.86688,-56.20764&loc=-34.86639,-56.20818&loc=-34.86563,-56.20894
issue1429-bad

@woodbri
Copy link

woodbri commented May 18, 2015

My example above is working correctly now on map.project-osrm.org.

@TheMarex
Copy link
Member

This was fixed by #1503

emiltin added a commit that referenced this issue Jun 17, 2015
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

5 participants