Skip to content
Demiton

Gps event

GPS events: ignition, speed, geofence crossings.

Part of Assets in the register catalog.

Register ID
gps_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.

Connectors

Connected today

Demiton keeps this register current from these systems now.

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
  • Geotab

Fields

14 fields: 4 required, 10 optional.

Required

Every record carries these fields.

assetText

The machine the event is about; the shelf's only required coordinate.

Example: 9301

occurred_atDate and timeISO 8601, with time zone

When the event happened; the temporal coordinate.

Example: 2026-08-11T06:52:00Z

source_systemText

Which bound system emitted the row.

Example: NAVMAN

event_typeText

The discriminator that tells an ignition event from a speed or geofence crossing.

Example: engine_on

Optional

Present when the source system records them.

latitudeDecimal numberUnit: degrees

GNSS-native latitude from the raw GPS block.

Example: -23.5266

longitudeDecimal numberUnit: degrees

GNSS-native longitude from the raw GPS block.

Example: 148.1612

coordinate_datumText

The horizontal frame/realisation and epoch the lat/lng pair is expressed in (expected: GNSS native, WGS 84 ensemble EPSG:4326)

coordinate_precision_classText

Whether the position is full precision or a reduced/precision-limited state.

geographic_areaText

The resolved geofence/area the asset was located at.

place_labelText

The human-readable location delivered by the source.

Example: Emerald Street Site Compound

deviceNumber

The telematics unit that produced the event, distinct from the asset identity.

tripNumber

The source trip/journey grouping the event belongs to.

operatorNumber

The driver/operator active on the machine.

financial_periodText

The accounting period the event falls in; derived, no raw source field.

Example record

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

gps_event.example.json
{
"asset": "9301",
"event_type": "engine_on",
"latitude": -23.5266,
"longitude": 148.1612,
"occurred_at": "2026-08-11T06:52:00Z",
"place_label": "Emerald Street Site Compound",
"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.

Schema URL
https://docs.demiton.io/registers/gps_event/v1.json
Show 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 keep current from them, on your data, in a 30-minute call.

Book a 30-minute callStart free