Hi Anton,
I would like to propose a new filter that considers [and store in DB] only valid location within a geofence, and ignores the positions outside of this geofence.
Even with some filters configured, I have the position of some vehicles that are on the sea.
<entry key='filter.enable'>true</entry>
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.duplicate'>false</entry>
<entry key='filter.maxSpeed'>25000</entry>
<entry key='filter.future'>86400</entry>
<entry key='filter.distance'>100</entry>
<entry key='coordinates.maxError'>2000</entry>
to avoid this situation:
https://drive.google.com/file/d/1Stsgj5dpO5jdQG-EqF6mp-TnbIBTzEuW/view?usp=sharing
Before opening a topic in Traccar GitHub, I would like to know if this makes sense.
JB
I guess it makes some sense.
IMHO it is worth it. The bugs from cheap devices that send aleatory wrong packets would be avoided and would not mess with the reports feature
Exactly, I already opened a ticket.
Hi Anton,
I would like to propose a new filter that considers [and store in DB] only valid location within a geofence, and ignores the positions outside of this geofence.
Even with some filters configured, I have the position of some vehicles that are on the sea.
<entry key='filter.enable'>true</entry> <entry key='filter.invalid'>true</entry> <entry key='filter.zero'>true</entry> <entry key='filter.duplicate'>false</entry> <entry key='filter.maxSpeed'>25000</entry> <entry key='filter.future'>86400</entry> <entry key='filter.distance'>100</entry> <entry key='coordinates.maxError'>2000</entry>
to avoid this situation:
https://drive.google.com/file/d/1Stsgj5dpO5jdQG-EqF6mp-TnbIBTzEuW/view?usp=sharing
Before opening a topic in Traccar GitHub, I would like to know if this makes sense.
JB