InsightData & licensing
Observing the planet as one network
No single owner can observe a planet. Weather services, utilities, ports, researchers and communities each run instruments, and observation works best when they act as one network of many owners1.
A three-tier diagram: five owners of stations, from a national weather service to community stations, publish through a shared catalogue and message broker to warning services, planners and researchers.
Key points
- No single owner can observe a planet, but many owners can when their stations are built to join.
- Open data models let every station describe itself in terms that others can read.
- Shared time and evidence-based identity make records from different owners comparable and trustworthy.
- Federation lets each owner keep its own systems while publishing through shared services with more than one path.
- Provenance, quality and licence travel with each value, so users can judge it without asking.
Many owners, one picture
The instruments that watch the weather, the water and the ground belong to many hands. National services, cities, utilities, ports, universities and volunteers each place sensors for their own purpose and on their own budget.
Each owner sees a piece of the picture. A flood crosses a border, a storm crosses a coast, and a heat wave crosses every network at once, so the questions people ask are bigger than any one owner's map.
The meteorological community has answered this with an overarching framework for all its observing systems, which promotes network integration and partnership so that members can build capability, widen coverage and improve economic efficiency1.
Gaps remain. In some parts of the world observations are not made or not exchanged internationally, and in others they are not made or exchanged often enough2.
That is why a basic surface network is now being designed, defined and monitored at the global level rather than country by country2.
The stakes are public. The United Nations has set the aim that everyone on Earth is protected by early warning systems by the end of 20273.
No single operator can meet a goal like that alone. A network of many owners can, if each piece is built to join the others and to keep working when one of them is missing.
Open data models: one way to say what was measured
Joining starts with language. If one owner records a gauge as a row in a spreadsheet and another as a file named by date, nobody can merge the two without a translator.
Open data models remove the translator. OGC SensorThings gives an open, standard way to manage and retrieve observations and metadata from different sensor systems over the web4.
An exploded stack of the parts of a shared observation model: the platform, its location, the sensor, the observed property, the observation, the feature of interest and the result quality.
Its sensing model names the parts that every observation shares: the thing that carries the sensor, its location, the sensor, the property observed, the observation and the feature of interest it describes5.
An observation in that model can also carry a statement of result quality and the period in which the result may be used5.
Common models do not force owners to buy the same equipment. They only ask that every station describes itself in terms that others can read, which leaves each owner free to choose instruments for its own needs.
The same idea applies to web access. OGC API Features provides building blocks to create, modify and query features on the web, so stations and records can be shared with ordinary tools6.
A shared model also makes gaps visible. When every station is described the same way, a catalogue can show where a property is measured, where it is not, and where a record has gone quiet.
Shared time and shared identity
Two more things must be shared before records can be merged: the moment and the source. A value is only comparable with another if both clocks point to the same reference.
Coordinated Universal Time is that reference. National metrology institutes maintain physical realisations of it and contribute their clock data to the international bureau that publishes the time scale7.
The same four instruments drawn twice. On the left each owner runs its own small rack and nothing is shared. On the right every instrument links to one shared edge node with a common timing antenna.
Shared time also exposes faults. When many stations from different owners report against one reference, a clock that drifts or a station that has been tampered with stands out against its neighbours.
Identity matters just as much. In a network of many owners, nobody can trust a station because of where it is plugged in or who bought it.
Zero trust architecture states this plainly: no implicit trust is granted to assets based solely on their network location or ownership, and authentication and authorisation happen before a session is established8.
Remote attestation supplies the evidence for that decision. An attester produces believable information about itself, a verifier appraises it, and a relying party decides whether to treat the attester as trustworthy9.
Together these let a station from one owner join another owner's network on evidence rather than on reputation. The same rules apply to a national agency and to a school with one weather mast.
Federation: publish once, reach everyone
Federation is how many networks act as one without merging into one. Each owner keeps its own systems and publishes through shared services that no single owner controls.
The WMO Information System is a working example: a framework for data sharing across all WMO domains and disciplines, built on open standards and web technologies10.
A three-tier federation: three publishing centres send notifications to two brokers; the brokers feed a cache and a discovery catalogue, and forecasting and applications subscribe to both brokers.
Its technical specifications and implementation plan were approved in October 2022, and it will gradually replace the older global telecommunication system10.
In that design a publisher's node announces each new resource with a notification message over MQTT, and everyone subscribed to that dataset's topic receives it at once11.
Global brokers republish the notifications for resilience, and consumers are advised to subscribe to more than one broker so that notifications keep arriving if one fails11.
Global caches keep copies of core data for rapid access, so a small national centre does not have to serve the whole world from its own link11.
The lesson travels beyond weather. A federation needs open message formats, more than one path for every message, and a catalogue that tells users what exists and where to find it.
Federation also spreads the effort. Each owner looks after its own stations and its own node, while shared services run in more than one place so that none of them becomes a single point of failure.
Evidence that travels with the data
A shared network is only as trustworthy as the weakest record in it. Users need to know where each value came from, what was done to it and who was responsible.
Provenance is information about the entities, activities and people involved in producing data, and it can be used to assess its quality, reliability or trustworthiness12.
An exploded stack of what travels with each value: the value, its time and time quality, the station identity, the method and calibration, quality flags, provenance and the licence.
The W3C PROV family defines a model, serialisations and supporting definitions so that this information can be exchanged between very different systems12.
The FAIR principles ask the same of research data in general: metadata should be rich, carry a clear usage licence, be associated with detailed provenance and meet community standards13.
When evidence travels with each value, a user far downstream can judge it without calling the owner. When it is stripped away, every merged record becomes a matter of faith.
Corrections need the same path. If a calibration upstream turns out to be wrong, the record should show which values depended on it and which have since been reissued.
Evidence also protects owners. A station that publishes its quality flags and its calibration history can show that its data was sound, even when someone else's analysis went wrong.
Built from open standards that already exist
None of this needs a new invention. The building blocks are published, open and in use, and the work lies in joining them so that owners can take part without giving up control.
Provenance has had a W3C model since 2013, and sensor observations have had an OGC web model since 20161214.
A timeline from 2012 to 2030 with the W3C provenance model, the FAIR principles, OGC SensorThings, zero trust architecture, the WMO Information System 2.0 specifications, the remote attestation architecture and the 2027 early warnings target.
The FAIR principles for data were published in 2016, and zero trust architecture and remote attestation give the vocabulary for admitting stations on evidence1389.
What remains is discipline. Every owner publishes in open models, keeps time to a shared reference, proves the identity of its stations and sends the evidence with every value.
Start small. A single station that keeps good time, describes itself openly and publishes its evidence is already ready for the wider network, even before anyone else connects to it.
Nexus Observatory Inc. designs observing sites and software around these open standards, so that each station can join a wider network from the day it is installed.
The result is a network that no single party owns and every party can rely on. Many owners, one picture, and a record that anyone can check.
Questions and answers
Does one network mean one owner or one cloud?
No. Each owner keeps its own stations and systems and publishes through shared services, as the WMO Information System does with brokers, caches and a catalogue11.
Why not trust stations that sit inside a known network?
Because location and ownership are not evidence. Zero trust architecture grants no implicit trust on either basis and authenticates each subject and device before a session8.
Glossary
- Federation
- Separate networks that keep their own systems and share data through common services and open formats.
- Provenance
- Information about the entities, activities and people involved in producing data12.
- Remote attestation
- A process in which a device produces evidence about its own state for a verifier to appraise9.
References
- Standard or official statistic: WMO Integrated Global Observing System (WIGOS). World Meteorological Organization. community.wmo.int (accessed )
- Standard or official statistic: GBON: Global Basic Observing Network. World Meteorological Organization. community.wmo.int (accessed )
- Peer-reviewed or intergovernmental: Early Warnings for All. United Nations. un.org (accessed )
- Standard or official statistic: OGC SensorThings API Standard. Open Geospatial Consortium. ogc.org (accessed )
- Standard or official statistic: OGC SensorThings API Part 1: Sensing, Version 1.1. Open Geospatial Consortium. . docs.ogc.org (accessed )
- Standard or official statistic: OGC API Features Standard. Open Geospatial Consortium. ogc.org (accessed )
- Standard or official statistic: Time metrology. BIPM. bipm.org (accessed )
- Government or regulator: SP 800-207: Zero Trust Architecture. NIST. . csrc.nist.gov (accessed )
- Standard or official statistic: RFC 9334: Remote ATtestation procedureS (RATS) Architecture. IETF. . rfc-editor.org (accessed )
- Standard or official statistic: WMO Information System (WIS). World Meteorological Organization. community.wmo.int (accessed )
- Standard or official statistic: Guide to the WMO Information System, Volume II: WIS 2.0. World Meteorological Organization. wmo-im.github.io (accessed )
- Standard or official statistic: PROV-Overview: An Overview of the PROV Family of Documents. W3C. . w3.org (accessed )
- Peer-reviewed or intergovernmental: The FAIR Guiding Principles for scientific data management and stewardship. Scientific Data. . pmc.ncbi.nlm.nih.gov (accessed )
- Standard or official statistic: OGC SensorThings API Part 1: Sensing, Version 1.0. Open Geospatial Consortium. . docs.ogc.org (accessed )
As of