I am new to graphhopper and osm maps.
The problem I am facing is a problem with wrong boundary box in graphhopper when I work with osm map.
I don’t entirely understand who is settings bbox when I import osm map, but according to graphhopper logs:
c.g.reader.osm.GraphHopperOSM - graph CH|car,foot|RAM_STORE ... bounds:0.09002685748100707,0.10008011236965908,0.24673715785303318,0.25557596807724164
c.g.http.GraphHopperManaged - loaded graph at:/data/slaskie-latest.osm-gh, data_reader_file:/data/slaskie-latest.osm.pbf, encoded ... bounds:0.09002685748100707,0.10008011236965908,0.24673715785303318,0.25557596807724164
I assume that during graphhopper start two configs are loaded -> graphhoppers, and osms. I don’t understand why do they have exactly the same
In effect I have got centered view on the Athlantic Ocean with
what (of course) is not my working area. I don’t know exactly where the problem might be placed. I was wondering to (somehow) override custom graphhopper config to set whole world as a working area (bbox= -180, 180, -90, 90).
Can anyone hava an idea where problem might be?
One more small question, and I’m sorry in advance if that would be stupid but everyone write about
config.yml file, but in the official repository there is
config-example.yml. Is is just a forum ‘jargon’ to talk about
config-example as a simple
config file or I need to somehow create
config.yml file in project structure?
Thank you in advance for any advice.