--- title: "Drinking water treatment and networks | Nexus Observatory" description: "A drinking water utility must deliver safe water every hour and lose as little of it as possible on the way. Quality sensors from source to network…" url: https://observatory.global/industries/water/drinking-water/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Water](https://observatory.global/industries/water/) / [Specialized fields](https://observatory.global/industries/water/fields/) / **Drinking water treatment and networks** # Drinking water, watched from source to tap. A drinking water utility must deliver safe water every hour and lose as little of it as possible on the way. Quality sensors from source to network, pressure and flow by district, acoustic leak listening and treatment plant data give operators an early view of contamination, bursts and losses, on an observation network kept apart from plant control and secured end to end. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Water **Measurements**: 5 **Sources cited**: 5 1. Water · Drinking water treatment and networks Safe water, every hour, with less lost A drinking water utility runs treatment plants, reservoirs and a buried network that must deliver safe water every hour. Contamination can enter anywhere from source to tap, and leaks quietly lose treated water. Observation gives operators early warning of both, without touching the control systems that run the plant. 2. What is measured Quality, pressure, flow and sound Quality sensors measure turbidity, disinfectant residual, pH and conductivity from intake to network; flow and pressure sensors measure each district; acoustic loggers listen for leaks at night; level sensors watch reservoirs. Laboratory compliance samples remain the measurements of record. Each reading carries its point. InstrumentsQuality sensors · Flow · Pressure · Leak loggers · Reservoir levels 3. The base node Event detection at the edge Industrial gateways read quality and flow sensors over Modbus. The edge node signs every value, runs event detection that compares readings across the network, flags burst patterns and passes data out through a security gateway that lets nothing back in. 4. Radio and links City radio and utility fibre Leak loggers and chamber sensors report from batteries over LoRaWAN; district stations use cellular; plants and major sites use utility fibre; utilities with private networks use them for stations and crews. Every connection sits in a defined security zone. Each zone's conduits are reviewed. LinksLoRaWAN · Public cellular · Fibre · Private LTE 5. How it works From a sensor to a response A falling disinfectant residual is read by the gateway, checked by the edge's event rules against nearby points, signed and passed through the security gateway to the historian. The alert reaches the quality team with its data and the actions the water safety plan sets out. 6. From order to operation · Order Scope from the water safety plan The scope reads the water safety plan, the district structure, the loss programme and the security architecture. Nexus Observatory Inc. returns a monitoring design per district and plant, the network separation plan, the integration with control systems and a price per district. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey districts and plants Crews visit district inlets, chambers, hydrants, reservoirs and plants with network and operations staff. They check access, power, coverage, existing instruments and security zones, and record each point against the utility's asset records. Chambers that flood or cannot be entered safely are noted, and alternative points are chosen before the design is fixed. 8. From order to operation · Permits Street works and security review Work in the street follows the highway authority's permits and traffic management. Every device placement is reviewed against the utility's security zones, and changes to plant systems follow management of change. Nothing is connected to plant networks until operations and security have signed off the design. 9. From order to operation · Build Build devices for chambers and plants Quality and pressure stations, leak loggers, gateways and edge nodes are built, hardened and tested, each enrolled with its identity and asset number so readings arrive tied to the right place in the network. Every device ships with its security configuration already applied and documented. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install district by district Installation proceeds district by district: inlet stations, quality points, leak loggers on hydrants and valves, reservoir levels and plant gateways. Each device is checked and photographed, and the asset record updated. Customers in affected streets are told about works in advance, and supply is not interrupted to install network sensors. 11. From order to operation · Commission Commission against samples Each device proves its identity, then quality sensors are compared with laboratory samples, pressure with gauges and flow with meters. Event detection rules run in observation before they alert, and alarms are tested end to end. Results are signed into each device's record. 12. From order to operation · Operate Early warning of quality and loss Operators see quality across the network, pressure and flow by district and leak alerts with their locations. A quality event arrives with its data and the actions the water safety plan sets out, and every response is logged. Leak alerts reach repair crews as work orders. 13. From order to operation · Maintain Clean, calibrate and close losses Quality sensors are cleaned and calibrated on schedule, leak loggers are moved to new districts as losses fall and software moves in rings. The loss record shows what was found, fixed and saved. Security updates follow the utility's programme and are tested before they reach the fleet. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For quality, network and regulators Water quality teams and health authorities receive quality series and alerts; network managers see pressure, flow and losses by district; repair crews receive leak locations; regulators receive compliance records. All come from the same signed readings. Each carries its calibration record and quality flags. [See the data products](https://observatory.global/data-products/) 15. Evidence Evidence from source to tap Calibrations, laboratory comparisons, every alert, every response and every change are signed and kept. Monitoring supports the water safety plan and the drinking water rules that apply, loss work follows recognised water audit methods, and security follows the industrial security series. Drawn againstWHO Guidelines for Drinking-water Quality · Directive (EU) 2020/2184 · AWWA M36 · ISA/IEC 62443 16. What you get Environmental and permit monitoring Emissions, water quality, noise and dust monitoring for permit conditions, with traceable calibration and evidence bundles. Delivered as managed service and data licence, for industrial operators, municipalities, regulators. Scale: Site to portfolio. Service levels are written as numbers you can measure on your own dashboard. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan drinking water treatment and networks with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for drinking water treatment and networks. 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 deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) **01** The place and its hazards ## Where it runs, and what can go wrong. Operating contextDrinking water utilities abstract from rivers, reservoirs or aquifers, treat the water and distribute it through networks of mains, pumps and storage divided into metered districts. Water safety plans manage risk from catchment to tap, and drinking water rules set quality parameters and monitoring. Leaks waste a large share of treated water in many networks, and control systems are critical infrastructure. Hazards - Contamination at the source, in treatment or in the network - Bursts and leaks, visible and hidden - Low pressure and supply interruptions - Treatment failures, such as disinfection or turbidity excursions - Cyber intrusion into plant and network control **02** What must be measured ## What, where, how often, and under which rules. Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below. | Measurement | Where | Cadence | Sources | | --- | --- | --- | --- | | Turbidity, disinfectant residual, pH and conductivity | Source intakes, treatment stages, reservoirs and network points | Continuous | 123 | | Pressure and flow by district | District inlets and critical points | Continuous | 4 | | Leak noise | Hydrants, valves and fittings, by acoustic loggers | Nightly listening, with alerts | 4 | | Reservoir and tank levels | Service reservoirs and towers | Continuous | 1 | | Laboratory compliance samples | Sampling points the rules define | On the regulatory schedule | 23 | **03** The observation stack ## From one base unit to a network. The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol. 1. **01** Base unit A network station: quality and pressure sensors read through an industrial gateway, and a node that signs every value. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A district: inlet flow and pressure, quality points, leak loggers and reservoir levels, joined to the utility's edge. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every district, reservoir and plant run as one fleet, with one water quality and loss record. [Managed offers →](https://observatory.global/industries/water/solutions/) 4. **04** Network Utilities, health authorities and regulators read federated records, each with the access the rules give them. [The open protocol →](https://observatory.global/protocol/) - **01** Flow meter - **02** Water quality sonde - **03** Acoustic sensor - **04** OT gateway (OPC UA, Modbus) - **05** Edge node (Wedge) - **06** Zero-trust gateway - **07** Fibre terminal - **08** Battery case - **09** Shelter Radio and links ### LoRaWAN Leak loggers and small sensors in chambers report from batteries, often through city LoRaWAN networks. Radio and links ### Public cellular District stations and reservoirs without utility fibre report over cellular. Radio and links ### Fibre Treatment plants and major sites join the utility's network over fibre. Radio and links ### Private LTE Utilities with private networks carry station data and crew traffic on spectrum they control. Edge computeAn edge node compares quality across the network with event detection rules, flags flow and pressure patterns that suggest bursts and passes data out through a security gateway. PowerChamber and hydrant devices run on batteries; district stations and reservoirs use site power with battery backup. **04** How it works ## From the instrument to the product. One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks. Drinking water treatment and networks: data path – of 08 01 Instruments Measurement with sensor identity andcalibration 02 Gateway 03 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 04 Local network 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products OPC UA (IEC 62541)OGC SensorThings APIISA/IEC 62443 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment 01 Flow meter SDI-12 · RS-485 · Ethernet 02 Water quality sonde SDI-12 · RS-485 · Ethernet 03 Acoustic sensor SDI-12 · RS-485 · Ethernet 04 OT gateway (OPC UA, Modbus) Ethernet · RS-485 · CAN · AnalogueI/O 05 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 06 Zero-trust gateway Ethernet · Fibre 07 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Network water quality with eventalerts District pressure, flow and losses Leak locations for repair Compliance records 08 Battery case USB 09 Shelter RS-485 · Modbus RS-485 · Modbus Ethernet Ethernet · opc-ua Ethernet Fibre Fibre From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation. | Item | Equipment | Data ports | Protocols | Power in | | --- | --- | --- | --- | --- | | 01 | **Flow meter** Open-channel or pipe flow meter (Doppler, ultrasonic, electromagnetic). | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 02 | **Water quality sonde** Multi-parameter sonde for temperature, conductivity, pH, dissolved oxygen and turbidity. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 03 | **Acoustic sensor** Sound level meter, acoustic event detector or infrasound array element. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 04 | **OT gateway (OPC UA, Modbus)** Read-only bridge from industrial fieldbuses and controllers (Modbus, OPC UA, DNP3, IEC 61850, CAN) to the site network, behind a security boundary. | EthernetRS-485CANAnalogue I/O | OPC UA, Modbus, DNP3 (IEEE 1815), IEC 61850 (MMS, GOOSE), MQTT 5 | 24 V DC | | 05 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains | | 06 | **Zero-trust gateway** Gateway that terminates encrypted tunnels, enforces segmentation and gates every flow by identity and policy. | EthernetFibre | — | 12 V DC, AC mains | | 07 | **Fibre terminal** Optical network terminal or media converter that lands fibre backhaul at a site. | FibreEthernet | IEEE 1588 PTP | 12 V DC, 48 V DC, AC mains | | 08 | **Battery case** Portable battery pack with DC outputs for field kits. | USB | Modbus | AC mains, HV DC, USB PD | | 09 | **Shelter** Walk-in shelter or container with HVAC, fire detection and power distribution. | — | — | — | How it scales 01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding. **Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. **Telemetry**: OpenTelemetry OTLP. **Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. **Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. **Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. **Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. **Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. **05** From order to operation ## Every step, from the first call to a running site. The same crew and the same record carry the work from scope to maintenance. 1. 01 Order Scope from the water safety plan The scope reads the water safety plan, the district structure, the loss programme and the security architecture. Nexus Observatory Inc. returns a monitoring design per district and plant, the network separation plan, the integration with control systems and a price per district. 1 2. 02 Survey Survey districts and plants Crews visit district inlets, chambers, hydrants, reservoirs and plants with network and operations staff. They check access, power, coverage, existing instruments and security zones, and record each point against the utility's asset records. Chambers that flood or cannot be entered safely are noted, and alternative points are chosen before the design is fixed. 3. 03 Permits Street works and security review Work in the street follows the highway authority's permits and traffic management. Every device placement is reviewed against the utility's security zones, and changes to plant systems follow management of change. Nothing is connected to plant networks until operations and security have signed off the design. 5 4. 04 Build Build devices for chambers and plants Quality and pressure stations, leak loggers, gateways and edge nodes are built, hardened and tested, each enrolled with its identity and asset number so readings arrive tied to the right place in the network. Every device ships with its security configuration already applied and documented. 5. 05 Install Install district by district Installation proceeds district by district: inlet stations, quality points, leak loggers on hydrants and valves, reservoir levels and plant gateways. Each device is checked and photographed, and the asset record updated. Customers in affected streets are told about works in advance, and supply is not interrupted to install network sensors. 6. 06 Commission Commission against samples Each device proves its identity, then quality sensors are compared with laboratory samples, pressure with gauges and flow with meters. Event detection rules run in observation before they alert, and alarms are tested end to end. Results are signed into each device's record. 7. 07 Operate Early warning of quality and loss Operators see quality across the network, pressure and flow by district and leak alerts with their locations. A quality event arrives with its data and the actions the water safety plan sets out, and every response is logged. Leak alerts reach repair crews as work orders. 8. 08 Maintain Clean, calibrate and close losses Quality sensors are cleaned and calibrated on schedule, leak loggers are moved to new districts as losses fall and software moves in rings. The loss record shows what was found, fixed and saved. Security updates follow the utility's programme and are tested before they reach the fleet. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Network water quality with event alerts** Water quality teams and health authorities - **District pressure, flow and losses** Network managers - **Leak locations for repair** Leak detection and repair crews - **Compliance records** Regulators Integration - **Control system and historian** Data reaches the historian over OPC UA through a security gateway. - **Laboratory system** Compliance samples are joined to sensor series. - **Work management and GIS** Leak alerts open work orders tied to the asset and map. Exchanged through OPC UA (IEC 62541), OGC SensorThings API, ISA/IEC 62443. **07** Questions buyers ask ## Before you scope it. Do sensors replace compliance sampling? No. Compliance follows the regulatory sampling; sensors add continuous early warning between samples. Does this connect to our control system? Only through a security gateway that lets data out, under the utility's security programme. How are leaks found? Acoustic loggers listen at night, flow and pressure patterns narrow down the area, and crews confirm before digging. Can we start with one district? Yes. One district is a complete site; others repeat it. **08** Resources ## The sources behind this page. Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does. 1. **1** [Guidelines for Drinking-water Quality, and water safety plans](https://www.who.int/) World Health Organization 2. **2** [Directive (EU) 2020/2184 on the quality of water intended for human consumption](https://eur-lex.europa.eu/eli/dir/2020/2184/oj) European Union · 2020 3. **3** [40 CFR Part 141: National Primary Drinking Water Regulations](https://www.ecfr.gov/current/title-40/part-141) US Environmental Protection Agency (eCFR) 4. **4** [AWWA Manual M36: Water Audits and Loss Control Programs](https://www.awwa.org/) American Water Works Association 5. **5** [ISA/IEC 62443 series: security for industrial automation and control systems](https://www.isa.org/standards-and-publications/isa-standards/isa-iec-62443-series-of-standards) ISA and IEC **09** Related ## Use cases and solutions. [Solution Environmental and permit monitoringEmissions, water quality, noise and dust monitoring for permit conditions, with traceable calibration and evidence bundles.Solutions for water →](https://observatory.global/industries/water/solutions/#environmental-compliance) [Solution Operational-technology assurance for observing sitesIdentity, attestation, segmentation and monitoring for instruments and edge nodes, with evidence for audits.Solutions for water →](https://observatory.global/industries/water/solutions/#ot-site-assurance) [Solution Municipal sensing and connectivity layersCity-wide LPWAN or private 5G as a shared layer for public sensors and services.Solutions for water →](https://observatory.global/industries/water/solutions/#municipal-connectivity) **10** Water: specialized fields ## Other fields of this industry. [Specialized field Rivers and flood warningRiver level and flow, rainfall and cameras at gauging stations, flood forecasts and warnings issued by the authority, on links that keep working when the river rises.The full field →](https://observatory.global/industries/water/rivers-floods/) [Specialized field Groundwater and aquifersWater levels, salinity and abstraction in monitoring and production wells, on battery endpoints and LoRaWAN, for aquifer management, licensing and drought planning.The full field →](https://observatory.global/industries/water/groundwater/) [Specialized field Wastewater and sewer networksSewer levels and overflow events, pumping station status, treatment plant effluent and receiving water quality, to cut overflows and prove compliance.The full field →](https://observatory.global/industries/water/wastewater/) [Specialized field Lakes and reservoirsBuoys and profilers for temperature, oxygen and algae, inflow and level, satellite views of blooms, so water suppliers and lake managers act before a bloom closes a source or a beach.The full field →](https://observatory.global/industries/water/lakes-reservoirs/) ### Bring us the site. Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details. [Plan a deployment](https://observatory.global/contact/deployment/) [Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) [Request a quote](https://observatory.global/contact/hardware-quote/) [Nexus Observatory](https://observatory.global/)**Water** . Every catchment, gauged.[Talk to us](https://observatory.global/contact/) Water - [Overview](https://observatory.global/industries/water/) - [Explainer](https://observatory.global/industries/water/explainer/) - [Specialized fields](https://observatory.global/industries/water/fields/) - [Use cases](https://observatory.global/industries/water/use-cases/) - [Solutions](https://observatory.global/industries/water/solutions/) - [Platforms](https://observatory.global/industries/water/platforms/) - [Resources](https://observatory.global/industries/water/resources/) - [Contact](https://observatory.global/industries/water/contact/) Platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Consortium](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/)