Data Connector data dictionary

Explore every table and column in the Data Connector, with a clear meaning for each one.

Note: The Geotab Data Connector is a paid app available via the Marketplace for an additional cost. See the Apps in Marketplace help article to learn how to manage paid apps.

The Geotab Data Connector is a tool designed for fleet managers to import curated data sourced from their own fleets into their preferred BI or visualization tool without manually running MyGeotab reports. The topics in this article define the columns available in each data asset.

To connect your BI tool, see Connecting your BI tool. To see how the tables are used in ready-made dashboards, see Data Connector templates.

Data availability by rate plan

Review which Data Connector columns your rate plan includes and how far back your data goes.

Depending on your device's rate plan, some columns may or may not be available. The following table gives a general overview of feature availability per plan. For a comprehensive overview of all rate plan features, see Rate plans.


Table and column group	Base	Regulatory	Pro	ProPlus	GO Plan
Table: Vehicle KPI	Partial	Partial	Yes	Yes	Yes
Utilization columns (e.g. Driving, Idling, Number of Trips)	Yes	Yes	Yes	Yes	Yes
Engine-status related columns (e.g. Fuel and Odometer)	No	No	Yes	Yes	Yes
Fault-related columns	No	No	Yes	Yes	Yes
Table: Latest Vehicle Metadata	Partial	Partial	Yes	Yes	Yes
Engine-status related columns (e.g. Fuel and Odometer)	No	No	Yes	Yes	Yes
Fault-related columns	No	No	Yes	Yes	Yes
Table: Vehicle Groups	Yes	Yes	Yes	Yes	Yes
Table: Safety Predictive Analytics and Benchmarks	Yes*	Yes*	Yes	Yes	Yes
Tables: Maintenance Insights	No	No	Yes	Yes

* Detected collisions will be unavailable on these rate plans.

Historical data

Historical data (KPI) is provided from January 1, 2023 onward. Some databases may have limited historical data availability, including but not limited to their tenure or active device plans with Geotab. For Safety Benchmarks and Maintenance Insights, historical data is also provided from January 1, 2023 onward.

Data assumptions

Learn how permissions, time zones, VINs, and units affect the data you see in the Data Connector.

Viewing permission: Users can only view data and rows that they have permission to access in MyGeotab.
- When you change a permission setting in MyGeotab, it can take up to 10 minutes for the change to be reflected in the Geotab Data Connector.
- When you change a device's group membership in MyGeotab, it can take up to 1 hour for the new group membership to be reflected in the Geotab Data Connector.
- Currently, MyGeotab's fine-grain data clearances for specific metrics (such as fuel and engine measurements) are not reflected in the corresponding metrics in the Data Connector. Users can access all metrics listed in the data dictionary for the devices they have permission to view.
Time zone consideration:
- For Vehicle KPI tables: Data is aggregated on a local-time basis, based on the time zone set for each device in MyGeotab. For devices with no specified time zone, the default time zone is America/New_York (UTC-4 during daylight saving time, otherwise UTC-5).
- For Driver KPI tables: Data is aggregated on a local-time basis, based on the time zone set for each user in MyGeotab. For users with no specified time zone, the default time zone is America/New_York (UTC-4 during daylight saving time, otherwise UTC-5).
- For Safety Benchmarks tables: Data is aggregated on a daily basis, based on UTC date.
Vehicle identification: Vehicle Identification Number (VIN) is decoded from the engine on a best-effort basis. If the engine-decoded VIN is not available, the user-entered VIN from the MyGeotab asset page may be used and displayed. Vehicle characteristics derived from the VIN are also limited by the validity of the decoded VIN and the availability of the VIN decoding rule.
Utilization metrics: Utilization metrics such as distance, total engine hours, drive time, idle time, and trip counts are calculated from the MyGeotab trip history. The aggregation is based on the trip start time.
Fuel and energy-related metrics: Fuel-related metrics such as fuel and energy distance, total fuel used, and idle fuel used are calculated on a trip-start-time basis.
- In the hourly aggregate view, if a vehicle has a trip that starts at 2:15 PM and ends at 5:07 PM, fuel-related metrics may be null or 0 for the 2:00 PM to 4:00 PM time range. For the 5:00 PM reading, the fuel-related metrics for the entire trip are displayed.
Units: Metric units are used, unless otherwise indicated.

Vocation types

Review the vocation types that Geotab assigns to each vehicle.

Geotab uses a patented machine learning algorithm to determine the vocation (purpose) of each vehicle based on its collected data. Fleet managers can use this information for Origin/Destination analysis to see which types of jobs their vehicles perform.

The following table lists the vocation types and their descriptions.


Vocation Name	Description
Long Haul	The vehicle has a very large range of activity and typically does not rest in the same location. The vehicle is also neither hub-and-spoke nor door-to-door.
Regional	The vehicle has a wide range of activity, over the 150-air-mile threshold for short-haul exemption, but tends to rest in the same location often. The vehicle is also neither hub-and-spoke nor door-to-door.
Local	The vehicle's range of activity is below 150-air-miles, and thus qualifies for the short-haul exemption under Hours of Service Regulations. In addition, the vehicle does not exhibit behavior in line with other vocations, such as hub-and-spoke and door-to-door.
Door to Door	The vehicle makes significantly more stops than most per work day, but also tends to spend very little time per stop.
Hub and Spoke	The vehicle spends many of its work days making multiple round trips from a singular location (a centralized hub). Typically, the vehicle averages over one round trip per working day, with these round trips accounting for the majority of its total mileage.

Vehicle KPI tables

Review the Vehicle KPI tables and what each column means.

The Vehicle KPI tables provide an aggregated summary at an asset level. Based on the selected time aggregation level (daily or monthly), each row provides a summary for each asset. Data is available from January 1, 2023 onward.

Note:

Fuel and EV energy used data is only available from July 2023 onward.

Aggregation level:

By time: Daily and Monthly, based on the device-designated time zone (configured in MyGeotab)
By entity: Asset ID

Refresh frequency: Hourly.

Table names:

VehicleKpi_Daily
VehicleKpi_Monthly

VehicleKpi_Daily


