Skip to content
Nexus Observatory

/

Government

/

Resources
Resources for government.

Learning paths, the standards cited across this site and the explainers that show the systems in 3D.

Plan a deploymentUse casesOpen the explainer

Reference design, drawn to scale · drag to turn

  1. Government · Resources

    National observing infrastructure, delivered as one programme

    Programmes that build a country’s observing capability: national station networks, connectivity for remote sites, data platforms every ministry can read, and the qualification and training that keep it running long after commissioning. Needs: gaps in national network coverage, data exchange across agencies, station uptime and data completeness, skills to operate and maintain and evidence for funders and auditors.

  2. Story

    Orbit

    A worked story shows how a government deployment runs end to end, from the instruments and the radio to the edge, the console and the people who act on the result. Each story names its sources and the standards it relies on.

    Read the stories
  3. Story

    Observation grid

    A worked story shows how a government deployment runs end to end, from the instruments and the radio to the edge, the console and the people who act on the result. Each story names its sources and the standards it relies on.

    Read the stories
  4. Story

    Timing pnt

    A worked story shows how a government deployment runs end to end, from the instruments and the radio to the edge, the console and the people who act on the result. Each story names its sources and the standards it relies on.

    Read the stories
  5. Story

    Provenance

    A worked story shows how a government deployment runs end to end, from the instruments and the radio to the edge, the console and the people who act on the result. Each story names its sources and the standards it relies on.

    Read the stories
  6. What must be measured

    Government: what must be measured

    Gaps in national network coverage, data exchange across agencies, station uptime and data completeness, skills to operate and maintain and evidence for funders and auditors. Each is measured by instruments sited to recognised practice, read by a base node that stamps, checks and signs every value.

  7. Trust

    Every node proves what it is

    A node joins only after its hardware root of trust answers an attestation challenge. Keys stay in secure hardware, software arrives signed, and every reading carries a signature, so its origin can be checked by anyone downstream without asking us.

  8. Time and place

    Every reading carries when and where

    Readings are stamped against a disciplined clock, from satellite time or a PTP grandmaster, together with the station position and its siting record. When time or position is degraded, the record says so instead of hiding it, and every analyst downstream sees the same warning.

  9. Updates

    Updates in rings, with rollback

    Software and configuration reach the fleet in rings: a canary site first, then a few, then all, each ring gated on health and data completeness. A failed gate stops the wave and returns each node to its last good release, without a site visit.

  10. Operations

    Every node watched, every incident closed

    The operations console shows every node with its state, its plan and its evidence. Alerts arrive with their data and a runbook; acknowledging one opens a work order, and an incident closes only when the cause is recorded and the fix verified.

  11. Field service

    One crew, from survey to repair

    The same crew surveys, installs, commissions, calibrates and repairs, working from the site’s own record. Each visit updates it, so the next crew knows exactly what is there, when it was last checked and why it was changed. Spares and references are planned from that history.

  12. What you get

    National observing network programmes

    Build-operate-transfer of national observing infrastructure as digital public infrastructure, with transfer of skills and records. Delivered as build-operate-transfer and professional services, for governments, development lenders financing them. Scale: National. Service levels are written as numbers you can measure on your own dashboard.

    Talk to sales
  13. Next step

    Plan a government deployment

    Tell us the sites, the measurements and the people who will use them. We reply with a design and a scope for government. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace.

    Plan a deploymentOpen the StudioRead the stories

01Learning paths

From first principles to a commissioned site.

01

Academy

The principles of observation, the protocol and the lifecycle of a site.Start learning →

02

Training and enablement

Operator, crew and engineer training on the systems you own.The training platform →

03

Explainers

The systems in 3D, chapter by chapter, drawn to scale.Open the explainer →

02Standards

The standards cited on this site.

  • OGC SensorThings API 1.1
  • Municipal open-data terms
  • WMO-No. 8 (CIMO Guide)
  • WMO-No. 1160 (Manual on WIGOS, GBON)
  • WMO WIS 2.0
  • WMO-No. 306 (BUFR)
  • OASIS CAP 1.2 (outbound alerts)
  • NWCG RAWS standards
  • NFPA 1600
  • 3GPP Band 106
  • IEC 61850
  • IEEE 1547 / 2030.5
  • NERC CIP
  • FDSN station metadata and data formats
  • IOOS and IMOS quality-control procedures
  • FAIR data principles
  • WMO hydrological observing practices
  • National gauge standards
  • 3GPP LTE/NR
  • OASIS CAP 1.2
  • National incident-management systems
  • ICOS and eLTER quality levels
  • netCDF/CF
  • OGC SensorThings API
  • National mesonet programme standards
  • WMO-No. 8
  • Cantonal and provincial avalanche-safety codes
  • NTCIP 1204
  • IGS RINEX
  • INTERMAGNET

03Explainer and stories

See it at work.

The industry in 3D, and field stories with the systems in each and the sources behind them.

Explainer

Government, explained

National observing infrastructure, delivered as one programme.Open the explainer →
Orbit

Orbits as infrastructure

Low orbits are fast and crowded, high orbits slow and spacious. Every choice of altitude is a trade between delay, footprint and how long the satellite…Read the story →
End to end

An observation grid, end to end

An observation is not a reading. It is a reading with a place, a time, a calibration and a path that anyone can follow back. An observing grid is the…Read the story →
Timing and PNT

Time as infrastructure

A 5G cell must hold its phase within 3 µs of its neighbours, ±1.5 µs of a common reference; a synchrophasor’s one per cent vector error leaves room for only…Read the story →
Data provenance chain

From sensor to record

A published observation should carry its own history: which instrument made it, when, under which calibration, and every step since. The web already has a…Read the story →
Federation across agencies

Many agencies, one picture

No single agency observes everything it needs. Federation lets each keep its own systems and still share: common interfaces, common catalogues and common…Read the story →
Resilient operations

When the links fail

Observing systems matter most on the days infrastructure fails. Designing for that day means local autonomy, stored power, store-and-forward delivery and…Read the story →

04Terms

What people search for in this industry.

multi-hazard early warning systemGBONWIS 2.0automatic weather station tenderwildfire detection cameraflood sensor networkCAP alertingdeployable cellimpact-based forecastingEW4Allfield campaign logisticsautonomous weather station polarstream gauge telemetrywave buoypassive acoustic monitoringseismic station hostingresearch infrastructure in-situ dataFAIR data

Bring us the site.

Survey, design, deployment and operation for government. The form names who receives your details.

Talk to usPlan a deployment

Resources for government.

Reference design, drawn to scale · drag to turn