A stop is one or more consecutive messages with a zero speed. Stops can be registered at lights, intersections, in traffic jams, etc.
Stops should be distinguished from parkings. Parameters to detect trips, parkings, and stops are adjusted in the trip detector. If there are several messages in succession, they are united in one stop. If the total time of such a stop reaches Minimum parking time, it is registered as a parking (not as a stop).
The information which can be presented in this kind of report is described below.
|Beginning||The time when the stop started.|
|End||The time when the stop ended.|
|Duration||The total time of the stop.|
|Total time||The time from the beginning of the first stop to the end of the last stop.|
|Off-time||The time from the end of the previous stop to the beginning of the current one (to be defined beginning from the second stop).|
|Location||The address where the unit stopped.|
|Coordinates||The coordinates of the unit at the moment of a stop (in decimal degrees).|
|Driver||The name of the driver (if available).|
|Trailer||The name of the trailer (if bound).|
|Count||The number of stops.|
|Counter||The counter sensor values (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).|
|Notes||An empty column for your custom comments.|
|Avg weight||The average weight value registered for the stop interval.|
|Min weight||The minimum weight value registered for the stop interval.|
|Max weight||The maximum weight value registered for the stop interval.|
|Initial weight||The weight value at the beginning of the stop interval.|
|Final weight||The weight value at the end of the stop interval.|
See data in reports to learn how time (duration) can be formatted.
Interval filtration (by stop duration, sensor state, driver, trailer, fuel fillings and thefts) can be applied to this table.
This kind of report can be supplemented with the corresponding markers on the map.
Stops should be distinguished from parkings.