Signals · CO₂ · Locations

Make every movean informed one.

Disruption signals with their evidence. Transport emissions with an explanation. Shared location identities that connect your logistics data.

  • Source-linked signals
  • Explainable CO₂e
  • UN/LOCODE identities
Flight activity · simulated

Location identity

NLRTM · Rotterdam

UN/LOCODE · captured example

Source → event → context

Evidence stays connected

Source IDs · location anchors

Sample shipment footprint

1,842.6 kg CO₂e

Ocean + rail · synthetic total

Transport legs only

Separate shipment, not the simulated flight

01 · Signal Intelligence

Know what changed. See why.

Follow a captured report into an event, an anchor and the evidence behind it.

01 / Source report

Volcanic ash disrupts flights in Sicily.

Reported in the source

The report describes a temporary closure at Catania airport and a flight diverted to Palermo.

src:20260926-140000-2689721 · STATED

02 / Connected context

ITPMOPalermo · LOCODE

How to read the connection

Palermo is the returned location anchor and the reported diversion destination. It is not the airport described as closed. This relationship does not predict a downstream delay.

03 / Structured record

Signal
sig_0001HM
Event
PORT_CLOSURE
Returned anchor
ITPMO
Severity
HIGH
Extraction confidence
0.446
Review state
No review pending · resolved anchor
  • Evidence stays attached Source IDs and evidence spans travel with the structured record.
  • Context stays explicit Location anchors, confidence and review flags help you judge what the record supports.

02 · CO₂ Emissions

A footprint with an explanation.

Read the total alongside its transport legs, boundary and data provenance.

GLEC Framework v3.2 (ISO 14083-aligned)

Synthetic illustration · no live calculation

Illustrative shipment footprint

1,842.6kg CO₂e

Operations + energy provision · transport legs only

  1. Ocean

    1,694.0 kg CO₂e

    Shanghai · CNSHA Rotterdam · NLRTM

    Synthetic display value · no applied factor

  2. Rail

    148.6 kg CO₂e

    Rotterdam · NLRTM Duisburg · DEDUI

    Synthetic display value · no applied factor

  • GLEC Framework v3.2 (ISO 14083-aligned)

    The methodology reference describes an accounting approach. It is not a certification or a guarantee of factor availability.

  • Make the boundary visible

    Distinguish operations from energy provision, and state which transport legs and other activities are included.

Calculation boundary & methodology
Methodology reference
GLEC Framework v3.2 (ISO 14083-aligned)
Included
Two transport legs; operations and energy provision (well-to-wheel / well-to-wake).
Excluded
Hub operations and refrigeration in this illustration.
Factor provenance
Synthetic presentation values only; no licensed factor table or live factor selection is reproduced.
Availability
Actual calculation coverage depends on the selected dataset and permitted use. This example does not establish production factor coverage.
Invented display totals, not calculated from a published factor set.

03 · Location Intelligence

One place. One shared identity.

Resolve names and aliases into a structured trade location. Use the same identifier when connecting your Signals and Emissions data.

  • Signals

    Read a signal’s anchor alongside its evidence. A matching location identity is context, not proof of an impact.

  • Emissions

    Identify a transport leg’s endpoints consistently. Coordinates alone do not establish a route or an emission factor.

Explore the Locations reference

Captured location example · selected fields

NLRTMRotterdam
Country
NL · Netherlands
Functions
port · rail · road · airport · postal
Latitude
51.9167
Longitude
4.5

UN/LOCODE record · captured 7 September 2026. Selected fields shown.

The platform

Connected data. Clear boundaries.

Explore the documented Signals and Locations APIs, and the emissions calculation approach. Track & Trace and compound intelligence below remain illustrative product previews, not available API commitments.

Foundation · Locations Use UN/LOCODE as a shared location identity. Start with GET /v1/locations/NLRTM and keep the source record alongside the attributes you use.

How to read a signal

Follow the evidence through the structure.

