[GraphHopper] GPS-exact routing prioritizes snapping over length

[Joel Haasnoot]

Hi,
I've gotten GPS-exact results working thanks to Philipp, and so far I'm
seeing great results. Mostly everything works and the paths are looking
great.
I have however run into a slight issue. I suspect it's due to the way the
routing and snapping is designed. I have several situations where I have
two parallel paths a and b which eventually converge. My departure point is
on path a but my destination path is closest to path b, but in a place
where a and b are still parallel. The routing will choose a much longer
path which routes me past my destination on path a and then switches
back/double back on path b.
I've attached two screenshots which show an overview and a detail of my
destination point, in which you can see two paths are parallel.

Is there any way to add some sort of prioritization to always choose a
shorter path over a closer snap to a path?

Joel Haasnoot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20131230/106b0b93/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-SnappingVsLength2.png
Type: image/png
Size: 322544 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20131230/106b0b93/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-SnappingVsLength.png
Type: image/png
Size: 15683 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/graphhopper/attachments/20131230/106b0b93/attachment-0001.png>