Rides

Rides

gTrack can track rides between geofences if one of them (or several) is set as the starting point, and the other (or several) as the final one. Two factors are important to generate such report: when a unit leaves the starting geofence and when it enters the final one. In such case a ride between geofences is considered complete. In addition, all rides between geofences are determined taking into account the trip detector.

This report is useful, for instance, to control the transportation of a cargo from one place to another in several trips.

Preparing Geofences

To get a report on rides between geofences, ypu must first create geofences that determine the beginning and end of the ride. The beginning and the end can be the same geofence if the ride starts and ends in one place, for example, if you need to transport cargo from point A to point B and this will take more than one trip. Create two geofences and then specify them as the starting and ending points in the report template.


Ride Parameters

When you create a report template for rides, you can set additional parameters for it.

Allow circle ride
Check this option if the beginning and end of the ride must be in the same geofence. At the same time, in order for the report to work, it is necessary that a geofence (or a unit) have both boxes checked — beginning and end of the ride.

Show the rides finished with a stop
This can be used as an additional filter. If this option is selected, only visiting the geofences with a stop at the final point are considered the end of the ride. Note that a stop is considered to be a unit state in which its speed is less than the minimum moving speed indicated in the trip detector. A ride begins when a unit leaves the starting point. If a unit enters the final destination (after the beginning of the ride has been detected), but does not make a stop there, the ride continues.

Starting and terminal points
In this section you choose which geofences and units will be analyzed in the report. You can not only use the geofences from the resource in which the report template is created, but also the geofences from other resources to which the user has the access right View geofences. The resource is chosen in the dropdown list above the geofences' names. It is also possible to choose the All option — then the list will contain the geofences from all the resources to which the user has the necessary access right. The geofences in the list are sorted by name. To quickly find one, use the dynamic filter.

Besides, you can choose units as so-called 'moving geofences'. For them, set radius to outline unit's area. Geofences and units on the lists are sorted by name. If the list is large, it is convenient to use name mask to quickly find necessary items. You can even set ride beginning at unit's area and ride end at an ordinary geofence.


Besides, intervals filtration can be applied to this table: by duration, mileage, engine hours, speed range, trips, stops, parkings, sensor state, driver, trailer, fuel thefts, fillings, and geofences/units.

Note that monitoring system provides a possibility of detecting geofence visit in case a trip intersects a geofence by any segment of its track. This option can be enabled in the advanced settings of a report template.

Report on Rides

The report on rides gives the list of all performed rides. The table can contain the following information:

  • Ride: ride mane consists of starting geofence name and final geofence name hyphenated compound.
  • Ride from: can be used instead of the previous column. Only the departure geofence is indicated here.
  • Ride to: destination geofence.
  • Beginning: date and time when the ride began.
  • End: date and time when the ride ended.
  • Mileage: distance traveled in this ride.
  • Mileage (adjusted): mileage subject to the coefficient set in unit properties ('Advanced' tab).
  • Ride duration: how much time it took to perform the ride.
  • Total time: time from the first ride beginning to the last ride end.
  • Parkings duration: time spent in parkings.
  • Avg speed: average speed calculated for this ride.
  • Max speed: maximum speed registered during this ride.
  • Driver: driver's name if he was identified.
  • Trailer: trailer's name if any was bound.
  • Counter: counter sensor value (can be helpful either in grouping table data by years/months/weeks/days/shifts or for the reports on unit groups).
  • Initial counter: counter value at the beginning.
  • Finale counter: counter value at the end.
  • Avg temperature: average temperature value registered in a ride.
  • Min temperature: minimum temperature value registered in a ride.
  • Max temperature: maximum temperature value registered in a ride.
  • Initial temperature: temperature value in the beginning of a ride.
  • Final temperature: temperature value in the end of a ride.
  • Count: the number of rides.
  • Status: unit status registered during the current ride (if there are several, the first one is displayed).
  • Cargo weight: weight of a cargo transported within a trip between geofences.
  • Consumed: the volume of consumed fuel detected by any sort of fuel sensor. If several such sensors are available, their values sum up.
  • Consumed by ImpFCS/AbsFCS/InsFCS/FLS/math: the volume of consumed fuel detected by a fuel sensor (like impulse/absolute/instant fuel consumption sensor, fuel level sensor) or calculated by math.
  • Avg consumption: average fuel consumption by any sort of fuel sensor. If several such sensors are available, their values sum up.
  • Avg consumption by ImpFCS/AbsFCS/InsFCS/FLS/math: average fuel consumption in the ride detected by one of the methods mentioned above.
  • Initial fuel level: fuel level at the beginning of the ride.
  • Final fuel level: fuel level at the end of the ride.
  • Max fuel level: maximum fuel level.
  • Min fuel level: minimum fuel level.
  • Penalties: penalties calculated for adjusted 'Eco Driving' criteria.
  • Rank: received penalty points converted into a grade using 6 point scoring system.
  • Notes: an empty column for your custom comments.


See also Unfinished Rides.


    • Related Articles

    • Unfinished Rides

      See the Rides topic to learn how to prepare rides for this report. Unfinished is a ride when a unit left a beginning-ride geofence and after a while entered a beginning-ride geofence again. This can be the same geofence (if circle rides are not ...

    • Usage

      While Tracking Online Geofences can be displayed on the map (the ones that have flags in the panel 'Geofences' are shown). That simplifies the visual perception of the map and enriches it. Different regions can be selected by different colors and you ...

    • Usage of Drivers

      While Tracking Online The name of the driver is displayed (if available) in unit's tooltip and in extended unit information. To activate this option, check Driver in User Settings. The photo and phone number is also displayed if available. Besides, ...

    • Tables

      he following tables (for units and unit groups) can be added to a report:                                                                                       Table Parameters Intervals Filtration Account Tree (for resource) Chat Check Points ...

    • Tracks on Map

      The routes traveled by a unit in a chosen period of time can be shown on the map. To do this, choose in the report's template dialog one of the options — Trip routes, All messages on map or Colored trip routes. These options are similar but a bit ...