Geotab (LogRecord)
The Geotab (LogRecord) feed type in ArcGIS Velocity periodically polls a Geotab LogRecord database table for real-time automatic vehicle location (AVL) data by sending HTTP requests to a specified URL. Unlike the Geotab (DeviceStatusInfo) feed type, it requests data from the Geotab database's LogRecord table. The LogRecord table is generally updated more frequently than the Geotab database's DeviceStatusInfo table, although it contains fewer attributes than the DeviceStatusInfo table. As a result, the Geotab (LogRecord) feed can receive location updates more frequently.
Examples
The following are example use cases for the feed:
A city wants to monitor its fleet of snowplow trucks during the winter season. The Geotab (LogRecord) feed is used to observe the real-time location of each truck and gather more information, such as whether the plow blade is engaged or whether the bin storing deicing salt is at a low threshold.
A waste management company wants to improve the efficiency of its fleet through data analysis. The Geotab (LogRecord) feed is used to collect each vehicle's location, driver, load weight, idle time, and fuel level in real time.
Usage notes
Note the following when working with the feed:
The Geotab (LogRecord) feed constructs events using data from tables in the Geotab database. For example, location, speed, and bearing attributes are retrieved from the LogRecord table. The device table helps retrieve more attribute information, such as the VIN and vehicle license plate. Group names and group IDs associated with each device are obtained from the group table. For more information, refer to the Schema section.
The data from Geotab is highly normalized, and the Geotab (LogRecord) feed follows a fixed schema by default. The feed automatically sets the location, date and time, and
TrackIDfield. TheTrackIDfield can be changed.Optional diagnostic IDs can be provided to enhance the schema with more attribute values. For example, if a vehicle is equipped with a sensor to monitor total fuel usage, providing the
DiagnosticDeviceTotalFuelIddiagnostic ID causes the feed to collect this information in a new attribute field. Diagnostic fields are reflected in the feed schema.One or more optional groups can be specified to limit the type of device data that is retrieved from the Geotab (LogRecord) feed.
More fields with driver information can be appended to the default schema of the Geotab (LogRecord) feed. Only choose fields that have values provided by Geotab. If a field is unknown, the value may be null, an empty string, or a predefined string from Geotab. For more information, refer to the Additional fields section.
The recommended interval to poll for Geotab data is every 30 seconds or greater.
Schema
The following table lists the schema attributes and their data types for the feed:
|
Attribute |
Data type |
|---|---|
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
Float64 |
|
|
Float64 |
|
|
Float64 |
|
|
String |
|
|
String |
Additional fields
The following table lists the additional attribute fields and their data types for the feed:
|
Attribute |
Data type |
|---|---|
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
|
|
String |
Parameters
The following table describes the parameters for the feed:
|
Parameter |
Description |
Data type |
|---|---|---|
|
URL |
The URL used to authenticate Geotab. For example, |
String |
|
Database |
The name of the Geotab database. |
String |
|
Username |
The username used to authenticate Geotab. |
String |
|
Password |
The password used to authenticate Geotab. |
Password |
|
Get latest locations only |
When the parameter is checked, the feed only returns the latest observation for each When the parameter is not checked, the feed returns all observations for each |
Boolean |
|
Groups (optional) |
Optional group names used to filter for entity members. For example, street sweeping vehicles may belong to a group named Note:Specify multiple groups using a semicolon. |
String |
|
Diagnostic IDs (optional) |
Optional diagnostic IDs used to obtain diagnostic values. For example, A diagnostic value field and a diagnostic timestamp field are added for each diagnostic ID. Note:Specify multiple diagnostic IDs using a semicolon. |
String |
|
Additional fields |
A list of additional fields that can be used to enrich the feed schema with driver information. Note:Only choose fields that have values provided by Geotab. Otherwise, the resulting value may be null, an empty string, or a predefined string from Geotab. |
String |
|
Additional logging (optional) |
Specifies whether logging for raw HTTP requests and responses issued by Velocity to the Geotab API are turned on. Note:Turn this parameter on for troubleshooting purposes and turn it off when troubleshooting is complete. Once turned on, start the feed; the debug level logs are available on the feed logs page. Contact Esri Technical Support for help with troubleshooting, if necessary. |
Boolean |
Considerations and limitations
Consider the following when using the feed:
At each polling interval, Geotab provides the data it compiled at the last poll and does not include data compiled afterward. The provided data may be older than the timestamp of the last poll made by the feed.
Diagnostic values update at a different rate than other device data. For this reason, each diagnostic field is accompanied by a timestamp field. Consider whether diagnostic values are temporally relevant to the latest timestamp of the other data retrieved from Geotab.
When specifying unique diagnostic IDs, you can use groups to filter the type of devices coming from Geotab first. Each diagnostic ID enhances the schema for all the vehicles from Geotab. For example, a diagnostic that captures the status of a snowplow blade is appended to all vehicle types from Geotab, not just the snowplow trucks. For vehicles without the sensor, the diagnostic value is null. If a snowplow group is defined first, only snowplow trucks are retrieved from Geotab and include the custom diagnostic field for the relevant snowplow blade status.
Additional fields only have values if Geotab provides them in the database. Consider the information reported by your organization's Geotab devices before choosing any additional fields. Fields without a value are null, an empty string, or contain a predefined string from Geotab.
If the user credentials are invalid, the feed retries the connection up to three times. Invalid credentials errors appear in the logs. The feed automatically attempts to restart after a delay, based on the configured recurrence schedule.