Filtering Positions for Database Storage While Keeping Live Data in WebSocket
Not supported currently. Filtering will filter it everywhere. You should probably just clear the database later or have a trigger function.
Thank you for your assistance! I’d like to take this a step further and explore modifying Traccar’s source code to filter positions before they are saved to the database. From my understanding, the WebSocket receives live data from devices before it is saved to the database.
Could you please guide me on which files or components I need to modify to implement custom filtering logic before positions are saved to the database?
Specifically:
- Which part of the code handles the incoming data from devices before it is saved to the database?
- Where can I add custom logic to filter positions based on my conditions?
- Are there any best practices or precautions I should keep in mind while making these changes?
Hi Traccar Community
I’m exploring the possibility of filtering which positions are saved in the Traccar database while still receiving live positions via WebSocket. Specifically, I’d like to apply filters based on the following conditions (separated by OR logic):
Minimum distance: 200 meters
Minimum time: 10 minutes
Minimum angle: 20 degrees
Minimum speed: 10 km/h
The goal is to ensure that only positions meeting these conditions are saved in the database, while still receiving all live positions in real-time through the WebSocket connection (e.g., if my GPS device sends data every 10 seconds, I want to see all updates in the WebSocket but only save filtered records to the database).
Is this functionality currently supported in Traccar? If not, are there any recommended approaches or workarounds to achieve this?
Thank you in advance for your help