Page 1 of 1

GUIDE: Trip Definitions

Posted: Fri Mar 28, 2014 4:23 pm
by johan
Note: for an updated version of this and other articles, we recommend you to check our knowledge base here

Trip Definition

Set any input from the device (e.g. Ignition) or a Device Mapper Script to define what is a trip and what is idle.


1. Open "Device Mapper" from the Admin menu in VehicleTracker.

2. Under "Trip Definition" you can select how trip and idle is defined.

To let GpsGate automatically determine when the vehicle is moving or idle select "GPS movement". This is the default, and has been the only option in GpsGate until now.

To let an input from the GPS tracker determine if the vehicle is moving or not, select "Device Input". This can typically be Ignition or a motion detection input on the device. True means "trip", False means "idle".

You can also create a Device Mapper Script, which returns a boolean variable, and select it as Trip Defintion. First create the script, then select it as "Device Input". In this way you can create more complex algorithms for what is a trip and what is idle. More about Device Mapper Scripting here:

Minimum Idle Time defines the minimum time a vehicle needs to be idle before a idle spot is created. Default 2 minutes.


All features in GpsGate which uses trips and idle spots will now consider this feature, e.g reports and tracks drawn o the map.

View Trips rather than whole day Tracks.

Trip View feature, offers a practical and visual way to observe individual trips on the map.

Change historical data

When you change Trip Definition for a Device Type, you need to reprocess tracks for affected users for the change to take effect on historical data.

To reprocess old track data use the "Developer Tools".
(Make sure the "Developer Tools" plugin is up to date. Update from

Same types of devices with different Trip Definitions?

You can create new Device Types under SiteAdmin -> Devices -> Types


If you want to have SiteAdmin and a VehicleTracker application open at the same time, use two types of browsers. Firefox + Chrome.


GpsGate Support

RE: GUIDE: Trip Definitions

Posted: Mon Mar 31, 2014 7:27 am
by Alon
Will you consider differentiate between 'vehicle idle' and 'driver idle'?
Vehicle's idle is when IGN (or other signal by your choice) is ON but the vehicle does not move (with any limitation of you need, like speed above 5kph, etc.). When IGN is OFF the vehicle is neither RUN or IDLE. This will be used to report fuel waste.
Driver's idle is anytime during a working hours (or from first ignition to last off) the driver does not drive (doesn't matter if vehicle is in idle or not, per my explanation above). This will be used for resources (drivers) use improvements.

I hope it makes sense...

RE: GUIDE: Trip Definitions

Posted: Mon Mar 31, 2014 10:52 am
by johan
You can always create more specialized reports which consider more inputs.


GpsGate Support

RE: GUIDE: Trip Definitions

Posted: Sun Apr 26, 2015 5:10 am
by piter197
Hi Support,

Instead of using input in device to define trip, can we use Geofence?
Or any kind work around to achieve this?

Thank you.

Best Regards,

RE: GUIDE: Trip Definitions

Posted: Sun Apr 26, 2015 4:04 pm
by johan
Do something with Event Rules + EV100x report (or customize them).

The trips you see in TR100x reports can not be defined using geofences.


GpsGate Support

RE: GUIDE: Trip Definitions

Posted: Sun Apr 26, 2015 8:31 pm
by ggsgeek
We have done very complicated and advanced Trip Report using Event Rules and Report Data Provider. I would advise considering that path if your Trip Report requires advanced data. Event Rule can be setup to define a Trip Life cycle.

Re: GUIDE: Trip Definitions

Posted: Wed Mar 28, 2018 5:55 pm
by bertagnan
using trip definition by input (e.g. ignition) is not working in the following case:

while it looks to be working fine in this condition:

It is like if the system is considering the idleing only between two off, while between and off and on the input has remained indeed off.

Any workaround to solve this?

Edit: We checked this option:

Extended idle state
Idle state is extended by one point by including the first point of a trip

which we didn't really understand the meaning and it looks now it is working perfectly taking also into account the "fat point" filtering. Please advice if you see anything wrong.