Vehicle location
Vehicle location is one of Demiton's published registers for Australian civil construction. Last-known GPS position of each vehicle. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
Part of Assets in the register catalog.
- Register ID
vehicle_locationUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- An eventSomething that happened at a point in time.
- Status
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- GDA2020 / MGA2020Geocentric Datum of Australia 2020 and Map Grid of Australia 2020 (EPSG:7844 / EPSG:78xx zones)
- National Measurement Act 1960 (Cth) s 8ARecognized-Value Standard of Measurement of Position Determination 2017 (legal definition of GDA2020)
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- Workplace Surveillance Act 2005 (NSW)Workplace Surveillance Act 2005 (tracking surveillance of employees)
- GDPRGeneral Data Protection Regulation (GDPR)
- ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)
- WGS 84 (EPSG:4326)World Geodetic System 1984 datum ensemble (EPSG:6326)
- ICO monitoring workers guidanceICO Employment practices and data protection: monitoring workers
- UK GDPRUK GDPR and Data Protection Act 2018
- 49 CFR Part 395 Subpart BFMCSA - Hours of Service of Drivers - Electronic Logging Devices
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- EROAD
- GeotabPartial
Fields
16 fields: 2 required, 14 optional.
Required
Every record carries these fields.
- assetText
The vehicle/plant the snapshot is about; the shelf's only required coordinate.
Example:
9301- occurred_atDate and time
When the last event on the unit happened; the shelf's temporal coordinate.
Example:
2026-06-15T15:58:00
Optional
Present when the source system records them.
- tripNumber
The source trip/journey the last event belongs to.
- deviceNumber
The telematics unit that produced the reading, distinct from the asset identity.
Example:
771201- odometerDecimal number
GPS-sourced lifetime odometer meter.
Example:
18244.6- operatorNumber
The driver/operator active on the unit.
Example:
5502- fuel_periodDecimal number
Fuel consumed over the reading window.
Example:
61.2- place_labelText
The human-readable location text delivered by the source.
Example:
Emerald Street, Yamala QLD 4702- readings_atDate and time
When the meter readings were taken, distinct from the last-event time.
Example:
2026-06-15T15:58:00- engine_hoursDecimal number
GPS-sourced lifetime engine-hours meter.
Example:
3210.4- odometer_canDecimal number
CAN-bus twin of
odometer- distance_periodDecimal number
Distance accumulated over the reading window (delta, not a lifetime meter)
Example:
42.3- last_event_typeText
The discriminator for what the last event was (type/subtype), for a state snapshot.
Example:
ignition_off- engine_hours_canDecimal number
CAN-bus twin of
engine_hours- financial_periodText
The accounting period the snapshot falls in; derived, no raw source field.
Example:
2026-06- engine_hours_periodDecimal number
Engine hours accumulated over the reading window.
Example:
8.9
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Financial periodcontext for the record, from
When known - Assetwhat the record is about, from
Always set
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "asset": "9301", "device": 771201, "distance_period": 42.3, "engine_hours": 3210.4, "engine_hours_period": 8.9, "financial_period": "2026-06", "fuel_period": 61.2, "last_event_type": "ignition_off", "occurred_at": "2026-06-15T15:58:00", "odometer": 18244.6, "operator": 5502, "place_label": "Emerald Street, Yamala QLD 4702", "readings_at": "2026-06-15T15:58:00", "source_system": "NAVMAN"}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/vehicle_location/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.