No, but you can enable distance filtering.
I looked at the distance filtering and trying to correct the trips.
<entry key='filter.distance'>50</entry>
<entry key='filter.enable'>true</entry>
<entry key='report.trip.minimalTripDuration'>15</entry>
<entry key='report.trip.minimalTripDistance'>100</entry>
<entry key='report.trip.minimalParkingDuration'>30</entry>
The way I understand this, filter.distance will ignore movements less than 50 from the counter for the device.
The report.trip.minimal related settings will mean a trip will have to be longer than 15 seconds & more than 100 meters to count as a trip, and stop will have to exceed 30 seconds to register as a stop?
Am I correct in how I understand and have configured this?
Documentation for filtering and trips:
https://www.traccar.org/configuration-file/
https://www.traccar.org/documentation/trips-stops/
Can this be changed or configured some how?
Vehicles show they've traveled 200-300m over night that haven't moved, often clocking up almost 2km when they are stationary just to gps accuracy changes between updates.
The same extends to trips, vehicles show trips that haven't had the ignition on just because of the location accuracy.
To fix this could it be that it needs to have Ignition ON to start a trip and Ignition OFF to end that trip?
And Ignition OFF distance isn't counted?