--- title: "Pipelines and midstream monitoring | Nexus Observatory" description: "A pipeline crosses rivers, farms, faults and towns, and most of it is buried out of sight. Its operator must know where it leaks…" url: https://observatory.global/industries/energy/pipelines/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Energy](https://observatory.global/industries/energy/) / [Specialized fields](https://observatory.global/industries/energy/fields/) / **Pipelines and midstream** # Pipelines, watched from end to end. A pipeline crosses rivers, farms, faults and towns, and most of it is buried out of sight. Its operator must know where it leaks, whether its protection against corrosion works and whether the ground around it moves. An observation network along the right-of-way reads pressure and flow, cathodic protection, ground movement and stations, and keeps one record for the control room and the regulator. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Energy **Measurements**: 5 **Sources cited**: 7 1. Energy · Pipelines and midstream Hundreds of kilometres, mostly out of sight A pipeline is long, buried and exposed to everything along its route: corrosion, diggers, landslides and rivers. Its control room sees pressure and flow, but integrity depends on what happens between the stations. Observation along the right-of-way fills that gap with readings that are tied to the line itself. 2. What is measured Pressure, protection, ground and activity Pressure and flow are read at valve sites; cathodic protection potentials at test posts and rectifiers; ground movement and strain at slopes and crossings; activity on the right-of-way by acoustic sensing and cameras; gas, fire and machine condition at stations. Satellite radar adds the ground between sensors. InstrumentsPressure and flow · Cathodic protection · Slope and strain · Acoustic sensing · Cameras 3. The base node A node at every valve site Each valve site's base node reads instruments through an industrial gateway and hears test-post endpoints through a LoRaWAN gateway. It ties every reading to the line's stationing, signs it, keeps local trends and raises an alarm on a sudden change in pressure or flow. 4. Radio and links Links along the right-of-way LoRaWAN carries test-post and slope readings to valve sites. Satellite or 3GPP non-terrestrial links join remote valve sites to the control room, fibre laid with the pipe serves where it exists, and private networks serve stations and terminals. Each link is chosen per section from the survey. RadioLoRaWAN · Satellite · Fibre · Private LTE 5. How it works From a test post to the integrity record A test post's potential is read by its endpoint, sent over LoRaWAN to the valve site, tied to stationing and signed by the node, then carried over satellite to the record. There it joins the protection history of that section and raises a flag if protection falls short. 6. From order to operation · Order Scope the line and its risks The scope reads the operator's integrity management plan, high-consequence areas, known geohazards and leak detection approach. Nexus Observatory Inc. returns the sensor plan per section, the radio design along the right-of-way, the integration with the control room and a price per section and per station. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Walk the right-of-way Crews survey valve sites, test posts, crossings and slopes with the operator's integrity engineers, measure coverage for LoRaWAN and satellite, confirm power at each site and check landowner access. Every position is recorded against the pipeline's stationing so data and records line up. 8. From order to operation · Permits Landowners, crossings and the control room Work on the right-of-way follows landowner agreements, crossing permits and the operator's excavation and hot-work rules. Changes that touch the control room follow its management of change, so new alarms reach controllers only after review. Every agreement and approval is kept with the section it covers, so the next crew knows the conditions before arriving. 9. From order to operation · Build Build per site type Valve-site stations, test-post endpoints, slope sensors and station kits are built and tested by type, each enrolled with its identity and labelled with its stationing. Gateways are configured with the section they serve, so each reading arrives tied to its place on the line. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install section by section Gateways and backhaul go in first, then test-post endpoints, valve-site instruments, slope and crossing sensors and right-of-way cameras. Each installation is checked against the alignment sheets and photographed, and landowners are told what was installed. Gateways at valve sites are mounted inside existing fenced areas wherever possible. 11. From order to operation · Commission Commission against field readings Each node proves its identity, then remote cathodic protection readings are compared with a technician's manual readings, pressure and flow with the control system's values, and slope sensors with survey. Alarms are tested from the field to the control room console. 12. From order to operation · Operate One line, one picture Controllers see pressure, flow and alarms in context; integrity engineers see protection potentials, ground movement and crossing status along the line; station teams see machine condition. Every alarm and response is logged for review against the operator's procedures. Alarms reach the right person first: controllers for pressure, integrity staff for protection and ground. 13. From order to operation · Maintain Keep the record complete Endpoints are serviced on schedule, sensors are added where new geohazards are identified and software moves in rings. The integrity record built from these readings feeds the operator's inspection planning and its reports, year after year. Endpoints whose readings drift are flagged for a field check before their data is relied on. [Book field services](https://observatory.global/contact/field-service/) 14. Data products Products for control, integrity and prevention Controllers receive alarms with context; corrosion engineers receive protection records along the line; geotechnical engineers see ground movement at crossings; damage prevention teams receive right-of-way alerts; station teams see machine condition. All are tied to the same stationing and the same signed readings. [See the data products](https://observatory.global/data-products/) 15. Evidence An integrity record a regulator can read Every reading, alarm, response and change is signed and kept against the pipeline's stationing. Monitoring follows the operator's integrity management plan and the pipeline safety rules that apply, so inspectors can follow any conclusion back to the readings and the people who acted on them. Drawn against49 CFR Parts 192 and 195 · API RP 1130 · CSA Z662 · ISO 15589-1 16. What you get Structural and ground-movement monitoring GNSS, InSAR, tilt, strain and fibre sensing on bridges, dams, slopes, tailings and pipelines, with alert thresholds set by the owner. Delivered as managed service and data licence, for infrastructure, mining and pipeline operators, transport agencies. Scale: Asset portfolios. 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 pipelines and midstream 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 pipelines and midstream. 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 contextTransmission and gathering pipelines carry gas and liquids over long distances between producing fields, processing plants, storage and markets, driven by compressor and pump stations. Integrity management covers corrosion, third-party damage, geohazards and leaks. Control rooms watch pressure and flow continuously, and regulations set duties for leak detection, inspection and emergency response. Hazards - Leaks and ruptures from corrosion, cracking or third-party damage - Failure of cathodic protection against corrosion - Ground movement, landslides and river scour at crossings - Unauthorised excavation near the line - Fire and gas release at compressor and pump stations **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 | | --- | --- | --- | --- | | Pressure and flow for leak detection | Inlet, outlet and block valve sites along the line | Continuous | 12 | | Cathodic protection potentials | Test posts and rectifiers along the line | Continuous remote reads, with surveys on the schedule the rules set | 34 | | Ground movement and pipe strain | Slopes, faults and river crossings identified as geohazards | Continuous, with satellite radar between stations | 56 | | Third-party activity on the right-of-way | High-consequence areas, by acoustic sensing, cameras and patrols | Continuous | 4 | | Station gas, fire and machine condition | Compressor and pump stations | Continuous | 7 | **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 valve-site station: pressure and flow through an industrial gateway, cathodic protection test points on a battery endpoint, and a node that signs and keeps every value. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A section between stations: valve sites, test posts, geohazard sensors and right-of-way cameras, joined by LoRaWAN and satellite to the control room. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every section and station of the line run as one fleet, with one integrity record and one alarm policy. [Managed offers →](https://observatory.global/industries/energy/solutions/) 4. **04** Network Interconnected systems and the regulator's reviewers read one federated record, each with the access the agreement gives them. [The open protocol →](https://observatory.global/protocol/) - **01** Flow meter - **02** Acoustic sensor - **03** LPWAN endpoint - **04** LoRaWAN gateway - **05** OT gateway (OPC UA, Modbus) - **06** Edge node (Wedge) - **07** 3GPP NTN terminal - **08** Solar array - **09** Pole Radio and links ### LoRaWAN Cathodic protection test posts and slope sensors sit every few kilometres with no power; battery endpoints report through gateways at valve sites. Radio and links ### Satellite Valve sites in remote country reach the control room over satellite or 3GPP non-terrestrial links. Radio and links ### Fibre Where fibre is laid with the pipe, it carries station data and can also serve as a distributed acoustic sensor. Radio and links ### Private LTE Around stations and terminals, a private network carries cameras, crew devices and control data. Edge computeStation and valve-site nodes keep pressure and flow trends locally and raise an alarm on a sudden change, while the control room's leak detection compares the whole line. PowerValve sites use station power where available and solar elsewhere; test-post endpoints run on batteries for long periods between visits. **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. Pipelines and midstream: data path – of 08 01 Instruments Measurement with sensor identity andcalibration 02 Field radio 03 Gateway 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 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)DNP3 (IEEE 1815)OGC SensorThings API 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment Cathodic protection test points Not in the reference kit 01 Flow meter SDI-12 · RS-485 · Ethernet 02 Acoustic sensor SDI-12 · RS-485 · Ethernet 03 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 04 LoRaWAN gateway Ethernet · RF · GNSS antenna 05 OT gateway (OPC UA, Modbus) Ethernet · RS-485 · CAN · AnalogueI/O 06 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 07 3GPP NTN terminal Ethernet · USB · RS-232 Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Leak and pressure alarmswith context Cathodic protection recordsalong the line Geohazard and crossingmonitoring Right-of-way activity alerts Station condition records 08 Solar array RS-485 09 Pole Analogue I/O RS-485 · Modbus Ethernet LoRaWAN Ethernet Ethernet · opc-ua Ethernet 3GPP NTN 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 | **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 | | 03 | **LPWAN endpoint** Battery-powered endpoint on LoRaWAN, NB-IoT or LTE-M that carries one or more sensors. | Analogue I/OSDI-12RS-485 | LoRaWAN, OMA LwM2M, CoAP | Internal battery, Energy harvesting | | 04 | **LoRaWAN gateway** Multi-channel LoRaWAN gateway that forwards uplinks to a network server and schedules downlinks within duty limits. | EthernetRFGNSS antenna | LoRaWAN, MQTT 5 | PoE, 12 V DC | | 05 | **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 | | 06 | **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 | | 07 | **3GPP NTN terminal** Terminal using the 3GPP non-terrestrial network air interface (NR-NTN or IoT-NTN) to reach a satellite access node directly. | EthernetUSBRS-232 | 3GPP NR or IoT NTN, OMA LwM2M, MQTT 5 | 12 V DC, Internal battery | | 08 | **Solar array** PV modules with charge controller sized to the site's load and climate. | RS-485 | Modbus | — | | 09 | **Pole** Utility, street or dedicated pole with clamp positions. | — | — | — | 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 the line and its risks The scope reads the operator's integrity management plan, high-consequence areas, known geohazards and leak detection approach. Nexus Observatory Inc. returns the sensor plan per section, the radio design along the right-of-way, the integration with the control room and a price per section and per station. 45 2. 02 Survey Walk the right-of-way Crews survey valve sites, test posts, crossings and slopes with the operator's integrity engineers, measure coverage for LoRaWAN and satellite, confirm power at each site and check landowner access. Every position is recorded against the pipeline's stationing so data and records line up. 3. 03 Permits Landowners, crossings and the control room Work on the right-of-way follows landowner agreements, crossing permits and the operator's excavation and hot-work rules. Changes that touch the control room follow its management of change, so new alarms reach controllers only after review. Every agreement and approval is kept with the section it covers, so the next crew knows the conditions before arriving. 4. 04 Build Build per site type Valve-site stations, test-post endpoints, slope sensors and station kits are built and tested by type, each enrolled with its identity and labelled with its stationing. Gateways are configured with the section they serve, so each reading arrives tied to its place on the line. 5. 05 Install Install section by section Gateways and backhaul go in first, then test-post endpoints, valve-site instruments, slope and crossing sensors and right-of-way cameras. Each installation is checked against the alignment sheets and photographed, and landowners are told what was installed. Gateways at valve sites are mounted inside existing fenced areas wherever possible. 6. 06 Commission Commission against field readings Each node proves its identity, then remote cathodic protection readings are compared with a technician's manual readings, pressure and flow with the control system's values, and slope sensors with survey. Alarms are tested from the field to the control room console. 7. 07 Operate One line, one picture Controllers see pressure, flow and alarms in context; integrity engineers see protection potentials, ground movement and crossing status along the line; station teams see machine condition. Every alarm and response is logged for review against the operator's procedures. Alarms reach the right person first: controllers for pressure, integrity staff for protection and ground. 8. 08 Maintain Keep the record complete Endpoints are serviced on schedule, sensors are added where new geohazards are identified and software moves in rings. The integrity record built from these readings feeds the operator's inspection planning and its reports, year after year. Endpoints whose readings drift are flagged for a field check before their data is relied on. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Leak and pressure alarms with context** Control room controllers - **Cathodic protection records along the line** Corrosion and integrity engineers, regulators - **Geohazard and crossing monitoring** Integrity and geotechnical engineers - **Right-of-way activity alerts** Damage prevention teams - **Station condition records** Station maintenance teams Integration - **Pipeline SCADA and leak detection** Field data arrives through industrial gateways over OPC UA and DNP3 alongside the control system's own points. - **Integrity management and GIS** Readings are tied to pipeline stationing and delivered as layers in the operator's GIS. - **Damage prevention** Right-of-way alerts reach the one-call and patrol workflows. Exchanged through OPC UA (IEC 62541), DNP3 (IEEE 1815), OGC SensorThings API. **07** Questions buyers ask ## Before you scope it. Does this replace our leak detection system? No. It adds field data and alarms beside the control room's leak detection, which remains the system of record. Can remote cathodic protection reads replace annual surveys? Remote reads add continuous data between surveys; whether they replace any survey depends on the rules that apply to the line. How are geohazards found between sensors? Satellite radar interferometry covers the line between ground sensors and flags movement for a closer look. Can we start with high-consequence areas? Yes. Most programmes start with high-consequence areas and known geohazards, then extend along the line. **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** [API RP 1130: Computational Pipeline Monitoring for Liquids](https://www.api.org/) American Petroleum Institute 2. **2** [49 CFR Part 195: Transportation of hazardous liquids by pipeline](https://www.ecfr.gov/current/title-49/part-195) US Pipeline and Hazardous Materials Safety Administration (eCFR) 3. **3** [ISO 15589-1: Cathodic protection of pipeline systems, on-land pipelines](https://www.iso.org/search.html?q=ISO%2015589) International Organization for Standardization 4. **4** [49 CFR Part 192: Transportation of natural and other gas by pipeline](https://www.ecfr.gov/current/title-49/part-192) US Pipeline and Hazardous Materials Safety Administration (eCFR) 5. **5** [CSA Z662: Oil and gas pipeline systems](https://www.csagroup.org/) CSA Group 6. **6** [Copernicus Sentinel-1 radar mission](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1) European Space Agency 7. **7** [ISO 20816: Mechanical vibration, measurement and evaluation of machine vibration](https://www.iso.org/search.html?q=ISO%2020816) International Organization for Standardization **09** Related ## Use cases and solutions. [Solution Structural and ground-movement monitoringGNSS, InSAR, tilt, strain and fibre sensing on bridges, dams, slopes, tailings and pipelines, with alert thresholds set by the owner.Solutions for energy →](https://observatory.global/industries/energy/solutions/#infrastructure-monitoring) [Solution Transport and logistics corridor sensingRoad weather, rail condition, port and cold-chain sensing along corridors, with connectivity where coverage ends.Solutions for energy →](https://observatory.global/industries/energy/solutions/#corridor-sensing) [Solution Satellite and non-terrestrial backhaulLEO and GEO backhaul, 3GPP non-terrestrial integration and direct-to-device fallbacks for remote sites.Solutions for energy →](https://observatory.global/industries/energy/solutions/#ntn-backhaul) **10** Energy: specialized fields ## Other fields of this industry. [Specialized field Upstream oil and gasMethane detection and quantification at wellpads and facilities, flare and tank monitoring, wellhead flow and pressure, on satellite and private links for sites with no one on them.The full field →](https://observatory.global/industries/energy/upstream-oil-gas/) [Specialized field Thermal power plantsContinuous emissions, machine condition, cooling water and plant weather for gas, coal and biomass plants, with an industrial network that keeps the control system separate and secure.The full field →](https://observatory.global/industries/energy/thermal-generation/) [Specialized field Hydropower and damsDam safety instruments, reservoir and river levels, inflow forecasting and downstream warning, with links that keep working in the flood the dam is there to hold.The full field →](https://observatory.global/industries/energy/hydropower/) [Specialized field Wind farmsWind resource and power performance, turbine condition, icing, lightning and wildlife monitoring, from the first met mast to an operating farm on one record.The full field →](https://observatory.global/industries/energy/wind/) [Specialized field Solar power plantsIrradiance, module temperature, soiling, inverter output and plant weather to international monitoring classes, for bankable performance ratios and fewer surprises in operation.The full field →](https://observatory.global/industries/energy/solar/) [Specialized field Transmission networksLine ratings from measured weather and conductor state, wildfire and vegetation watch, substation automation and synchrophasor timing, on private LTE, microwave and fibre along the corridor.The full field →](https://observatory.global/industries/energy/transmission/) [Specialized field Distribution networks and the grid edgeFeeder and transformer monitoring, distributed energy resources, fault location and outage evidence, on a utility private network that reaches every pole and substation.The full field →](https://observatory.global/industries/energy/distribution/) ### 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/)**Energy** . The grid edge, observed.[Talk to us](https://observatory.global/contact/) Energy - [Overview](https://observatory.global/industries/energy/) - [Explainer](https://observatory.global/industries/energy/explainer/) - [Specialized fields](https://observatory.global/industries/energy/fields/) - [Use cases](https://observatory.global/industries/energy/use-cases/) - [Solutions](https://observatory.global/industries/energy/solutions/) - [Platforms](https://observatory.global/industries/energy/platforms/) - [Resources](https://observatory.global/industries/energy/resources/) - [Contact](https://observatory.global/industries/energy/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/)