Fields in the sample
| Field | Meaning |
|---|---|
| reg_no | Vehicle registration number |
| latitude, longitude | Position in decimal degrees |
| speed | Speed of the vehicle |
| bearing | Direction of travel |
| ignition_status | ON or OFF |
| vehicle_status | Status of the vehicle data, such as NODATA |
| status | Device status |
| address | Address for the position |
| odo_distance | Distance on the odometer |
| fuel_litre | Fuel level, when a sensor is fitted |
| inside_geofence | Y or N, if the vehicle is inside a set zone |
| vehicle_type | Type of vehicle |
| vehicle_id, device_id | Identifiers |
| date | Time as a number in milliseconds |
| iso_date | Time as an ISO date |
| expiry_date | Expiry date of the plan, in the Push sample |
Notes
- Fields can vary by device and plan
- Fuel needs a sensor
- Driver behaviour needs a supporting device
- We confirm the exact fields for your account
Questions we hear often
Can you add a field?
Often yes. Tell us what you need.
Is history available?
Historical data can be provided. Ask us how.