Discrepancy in routing

I have 2 separate deployments for Graphopper directions API with same configuration file. The only difference is that one uses whole US and the other one uses only Maryland. For some routes, sometimes both are giving me different results.

This is the US

This is for MD

Also the one which is configured with MD has same result when compared with Graphhopper online map.
Here are my Lat/Lngs
39.066074,-77.04921
38.80518,-76.96701

Here is my configuration file:

Can you add a via-point to enforce the straight route (the one you get for the US instance) also on your MD instance? Does it yield the same time and distance as for the US instance? And is it even shorter/faster than the route you get without the via-point?

with US map your route goes in DC, no?

Oh yes. So as MD doesn’t include DC that is why it is not going through DC.

For things like this it also helps sometimes to enable ‘Local MVT’ in the map’s layers menu. It might take some time to load, but it will display GraphHopper’s routing graph. So you would probably see that DC is missing.

1 Like

Just one more thing. Why My route doesn’t match with online map portal ?

Online:

My Response

This is most likely because the hosted service applies a special treatment for urban areas that is not (and cannot easily be) included in the open source engine: Difference between open source car and graphhopper maps car

One of our goals is to get rid of this discrepancy and hopefully this pull request https://github.com/graphhopper/graphhopper/pull/2637 will make this possible. You could already try this branch to slow down the speed in the city center. And if you do please do not hesitate to share your results here :slight_smile:

Powered by Discourse