map-matching-0.8.0.zip_Map matching_gps 地图匹配_graphhopper工具_map-m

## Map Matching based on GraphHopper [](http://travis-ci.org/graphhopper/map-matching) Map matching is the process to match a sequence of real world coordinates into a digital map. Read more at [Wikipedia](https://en.wikipedia.org/wiki/Map_matching). It can be used for tracking vehicles' GPS information, important for further digital analysis. Or e.g. attaching turn instructions for any recorded GPX route. Currently this project is under heavy development but produces already good results for various use cases. Let us know if not and create an issue! See the demo in action (black is GPS track, green is matched result):  ### License Apache License 2.0 ### Discussion Discussion happens [here](https://discuss.graphhopper.com/c/graphhopper/map-matching). ### Installation and Usage Java 8 and Maven >=3.3 are required. For the 'core' module Java 7 is sufficient. Then you need to import the area you want to do map-matching on: ```bash ./map-matching.sh action=import datasource=./some-dir/osm-file.pbf vehicle=car ``` As an example you use `datasource=./map-data/leipzig_germany.osm.pbf` as road network base or any other pbf or xml from [here](http://download.geofabrik.de/). The optional parameter `vehicle` defines the routing profile like `car`, `bike`, `motorcycle` or `foot`. You can also provide a comma separated list. For all supported values see the variables in the [FlagEncoderFactory](https://github.com/graphhopper/graphhopper/blob/0.7/core/src/main/java/com/graphhopper/routing/util/FlagEncoderFactory.java) of GraphHopper. If you have already imported a datasource with a specific profile, you need to remove the folder graph-cache in your map-matching root directory. Now you can do these matches: ```bash ./map-matching.sh action=match gpx=./some-dir/*.gpx ``` As example use `gpx=./matching-core/src/test/resources/*.gpx` or one specific gpx file. Possible arguments are: ```bash instructions=de # default=, type=String, if an country-iso-code (like en or de) is specified turn instructions are included in the output, leave empty or default to avoid this gps_accuracy=15 # default=15, type=int, unit=meter, the precision of the used device ``` This will produce gpx results similar named as the input files. ### UI and matching Service Start via: ```bash ./map-matching.sh action=start-server ``` Access the simple UI via localhost:8989. You can post GPX files and get back snapped results as GPX or as compatible GraphHopper JSON. An example curl request is: ```bash curl -XPOST -H "Content-Type: application/gpx+xml" -d @/path/to/gpx/file.gpx "localhost:8989/match?vehicle=car&type=json" ``` #### Development tools Determine the maximum bounds of one or more GPX file: ```bash ./map-matching.sh action=getbounds gpx=./track-data/.*gpx ``` #### Java usage Or use this Java snippet: ```java // import OpenStreetMap data GraphHopper hopper = new GraphHopper(); hopper.setOSMFile("./map-data/leipzig_germany.osm.pbf"); hopper.setGraphHopperLocation("./target/mapmatchingtest"); CarFlagEncoder encoder = new CarFlagEncoder(); hopper.setEncodingManager(new EncodingManager(encoder)); hopper.getCHFactoryDecorator().setEnabled(false); hopper.importOrLoad(); // create MapMatching object, can and should be shared accross threads GraphHopperStorage graph = hopper.getGraphHopperStorage(); LocationIndexMatch locationIndex = new LocationIndexMatch(graph, (LocationIndexTree) hopper.getLocationIndex()); MapMatching mapMatching = new MapMatching(graph, locationIndex, encoder); // do the actual matching, get the GPX entries from a file or via stream List<GPXEntry> inputGPXEntries = new GPXFile().doImport("nice.gpx").getEntries(); MatchResult mr = mapMatching.doWork(inputGPXEntries); // return GraphHopper edges with all associated GPX entries List<EdgeMatch> matches = mr.getEdgeMatches(); // now do something with the edges like storing the edgeIds or doing fetchWayGeometry etc matches.get(0).getEdgeState(); ``` with this maven dependency: ```xml <dependency> <groupId>com.graphhopper</groupId> <artifactId>map-matching</artifactId> <!-- or 0.8-SNAPSHOT for the unstable --> <version>0.7.0</version> </dependency> ``` ### Note Note that the edge and node IDs from GraphHopper will change for different PBF files, like when updating the OSM data. ### About See [this project](https://github.com/bmwcarit/hmm-lib) from [Stefan](https://github.com/stefanholder) which is used in combination with the GraphHopper routing engine and is used as the algorithmic approach now. Before it was [this faster but more heuristic approach](https://karussell.wordpress.com/2014/07/28/digitalizing-gpx-points-or-how-to-track-vehicles-with-graphhopper/).