The whole OSM reading stuff should be in a separate source module 'import-osm' which needs a bit refactoring so that we can finally do
hopper = new GraphHopperOSM().setOSMFile(...)
and on Android etc we should be able to avoid setting OSM related stuff and just do:
hopper = new GraphHopper();
We should use the change to separate OSM better from the core. Furthermore we could easier integrate other readers like #277 and #616.
You mean like split into modules for graph creation, perform routing etc. (like the current tools) ?
Yes. Just moving the import code out of core, so that Android and iOS does not need to exclude those xml reading stuff. Or if Android at some point implements its, it can just add it as dependency
In mobile platforms the import (aka creation) of graphs is a bit difficult due to device restrictions.
initial commit to separate core from osm reader, fixes #450
separate core from osm reader, fixes #450
separate module for OSM import, fixes #450
@karussell nice work!