We are running Traccar with GPS trackers installed on marine speedboats. The main issue we’re facing is that when the boat stops, some trackers stop sending data entirely. Because of this, the stop detection doesn’t work properly.
We tried using the configuration parameters:
<entry key='report.trip.minDistance'>100</entry>
<entry key='report.trip.minTripDuration'>60</entry>
<entry key='report.trip.minParkingDuration'>120</entry>
This works fine when data is being transmitted, but since the trackers stop reporting while stationary, the system never generates a proper "stop" event.
We considered using report.trip.minimalNoDataDuration to handle this. The problem, however, is that our devices sometimes lose 4G coverage at sea for up to an hour. If we set report.trip.minimalNoDataDuration to a short value (e.g., 5 minutes), it splits trips incorrectly during these network blackouts.
What we really need is a way to make report.trip.minimalNoDataDuration conditional on speed. For example:
If the boat is moving above 10 knots, the trip should continue even if there’s no data for a while (due to 4G gaps).
If the boat speed drops below 2 knots and there’s no data for some time, then the trip should end.
This kind of speed-dependent handling would solve the problem of false trip splits in poor network coverage while still detecting proper stops when the tracker stops sending data at low speed.
Please provide a link to where you found those configuration parameters.
I don't see the parameters you tried on that page.
We are running Traccar with GPS trackers installed on marine speedboats. The main issue we’re facing is that when the boat stops, some trackers stop sending data entirely. Because of this, the stop detection doesn’t work properly.
We tried using the configuration parameters:
<entry key='report.trip.minDistance'>100</entry> <entry key='report.trip.minTripDuration'>60</entry> <entry key='report.trip.minParkingDuration'>120</entry>This works fine when data is being transmitted, but since the trackers stop reporting while stationary, the system never generates a proper "stop" event.
We considered using report.trip.minimalNoDataDuration to handle this. The problem, however, is that our devices sometimes lose 4G coverage at sea for up to an hour. If we set report.trip.minimalNoDataDuration to a short value (e.g., 5 minutes), it splits trips incorrectly during these network blackouts.
What we really need is a way to make report.trip.minimalNoDataDuration conditional on speed. For example:
If the boat is moving above 10 knots, the trip should continue even if there’s no data for a while (due to 4G gaps).
If the boat speed drops below 2 knots and there’s no data for some time, then the trip should end.
This kind of speed-dependent handling would solve the problem of false trip splits in poor network coverage while still detecting proper stops when the tracker stops sending data at low speed.