Column	Type	Description
`DeviceId`	STRING	The id of the telematics device, as designated on MyGeotab.
`Local_Date`	DATE	The local date of the day for the displayed data. The local timezone is defined in MyGeotab.
`TimeZoneId`	STRING	The timezone id used to capture the boundaries for the local date, for the device.
`SerialNo`	STRING	The serial number of the telematics device that was last connected to the DeviceId for the given local date.
`Vin`	STRING	The id for the vehicle (Vehicle Identification Number) that was last connected to the telematics device for the given local date.
`MinOdometer_Km`	FLOAT	The lowest value for the odometer (in km) measured for the specified VIN within the local date.
`MaxOdometer_Km`	FLOAT	The highest value for the odometer (in km) measured for the specified VIN within the local date.
`DriveDuration_Seconds`	FLOAT	Total time (in seconds) that the DeviceId was actively in a trip, measured for trips that started within the local date.
`IdleDuration_Seconds`	FLOAT	Total time (in seconds) that the DeviceId was idling measured for trips that started within the local date. Individual trip idling time accrues when speed is 0 and ignition is on, and accounts for the beginning of the trip to the beginning of the next trip.
`TotalEngine_Hours`	FLOAT	Total time (in hours) that the DeviceId's vehicle engine was on for all trips that began within the local date. Derived from DriveDuration + IdleDuration.
`Distance_Km`	FLOAT	Total distance (in km) that the DeviceId has driven, measured within the local date by GPS position changes or odometer changes.
`Trip_Count`	INTEGER	The number of trips for the DeviceId that began within the local date.
`LatestLongitude`	FLOAT	The last valid GPS longitude measured for the DeviceId within the local date.
`LatestLatitude`	FLOAT	The last valid GPS latitude measured for the DeviceId within the local date.
`StopDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was stopped at the end of the trip. This also includes any idling done at the end of a trip. Measured for trips that started within the local date.
`WorkDistance_Km`	FLOAT	The distance (in km) the vehicle was driven during work hours. Measured for trips that started within the local date.
`WorkDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was driven during work hours. Measured for trips that started within the local date.
`WorkStopDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was stopped during work hours. Measured for trips that started within the local date.
`AfterHours_Count`	INTEGER	Number of trips that started after work hours. Measured for trips that started within the local date.
`AfterHoursDistance_Km`	FLOAT	The distance (in km) the vehicle was driven after work hours. Measured for trips that started within the local date.
`AfterHoursDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was driven after work hours. Measured for trips that started within the local date.
`AfterHoursStopDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was stopped after work hours. Measured for trips that started within the local date.
`TotalFuel_Litres`	FLOAT	The total fuel used (in liters) for the DeviceId. Note that this field captures the total fuel used across all trips that began within this specific local date, meaning that it can capture more than a single day's worth of fuel usage when a trip ends on another day.
`IdleFuel_Litres`	FLOAT	The total fuel used (in liters) for the DeviceId while the vehicle is stationary and not moving. Note that this field captures the idle fuel used across all trips that began within this specific local date, meaning that it can capture more than a single day's worth of fuel usage when a trip ends on another day.
`EnergyUsedWhileDriving_kWh`	FLOAT	The total energy used (in kWh) for the DeviceId while the vehicle is driving. Note that this field captures the total energy used across all trips that began within this specific local date, meaning that it can capture more than a single day's worth of energy usage when a trip ends on another day.
`FuelEnergyDistance_Km (previously FuelEconomy_Distance_Km)`	FLOAT	The distance (in km) that fuel and/or energy usage was accounted for. Note that this field captures the total distance accumulated across all trips that began within this specific local date (as long as fuel and/or energy readings were available).
`UniqueVehicleFault_Count`	INTEGER	The number of unique engine/vehicle fault codes for the DeviceId measured within the local date. Note that we currently measure faults through the OBDII and J1939 protocol, as well as custom reverse-engineered fault codes for select vehicle makes and manufacturers.
`UniqueDeviceFault_Count`	INTEGER	The number of unique fault codes for the DeviceId, originating from the telematics device itself, measured within the local date. This count includes faults such as device health and connectivity issues.
`Device_Health`	STRING	Identifies whether the telematics device is working properly and is measuring vehicle activity (GPS/Engine Status/Faults) within the local date.

VehicleKpi_Monthly


Column	Type	Description
`DeviceId`	STRING	The ID of the telematics device, as designated on MyGeotab.
`Local_MonthStartDate`	DATE	The first day of the calendar month, based on the local timezone set on the DeviceId on MyGeotab.
`TimeZoneId`	STRING	The last seen timezone id for the month, used to capture the boundaries for the local dates, for the device.
`SerialNo`	STRING	The serial number of the telematics device that was last connected to the DeviceId for the given local month.
`Vin`	STRING	The Vehicle Identification Number of the vehicle that was last connected to the telematics device for the given local month.
`MinOdometer_Km`	FLOAT	The lowest value for the odometer (in km) measured for the specified VIN within the local month.
`MaxOdometer_Km`	FLOAT	The highest value for the odometer (in km) measured for the specified VIN within the local month.
`DriveDuration_Seconds`	FLOAT	Total time (in seconds) that the DeviceId was actively in operation (without idle) measured for trips that started within the local month.
`IdleDuration_Seconds`	FLOAT	Total time (in seconds) that the DeviceId was idling measured for trips that started within the local month. Individual trip idling time accrues when speed is 0 and ignition is on, and accounts for the beginning of the trip to the beginning of the next trip.
`TotalEngine_Hours`	FLOAT	Total time (in hours) that the DeviceId's vehicle engine was on for all trips that began within the local month. Derived from DriveDuration + IdleDuration.
`Distance_Km`	FLOAT	Total distance (in km) that the DeviceId has driven, measured within the local month by GPS position changes or odometer changes.
`Trip_Count`	INTEGER	The number of trips for the DeviceId that began within the local month.
`LatestLongitude`	FLOAT	The last valid GPS longitude measured for the DeviceId within the local month.
`LatestLatitude`	FLOAT	The last valid GPS latitude measured for the DeviceId within the local month.
`StopDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was stopped at the end of the trip. This also includes any idling done at the end of a trip. Measured for trips that started within the local month.
`WorkDistance_Km`	FLOAT	The distance (in km) the vehicle was driven during work hours. Measured for trips that started within the local month.
`WorkDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was driven during work hours. Measured for trips that started within the local month.
`WorkStopDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was stopped during work hours. Measured for trips that started within the local month.
`AfterHours_Count`	INTEGER	Number of trips that started after work hours. Measured for trips that started within the local month.
`AfterHoursDistance_Km`	FLOAT	The distance (in km) the vehicle was driven after work hours. Measured for trips that started within the local month.
`AfterHoursDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was driven after work hours. Measured for trips that started within the local month.
`AfterHoursStopDuration_Seconds`	FLOAT	The duration (in seconds) the vehicle was stopped after work hours. Measured for trips that started within the local month.
`TotalFuel_Litres`	FLOAT	The total fuel used (in liters) for the DeviceId. Note that this field captures the total fuel used across all trips that began within this specific local month, meaning that it can capture more than the single month's worth of fuel usage when a trip ends in another month..
`IdleFuel_Litres`	FLOAT	The total fuel used (in liters) for the DeviceId while the vehicle is stationary and not moving. Note that this field captures the idle fuel used across all trips that began within this specific local month, meaning that it can capture more than the single month's worth of fuel usage when a trip ends in another month.
`EnergyUsedWhileDriving_kWh`	FLOAT	The total energy used (in kWh) for the DeviceId while the vehicle is driving. Note that this field captures the total energy used across all trips that began within this specific local month, meaning that it can capture more than the single month's worth of fuel usage when a trip ends in another month.
`FuelEnergyDistance_Km`	FLOAT	The distance (in km) that fuel and/or energy usage was accounted for. Note that this field captures the total distance accumulated across all trips that began within this specific local month (as long as fuel and/or energy readings were available).
`UniqueVehicleFault_Count`	INTEGER	The number of unique engine/vehicle fault codes for the DeviceId measured within the local month. Note that we currently measure faults through the OBDII and J1939 protocol, as well as custom reverse-engineered fault codes for select vehicle makes/manufacturers.
`UniqueDeviceFault_Count`	INTEGER	The number of unique fault codes for the DeviceId, originating from the telematics device itself, measured within the local month. This count includes faults such as device health and connectivity issues.
`Device_Health`	STRING	Identifies whether the telematics device is working properly and is measuring vehicle activity (GPS/Engine Status/Faults) within the month.

Vehicle metadata and group tables

Review the vehicle and group tables, and what each column means.

LatestVehicleMetadata

The Vehicle Latest Metadata table provides additional context and grouping potential for the other aggregated summary tables. Each row captures metadata about the vehicle and the device, allowing a connection to other aggregated summary tables using VIN and DeviceId.

Aggregation level:

By entity: VIN and DeviceId

Refresh frequency: Hourly

Table names:

LatestVehicleMetadata

Note:

If a telematics device was associated with more than one vehicle, there can be more than one row for that device in the SerialNo column. Use the DateFrom and DateTo columns to determine which vehicle is currently assigned (when the DateTo field is the placeholder date 2050-01-01). If an active telematics device fails to associate a vehicle's VIN with the device, an extra row with no VIN is displayed in the Vehicle Latest Metadata table with a DateTo date of 2050.


Column	Type	Description
`Vin`	STRING	The Vehicle Identification Number (VIN) is a 17 character alphanumeric string for the vehicle that is connected to the telematics device. This field is null if the device is unable to read the VIN.
`DeviceName`	STRING	The name of the telematics device, as designated on MyGeotab.
`DeviceId`	STRING	The ID of the telematics device, as designated on MyGeotab.
`Device_Health`	STRING	This is a string to identify whether the telematics device is working properly and is measuring vehicle activity within the last 24 hours.
`DeviceTimeZoneId`	STRING	The timezone name that is used to convert the UTC timestamp to the local datetime.
`DeviceTimeZoneOffset`	STRING	The timezone offset associated to the `DeviceTimeZoneId` that is used to convert the UTC timestamp to the local datetime.
`SerialNo`	STRING	The serial number of the telematics device installed in the vehicle.
`DateFrom`	TIMESTAMP	The UTC timestamp for when we observed the telematics device associated to the specified VIN. If the device is disconnected and reconnected to the same VIN, this will be the latest reconnection timestamp. If the VIN is empty or null, the DateFrom date represents the first timestamp of when the telematics device was associated with the MyGeotab database.
`DateTo`	TIMESTAMP	The ending UTC timestamp for when we observed the telematics device associated to the specified VIN. If the device is disconnected and reconnected to the same vehicle VIN, this field will be updated to the latest reconnection instance. If the VIN is empty or null, the DateTo date represents the last timestamp of when the telematics device is associated with the MyGeotab database. A DateTo date of 2050 represents indefinitely active.
`Year`	STRING	Model year of the vehicle, decoded from the VIN.
`Manufacturer`	STRING	Manufacturer of the vehicle, decoded from the VIN.
`Model`	STRING	Model of the vehicle, decoded from the VIN.
`Engine`	STRING	Engine of the vehicle, decoded from the VIN.
`FuelType`	STRING	Fuel type of the vehicle, decoded from the VIN.
`WeightClass`	STRING	Weight class of the vehicle, decoded from the VIN.
`VocationName`	STRING	Geotab's patented, machine-learning label for the driving behavior/pattern of the vehicle.
`VocationDescription`	STRING	Geotab's patented, machine-learning label for the driving behavior/pattern of the vehicle. This column is the detailed description about the vocation assigned.
`DevicePlans`	STRING	The most-recent, comma-separated list of device plans active on the device.
`LastOdometer_DateTime`	TIMESTAMP	The UTC timestamp for the last valid measured odometer reading.
`LastOdometer_Km`	FLOAT	The most recent odometer value for the vehicle, in kilometres. This is sourced directly from device odometer readings when available, and estimated from trip distance data where direct readings are not supported by the vehicle or device configuration.
`LastEngine_Hours`	FLOAT	The most recent engine hours value for the vehicle. This is sourced directly from device engine status readings when available, and estimated from trip duration data where direct readings are not supported by the vehicle or device configuration.
`LastEngineStatus_DateTime`	TIMESTAMP	The UTC timestamp for the last measured engine status reading.
`LastGps_DateTime`	TIMESTAMP	The UTC timestamp for the last measured GPS reading.
`LastGps_Latitude`	FLOAT	The latitude for the last valid measured GPS reading.
`LastGps_Longitude`	FLOAT	The longitude for the last valid measured GPS reading.
`LastGps_Speed`	INTEGER	The speed (in km/h) for the last valid measured GPS reading.
`Last24Hours_ActiveVehicleFaults`	INTEGER	The number of unique engine/vehicle fault codes measured within the last 24 hours. Note that we currently measure faults through the OBDII and J1939 protocol, as well as custom reverse-engineered fault codes for select vehicle makes/manufacturers.
`Last24Hours_ActiveDeviceFaults`	INTEGER	The number of unique fault codes, originating from the telematics device itself, measured within the last 24 hours. This count includes faults such as device health and connectivity issues.

DeviceGroups

The Vehicle Groups table provides the mapping from the DeviceId and SerialNo to the MyGeotab groups that the device belongs to. For each device that is a member of a child group, or a member of multiple groups, this table has one row for every group that the device is connected to.

Aggregation level:

By entity: DeviceId

Refresh frequency: Daily

Table names:

DeviceGroups

Note:

For complex group trees in MyGeotab, up to 100 layers of depth are currently supported.


Column	Type	Description
`SerialNo`	STRING	The serial number of the telematics device installed in the vehicle.
`DeviceId`	STRING	The ID of the telematics device, as designated in MyGeotab.
`GroupId`	STRING	The group ID (in MyGeotab) that the device belongs to.
`ImmediateGroup`	BOOLEAN	This field is True if the telematics device is explicitly part of this group. This field is False if the telematics device inherited the group membership as a parent group.
`GroupName`	STRING	The name of the group (in MyGeotab) that the device belongs to.

Driver KPI tables

Review the Driver KPI tables and what each column means.

The Driver KPI tables provide an aggregated summary at a driver level. Based on the selected time aggregation level (daily or monthly), each row provides a summary for each driver. For drivers who accumulate driving activity across different assets, the Driver KPI tables include all driving activity for the driver ID in the same aggregate. Data is available from January 1, 2023 onward.

Aggregation level:

By time: Daily and Monthly, based on the user-designated time zone (configured in MyGeotab)
By entity: Driver ID

Refresh frequency: Hourly.

Table names:

DriverKpi_Daily
DriverKpi_Monthly

DriverKpi_Daily


Column	Type	Description
`DriverId`	STRING	The ID of the telematics driver, as designated on MyGeotab.
`Local_Date`	DATE	The local date of the day for the displayed data. The local timezone is defined in MyGeotab.
`TimeZoneId`	STRING	The timezone ID used to capture the boundaries for the local date, for the driver.
`DriveDuration_Seconds`	FLOAT	Total time (in seconds) that the DriverId was actively in operation (without idle) measured within the local date.
`IdleDuration_Seconds`	FLOAT	Total time (in seconds) that the DriverId was idling measured within the local date.
`Distance_Km`	FLOAT	Total distance (in km) that the DriverId has driven, measured within the local date by GPS position changes or odometer changes.
`Trip_Count`	INTEGER	The number of trips for the DriverId that began within the local date.
`LatestLongitude`	FLOAT	The last valid GPS longitude measured for the DriverId within the local date.
`LatestLatitude`	FLOAT	The last valid GPS latitude measured for the DriverId within the local date.
`StopDuration_Seconds`	FLOAT	The duration (in seconds) the driver was stopped at the end of the trip. This also includes any idling done at the end of a trip. Measured for trips that started within the local date.
`WorkDistance_Km`	FLOAT	The distance (in km) the driver drove during work hours. Measured for trips that started within the local date.
`WorkDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the driver drove during work hours. Measured for trips that started within the local date.
`WorkStopDuration_Seconds`	FLOAT	The duration (in seconds) the driver was stopped during work hours. Measured for trips that started within the local date.
`AfterHours_Count`	INTEGER	Number of trips that started after work hours. Measured for trips that started within the local date.
`AfterHoursDistance_Km`	FLOAT	The distance (in km) the driver drove after work hours. Measured for trips that started within the local date.
`AfterHoursDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the driver drove after work hours. Measured for trips that started within the local date
`AfterHoursStopDuration_Seconds`	FLOAT	The duration (in seconds) the driver was stopped after work hours. Measured for trips that started within the local date.

DriverKpi_Monthly


Column	Type	Description
`DriverId`	STRING	The ID of the telematics driver, as designated on MyGeotab.
`Local_MonthStartDate`	DATE	The first day of the calendar month, based on the local timezone set on the DriverId on MyGeotab.
`TimeZoneId`	STRING	The last seen timezone ID for the month, used to capture the boundaries for the local dates, for the driver.
`DriveDuration_Seconds`	FLOAT	Total time (in seconds) that the DriverId was actively in operation (without idle) measured within the local month.
`IdleDuration_Seconds`	FLOAT	Total time (in seconds) that the DriverId was idling measured within the local month.
`Distance_Km`	FLOAT	Total distance (in km) that the DriverId has driven, measured within the local month by GPS position changes or odometer changes.
`Trip_Count`	INTEGER	The number of trips for the DriverId that began within the local month.
`LatestLongitude`	FLOAT	The last valid GPS longitude measured for the DriverId within the local month.
`LatestLatitude`	FLOAT	The last valid GPS latitude measured for the DriverId within the local month.
`StopDuration_Seconds`	FLOAT	The duration (in seconds) the driver was stopped at the end of the trip. This also includes any idling done at the end of a trip. Measured for trips that started within the local month.
`WorkDistance_Km`	FLOAT	The distance (in km) the driver drove during work hours. Measured for trips that started within the local month.
`WorkDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the driver drove during work hours. Measured for trips that started within the local month.
`WorkStopDuration_Seconds`	FLOAT	The duration (in seconds) the driver was stopped during work hours. Measured for trips that started within the local month.
`AfterHours_Count`	INTEGER	Number of trips that started after work hours. Measured for trips that started within the local month.
`AfterHoursDistance_Km`	FLOAT	The distance (in km) the driver drove after work hours. Measured for trips that started within the local month.
`AfterHoursDrivingDuration_Seconds`	FLOAT	The duration (in seconds) the driver drove after work hours. Measured for trips that started within the local month.
`AfterHoursStopDuration_Seconds`	FLOAT	The duration (in seconds) the driver was stopped after work hours. Measured for trips that started within the local month.

