Clarification on filter.limit Usage in traccar.xml (v6.7.1)

Haider 7 days ago

I'm using Traccar version 6.7.1, and I’ve noticed that some of my GPS devices occasionally report incorrect positions — for example, suddenly jumping thousands of kilometers in a single update. These jumps are clearly inaccurate and cause confusion for clients.

I’ve read in community discussions and seen code references that Traccar supports the following filter options:

<entry key='filter.enable'>true</entry>
<entry key='filter.limit'>100000</entry>

From what I understand:

filter.limit is supposed to reject GPS jumps over a certain distance (in meters), in this case, 100 km.

However, this parameter is not listed in the official documentation, and some sources suggest it may be related to time gaps instead.

Could you please confirm:

  1. Is filter.limit officially supported in version 6.7.1?

  2. Does it filter based on distance between points or the time interval?

  3. What’s the recommended way to prevent such fake GPS jumps?

Thanks in advance for your help!

Track-trace7 days ago

Did you try coordinates filter max error?

Track-trace7 days ago
Anton Tananaev7 days ago

Haider where did you find filter.limit? Can you please provide a link.

Haider 7 days ago

Dear Anton Tananaev and Track-trace,

I already checked the configuration files, and I couldn’t find filter.limit, which is exactly why I created this post — to confirm if it’s officially supported or not.

Secondly, I’ve already tried using several filters, but when I added too many, the devices started stuck and stopped updating locations. For example, the device would show as parked for hours even though it was moving, and only after a server reboot would it start updating correctly.

Here’s what I had configured:

<entry key='filter.enable'>true</entry>
<entry key='coordinates.filter'>true</entry> 
<entry key='coordinates.minError'>50</entry>
<entry key='filter.distance'>20</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.invalid'>true</entry> 
<entry key='filter.future'>3600</entry>	
<entry key='filter.skipLimit'>25</entry>	
<entry key='filter.maxSpeed'>180</entry> 

I removed these lines:

<entry key='coordinates.filter'>true</entry> 
<entry key='coordinates.minError'>50</entry>
<entry key='filter.distance'>20</entry>
<entry key='filter.invalid'>true</entry>

After removing them, the device stopped getting stuck — but now, sometimes it jumps to wrong locations again.

As for the source of filter.limit, I got it from ChatGPT, and they provided screenshots and links referring to the Traccar GitHub and forums. But when I checked those links myself, I couldn’t find this setting directly mentioned, which is why I’m asking for official confirmation here.

Thanks.

chatgpt

Haider 6 days ago

????

Track-trace5 days ago

So where is the max error as suggested?