Skip to content

GPS and telematics

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade D · dataset: Stream (a timestamped recording) · type gps

What it is

A GPS or telematics feed. In the test estate it is an NMEA 0183 gateway for the trailer GPS units. The connector reference is Telemetry.

Grade

D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typegps
Other spellings that resolvetelematics, eld, nmea, tracker
Settingsprovider, endpoint, asset_ids, lookback_minutes, collect_seconds, include_sensors
Credentialstoken, api_key, password

The test connection

Trailer GPS gateway

SettingTest value
providernmea
endpointgps-gw.quillmere.invalid:10110
asset_idsGPS-101,GPS-102,GPS-103,GPS-104,GPS-105,GPS-106,GPS-107,GPS-108,GPS-109,GPS-110
lookback_minutes60
collect_seconds30
include_sensorsfalse

This connection takes no credential.

FACE refuses this test connection as written. Provider nmea is a raw TCP stream with no encryption, so FACE cannot secure it and will not save or read it. The recording stays here as the shape of the test estate’s GPS data. To connect a real tracker, use its https:// API: provider samsara, geotab or generic_rest, with endpoint an https:// address and the tracker’s credential.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download the unit files from nmea/ in the recording below and open them next to expected.json. An NMEA feed carries no device id: assets.json in the recording maps each file to its unit.
  2. To read live positions, add a connection in Settings › Integrations › Systems to a tracker’s https:// API (samsara, geotab or generic_rest), with its asset_ids. Then open Live sensors or Devices from the connection’s card on Ask.

What FACE finds

GPS has no catalogue. An NMEA feed is a raw TCP socket, which FACE does not connect to; the model below is the recording’s shape. Over a tracker’s API, FACE reads positions for collect_seconds and attributes them to asset_ids.

DatasetKindDomainPrimary keyRowsFields
GPRMCnmea_sentencetelematicsnone2319

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 1 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
deviceGPRMC.device_idbigquery, cctv, databricks, files, iot, kafka, mqtt, postgres, rfid, servicenow

Evidence it holds for the planted anomalies:

  • ANOM-5, A GPS route deviation. streams/gps/nmea/GPS-106.nmea, look for $GPRMC,104146.00,A,3812.2682,N,08953.6706,W,44.8,148.0,110926,,,A*74 (the off-corridor fix as the unit sent it).

See all connectors at once for the walkthrough across every source.

Download

Streams are dialled and held open, so their datasets are replay recordings under streams/gps/, not a zip. Download the files, and use them as described above.

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.