On Oct 10, 2014, at 9:46 AM, Emux <[email protected]> wrote:
The issue here is because of graph structure changes among GraphHopper versions. We usually need to use the same GraphHopper version for reading the graph with the version that created them. This isn't a strict rule, but something to have in mind if we come along versions with graph structure changes. Sure, what I am wondering is when the graph structures have changed in the code. Is there any documentation about this, or in which way they have changed? If they are just structural changes in the objects I might be able to write a converter between the different versions. From the code it looks like a normal data access object. On Fri, Oct 10, 2014 at 9:46 AM, Emux <[email protected]> wrote: > GraphHopper being a routing library is independent of the map library we > may want to use it. > If works with Mapsforge and of course it can work with Java, Osmdroid, > Mapbox, web maps etc. > > The issue here is because of graph structure changes among GraphHopper > versions. > We usually need to use the same GraphHopper version for reading the graph > with the version that created them. > This isn't a strict rule, but something to have in mind if we come along > versions with graph structure changes. > > -- > Emux > Cruiser <http://wiki.openstreetmap.org/wiki/Cruiser> - Atlas > <http://wiki.openstreetmap.org/wiki/Atlas_%28navigation_application%29> > > _______________________________________________ > GraphHopper mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/graphhopper > >
_______________________________________________ GraphHopper mailing list [email protected] https://lists.openstreetmap.org/listinfo/graphhopper
