Sudden jumps in position due to GPS device error, its effect to Traccar Server
I can confirm that.
off course someone else besides you Anton...I just want to make sure I'm not the only one seeing this. I will continue to troubleshoot on my end, maybe its a user error.
is this case only can configure at version 3.13 ?
Yes, I believe maxSpeed is only available since 3.13.
Hi Anton
we updated our Traccar to 3.13 and implemented below configuration :
<entry key='filter.enable'>true</entry> <entry key='filter.zero'>true</entry> <entry key='filter.invalid'>true</entry> <entry key='filter.maxSpeed'>150</entry> <entry key='coordinates.filter'>true</entry> <entry key='coordinates.minError'>50</entry> <entry key='coordinates.maxError'>300000</entry>
restarted the engine, but still find valid coordinates but jumping with distance up to 1 millions meter in 10 seconds
do you have any idea how to check that the filter.maxSpeed is actually working ?
for we checked the logs, there is maxspeed filtering :
cat logs/traccar.log.20170809 | grep MaxSpeed 2017-08-09 07:52:49 INFO: Position filtered by MaxSpeed filters from device: 351608083984653 with id: 1720 2017-08-09 07:52:55 INFO: Position filtered by Zero MaxSpeed filters from device: 27028270650 with id: 1003
but we still have that huge distance jumping with very short amount of time (around 10s)
Check this thread:
Hi Anton, just want to confirm
By the update from that github
If i set maxSpeed value to 1
Would it be 1 knot
Or still 1000 knot ?
Since u have said u fix it but the other people said to take into account that the value is 1000 times higher
It's fixed in the code, but not in the official release yet. It will be included in the next release.
Hi Anton
We have this code on our traccar (just updated 2 days ago from 3.9 to 3.13)
private boolean filterMaxSpeed(Position position, Position last) {
if (filterMaxSpeed != 0 && last != null) {
double distance = position.getDouble(Position.KEY_DISTANCE);
long time = position.getFixTime().getTime() - last.getFixTime().getTime();
return UnitsConverter.knotsFromMps(distance / (time / 1000)) > filterMaxSpeed;
}
return false;
}But the jumping is still there
How do you have this code if you updated to 3.13? I'm confused by your statement.
We updated our Traccar to 3.13 2-3 days ago
Then implemented the maxSpeed filter
After a day, i reviewed the result data stored in database
And still found jumping coordinate with huge distance
Ask this forum and you gave me the github link
I pass the github link to our developer
They said the code inside that github is exactly the same as in our Traccar
So the situation i have right now is
Traccar 3.13
Checked the github and the fixed code is already implemented in our Traccar 3.13
But still have jumping coordinates with huge distance value
If you are using a version built from "master" branch, then it's NOT 3.13!!! You are contradicting yourself.
I'm looking to enable this filtering, but trying to work out my best value is giving me trouble. For example, I have the following rows in the positions table:
id protocol deviceid servertime devicetime fixtime 1 valid latitude longitude altitude speed course address attributes accuracy network
7155682 teltonika 50 2018-03-24 13:30:10 2018-03-24 13:29:15 2018-03-24 13:29:15 1 50.5790323 -3.6626038 35 0 0 NULL {"priority":0,"sat":18,"event":0,"io199":0,"distance":0.0,"totalDistance":5478340.61,"motion":false} 0 null
7155572 teltonika 50 2018-03-24 13:24:18 2018-03-24 13:24:15 2018-03-24 13:24:15 1 50.5790323 -3.6626038 34 0 0 NULL {"priority":0,"sat":18,"event":0,"io199":0,"distance":0.0,"totalDistance":5478340.61,"motion":false} 0 null
7155524 teltonika 50 2018-03-24 13:21:38 2018-03-24 13:21:35 2018-03-24 13:21:35 1 50.5790323 -3.6626038 35 0 0 NULL {"priority":0,"sat":19,"event":0,"io199":0,"distance":0.0,"totalDistance":5478340.61,"motion":false} 0 null
7155508 teltonika 50 2018-03-24 13:21:06 2018-03-24 13:20:35 2018-03-24 13:20:35 1 50.5790323 -3.6626038 43 0 0 NULL {"priority":0,"sat":15,"event":0,"io199":0,"distance":11.76,"totalDistance":5478340.61,"motion":false} 0 null
7155478 teltonika 50 2018-03-24 13:20:09 2018-03-24 13:19:35 2018-03-24 13:19:35 1 50.5789435 -3.6626938 20 0 278 NULL {"priority":0,"sat":7,"event":0,"io199":0,"distance":44607.42,"totalDistance":5478328.85,"motion":false} 0 null
7155464 teltonika 50 2018-03-24 13:19:21 2018-03-24 13:18:57 2018-03-24 13:18:57 1 50.9650813 -3.49334 -1757 52.3758 275 NULL {"priority":0,"sat":4,"event":0,"io199":0,"distance":1545.53,"totalDistance":5433721.43,"motion":true} 0 null
7155462 teltonika 50 2018-03-24 13:18:57 2018-03-24 13:18:32 2018-03-24 13:18:32 1 50.9570655 -3.511338 -2535 58.3154 278 NULL {"priority":0,"sat":5,"event":0,"io199":0,"distance":43416.64,"totalDistance":5432175.9,"motion":true} 0 null
7155461 teltonika 50 2018-03-24 13:18:57 2018-03-24 13:18:18 2018-03-24 13:18:18 1 50.5789788 -3.6627046 39 0 0 NULL {"priority":0,"sat":16,"event":0,"io199":0,"distance":0.0,"totalDistance":5388759.26,"motion":false} 0 null
How is the speed evaluated? I would say that to cover 43416m in 14s is 6028.1 knots, not the 58.3154 shown. I guess the altitude (which is clearly wrong) should be factored but still the stored speed seems to be wrong also.
I am running Traccar v3.14 and using Teltonika FM11110 trackers.
Please ignore my above comment - I have started a separate thread #29482.
Hi Anton,
I have tried "1" and "10" to no effect. It'll be good if someone else can confirm the "maxSpeed" filter on 3.13 is working.