The coordinate position jumps

I set these values ​​in the config, but the coordinates still jump. What else am I missing?

    <entry key='filter.enable'>true</entry>
    <entry key='filter.zero'>true</entry>
    <entry key='filter.future'>86400</entry>
    <entry key='filter.invalid'>true</entry>
    <entry key='filter.duplicate'>true</entry>
    <entry key='filter.static'>true</entry>
    <entry key='filter.skipLimit'>35</entry>
    <entry key='filter.minPeriod'>25</entry>
    <entry key='filter.maxSpeed'>130</entry>
    <entry key='filter.distance'>50</entry>
    <entry key='filter.approximate'>false</entry>
    <entry key='filter.accuracy'>60</entry>
    <entry key='coordinates.filter'>true</entry>
    <entry key='coordinates.minError'>60</entry>

There is no logic in setting <entry key='filter.skipLimit'>35</entry> to 35 seconds.

How about first try and set it to 600 (10 minutes) ?

Because I thought that if I set the period too long, it would cut off moving cars.

Just try the new setting. Restart your server. And check after an hour what it shows on the map for those trackers.
The edit and restart should only take a minute.

As already pointed, your filter.skipLimit makes most other filtering completely useless. You have to make a choice here. Either you want to get rid of those jumps or you want to track every move accurately. You can't have both.

it turns out that you can't filter jumps when it's standing still, when the speed is 0? And when moving, save more often. Because on the screen, the car was standing still all day.

Was the speed actually zero if you look at the data?

sorted all jumps by database
it turns out that even though the car is standing still, the coordinates come from 1-3 km/h

is it possible to somehow filter coordinates that have a speed of less than 5 km/h

Speed a distance filtering is essentially the same thing in this case. The result will be the same.

Proposed Solution

To avoid the issue you mentioned, you can adjust the values of these filters to be more appropriate for small movements and situations where GPS accuracy may vary. Here are some suggested adjustments:

• Reduce filter.distance:

  <entry key='filter.distance'>10</entry>

  This will allow the system to record smaller movements, such as entering a garage.

• Adjust filter.accuracy:

  <entry key='filter.accuracy'>100</entry>

  This will permit the recording of positions with lower accuracy, which is acceptable in areas where GPS may have precision errors.

Adjusted Configuration Example

<entry key='filter.enable'>true</entry>
<entry key='filter.distance'>10</entry>
<entry key='filter.accuracy'>100</entry>
<entry key='coordinates.maxError'>0</entry>

Additional Considerations

• Monitor Results: After making these adjustments, monitor the system's behavior to ensure the recorded positions are accurate and correctly reflect the vehicle's movement.
• Field Testing: Conduct tests in various scenarios (short and long movements) to validate that the adjusted filters work correctly.

Conclusion

The filter.distance and filter.accuracy are powerful tools to maintain the accuracy of recorded positions but need to be configured appropriately to suit specific usage conditions. By adjusting these values, you can minimize the issue of skipped positions and ensure the system records the vehicle's movements more accurately, even in situations where the movement is minimal or the GPS accuracy varies.

For more details on Traccar configuration, you can refer to the official Traccar documentation [❞].

thank you very much
I will adjust the parameters and test