Nexus Observatory Sign inCreate account
Nexus Observatory

/

Data & licensing

/

Publication

Routes from licensed to open release.

Publication, inside Data & licensing: OGC SensorThings API, OGC API – Connected Systems, observation models and ontologies, OPC UA information models and more. Every item is traced to its specification, from OGC SensorThings API Part 1 (Sensing) 1.1 to OGC SensorThings API Part 2 (Tasking Core), and runs on the open Observatory Protocol.

Plan with usArchitectureThe protocol
Technologies
9
At the frontier
0
Protocol functions
3 of 8
Industries served
19

Reference design, drawn to scale · drag to turn · hover a part

01What it is

Open standards and interoperability.

How observations move from the edge into stores, catalogues and APIs with their provenance, licence and residency attached, and how they interoperate through open standards and the open Observatory Protocol. Each technology below carries what it is, what we do with it, and the standard it is drawn against.

Data, software and interoperability

OGC SensorThings API

Open API for things, sensors, datastreams and observations, plus tasking.

We design, integrate and operate.

OGC SensorThings API Part 1 (Sensing) 1.1 · OGC SensorThings API Part 2 (Tasking Core)

Data, software and interoperability

OGC API – Connected Systems

System, deployment, procedure and datastream resources with commands, built on OGC API – Features.

We design, integrate and operate.

OGC API – Connected Systems Part 1 (Feature Resources) · Part 2 (Dynamic Data)

Data, software and interoperability

Observation models and ontologies

The conceptual model and semantic web ontology for observations and samples.

We design.

ISO 19156:2023 (observations, measurements and samples) · W3C/OGC SOSA/SSN

Data, software and interoperability

OPC UA information models

Industrial information models and companion specifications for equipment data.

We design and integrate.

IEC 62541 series · OPC UA companion specifications

Data, software and interoperability

Context information management

Linked-data APIs for entities and their context in cities and infrastructure.

We integrate.

ETSI GS CIM 009 (NGSI-LD API)

Data, software and interoperability

Asset administration shell

Standard digital representation of an industrial asset and its submodels.

We integrate.

IEC 63278-1 (asset administration shell structure)

Data, software and interoperability

Hydro and met data encodings

Agency encodings for water and weather data exchange.

We integrate.

OGC WaterML 2.0 · WMO BUFR (FM 94)

Data, software and interoperability

Node roles and profiles

The roles a node can play and the profiles that bundle its capabilities.

We design and integrate.

Observatory Protocol specification (Nexus Consortium)

Data, software and interoperability

Enrolment and admission state machines

The states a device and a provider move through, from manifest to admitted for scope.

We design, integrate and operate.

Observatory Protocol specification (Nexus Consortium)

02Architecture

Where it sits, and what it speaks.

Publication draws on 1 domain and 8 layers of the spectrum; the highlighted layers carry this area. It speaks 3 of the protocol’s 8 core functions.

Ingest and streaming

8

Storage and data lakes

6

Metadata, provenance and catalogues

8

Open standards and interoperability

7

APIs and SDKs

7

Licensing, residency and governance

8

Digital twins and observability

7

Open protocol interfaces and federation

8

01JoinIdentity, attestation quote, signed policy.

02AdmitAdmitted for a stated scope, nothing wider.

03DescribeWhat, where, how and by whom, with calibration.

04TimeOne clock across the grid, with its error bound.

05ObserveEvery value with quality and provenance.

06QualifyTested against the specification, state on record.

07FederateSigned exchange across grids and trust domains.

08OrchestrateSoftware and configuration by signed plan.

03On the grid

Every site joins one observing grid.

The open networks on the grid today, over real relief and the geodesic cells we count them into, filtered to the hydrology domain this area serves. A site built here enrols into the same grid.

04In the field

Where this runs, sector by sector.

5 deployment scenarios from the sector research that rely on publication.

Government and public safety

Urban street-flood sensor network

Open-hardware depth sensors with open data and alerts to emergency management.
Communities and rural

Indigenous-owned community cellular

Unused 800 MHz and 1900 MHz spectrum through an access-licensing framework with a priority window for Indigenous applicants.
Scientific

Citizen seismology and school seismographs

Compact seismographs feeding open data networks.
Environment and climate

Biodiversity measurement with acoustics and camera traps

Acoustic baselines as a biodiversity data source; no registry methodology accepting acoustic data was found.
Energy

Bankable solar and wind measurement campaigns

Accepted standards, traceable calibration and transparent data handling.

05Open and enterprise

Open by default. Enterprise by contract.

The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.

Open, on the main site

  • Open tier
  • Dataset cards

Enterprise, on this site

  • Paid tiers
  • Residency by contract

06The rest of the line

Data & licensing, area by area.

Data & licensing

Products

Observations, derived layers and evidence.
Data & licensing

Tiers

Research, commercial, enterprise, government.
Data & licensing

API

One interface for every product.
Data & licensing

Residency

Where data lives, fixed by contract.

Bring us the site.

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

Talk to uscontact@observatory.global

Routes from licensed to open release.

Publication, inside Data & licensing: OGC SensorThings API, OGC API – Connected Systems, observation models and ontologies, OPC UA information models and more. Every item is traced to its specification, from OGC SensorThings API Part 1 (Sensing) 1.1 to OGC SensorThings API Part 2 (Tasking Core), and runs on the open Observatory Protocol.

01What it is

02Architecture

Where it sits, and what it speaks.

03On the grid

04In the field

Where this runs, sector by sector.

05Open and enterprise

Open by default. Enterprise by contract.

The open counterpart lives on the main site for anyone to read and run. The enterprise service is designed, deployed and operated with you, under contract.

Open, on the main site
    Enterprise, on this site
      06The rest of the line

      Bring us the site.