[GraphHopper] Issues detecting driving paths along one way streets?

[Rodney O'Donnell]

Hi,

Congrats on releasing v0.3!

I'm looking at replacing the car/foot routing component we use at
rome2rio.com with the graphhopper web API.
It looks great so far, however graphhopper is unable to find a route for
4-5% of our queries.

A lot of these failures involve one way streets ... particularly around
trains stations and airports (which we see a lot of).
I've hacked up a change which naively tries routing from positions near the
origin/destination/waypoint, which works ok, but isn't particularly elegant.

I'm happy to trade off some accuracy with the origin/destination points to
increase the "recall" of finding routes.
Treating one-way roads as two way could also work for our use case.
Any thought on the best way to achieve this in graphhopper?


Examples:
http://graphhopper.com/maps/?point=45.461820,9.278362&point=45.48472,9.236413#
No route

http://graphhopper.com/maps/?point=45.461884,9.276520&point=45.48472,9.236413
# Works fine



http://graphhopper.com/maps/?point=40.734454,-74.163026&point=40.73722,-74.17129
# No route

http://graphhopper.com/maps/?point=40.734519,-74.16294&point=40.73722,-74.17129
# Works


Cheers!

Rod.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20140514/d948d331/attachment.html>