Driver metadata and group tables

Review the driver metadata and driver group tables and what each column means.

LatestDriverMetadata

The Driver Latest Metadata table provides additional context and grouping potential for the other aggregated summary tables. Each row captures metadata about the driver, allowing a connection to other aggregated summary tables using DriverId.

Aggregation level:

By entity: DriverId

Refresh frequency: Hourly

Table names:

LatestDriverMetadata


Column	Type	Description
`DriverId`	STRING	The driver ID as designated on MyGeotab.
`Name`	STRING	The display name for the driver.
`FirstName`	STRING	The first name for the driver.
`LastName`	STRING	The last name for the driver.
`ActiveFrom`	TIMESTAMP	The "active from" timestamp for the driver, signalling the start of the driver's account.
`ActiveTo`	TIMESTAMP	The "active to: timestamp for the driver, signalling the termination of the driver's account.
`TimeZoneId`	STRING	The last seen timezone ID for the driver used for aggregation.
`Designation`	STRING	The designation or title of the employee, blank or null are equivalent and indicate no designation is assigned

DriverGroups

The Driver Groups table provides the mapping from the DriverId to the MyGeotab groups that the driver belongs to. For each driver who is a member of a child group, or a member of multiple groups, this table has one row for every group that the driver is connected to.

Aggregation level:

