Best Configration for Mobile Client Traccar ?
You can see in the above picture the staff on the tracking next day from another location, but the application calculates 8.24 km and counts in the total distance. Please suggest proper settings to avoid such KM calculation
What you're asking for is not possible currently.
Please suggest the best configuration for tracking the Field staff with total km for payment. Currently set the following
<!-- Enable all filters -->
<entry key='filter.enable'>true</entry>
<!-- Ignore duplicate positions (same coordinates) -->
<entry key='filter.duplicate'>true</entry>
<!-- Ignore positions with zero coordinates -->
<entry key='filter.zero'>true</entry>
<!-- Minimum acceptable distance in meters
<entry key='filter.minDistance'>10</entry> -->
<!-- Minimum acceptable time interval between messages in seconds -->
<!-- <entry key='filter.minPeriod'>60</entry> -->
<!-- Ignore messages with bad accuracy (in meters) -->
<entry key='filter.maxAccuracy'>100</entry>
<!-- Ignore positions without fix (satellite) -->
<entry key='filter.invalid'>true</entry>
<!-- Ignore positions that are "static" (device didn’t move) -->
<entry key='filter.static'>true</entry>
<!-- Ignore jumps in location data (long unrealistic distance) -->
<entry key='filter.skipLimit'>300</entry>
<entry key='filter.minSpeed'>0.5</entry>
<entry key='filter.maxSpeed'>150</entry> <!-- Maximum speed (in km/h) to consider valid movement -->
<entry key='report.trip.minimalTripDistance'>50</entry> <!-- Minimum distance (in meters) to consider a trip -->
<entry key='report.trip.minimalTripDuration'>60</entry> <!-- Minimum duration (in seconds) to consider a trip -->
<entry key='report.trip.minimalParkingDuration'>300</entry> <!-- Minimum duration (in seconds) to consider a stop -->
<entry key='report.trip.minimalNoDataDuration'>3600</entry> <!-- Time gap (in seconds) to consider as stop due to no data -->
I want to track field staff to accurately calculate kilometers traveled for payment purposes. However, I’m facing an issue where, if a staff member turns off tracking in the mobile app and later turns it back on at a different location (e.g., from home to office), the system calculates the distance between those two points as a straight line. This results in incorrect distance tracking.
How can I ensure that kilometers are only calculated during the actual tracking period—i.e., between the point when tracking is started and when it is stopped—so that any gaps in tracking (when the app is off) are excluded from the KM calculation?
some