You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the "Minianal location displacement" setting cannot prevent the client from reporting many data points with similar locations.
This will cause the server to receive a lot of messy data, which will be reflected as fragmented lines on the map.
Perhaps my understanding of this function is biased, and this setting does not work for the "Move" mode. Is there a more effective way to control the client not to report such close distance data?
On the other hand, can the frontend interface add some smoothing to the route, so that the record looks more reasonable and clear. Thank you
The text was updated successfully, but these errors were encountered:
It works for me on Android. In significant mode I have inaccurate set to 200, minimal distance set to 50 and update set to 60s. It's too hard to blur my local map but I only get a location sent when I move.
Move mode will always send the location. Per the documentation, The locatorDisplacement option is ignored in this mode.
It seems that the "Minianal location displacement" setting cannot prevent the client from reporting many data points with similar locations.
This will cause the server to receive a lot of messy data, which will be reflected as fragmented lines on the map.
Perhaps my understanding of this function is biased, and this setting does not work for the "Move" mode. Is there a more effective way to control the client not to report such close distance data?
On the other hand, can the frontend interface add some smoothing to the route, so that the record looks more reasonable and clear. Thank you
The text was updated successfully, but these errors were encountered: