Hello,
I'm using Traccar version 6.6 on Ubuntu 22.04 with a PostgreSQL database. I intend to use only the filter.distance filter, configured individually in each device's attributes, for example: json {"filter.distance": 25}
In my traccar.xml file, I have all required settings enabled:
<entry key='filter.enable'>true</entry>
<entry key='filter.distance'>0</entry>
<entry key='logger.level'>debug</entry>
The server was restarted, configuration verified, and attributes are visible both in the database and API. However, Traccar does not seem to filter positions that are less than 25 meters apart.
For testing purposes, I even set filter.distance to 100000 (100 km), yet positions continue to be saved despite very small movement.
In the tracker-server.log file (with logger.level=debug), there are no entries about positions being filtered, which suggests that the filter may not be active at all.
Is there any additional condition required to activate filter.distance? Are there any known issues with this filter in version 6.6?
Thank you in advance for your assistance.
Robert
What if you just set filter.distance in the config itself for instance at 100 meter ?
Sorry for the confusion. I thought this functionality was available. A little facelift and it works.
Hello,
I'm using Traccar version 6.6 on Ubuntu 22.04 with a PostgreSQL database. I intend to use only the filter.distance filter, configured individually in each device's attributes, for example: json
{"filter.distance": 25}
In my traccar.xml file, I have all required settings enabled:
<entry key='filter.enable'>true</entry> <entry key='filter.distance'>0</entry> <entry key='logger.level'>debug</entry>
The server was restarted, configuration verified, and attributes are visible both in the database and API. However, Traccar does not seem to filter positions that are less than 25 meters apart.
For testing purposes, I even set filter.distance to 100000 (100 km), yet positions continue to be saved despite very small movement.
In the tracker-server.log file (with logger.level=debug), there are no entries about positions being filtered, which suggests that the filter may not be active at all.
Is there any additional condition required to activate filter.distance? Are there any known issues with this filter in version 6.6?
Thank you in advance for your assistance.
Robert