Negative distances...
Most likely your device is not reporting data in the chronological order and that's what's causing. This issue has been discussed many times on the forum.
Sorry, didn't knew. The bulk uploading then.
I'm sorry, I also opened the same subject a year ago... kill this thread.
Thank you very mucha again.
Or, wait...
¿Couldn't there be a way to "instruct" the server to treat distances between points according to their reported date/time instead of the time when they are being reported? This will solve the issue and would'nt alter any meaningful data or interpretation of it.
Currently it's not possible.
I didn't want to create new post since this is talking about exactly what i ve encountered today
A vps reported negative distance position which led to wrong speed calculation.
If i set filtet distance to maybe 5
Would this solve negative distance issues?
No, it won't. Negative distance usually means wrong position order. Newer versions of Traccar have an option server.buffering.threshold that might help with ordering data correctly.
I have found this odd behavior and i'm worried about it.
There's certain times when distances get reported negative, and I can't understand what's happening.
When he goes, distance is positive, when he gets back on the same track, distance is still positive, but some times, this strange thing appears.
Could it may be because the device stores data while there's no internet signal and then reports it in bulk, maybe server gets messy?
https://i.imgur.com/NTvjQy4.png