Thanks so much for your work for map matching. However, I get the following strange results.
Describe the bug
I get strange matching results with circles or multiple routes. The problem I encounter can be visualized in the follow figure (matched trajectory, matched points, matched route), where the red lines (points) represents the raw trajectory and the blue line (points) represents the matched trajectory.
matched trajectory, from `pgeom'

matched points, from pgeom

matched route, from mgeom

A similar issue can be found in #76 . However, I think the trajectory in my data do not have large noise.
Expected behavior
A matched trajectory without additional circle.
Program setting
I use latitude and longitude as the unit.
For ubodt:
<parameters>
<delta>0.2</delta>
</parameters>
For fmm:
<parameters>
<k>8</k>
<r>0.003</r>
<pf>0</pf>
<gps_error>0.0005</gps_error>
</parameters>
When I switch to stmatch, I get the same results. I also tried pytrack, another map matching tool, but get the same results.
Thanks so much for your work for map matching. However, I get the following strange results.
Describe the bug
I get strange matching results with circles or multiple routes. The problem I encounter can be visualized in the follow figure (matched trajectory, matched points, matched route), where the red lines (points) represents the raw trajectory and the blue line (points) represents the matched trajectory.
matched trajectory, from `pgeom'

matched points, from

pgeommatched route, from

mgeomA similar issue can be found in #76 . However, I think the trajectory in my data do not have large noise.
Expected behavior
A matched trajectory without additional circle.
Program setting
I use latitude and longitude as the unit.
For
ubodt:For
fmm:When I switch to
stmatch, I get the same results. I also triedpytrack, another map matching tool, but get the same results.