Stops

Stops

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 total time of such a stop reaches Minimum parking time, it is registered as a parking (not a stop).

The following information is presented in this kind of report:

  • Beginning: the time when the stop started.
  • End: the time when the stop ended.
  • Duration: total time of the stop.
  • Total time: time from the first stop beginning to the last stop end.
  • Off-time: time from the end of the previous stop to the beginning of this one (to be defined beginning from the second stop).
  • Location: the address where the unit stopped.
  • Coordinates: the unit's coordinates at the moment of a stop (in decimal degrees).
  • Driver: driver's name if available.
  • Trailer: trailer's name if any was bound.
  • Count: the number of stops.
  • Counter: 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: average weight value registered for the stop interval.
  • Min weight: minimum weight value registered for the stop interval.
  • Max weight: maximum weight value registered for the stop interval.
  • Initial weight: weight value in the beginning of the stop interval.
  • Final weight: weight value in the end of the stop interval.


See Data in Reports to learn how time (duration) can be formatted.

Intervals 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 by corresponding markers on the map.



    • Related Articles

    • Fuel Filling Is Not Detected

      We have refuelled the vehicle but cannot find this filling in the report. Why? Possible explanations and actions: 1. Incorrect settings for trip detector. The option to analyze fuel filling only at stops is set on the 'Fuel Consumption' tab of unit ...
    • Trip Not Detected

      A vehicle definitely moved (there are messages with 70 kph speed), however, this trip is not shown in the report. Possible explanations and actions: Movement detection is set incorrectly in the trip detector, e.g., the ignition sensor is out of ...
    • Deleting Accounts/Resources

      To delete an account or resource, you should possess the appropriate level of access to it. In most cases, the removal occurs when a service agreement is broken and a client stops using the system. To delete an account, click the delete button in the ...
    • Intervals Filtration

      Most table reports in the gTrack system involve retrieving time intervals which meet certain criteria from the unit's history. These are reports on trips, parkings, stops, engine hours, rounds, geofences and visited streets, reports on the operation ...
    • Intervals Filtration

      Several tables are supplied with additional parameters to filter intervals. There you can set conditions to select information to be displayed in the resulting report. These conditions affect reports that concern selecting intervals from the ...