Gps event

Gps event is one of Demiton's published registers for Australian civil construction. GPS events: ignition, speed, geofence crossings. 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

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

v1 (1.0.3)Current version.

Download JSON SchemaSee an example record

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)Australia · GDA2020 = ITRF2014 at epoch 2020.0 · public summary
• National Measurement Act 1960 (Cth) s 8ARecognized-Value Standard of Measurement of Position Determination 2017 (legal definition of GDA2020)Australia · Determination 2017 · clause s 8A · public summary
• Privacy Act 1988Privacy Act 1988 - Australian Privacy PrinciplesAustralia · APP Guidelines ch 3 v1.2 (2026-05-13) · clause APP 3 · verified against full text
• Workplace Surveillance Act 2005 (NSW)Workplace Surveillance Act 2005 (tracking surveillance of employees)Australia · in force (compilation 2025-06-14) · clause s 10 · public summary
• INSPIRE D2.8.I.1INSPIRE Data Specification on Coordinate Reference Systems - Technical Guidelines (ETRS89/EVRS)European Union · v3.2rc2, release 2024.1 (2024-01-31) · verified against full text
• GDPRGeneral Data Protection Regulation (GDPR)European Union · 2016 · public summary
• ISO/TS 15143-3Earth-moving machinery and mobile road construction machinery - Worksite data exchange - Telematics data (AEMP 2.0)International · 2020 (SA TS ISO 15143.3:2021 AU and PD ISO/TS 15143-3:2020 UK identical adoptions) · paywalled, from a secondary description
• WGS 84 (EPSG:4326)World Geodetic System 1984 datum ensemble (EPSG:6326)International · EPSG Dataset v13.102; record revised 2022-11-29 · verified against full text
• NZGD2000 / NZTM2000New Zealand Geodetic Datum 2000 and NZ Transverse Mercator 2000 (LINZ)New Zealand · official since 1998 (NZVD2016 vertical) · public summary
• ICO monitoring workers guidanceICO Employment practices and data protection: monitoring workersUnited Kingdom · current guidance (under review after the Data (Use and Access) Act) · verified against full text
• OSGB36 / ETRS89 (OSTN15)British National Grid, accessed from ETRS89 via OSTN15 (Ordnance Survey)United Kingdom · OSTN15 / OSGM15 · public summary
• UK GDPRUK GDPR and Data Protection Act 2018United Kingdom · as amended · public summary
• 49 CFR Part 395 Subpart BFMCSA - Hours of Service of Drivers - Electronic Logging DevicesUnited States · current (ELD mandate from 2017-12-18) · clause ss 395.26(b), (d), (i); 395.8(c), (k) · verified against full text
• NAD 83 (2011)North American Datum of 1983 (2011) epoch 2010.00 / NSRS (NGS)United States · NAD 83(2011); NATRF2022 replacement not confirmed effective · public summary

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Navman
• Trimble

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

13 fields: 3 required, 10 optional.

Required

Every record carries these fields.

assetText

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

Example: 9301

event_typeText

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

Example: engine_on

occurred_atDate and timeISO 8601, with time zone

When the event happened; the temporal coordinate.

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

Optional

Present when the source system records them.

tripNumber

The source trip/journey grouping the event belongs to.

deviceNumber

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

latitudeDecimal numberUnit: degrees

GNSS-native latitude from the raw GPS block.

Example: -23.5266

operatorNumber

The driver/operator active on the machine.

longitudeDecimal numberUnit: degrees

GNSS-native longitude from the raw GPS block.

Example: 148.1612

place_labelText

The human-readable location delivered by the source.

Example: Emerald Street Site Compound

geographic_areaText

The resolved geofence/area the asset was located at.

coordinate_datumText

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

financial_periodText

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

coordinate_precision_classText

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

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.

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…