By entity: DriverId

Refresh frequency: Daily

Table names:

DriverGroups

Note:

For complex group trees in MyGeotab, up to 100 layers of depth are currently supported.


Column	Type	Description
`DriverId`	STRING	The driver ID as designated on MyGeotab.
`GroupId`	STRING	The group ID (in MyGeotab) that the driver belongs to.
`ImmediateGroup`	BOOLEAN	This field is True if the driver is explicitly part of this group. This field is False if the driver inherited the group membership as a parent group.
`GroupName`	STRING	The name of the group (in MyGeotab) that the driver belongs to.

Predictive safety tables

Review the predictive safety tables and what each column means.

Predictive safety analytics monitors driving behavior and focuses on driving events such as sudden acceleration, hard braking, sharp turns, and driving above the speed limit. Vehicles with similar driving behavior are grouped together and analyzed to calculate the rate of collision within each group. Likewise, drivers with similar driving behavior are grouped together and analyzed to calculate the rate of collision within each group. Benchmarking compares a fleet's safety performance with similar fleets in the system, allowing you to see how a fleet compares to industry standards.

Aggregation level: Daily

Refresh frequency: Daily at approximately 11:30 PM UTC, with a lag of up to 2 days

Table names:

FleetSafety_Daily
VehicleSafety_Daily
DriverSafety_Daily

