Speeding event
Speeding event is one of Demiton's published registers for Australian civil construction. Speeding events from telematics. 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
speeding_eventUse 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)
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- Workplace Surveillance Act 2005 (NSW)Workplace Surveillance Act 2005 (tracking surveillance of employees)
- INSPIRE D2.8.I.1INSPIRE Data Specification on Coordinate Reference Systems - Technical Guidelines (ETRS89/EVRS)
- GDPRGeneral Data Protection Regulation (GDPR)
- EPSG Geodetic Parameter DatasetIOGP EPSG registry of coordinate reference system identifiers
- ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)
- RFC 7946The GeoJSON Format (IETF Proposed Standard)
- WGS 84 (EPSG:4326)World Geodetic System 1984 datum ensemble (EPSG:6326)
- NZGD2000 / NZTM2000New Zealand Geodetic Datum 2000 and NZ Transverse Mercator 2000 (LINZ)
- 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
- NAD 83 (2011)North American Datum of 1983 (2011) epoch 2010.00 / NSRS (NGS)
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
18 fields: 9 required, 6 optional, 3 defined by each organisation.
Required
Every record carries these fields.
- asset_idNumber
The asset the event belongs to; today the
ASSETanchor resolved from the payload's vehicle identifier.Example:
9301- positionGroup of fields
The event position, carried as one value so it can never be half-populated.
- speed_kmhNumber
The peak speed recorded for the event.
Example:
92.4- duration_sNumber
Duration of the overspeed event.
Example:
34- external_idText
Source-system event identity, used for idempotent re-harvest and cross-chunk de-duplication.
Example:
NAVMAN-SE-88213- occurred_atDate and time
When the overspeed event occurred, not when it was recorded.
Example:
2026-07-16T05:12:00Z- position_datumText
The datum/CRS identifier the coordinate is in (e.g. the EPSG code), plus the source frame where known.
Example:
EPSG:4326 (WGS84)- speed_offset_kmhNumber
How far over the threshold the event was.
Example:
12.4- speed_threshold_kmhNumber
The speed limit or threshold the event exceeded.
Example:
80
Optional
Present when the source system records them.
- trip_idNumber
The trip the event belongs to, where the source supplies one.
Example:
771023- device_idNumber
The telematics unit that produced the event.
Example:
44210- recorded_atDate and time
When the telematics platform stamped/synchronised the event.
Example:
2026-07-16T05:12:05Z- event_actionText
The TN360 action discriminator; the demo fixture carries
SEfor speed events.Example:
SE- source_unitsGroup of fields
The source unit per measure, where it is not the canonical unit.
- position_precisionText
Whether the coordinate is full precision or reduced (the US ELD personal-use mode is the worked example).
Example:
full
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- driver_idNumber
The driver the event is attributed to, where the tenant's policy permits storing it.
Example:
5501- event_typeText
The source event-type label, where a tenant's feed mixes event types.
Example:
Speeding- location_labelText
A human-readable place name or address string for the event.
Example:
Capricorn Highway near Emerald
Filed against
Records are indexed along these dimensions, so they can be asked for by any of them.
- Assetwhat the record is about, from
Always set - Financial periodcontext for the record, from
When known
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "asset_id": 9301, "device_id": 44210, "driver_id": 5501, "duration_s": 34, "event_action": "SE", "event_type": "Speeding", "external_id": "NAVMAN-SE-88213", "location_label": "Capricorn Highway near Emerald", "occurred_at": "2026-07-16T05:12:00Z", "position": { "lat": -23.5364, "lon": 148.1631 }, "position_datum": "EPSG:4326 (WGS84)", "position_precision": "full", "recorded_at": "2026-07-16T05:12:05Z", "source_system": "NAVMAN", "speed_kmh": 92.4, "speed_offset_kmh": 12.4, "speed_threshold_kmh": 80, "trip_id": 771023}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/speeding_event/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.