Hello Anton,
Sorry to bother you again. I have another question regarding coordinates.filter and coordinates.maxError.
I have this problem: from time to time, my tracker goes peculiar and jumps several kilometers. It happens often when the battery voltage goes too low. It reports the incorrect location until I charge it again, then it jumps back to the correct location. For example, this morning:
So I'm thinking of using
<entry key='coordinates.filter'>true</entry>
<entry key='coordinates.maxError'>5000</entry>
My tracker reports every 30 seconds, so 5 km should be plenty at bicycle speeds: even if I ride at 120 km/h (I do sometimes :)) the tracker could miss 5 reports before tripping the 5 km filter. It's doesn't seem very likely, but it can happen I guess.
What could also happen is, I leave the tracker on, I move the bike with a minivan, then when I get it out of the minivan, the location is many kilometers away from the starting point, tripping the filter again.
My questions are these:
1/ With coordinates.maxError set to 5000, am I correct into thinking that, if the tracker really does move farther than 5 km between location reports because the tracker fails to connect for too long for any reason, all subsequent location reports will get rewritten and the tracker will appear static forever after, unless I happen to move back within 5 km of the point where it got stuck?
2/ If the status changes to "unknown" or "offline", will that reset the coordinates filter? In other words, if Traccar "loses" the tracker because of the maxError filter, will it recover if I turn the tracker off and back on a few minutes afterwards?
Unfortunately, I can't use the filter.maxSpeed filter - which would seem more appropriate: for example, this morning, the bike was static for 2 hours before the jump occured (with filter.distance, no new positions got logged for 2 hours). When the jump happened, Traccar calculated an average speed of 15 km/h between the last correct position and the bogus one. 15 km/h is normal speed, so it wouldn't have caught it.
Thank you for your insight!
Hello Anton,
Sorry to bother you again. I have another question regarding coordinates.filter and coordinates.maxError.
I have this problem: from time to time, my tracker goes peculiar and jumps several kilometers. It happens often when the battery voltage goes too low. It reports the incorrect location until I charge it again, then it jumps back to the correct location. For example, this morning:
So I'm thinking of using
<entry key='coordinates.filter'>true</entry> <entry key='coordinates.maxError'>5000</entry>My tracker reports every 30 seconds, so 5 km should be plenty at bicycle speeds: even if I ride at 120 km/h (I do sometimes :)) the tracker could miss 5 reports before tripping the 5 km filter. It's doesn't seem very likely, but it can happen I guess.
What could also happen is, I leave the tracker on, I move the bike with a minivan, then when I get it out of the minivan, the location is many kilometers away from the starting point, tripping the filter again.
My questions are these:
1/ With coordinates.maxError set to 5000, am I correct into thinking that, if the tracker really does move farther than 5 km between location reports because the tracker fails to connect for too long for any reason, all subsequent location reports will get rewritten and the tracker will appear static forever after, unless I happen to move back within 5 km of the point where it got stuck?
2/ If the status changes to "unknown" or "offline", will that reset the coordinates filter? In other words, if Traccar "loses" the tracker because of the maxError filter, will it recover if I turn the tracker off and back on a few minutes afterwards?
Unfortunately, I can't use the filter.maxSpeed filter - which would seem more appropriate: for example, this morning, the bike was static for 2 hours before the jump occured (with filter.distance, no new positions got logged for 2 hours). When the jump happened, Traccar calculated an average speed of 15 km/h between the last correct position and the bogus one. 15 km/h is normal speed, so it wouldn't have caught it.
Thank you for your insight!