Speeding event

Speeding events from telematics.

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

v1Current version.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Navman

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

19 fields: 9 required, 6 optional, 4 defined by each organisation.

Required

Every record carries these fields.

asset_idNumber

The asset the event belongs to; today the ASSET anchor resolved from the payload's vehicle identifier.

Example: 9301

external_idText

Source-system event identity, used for idempotent re-harvest and cross-chunk de-duplication.

Example: NAVMAN-SE-88213

occurred_atDate and timeISO 8601, with time zone

When the overspeed event occurred, not when it was recorded.

Example: 2026-07-16T05:12:00Z

speed_kmhNumberUnit: km/h

The peak speed recorded for the event.

Example: 92.4

speed_threshold_kmhNumberUnit: km/h

The speed limit or threshold the event exceeded.

Example: 80

speed_offset_kmhNumberUnit: km/h

How far over the threshold the event was.

Example: 12.4

duration_sNumberUnit: s

Duration of the overspeed event.

Example: 34

positionGroup of fieldsUnit: decimal degrees

The event position, carried as one value so it can never be half-populated.

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)

Optional

Present when the source system records them.

event_actionText

The TN360 action discriminator; the demo fixture carries SE for speed events.

Example: SE

position_precisionText

Whether the coordinate is full precision or reduced (the US ELD personal-use mode is the worked example).

Example: full

recorded_atDate and timeISO 8601, with time zone

When the telematics platform stamped/synchronised the event.

Example: 2026-07-16T05:12:05Z

device_idNumber

The telematics unit that produced the event.

Example: 44210

trip_idNumber

The trip the event belongs to, where the source supplies one.

Example: 771023

source_unitsGroup of fields

The source unit per measure, where it is not the canonical unit.

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

source_systemText

Which bound system wrote the fact.

Example: NAVMAN

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

speeding_event.example.json

{
  "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.

Schema URL

https://docs.demiton.io/registers/speeding_event/v1.json

Show the full JSON Schema

Loading the schema…