31.07.2019, 21:45
Hi,
I am Using GraphHopper (with bike setting) and get the following (two similar) exceptions while routing on the border of the "oberbayern" and "schwaben" routing data:
SEVERE: Cannot route position list: 'com.graphhopper.util.exceptions.PointNotFoundException: Cannot find point 1: 48.33591627071882,11.07885431020705'
Watching DownloadableFinder.getDownloadableFor() I can see that the file: europe/germany/bayern/oberbayern-latest.osm.pbf is selected as data, based on the center distance and inclusion of the bounding box of the two waypoints in the bounding box of the file. However... then the point seems to not be present in the Oberbayern data ... continuing then within "schwaben" that decision then swings to the next tile of Routing data and then it works properly again
Error route (within Oberbayern Bounding Box):
longitude=11.141854035548846, latitude=48.325759113802
longitude=11.07885431020705, latitude=48.33591627071882
Success (within Schwaben Bounding Box):
longitude=11.07885431020705, latitude=48.33591627071882
longitude=10.988045441798846, latitude=48.35131933232875
Oberbayern
NW Corner: longitude=10.71268, latitude=49.09052
SE Corner: longitude=13.10138, latitude=47.39037
Schwaben
NW Corner: longitude=9.397266, latitude=49.0366
SE Corner: longitude=11.31348, latitude=47.11463
My theory here: the bounding box of the file is too generous for the actual content (a bit of OSM-Data missing at the edge of Oberbayern towards Schwaben).
Is that a known problem?
Are there easy tools to visualize the Routing Data content and see what is missing / included in which file?
Regards,
Thomas
I am Using GraphHopper (with bike setting) and get the following (two similar) exceptions while routing on the border of the "oberbayern" and "schwaben" routing data:
SEVERE: Cannot route position list: 'com.graphhopper.util.exceptions.PointNotFoundException: Cannot find point 1: 48.33591627071882,11.07885431020705'
Watching DownloadableFinder.getDownloadableFor() I can see that the file: europe/germany/bayern/oberbayern-latest.osm.pbf is selected as data, based on the center distance and inclusion of the bounding box of the two waypoints in the bounding box of the file. However... then the point seems to not be present in the Oberbayern data ... continuing then within "schwaben" that decision then swings to the next tile of Routing data and then it works properly again
Error route (within Oberbayern Bounding Box):
longitude=11.141854035548846, latitude=48.325759113802
longitude=11.07885431020705, latitude=48.33591627071882
Success (within Schwaben Bounding Box):
longitude=11.07885431020705, latitude=48.33591627071882
longitude=10.988045441798846, latitude=48.35131933232875
Oberbayern
NW Corner: longitude=10.71268, latitude=49.09052
SE Corner: longitude=13.10138, latitude=47.39037
Schwaben
NW Corner: longitude=9.397266, latitude=49.0366
SE Corner: longitude=11.31348, latitude=47.11463
My theory here: the bounding box of the file is too generous for the actual content (a bit of OSM-Data missing at the edge of Oberbayern towards Schwaben).
Is that a known problem?
Are there easy tools to visualize the Routing Data content and see what is missing / included in which file?
Regards,
Thomas
