Yes, you don't even need "filter.enable".
Okay, removed that and restarted, but its still moving about.
Is movement more than 50 meters?
Well, unless the scale of the map is really out, it really shouldn't be. I can try making the value higher and see if that changes things.
Will I see the coordinates being filtered in the log file? I suppose I can just watch them in the DB for a bit and see if they stay the same otherwise?
Yes, you can check database. Have you restarted service after changing config?
Yes, restarted after each change.
Okay, set it to 500, but it's still moving slightly.
Sorry, there were changes to coordinates filtering in 3.8. You need to set "coordinates.minError" parameter instead of "coordinates.error".
Aha, sorted!
Thanks! :)
What's the difference between "coordinates.filter" and "filter.distance"?
Please read documentation:
Of course I read that. Still not clear.
"Replaces position coordinates if it changes less than..."
Replaces with what? Is this a filter or a replacer?
Also, after you answered this with "yes" I got more confused, because the documentation for coordinates filter also mentions parking:
"Helps to avoid coordinates jumps during parking period."
coordinates.filter
- replaces coordinates with last knownfilter.distance
- filters out the whole record
I would put these 3 words "with last known" in the documentation.
Hi,
I have the following in my config on 3.8, but when parked, my tracker is still jumping around slightly:
Do I need to change anything else to get this working?
Thanks