A reported event, its extracted fields and a location relationship answer different questions. Keep each visible when you bring a signal into your product.

Observe

Start with the source-linked evidence. A statement in a report is evidence of what was reported, not an independent verification.

source IDevidence span

Extract

Inspect the event classification, severity and extraction confidence returned with the record.

eventconfidence

Connect

Read the location and anchor together. A country-level anchor is less specific than a resolved location; it is not a predicted downstream effect.

anchorUN/LOCODE

Use

Query the documented REST endpoints. Check coverage and review state, and retain provenance in your own workflow.

RESTcoverageprovenance
MSKU 705431-0 · booking NX-88213 · CNSHA → NLRTM
JUN 18 09:02
EQUIPMENT · GTIN · ACT
Gate in, full — Yangshan Terminal, CNSHA
JUN 19 22:47
EQUIPMENT · LOAD · ACT
Loaded aboard MV Nordic Star, voyage 226W
JUN 20 04:15
TRANSPORT · DEPA · ACT
Vessel departed CNSHA
JUL 17 06:00
TRANSPORT · ARRI · EST
Arrival NLRTM — illustrative estimate, not a live prediction

Product preview · illustrative

Track the journey in a shared event language

  • A shared event vocabulary

    This product preview uses DCSA-style shipment, transport and equipment event labels.

  • One journey, several observations

    The invented stream illustrates a gate-in, loading, departure and estimated arrival. It is not connected to carrier feeds.

  • Keep estimates distinct

    Reported observations and estimated arrivals carry different meanings. This preview makes no ETA prediction or tracking availability claim.

Compound intelligence · product concepts

Explore what connected data could enable.

Illustrative product previews, not available endpoints. All shipment delays, route scores and port statistics below are invented examples, not live predictions or measured baselines.

IMPACT · SIGNAL × T&T

Shipment exposure concept

A concept for reviewing shipments beside disruption records. The example delays are invented; no exposure endpoint is promised.

ROUTES · ALL THREE

Route comparison concept

A concept for displaying routing tradeoffs. Scores, labels and amounts are illustrative; no route recommendation is being made.

PERFORMANCE · AIS BASELINE

Port baseline concept

A concept for comparing port observations over time. These invented statistics are not measured port performance.

Developer APIs

Start with the documented interfaces.

Read authenticated Signals and Locations documentation for request parameters, captured responses and an explorer. The example host is a reserved placeholder; use the API base shown in your console.

Signal Intelligence
GET /v1/signals list signals
GET /v1/signals/{id} signal and evidence
GET /v1/signals/{id}/events signal history
GET /v1/signal-events event log
Locations · UN/LOCODE
GET /v1/locations/{locode} location identity
GET /v1/locations?q=Rotterdam name and alias search
curl · location lookup · placeholder host
# Use the API base shown in your authenticated console.
$ curl https://api.example.com/v1/locations/NLRTM \
    -H "Authorization: Bearer $NEXUS_API_KEY"

# Selected fields from the captured NLRTM example
{
  "locode": "NLRTM",
  "name": "Rotterdam",
  "countryCode": "NL",
  "coordinates": { "lat": 51.9167, "lng": 4.5 }
}

Build with evidence

Useful inputs for your own workflow.

Keep reported facts, calculation assumptions and your own decisions separate.

Freight platforms

Investigate disruption

Bring source-linked events into your operational workflow and inspect the location context before taking action.

Shippers

Explain a footprint

Review transport legs, accounting boundaries and data provenance alongside an emissions total.

Data teams

Connect place identities

Resolve a UN/LOCODE record and use its attributes consistently across your systems.

Risk teams

Retain the evidence

Inspect source, confidence and review state. Decide how each record fits your own assessment process.

Build on a clearer picture.

Explore the documented interfaces and shared location example. Create an account to continue in the developer console.

© 2026 Nexus — The Intelligent API Logistics Hub NLRTM · 51.9167° N · 4.5000° E