search

graphhopper / map-matching

The map matching functionality is now located in the main repository https://github.com/graphhopper/graphhopper#map-matching
https://www.graphhopper.com/open-source/
Apache License 2.0
785 stars 273 forks source link

Observing some considerable deviation #95

Closed arminus closed 7 years ago

arminus commented 7 years ago

I just gave the map-matcher a spin, here's an example of a DB built with the foot encoder and a GPX track downloaded from the web (i.e. not a raw/recorded track). There's quite some deviation at km 10-11 in the matched track on the right side and a smaller one at km 18/19. Are non-recorded tracks generally unsuited for the matcher or is there something else going on?

rawvsmatched

arminus commented 7 years ago

(I also tried bike and mtb encoders, same result)

karussell commented 7 years ago

If there are no paths in OSM how should GPS tracks be matched then? Or what do you mean? Also please move questions to our forum.

karussell commented 7 years ago

The difference at point "10" should be fixed in the latest master version. Did you try with master or a 0.8 release?