I meant:
...
However, due to the signal noise I get position updates which are pretty much "non-relevant", since they are predominately stationary and within a predefined geofence, see image below:
...
That's what filtering is for.
Hi, thank you for your quick reply!
But that works only for all devices, or? In case I have some devices with precise tracking positions, that would be "overwritten" as well?
Not sure I understand your questions.
Sorry for not being precise enough.
I have some devices which are not very precise. But they are located within a geofence area. And I know, as long as they are in this geofence area I am fine with it. Then I have some devices which are quite precise (using bluetooth, gps, ...) with low noise and I want their exact position. However, sometime devices of both categories are within the same geofence location. For the first type of devices a position mapping to the geofence location (your "filtering") would be great, since - lets say 95% - of the position updates are just noise. For the latter category the "false position updates" are very little. For those devices I do not want any filtering but the exact position.
Could this clear your questions?
Filtering can be applied to specific devices.
Ah, I think you pointed me to the right direction. I guess you mean a combination of: filter.skipAttributes and filter.skipAttributes.enable?
I somehow missed this in the docs. Thank you!
That's not what I mean. I mean literally filtering configuration can be applied per device.
Ah, you mean device based distance attribute. I think I need to reread the complete docs. Sorry, for not being better prepared. Thank you!
I have this problem too. Which device attribute would fix these jumps?
Hi. I just added it, so I cannot really say somehting. But I guess Anton means, that you can add per device an attribute:

And the docs https://www.traccar.org/configuration-file/ says:
filter.distance (via config or device):
Filter records by distance. The value is specified in meters. If the new position is closer than this value to the last one, it gets filtered out.
So its not mapped to a geofence as in my case initially thought, but it should work for most cases. I am not yet sure, if the heartbeat gets skipped as well (so no record update at all), or if it updates the previous position.
Hi Anton. Thank you for your hint. And I am really sorry about my lack of knowledge. I am not yet absolutely sure, but may it be that the "distance" attribute is filtering out the complete dataset? So the last seen is not updated anymore although data has "just been filtered out"?
If you misconfigure filtering, they can definitely start filtering everything. You should check logs first.
Hello,
please excuse my potential lack of knowledge. I really like the traccar and integrated some ESP32 devices. Some of these devices are predominantly within a geofence location. However, due to the signal noise I get position updates which are pretty much "non-relevant", since the are within a predefined geofence, see image below:

Now my question:
Is it possible to update the position of a device prior its database write operation to the position of the geofence? Best case would be to enable / disable it per device "flag". Reason: in my opinion it would:
a.) clear the appearance of the device position by avoiding these "non-sense" positions.
b.) Reduce DB storage size since noise positions would not be stored, but set to "known" position.
Thank you for your input and help!