FleetSafety_Daily


Column Name	Type	Description
`Date`	DATE	The UTC date for the displayed data.
`TotalCollisionCount_Daily`	INTEGER	Number of collisions detected by Geotab's ML model on that day for the whole fleet.
`ClusterDescription`	STRING	Description of the peer group that was used to benchmark your fleet.
`FleetsInCluster`	INTEGER	Number of fleets in your fleet's peer group.
`VehiclesInCluster`	INTEGER	Number of vehicles in your fleet's peer group.
`HarshAcceleration_Rank`	FLOAT	The rank (percentile) of the fleet's harsh acceleration performance. The higher this number, the better you rank compared to other fleets in your peer group.
`HarshBraking_Rank`	FLOAT	The rank (percentile) of the fleet's harsh braking performance. The higher this number, the better you rank compared to other fleets in your peer group.
`HarshCornering_Rank`	FLOAT	The rank (percentile) of the fleet's harsh cornering performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Seatbelt_Rank`	FLOAT	The rank (percentile) of the fleet's seatbelt performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Speeding_Rank`	FLOAT	The rank (percentile) of the fleet's speeding performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Safety_Rank`	FLOAT	The rank (percentile) of the fleet's overall safety performance. The higher this number, the better you rank compared to other fleets in your peer group.
`PredictedCollisionsPer1MillionKm`	FLOAT	Predicted number of collisions for the whole fleet for the next 1 million kilometers.
`PredictedCollisionsPer1MillionKm_Benchmark`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the fleet's peer group. It is equal to the average (mean) of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionKm_PeerGroupleader`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the fleet's peer group. It is equal to the 20th percentile of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionM`	FLOAT	Predicted number of collisions for the whole fleet for the next 1 million miles.
`PredictedCollisionsPer1MillionM_Benchmark`	FLOAT	Benchmark for PredictedCollisionsPer1MillionM among the fleet's peer group. It is equal to the average (mean) of PredictedCollisionsPer1MillionM within the peer group.
`PredictedCollisionsPer1MillionM_PeerGroupleader`	FLOAT	Benchmark for PredictedCollisionsPer1MillionM among the fleet's peer group. It is equal to the 20th percentile of PredictedCollisionsPer1MillionM within the peer group.

VehicleSafety_Daily


Column Name	Type	Description
`UTC_Date`	DATE	The UTC date for the displayed data.
`DeviceId`	STRING	The ID of the telematics device, as designated on MyGeotab.
`SerialNo`	STRING	The serial number of the telematics device installed in the vehicle.
`Vin`	STRING	The Vehicle Identification Number (VIN) is a 17-character alphanumeric string for the vehicle that is connected to the telematics device. This field is null if the device is unable to read the VIN.
`HarshAcceleration_Rank`	FLOAT	The rank (percentile) of the device's harsh acceleration performance. The higher this number, the better you rank compared to other fleets in your peer group.
`HarshBraking_Rank`	FLOAT	The rank (percentile) of the device's harsh braking performance. The higher this number, the better you rank compared to other fleets in your peer group.
`HarshCornering_Rank`	FLOAT	The rank (percentile) of the device's harsh cornering performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Seatbelt_Rank`	FLOAT	The rank (percentile) of the device's seatbelt performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Speeding_Rank`	FLOAT	The rank (percentile) of the device's speeding performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Safety_Rank`	FLOAT	The rank (percentile) of the device's overall safety performance. The higher this number, the better you rank compared to other fleets in your peer group.
`PredictedCollisionsPer1MillionKm`	FLOAT	Predicted number of collisions for the vehicle for the next 1 million kilometers.
`PredictedCollisionsPer1MillionKm_Benchmark`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the vehicle's peer group. It is equal to the average (mean) of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionKm_PeerGroupleader`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the vehicle's peer group. It is equal to the 20th percentile of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionM`	FLOAT	Predicted number of collisions for the vehicle for the next 1 million miles.
`PredictedCollisionsPer1MillionM_Benchmark`	FLOAT	Benchmark for PredictedCollisionsPer1MillionM among the vehicle's peer group. It is equal to the average (mean) of PredictedCollisionsPer1MillionM within the peer group.
`PredictedCollisionsPer1MillionM_PeerGroupleader`	FLOAT	Benchmark for PredictedCollisionsPer1MillionM among the vehicle's peer group. It is equal to the 20th percentile of PredictedCollisionsPer1MillionM within the peer group.
`CollisionProbabilityPer100ThousandKm`	FLOAT	Predicted probability of the vehicle having at least one collision, for the next 100,000 kilometers.
`CollisionProbabilityPer100ThousandKm_Benchmark`	FLOAT	Benchmark for CollisionProbabilityPer100ThousandKm among the vehicle's peer group. It is equal to the average (mean) of CollisionProbabilityPer100ThousandKm within the peer group.
`CollisionProbabilityPer100ThousandKm_PeerGroupleader`	FLOAT	Best performer for CollisionProbabilityPer100ThousandKm among the vehicle's peer group. It is equal to the 20-th percentile of PredictedProbability_KM within the peer group.
`CollisionProbabilityPer100ThousandM`	FLOAT	Predicted probability of the vehicle having at least one collision, for the next 100,000 miles
`CollisionProbabilityPer100ThousandM_Benchmark`	FLOAT	Benchmark for CollisionProbabilityPer100ThousandM among the vehicle's peer group. It is equal to the average (mean) of CollisionProbabilityPer100ThousandM within the peer group.
`CollisionProbabilityPer100ThousandM_PeerGroupleader`	FLOAT	Best performer for CollisionProbabilityPer100ThousandM among the vehicle's peer group. It is equal to the 20th percentile of CollisionProbabilityPer100ThousandM within the peer group.

DriverSafety_Daily


