Getting PointNotFound Error for Start position, but route works when end location is moved!

[sweta]

Hi,

I am serving Montana(US) area with following commands:
./graphhopper.sh -a web -i montana-latest.osm.pbf -o montana-gh

I am trying to find route between below locations:
Start: 47.0838,-109.729
End: 46.07748,-109.731295
It throws error: Cannot find point 1: 47.0838,-109.729

But if I change end point to 46.079639,-109.650807, it gives a successful route. How is changing end point resolving issue of PointNotFound for start?
How to overcome this issue in similar other situations?
Is there any threshold on road snap, if yes, how do I modify it?

Could you share what pbf file and config file is used in https://graphhopper.com/maps/ ?
As, I am trying to setup graphhopper for USA from geofabrikhttp://download.geofabrik.de/north-america/us.html. I have added foot endcoder in config-example.yml. But I am unable to get route from 46.0838,-109.729 to 46.079639,-109.650807 via car. While https://graphhopper.com/maps/ gives successful route for same location.

[easbar]

I can reproduce this on current montana-latest.pbf

@sweta

How is changing end point resolving issue of PointNotFound for start?

This indeed seems to be a bug (update: its fixed now). I think the point 46.07748,-109.731295 is the one that is not found, but the error message prints the wrong/other point.

I was able to resolve the points from your example by adding the foot profile (instead of just car). This affects the location index creation because some roads that are discarded for cars are included.

I was also able to resolve from your example by setting index.high_resolution: 1000 (instead of the default 300) just using the default car profile, or (better) setting index.max_region_search to 13 (instead of default 4), but using lower values might already help as well.