graphhopper/map-matching

Unexpected Matching Behavior

sobhan-moosavi opened this issue · 3 comments

sobhan-moosavi commented

I realized for some traces, the matched trace is significantly different from the original one. Especially for those parts of a trajectory closer to its origin and/or destination. See attached image as an example (the pink part is not part of the input trace but is included in the matched trace), with the gpx file attached as well. Would you please help me to realize what is the source of this issue?

Thanks

trajectory

449845923207.gpx.zip

karussell commented

I can reproduce the issue with a GPS accuracy of up to 40. Increasing it to 50 solved the problem though. Can you confirm this? (I suspect the algo has no other choice when the data is too weak)

sobhan-moosavi commented

Thanks for checking. I was also able to get reasonable result when used 50 as GPS accuracy. As I have a large set of trajectories with some of them having low accurate GPS data, would that hurt if I use a large accuracy (say 100) to map match all of them?

Thanks

karussell commented

The most real (restrictive) setting is better IMO. If you don't know this, maybe only increase this if the distance discrepancy is too big or some other workaround

  • 👍1