Column	Type	Description
`UTC_Date`	DATE	The UTC date for the displayed data.
`DriverId`	STRING	The ID of the Driver.
`HarshAcceleration_Rank`	FLOAT	The rank (percentile) of the driver's harsh acceleration performance. The higher this number, the better you rank compared to other fleets in your peer group.
`HarshBraking_Rank`	FLOAT	The rank (percentile) of the driver's harsh braking performance. The higher this number, the better you rank compared to other fleets in your peer group.
`HarshCornering_Rank`	FLOAT	The rank (percentile) of the driver's harsh cornering performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Seatbelt_Rank`	FLOAT	The rank (percentile) of the driver's seatbelt performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Speeding_Rank`	FLOAT	The rank (percentile) of the driver's speeding performance. The higher this number, the better you rank compared to other fleets in your peer group.
`Safety_Rank`	FLOAT	The rank (percentile) of the driver's overall safety performance. The higher this number, the better you rank compared to other fleets in your peer group.
`PredictedCollisionsPer1MillionKm`	FLOAT	Predicted number of collisions for the driver for the next 1 million kilometers.
`PredictedCollisionsPer1MillionKm_Benchmark`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the driver's peer group. It is equal to the average of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionKm_PeerGroupleader`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the driver's peer group. It is equal to the 20-th percentile of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionM`	FLOAT	Benchmark for PredictedCollisionsPer1MillionKm among the driver's peer group. It is equal to the 20th percentile of PredictedCollisionsPer1MillionKm within the peer group.
`PredictedCollisionsPer1MillionM_Benchmark`	FLOAT	Predicted number of collisions for the driver for the next 1 million miles.
`PredictedCollisionsPer1MillionM_PeerGroupleader`	FLOAT	Benchmark for PredictedCollisionsPer1MillionM among the driver's peer group. It is equal to the average (mean) of PredictedCollisionsPer1MillionM within the peer group.
`CollisionProbabilityPer100ThousandKm`	FLOAT	Predicted probability of the driver having at least one collision, for the next 100,000 kilometers.
`CollisionProbabilityPer100ThousandKm_Benchmark`	FLOAT	Benchmark for CollisionProbabilityPer100ThousandKm among the driver's peer group. It is equal to the average (mean) of CollisionProbabilityPer100ThousandKm within the peer group.
`CollisionProbabilityPer100ThousandKm_PeerGroupleader`	FLOAT	Best performer for CollisionProbabilityPer100ThousandKm among the driver's peer group. It is equal to the 20-th percentile of PredictedProbability_KM within the peer group.
`CollisionProbabilityPer100ThousandM`	FLOAT	Predicted probability of the driver having at least 1 collision, for the next 100,000 miles.
`CollisionProbabilityPer100ThousandM_Benchmark`	FLOAT	Benchmark for CollisionProbabilityPer100ThousandM among the driver's peer group. It is equal to the average (mean) of CollisionProbabilityPer100ThousandM within the peer group.
`CollisionProbabilityPer100ThousandM_PeerGroupleader`	FLOAT	Best performer for CollisionProbabilityPer100ThousandM among the driver's peer group. It is equal to the 20th percentile of CollisionProbabilityPer100ThousandM within the peer group.

Fault monitoring tables

Review the fault monitoring tables and what each column means.

Geotab gathers fault codes from various sources and stores them in the FaultData entity within MyGeotab. There are two primary sources for these codes:

Diagnostic Trouble Codes (DTCs): These codes signal potential vehicle problems. While some are legally mandated, others are manufacturer-specific. Common DTC standards include OBDII for light and medium-duty vehicles and J1939 for heavy-duty vehicles.
GoDevice-specific faults: These codes flag issues with the GO device itself, or they may combine vehicle data to generate a fault code based on device logic.

Fault monitoring helps you understand whether a fault is persistent, the lifecycle of a fault, and the history of faults on a vehicle. These tables provide a clearer, more organized view of fault data, making it easier to:

Identify persistent faults: By combining instances of faults and applying logic to determine that a fault cycle has ended, you can see how long a fault has persisted and which faults are currently present in the vehicle.
Troubleshoot efficiently: The tables provide a concise summary of fault information, so you can quickly diagnose issues and take corrective action.
Understand vehicle history: Fault lifecycles show not only persistent faults but also a clear historical record of the vehicle's issues.
Analyze fleet-wide trends: Improved data organization helps you identify patterns and trends in fault data across your entire fleet, leading to better maintenance planning and reduced downtime.

Fault monitoring provides the data you need to visualize faults and how long the vehicle has been driving with each issue, in both mileage and time. Use AnyStatesDateTimeFirstSeen and AnyStatesDateTimeLastSeen as a starting point, because they represent the entire fault cycle. Use the IsPersistentCycle column to determine which fault codes Geotab still considers active.

Columns with Pending, Active, and Confirmed faults provide more detailed information about the lifecycle of the DTC.

Aggregation level: Daily

Refresh frequency: Hourly

Table names:

FaultMonitoring
FaultMonitoring_Daily

FaultMonitoring


Column Name	Column Description
`DeviceId`	Unique identifier of an asset in the MyGeotab database.
`SourceId`	Unique identifier of the fault source in the MyGeotab database.
`FaultCode`	Decoded Fault Code.
`FaultCodeDescription`	Description of the Fault Code
`DiagnosticType`	Type of the FaultCode (e.g. OBDII, SPN, PID/SID etc.)
`FailureMode`	FailureMode of the FaultCode
`FailureModeDescription`	FailureMode Description
`Controller`	Controller of the FaultCode
`ControllerDescription`	Controller Description
`Component`	Component of the FaultCode
`AnyStatesDateTimeFirstSeen`	First DTCDateTime of the DTC Cycle
`AnyStatesDateTimeLastSeen`	Last DTCDateTime of the DTC Cycle
`IsPersistentCycle`	Indication whether or not the DTC cycle is considered as persistent/on-going. If the cycle is persistent the last seen DTC is not yet set as the DTC cycle end and can still update.
`PendingDateTimeFirstSeen`	DateTime of the first Pending DTC.
`PendingOdometerFirstSeen`	Odometer value of the first Pending DTC.
`PendingDateTimeLastSeen`	DateTime of the last Pending DTC.
`PendingOdometerLastSeen`	Odometer value of the last Pending DTC.
`PendingDuration`	Duration where the DTC cycle is in the pending state.
`PendingDistance`	Distance driven with DTC cycle in pending state.
`PendingCount`	Count of all Pending DTCs inside the cycle.
`ActiveDateTimeFirstSeen`	DateTime of the first Active DTC.
`ActiveOdometerFirstSeen`	Odometer value of the first Active DTC.
`ActiveDateTimeLastSeen`	DateTime of the last Active DTC.
`ActiveOdometerLastSeen`	Odometer value of the last Active DTC.
`ActiveDuration`	Duration where the DTC cycle is in the active state.
`ActiveDistance`	Distance driven with DTC cycle in active state.
`ActiveCount`	Count of all Active DTCs inside the cycle.
`ConfirmedDateTimeFirstSeen`	DateTime of the first Confirmed DTC.
`ConfirmedOdometerFirstSeen`	Odometer value of the first Confirmed DTC.
`ConfirmedDateTimeLastSeen`	DateTime of the last Confirmed DTC.
`ConfirmedOdometerLastSeen`	Odometer value of the last Confirmed DTC.
`ConfirmedDuration`	Duration where the DTC cycle is in the confirmed state.
`ConfirmedDistance`	Distance driven with DTC cycle in confirmed state.
`ConfirmedCount`	Count of all Confirmed DTCs inside the cycle.

