Location identity
NLRTM · Rotterdam
UN/LOCODE · captured example
Signals · CO₂ · Locations
Disruption signals with their evidence. Transport emissions with an explanation. Shared location identities that connect your logistics data.
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
Follow a captured report into an event, an anchor and the evidence behind it.
01 / Source report
Reported in the source
The report describes a temporary closure at Catania airport and a flight diverted to Palermo.
src:20260926-140000-2689721 · STATED02 / Connected context
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
02 · CO₂ Emissions
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
Operations + energy provision · transport legs only
Shanghai · CNSHA Rotterdam · NLRTM
Synthetic display value · no applied factor
Rotterdam · NLRTM Duisburg · DEDUI
Synthetic display value · no applied factor
The methodology reference describes an accounting approach. It is not a certification or a guarantee of factor availability.
Distinguish operations from energy provision, and state which transport legs and other activities are included.
03 · Location Intelligence
Resolve names and aliases into a structured trade location. Use the same identifier when connecting your Signals and Emissions data.
Read a signal’s anchor alongside its evidence. A matching location identity is context, not proof of an impact.
Identify a transport leg’s endpoints consistently. Coordinates alone do not establish a route or an emission factor.
Captured location example · selected fields
UN/LOCODE record · captured 7 September 2026. Selected fields shown.
The platform
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.
Read extracted events, location anchors and source evidence. Inspect confidence, review state and coverage before using a signal.
GET /v1/signals 02 · CO₂Understand totals, transport legs, calculation boundaries and factor provenance. The demonstration uses invented values.
Methodology and synthetic example 03 · LOCATIONSLook up a UN/LOCODE identity with geographic attributes, or search normalized location names and aliases.
GET /v1/locations/{locode} PREVIEW · T&T · illustrativeA product preview showing how DCSA-shaped shipment and transport events could sit beside shared location data.
Illustrative event stream PREVIEW · IMPACT · illustrativeA concept for relating shipment positions to disruptions. Sample scores and delays are invented, not predictions.
Product concept PREVIEW · ROUTES · illustrativeExplore possible route comparisons and port baselines. These examples do not promise routing, risk-scoring or statistics endpoints.
Product conceptsGET /v1/locations/NLRTM and keep the source record alongside the attributes you use.How to read a signal
A reported event, its extracted fields and a location relationship answer different questions. Keep each visible when you bring a signal into your product.
Start with the source-linked evidence. A statement in a report is evidence of what was reported, not an independent verification.
Inspect the event classification, severity and extraction confidence returned with the record.
Read the location and anchor together. A country-level anchor is less specific than a resolved location; it is not a predicted downstream effect.
Query the documented REST endpoints. Check coverage and review state, and retain provenance in your own workflow.
Product preview · illustrative
This product preview uses DCSA-style shipment, transport and equipment event labels.
The invented stream illustrates a gate-in, loading, departure and estimated arrival. It is not connected to carrier feeds.
Reported observations and estimated arrivals carry different meanings. This preview makes no ETA prediction or tracking availability claim.
Compound intelligence · product concepts
Illustrative product previews, not available endpoints. All shipment delays, route scores and port statistics below are invented examples, not live predictions or measured baselines.
A concept for reviewing shipments beside disruption records. The example delays are invented; no exposure endpoint is promised.
A concept for displaying routing tradeoffs. Scores, labels and amounts are illustrative; no route recommendation is being made.
A concept for comparing port observations over time. These invented statistics are not measured port performance.
Developer APIs
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.
# 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
Keep reported facts, calculation assumptions and your own decisions separate.
Bring source-linked events into your operational workflow and inspect the location context before taking action.
Review transport legs, accounting boundaries and data provenance alongside an emissions total.
Resolve a UN/LOCODE record and use its attributes consistently across your systems.
Inspect source, confidence and review state. Decide how each record fits your own assessment process.