Commit 4635118 changed the behavior of the nearest neighbor querying.
Since 4635118.
> curl "http://127.0.0.1:5000/viaroute?loc=52.5316730,13.4518220&loc=52.4700630,13.2642550"
{"status_message":"Cannot find route between points","status":207}%
> curl "http://127.0.0.1:5000/table?loc=52.5316730,13.4518220&loc=52.4700630,13.2642550"
{"distance_table":[[2147483647,2147483647],[2147483647,0]]}%
Before:
> curl "http://127.0.0.1:5000/viaroute?loc=52.5316730,13.4518220&loc=52.4700630,13.2642550"
{"status_message":"Cannot find route between points","status":207}%
> curl "http://127.0.0.1:5000/table?loc=52.5316730,13.4518220&loc=52.4700630,13.2642550"
{"distance_table":[[0,16766],[16796,0]]}%
I'm not sure why that commit should change the behavior of table since it was using IncrementalFindPhantomNodeForCoordinate before this commit. If anything viaroute should behave differently.
Might be worth to dig deeper here. There is something fishy going on.
Commit 4635118 changed the behavior of the nearest neighbor querying.
Since 4635118.
Before:
I'm not sure why that commit should change the behavior of
tablesince it was usingIncrementalFindPhantomNodeForCoordinatebefore this commit. If anythingviarouteshould behave differently.Might be worth to dig deeper here. There is something fishy going on.