FaultMonitoring_Daily

Provides the daily log of every fault cycle, between the times of AnyStatesDateTimeFirstSeen and AnyStatesDateTimeLastSeen.


Column Name	Column Description
`Local_Date`	Local date of the record in the timezone of the device/asset
`DeviceId`	Unique identifier of an asset in the MyGeotab database.
`SourceId`	Unique identifier of the fault source in the MyGeotab database.
`FaultCode`	Decoded Fault Code.
`FaultCodeDescription`	Description of the Fault Code
`DiagnosticType`	Type of the FaultCode (e.g. OBDII, SPN, PID/SID etc.)
`FailureMode`	FailureMode of the FaultCode
`FailureModeDescription`	FailureMode Description
`Controller`	Controller of the FaultCode
`ControllerDescription`	Controller Description
`Component`	Component of the FaultCode

Fault cycles

Learn how Geotab groups ignition cycles into fault cycles.

Fault cycles group ignition cycles and fault states together so you can track how long a fault has persisted on a vehicle.

Aggregate fault state cycles

Fault cycles are defined by combining consecutive ignition cycles and faults with the same state. The green boxes represent ignition cycles without a detected fault. All other colors represent a series of consecutive ignition cycles with faults in the corresponding state.

Ignition cycles grouped into two fault state cycles, Id 1 and Id 2.

Aggregate fault cycles

Geotab combines consecutive fault state cycles for every vehicle to form a fault cycle. The end of the cycle is defined by ignition cycles where no fault is recorded. If enough consecutive ignition cycles without the fault are detected, Geotab defines the cycle as not persistent.

Any new fault of the same type on the same vehicle opens a new cycle with a new ID.

Consecutive fault state cycles combined into a single aggregate fault cycle.

Visualizing fault monitoring

The following diagram shows how individual ignition cycle states in the input table are combined into aggregated fault cycles in the output table.

Input table of ignition cycle states transformed into an output table of aggregated fault cycles.

For the full list of fault monitoring data fields, see Fault monitoring tables.

Risk of breakdown (Beta)

Review the beta risk of breakdown model for OBD-II faults.

Important:

This data is currently under development and is a beta feature. It may change at any time and could produce unexpected results.

The risk of breakdown model correlates a fault's lifecycle with towing events. It calculates the percentage chance that a vehicle with an OBD-II fault will end in a towing event.

OBD-II fault lifecycle stages leading to a risk of breakdown score: cycle, tow, and downtime.

Fault severity levels

Geotab groups fault severity based on the relative chance of a tow:


Severity	Chance of tow
Low	0-4%
Medium	4-8.5%
High	8.5-15%
Critical	More than 15%

Exception event tables

Review the exception event tables and what each column means.

Exception events are triggered by rules configured in MyGeotab, which monitor driving conditions such as speeding, harsh braking, zone stops, and other custom or stock rule types. The Exception Events tables aggregate exception event data on a daily basis, capturing each event's count, total duration, and total distance at both the asset and driver level.

Aggregation level:

By time: Daily, based on the device- or driver-designated time zone (configured in MyGeotab)
By entity: Device ID (asset-based) or Driver ID (driver-based)

Refresh frequency: Hourly for data from the most recent 30 days, and daily for data beyond the most recent 30 days, up to 180 days.

Table names:

DeviceExceptionEvent_Daily
DriverExceptionEvent_Daily

DeviceExceptionEvent_Daily

Provides a daily aggregate of exception rule events at the device level. Each row captures the count, duration, and distance for a specific device and exception rule combination within a local date.


Column	Type	Description
`DeviceId`	STRING	The id of the telematics device, as designated on MyGeotab
`Local_Date`	DATE	The local date of the day for the displayed data. The local timezone is defined in MyGeotab
`TimeZoneId`	STRING	The timezone id used to capture the boundaries for the local date, for the device
`RuleId`	STRING	The unique id representing the rule that triggered the Exception Event
`Rulename`	STRING	The name of the rule
`Basetype`	STRING	The exception rule base type of the rule; either Custom, Stock or ZoneStop
`State`	STRING	Denotes the state of the Exception Event (Valid, Starred, CoachingCompleted, Positive Recognition, SavedFromLater, DriverRecognition, Dismissed, NeedsCoaching, MarkedForCoaching etc.)
`Distance_Km`	FLOAT	The distance (in km) traveled by the vehicle since the start of the Exception Event
`Duration_Seconds`	FLOAT	The total duration (in seconds) of the Exception Event since it started. This could exceed 24 hours is the Exception Event continuously expanded over several days
`Event_Count`	INTEGER	The count of ExceptionEvents that happened between the ActiveFrom and ActiveTo timestamps
`FirstActiveFrom`	TIMESTAMP	The date and time when the first ExceptionEvent started
`FirstActiveTo`	TIMESTAMP	The date and time when the first ExceptionEvent ended
`LastActiveFrom`	TIMESTAMP	The date and time when the last ExceptionEvent started
`LastActiveTo`	TIMESTAMP	The date and time when the first ExceptionEvent ended

DriverExceptionEvent_Daily

Provides a daily aggregate of exception rule events at the driver level. Each row captures the count, duration, and distance for a specific driver and exception rule combination within a local date.


Column	Type	Description
`DriverId`	STRING	Unique id for the driver, as designated on MyGeotab
`Local_Date`	DATE	The local date of the day for the displayed data. The local timezone is defined in MyGeotab
`TimeZoneId`	STRING	The timezone id used to capture the boundaries for the local date, for the device
`RuleId`	STRING	The unique id representing the rule that triggered the Exception Event
`RuleName`	STRING	The name of the rule
`BaseType`	STRING	The exception rule base type of the rule; either Custom, Stock or ZoneStop
`State`	STRING	Denotes the state of the Exception Event (Valid, Starred, CoachingCompleted, Positive Recognition, SavedFromLater, DriverRecognition, Dismissed, NeedsCoaching, MarkedForCoaching etc.)
`Distance_Km`	FLOAT	The distance (in km) traveled by the vehicle since the start of the Exception Event
`Duration_Seconds`	FLOAT	The total duration (in seconds) of the Exception Event since it started. This could exceed 24 hours is the Exception Event continuously expanded over several days
`Event_Count`	INTEGER	The count of ExceptionEvents that happened between the ActiveFrom and ActiveTo timestamps
`FirstActiveFrom`	TIMESTAMP	The date and time when the first ExceptionEvent started
`FirstActiveTo`	TIMESTAMP	The date and time when the first ExceptionEvent ended
`LastActiveFrom`	TIMESTAMP	The date and time when the last ExceptionEvent started
`LastActiveTo`	TIMESTAMP	The date and time when the last ExceptionEvent ended

