[GraphHopper] Routing between points - path is too short/long

[Peter K]

Hey

> Hi,
> I'm using Graphhopper as a library for a project that needs to
> precompute a few paths between points (railway lines in this case). I
> route between two lat/lon coordinates and extract the path from the
> response. My OSM data is a very sparse graph of just railway lines,
> which have long edges - but I'm routing between stations. Stations
> however are not neccesarily on the line.

Can you  connect the station and the lines in a post processing step?

>
> The routing works in principle, but the resulting paths are mostly
> either too short (guessing the end of the edge closest), or too long
> (the end of the edge?). Too long I could fix with postprocessing (tho
> I prefer not to do so), but too short means I'm missing part of the
> path. I've tried increasing the resolution of the index,
> with setPreciseIndexResolution(), but not seeing any change. Is there
> any way to improve this? Any ideas?

Do you mean GPS exact routing? This is implemented in the master.
Besides this no issues like this are known. So I would need some more
details what could go wrong.

Regards,
Peter.