Hello all, Peter and the other devs.
I’ve been playing around with map-matching (https://github.com/graphhopper/map-matching) to see if I can get GPS points matched to a path. Some quick tests seemed to show that this worked pretty well for what was needed.
Issue is that with the new GraphHopper 1.0-SNAPSHOT there seems to be a few breaking changes in how edges are processed.
matching-core : com.graphhopper.matching.MapMatching -> MapMatchedPath uses processEdge(edge.getEdge(), edge.getAdjNode(), prevEdge) that is no longer present in core / com.graphhopper.routing.Path
Similarly in matching-web : com.graphhopper.matching.cli.MatchCommand also fails as it expects PathMerger to supply a Graph and Weighting instead of a blank constructor.
I’m assuming I can pass in hopper and pull out the weighting value from AlgorithmOptions to pass into PathMerger.
So just wondering what the right steps would be to get map-matching working with the latest version of GraphHopper, given that it doesn’t look like the old methods are now applicable? - at least since commit - https://github.com/graphhopper/graphhopper/commit/9a5efe6e2b7332495709cfc42674017d7d047cfc
It might be that you are already planning to update the map-matching repo to work with the new GraphHopper modifications, in which case if you have an estimate on when that might be worked on would be appreciated.
Thanks v much,