IFTA reporting tables

Review the IFTA tables and what each column means.

The International Fuel Tax Agreement (IFTA) reporting tables provide road-traversal and fuel-transaction data for IFTA reporting. DeviceJurisdictionTraversalSummary contains jurisdiction-level road traversal records. FuelTransaction contains fuel purchase records enriched with the jurisdiction in which each transaction occurred.

The IFTA reporting model uses two Geotab Data Connector assets with different row grain. These assets are intentionally separate and should not be treated as a one-to-one join.

Table names:

DeviceJurisdictionTraversalSummary
FuelTransaction

DeviceJurisdictionTraversalSummary

Aggregation level: Device ID, jurisdiction, road type, and entry time

By entity: DeviceId (asset-based)
By time: Entry time


Column	Type	Description
`UTC_Date`	DATE	The UTC date of the traversal record.
`DeviceId`	STRING	Hexadecimal identifier for the device within a MyGeotab database.
`Vin`	STRING	VIN of the vehicle, if known.
`Country`	STRING	The country where the travel occurred (for example, USA or CAN).
`Jurisdiction`	STRING	The state, province, or other jurisdiction where the travel occurred.
`RoadType`	STRING	Type of road, including off-road or a road type from OSM_Ways.
`EnterTime`	TIMESTAMP	Timestamp of the entry event for this road segment.
`ExitTime`	TIMESTAMP	Timestamp of the exit event for this road segment.
`OriginLatitude`	FLOAT	Latitude of the starting location of the road segment.
`OriginLongitude`	FLOAT	Longitude of the starting location of the road segment.
`DestinationLatitude`	FLOAT	Latitude of the destination location of the road segment.
`DestinationLongitude`	FLOAT	Longitude of the destination location of the road segment.
`EnterOdometer_Km`	FLOAT	Odometer reading upon entering the segment, in kilometres.
`ExitOdometer_Km`	FLOAT	Odometer reading upon exiting the segment, in kilometres.
`TraverseTime_Seconds`	FLOAT	Time in seconds to traverse the road segment.
`OdometerDistance_Km`	FLOAT	Distance calculated from odometer data, in kilometres.
`GpsDistance_Km`	FLOAT	Distance covered by linear interpolation between GPS points, in kilometres.

FuelTransaction

Aggregation level: Fuel transaction ID and fuel transaction timestamp

By entity: Fuel transaction ID
By time: Fuel transaction timestamp


Column	Type	Description
`DeviceId`	STRING	Identifier for the vehicle associated with this fuel transaction.
`Id`	STRING	Unique identifier for the fuel transaction record.
`UTC_DateTime`	TIMESTAMP	Timestamp of when the fuel transaction was recorded.
`DriverId`	STRING	Identifier for the driver associated with this fuel transaction.
`DriverName`	STRING	The fuel cardholder name.
`VIN`	STRING	Vehicle identification number of the associated vehicle.
`Description`	STRING	Description of the vehicle.
`LicencePlate`	STRING	Licence plate of the vehicle.
`SerialNumber`	STRING	Serial number of the device.
`Provider`	STRING	Provider of this transaction.
`ExternalReference`	STRING	External reference to the transaction, typically an external identifier.
`SiteName`	STRING	Site or merchant name where the transaction took place.
`ProviderProductDescription`	STRING	Product description given by the provider.
`Odometer_Km`	FLOAT	Driver-recorded odometer reading, in kilometres.
`Volume_Litres`	FLOAT	Volume of fuel purchased, in litres.
`Cost`	FLOAT	Cost of the fuel transaction.
`CurrencyCode`	STRING	Currency code. Default: USD.
`ProductType`	STRING	Product type of this transaction.
`Jurisdiction`	STRING	Jurisdiction where the vehicle was located at the transaction time, derived from IFTA traversal records through last-known-value carry-forward.

EV charge session table

Review the EV charge session table and what each column means.

The EV Charge Sessions table provides one row per charging stop for each electric vehicle. A vehicle can report several short charging sessions while it stays plugged in at one stop. The table combines these sessions into one row, with the total charging time, total energy, peak power, and battery level at the start and end of the stop.

Aggregation level:

By entity: DeviceId and charging stop
By time: UTC charge start time

Note:

Charging at one stop can spread over more than one day. For these stops, only charging sessions that start within 1 day of the requested dates are read. The start time, end time, and totals for that stop can change depending on the date range requested. To get complete results, request a date range that covers the whole stop.

Table name: ChargeSession

ChargeSession


Column	Type	Description
`DeviceId`	STRING	The ID of the telematics device, as designated on MyGeotab.
`TripStop`	TIMESTAMP	The UTC timestamp of the trip stop where the vehicle charged. This field is null when the charge is not linked to a trip stop. Each such charge is returned as its own row.
`ChargeType`	STRING	The type of charging at this stop: AC, DC, or Unknown. When a stop has sessions of different types, the type follows this order: Unknown, then DC, then AC. For example, a stop with one AC session and one DC session shows DC.
`ChargeStart`	TIMESTAMP	The UTC timestamp when the first charging session at this stop began.
`ChargeEnd`	TIMESTAMP	The UTC timestamp when the last charging session at this stop ended.
`ChargeDuration_Seconds`	FLOAT	The total active charging time (in seconds) at this stop. Gaps between charging sessions are not included.
`EnergyConsumed_kWh`	FLOAT	The total energy consumed during charging (in kWh) at this stop. A value of 0 means the session is still in progress or the vehicle cannot report energy. This field is null if the vehicle does not report energy.
`PeakPower_kW`	FLOAT	The highest charging power (in kW) recorded during this stop. This field is null if the vehicle does not report charging power.
`MaxACVoltage_Volts`	FLOAT	The highest AC input voltage (in volts) recorded during this stop. This field is null for DC-only stops, or if the vehicle does not report AC voltage. If a stop starts with a short AC session and then switches to DC, this field shows the voltage from that short AC session.
`StartStateOfCharge`	FLOAT	The battery state of charge (in %) when charging started at this stop. This field is null if the vehicle does not report battery level.
`EndStateOfCharge`	FLOAT	The battery state of charge (in %) when charging ended at this stop. This field is null if the vehicle does not report battery level.
`Latitude`	FLOAT	The GPS latitude of the charging location, taken from the first charging session at this stop.
`Longitude`	FLOAT	The GPS longitude of the charging location, taken from the first charging session at this stop.
`ChargingStartedOdometer_Km`	FLOAT	The odometer reading (in km) at the start of the first charging session at this stop. This field is null if odometer data is not available.