--- title: "Excavations and tunnelling monitoring | Nexus Observatory" description: "A deep excavation or a tunnel drive under a city moves the ground around it, and the buildings, pipes and railways on top." url: https://observatory.global/industries/infrastructure/excavations-tunnelling/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Infrastructure](https://observatory.global/industries/infrastructure/) / [Specialized fields](https://observatory.global/industries/infrastructure/fields/) / **Excavations and tunnelling** # Excavations and tunnels, watched beside every neighbour. A deep excavation or a tunnel drive under a city moves the ground around it, and the buildings, pipes and railways on top. Automatic total stations, GNSS, inclinometers, piezometers and vibration sensors report to one record the designer, the contractor and the asset owners use to keep movement within its limits. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Infrastructure **Measurements**: 5 **Sources cited**: 4 1. Infrastructure · Excavations and tunnelling The ground moves, and so do the neighbours Digging a deep basement or driving a tunnel under a city moves the ground, and with it the buildings, pipes and railways above. The design predicts how much; the observational method checks it as the work advances. Readings that arrive in minutes, not days, let the team change the work before a neighbour is harmed. 2. What is measured Settlement, deflection, water and vibration Automatic total stations read prisms on façades for settlement and movement, in-place inclinometers follow walls and ground, piezometers watch the water around the works, and GNSS stations hold the reference outside the zone. Geophones on sensitive buildings record vibration from piling and tunnelling. InstrumentsAutomatic total stations · Inclinometers · Piezometers · GNSS · Geophones 3. The base node Every point against its prediction The zone's node computes movement from each total station cycle and GNSS solution, compares every point with its predicted value and its amber and red triggers, and alerts the designer, the contractor and the asset owner the moment a trigger is reached, signing every value. 4. Radio and links LoRaWAN from the boreholes Piezometers and inclinometers in boreholes reach a gateway over LoRaWAN at very low power, with no cables across a busy site. Total stations, GNSS and the gateway reach the project over cellular, and long tunnel drives use the tunnel's own fibre underground. LinksLoRaWAN · Public cellular · Fibre 5. How it works From a moving façade to a changed sequence As the excavation deepens, a total station sees a façade prism settle toward its amber trigger. The node compares it with the prediction and alerts the designer, who changes the excavation sequence and adds props. Settlement slows, and the record keeps every reading and decision. 6. From order to operation · Order Scope the works and the neighbours The scope reads the design's predicted movements and trigger levels, the zone of influence, the buildings, railways and utilities within it, and their owners' limits. Nexus Observatory Inc. returns the instrument plan, the communications design, the reporting to each asset owner and a price per point and per month. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Condition survey before work Crews survey every building in the zone with the designer: condition, cracks, foundations and where prisms and geophones can be fixed. They choose stable buildings for total stations with lines of sight, borehole positions, and GNSS reference sites outside the zone, and record coverage and power. 8. From order to operation · Permits Owners, access and limits Each building, railway and utility owner agrees access, fixings and the limits on its asset, often through formal agreements. The monitoring plan, triggers and actions are agreed with the designer and the client, and every agreement is kept with the zone's record. 9. From order to operation · Build Build to the monitoring plan Total stations, GNSS receivers, piezometers, inclinometers, geophones, endpoints and nodes are built, tested together and enrolled with their identities. Each point is configured with its predicted movement and triggers from the design, and labelled with its point code. Configurations are checked on the bench first. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install and baseline before excavation Crews fix prisms and geophones, drill and install piezometers and inclinometers, mount total stations on stable buildings and set GNSS references outside the zone. Every point is surveyed in, and a baseline period completes before the first excavation or the first ring. 11. From order to operation · Commission Prove the baseline Each node proves its identity. Total station cycles are checked for closure, GNSS for stability, piezometers against manual dips and inclinometers against a manual probe survey. Amber and red alerts are tested to the designer, the contractor and each asset owner. 12. From order to operation · Operate Build by the observational method Designers compare every point with its prediction as the work advances. Amber triggers bring review and changes to the work, red triggers stop it until the cause is understood. Asset owners see movements on their assets, and every decision is kept with its readings. 13. From order to operation · Maintain Keep lines of sight and boreholes Prisms are cleaned and replaced when blocked, total stations checked against references, borehole sensors read manually on schedule, and points re-established when works destroy them. Monitoring continues until movements stabilise, and every change is recorded. Spares are kept on site, so a lost point is restored within the shift. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For designers, contractors and owners Designers and contractors receive movement against prediction and triggers; designers, contractors and asset owners receive amber and red alerts; building, railway and utility owners receive their assets' movement reports; clients and insurers receive close-out records. Each product carries its survey and calibration. [See the data products](https://observatory.global/data-products/) 15. Evidence The observational method, on record Every reading, trigger, review and change is signed and kept. Instrumentation follows the geotechnical monitoring standard, design follows the observational method of the geotechnical code, vibration follows the building vibration standard, and records join the project information, so owners and insurers can check them. Drawn againstISO 18674 · EN 1997 · DIN 4150-3 · ISO 19650 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 excavations and tunnelling 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 excavations and tunnelling. 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 contextDeep basements, shafts and tunnels are designed with predicted ground movements and trigger levels, and built under the observational method: monitor, compare with prediction, and act when triggers are reached. Owners of nearby buildings, railways and utilities set their own limits, and monitoring follows geotechnical instrumentation standards. Hazards - Settlement damaging nearby buildings and utilities - Excessive wall deflection in deep excavations - Water inflow and loss of ground - Vibration from piling and tunnelling - Readings that arrive too late to change the work **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 | | --- | --- | --- | --- | | Settlement and movement of buildings | Prisms on façades read by automatic total stations | Continuous cycles, faster near the face | 12 | | Wall and ground deflection | In-place inclinometers in walls and boreholes | Continuous | 1 | | Pore water pressure | Piezometers around the excavation and above the tunnel | Continuous | 1 | | Ground movement at reference points | GNSS stations outside the zone of influence | Continuous | 1 | | Vibration | Geophones on sensitive buildings and assets | Continuous, events recorded in full | 34 | **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 monitoring point: a piezometer or inclinometer on a LoRaWAN endpoint, or a total station and GNSS on an edge node. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A works zone: points around the excavation or along the drive, total stations on stable buildings and cellular to the project. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every works zone of a project run as one fleet, with one trigger process and one record. [Managed offers →](https://observatory.global/industries/infrastructure/solutions/) 4. **04** Network Designers, contractors and asset owners share movement data through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** GNSS geodetic station - **02** Water level gauge - **03** Vibration and condition monitor - **04** LPWAN endpoint - **05** LoRaWAN gateway - **06** Edge node (Wedge) - **07** Cellular modem/router - **08** Battery case Radio and links ### LoRaWAN Piezometers and inclinometers in boreholes around the works reach a gateway at very low power, without cables across the site. Radio and links ### Public cellular Total stations, GNSS and the gateway reach the project over cellular. Radio and links ### Fibre Long tunnel drives use the tunnel's own fibre for points underground. Edge computeThe zone's node computes movement from each total station cycle and GNSS, compares every point with its predicted value and trigger levels, and alerts the designer and contractor at once when an amber or red trigger is reached. PowerTotal stations and nodes run on site or building power with batteries; borehole sensors on batteries for the life of the works. **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. Excavations and tunnelling: 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 ISO 18674OGC SensorThings APIISO 19650 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment In-place inclinometers andvibrating-wire piezometers Not in the reference kit 01 Water level gauge SDI-12 · RS-485 · Ethernet 02 GNSS geodetic station Ethernet · GNSS antenna · 1PPS/10MHz 03 Vibration and condition monitor Analogue I/O · RS-485 · Ethernet 04 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 05 LoRaWAN gateway Ethernet · RF · GNSS antenna 06 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 07 Cellular modem/router Ethernet · USB · RS-232 Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Movement against prediction andtriggers Amber and red alerts Asset movement reports Close-out records 08 Battery case USB Analogue I/O SDI-12 LoRaWAN Ethernet Ethernet RS-485 Ethernet LTE/NR 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 | **Water level gauge** Radar, pressure or float gauge for river, lake, reservoir or tide level. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 02 | **GNSS geodetic station** Continuously operating GNSS station on a stable monument for geodesy, deformation and atmospheric water vapour. | EthernetGNSS antenna1PPS/10 MHz | NTP with NTS | 12 V DC | | 03 | **Vibration and condition monitor** Accelerometer-based vibration and temperature sensor for rotating machinery and structural condition monitoring. | Analogue I/ORS-485Ethernet | Modbus, OPC UA, MQTT 5 | 12 V DC | | 04 | **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 | | 05 | **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 | | 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 | **Cellular modem/router** LTE or NR modem or router that uses a public carrier or private network as backhaul. | EthernetUSBRS-232 | 3GPP E-UTRA air interface, 3GPP NR air interface, OMA LwM2M | 12 V DC, PoE | | 08 | **Battery case** Portable battery pack with DC outputs for field kits. | USB | Modbus | AC mains, HV DC, USB PD | 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 works and the neighbours The scope reads the design's predicted movements and trigger levels, the zone of influence, the buildings, railways and utilities within it, and their owners' limits. Nexus Observatory Inc. returns the instrument plan, the communications design, the reporting to each asset owner and a price per point and per month. 2 2. 02 Survey Condition survey before work Crews survey every building in the zone with the designer: condition, cracks, foundations and where prisms and geophones can be fixed. They choose stable buildings for total stations with lines of sight, borehole positions, and GNSS reference sites outside the zone, and record coverage and power. 3. 03 Permits Owners, access and limits Each building, railway and utility owner agrees access, fixings and the limits on its asset, often through formal agreements. The monitoring plan, triggers and actions are agreed with the designer and the client, and every agreement is kept with the zone's record. 4. 04 Build Build to the monitoring plan Total stations, GNSS receivers, piezometers, inclinometers, geophones, endpoints and nodes are built, tested together and enrolled with their identities. Each point is configured with its predicted movement and triggers from the design, and labelled with its point code. Configurations are checked on the bench first. 5. 05 Install Install and baseline before excavation Crews fix prisms and geophones, drill and install piezometers and inclinometers, mount total stations on stable buildings and set GNSS references outside the zone. Every point is surveyed in, and a baseline period completes before the first excavation or the first ring. 1 6. 06 Commission Prove the baseline Each node proves its identity. Total station cycles are checked for closure, GNSS for stability, piezometers against manual dips and inclinometers against a manual probe survey. Amber and red alerts are tested to the designer, the contractor and each asset owner. 7. 07 Operate Build by the observational method Designers compare every point with its prediction as the work advances. Amber triggers bring review and changes to the work, red triggers stop it until the cause is understood. Asset owners see movements on their assets, and every decision is kept with its readings. 23 8. 08 Maintain Keep lines of sight and boreholes Prisms are cleaned and replaced when blocked, total stations checked against references, borehole sensors read manually on schedule, and points re-established when works destroy them. Monitoring continues until movements stabilise, and every change is recorded. Spares are kept on site, so a lost point is restored within the shift. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Movement against prediction and triggers** Designers and contractors - **Amber and red alerts** Designers, contractors and asset owners - **Asset movement reports** Building, railway and utility owners - **Close-out records** Clients and insurers Integration - **Project information model** Points and readings are linked to the model under ISO 19650 practice. - **Asset owners' systems** Each owner receives its assets' movements in the format agreed. - **Design checks** Readings are exported for back-analysis against the design predictions. Exchanged through ISO 18674, OGC SensorThings API, ISO 19650. **07** Questions buyers ask ## Before you scope it. Who sets the triggers? The designer, from the predicted movements and each asset owner's limits. What happens at a red trigger? The work stops at that location until the cause is understood, as the plan says. Can a railway owner see its track? Yes. Each owner receives its assets' movements as agreed. When does monitoring end? When movements have stabilised and the designer and owners agree. **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** [ISO 18674: Geotechnical investigation and testing, geotechnical monitoring by field instrumentation](https://www.iso.org/) International Organization for Standardization 2. **2** [EN 1997 (Eurocode 7): Geotechnical design, including the observational method](https://www.cencenelec.eu/) European Committee for Standardization 3. **3** [DIN 4150-3: Vibrations in buildings, effects on structures](https://www.din.de/) Deutsches Institut für Normung 4. **4** [ISO 4866: Mechanical vibration and shock, vibration of fixed structures, guidelines for measurement](https://www.iso.org/) 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 infrastructure →](https://observatory.global/industries/infrastructure/solutions/#infrastructure-monitoring) [Solution Physical condition data for lenders and asset ownersEO and sensor evidence on the physical state of collateral and assets: flood extent, subsidence, construction progress, land cover.Solutions for infrastructure →](https://observatory.global/industries/infrastructure/solutions/#asset-physical-data) **10** Infrastructure: specialized fields ## Other fields of this industry. [Specialized field Construction sitesDust, noise and vibration at the site boundary, wind for cranes and lifts, and site cameras, on cellular from the hoarding, so a site keeps its permit limits and answers its neighbours with evidence.The full field →](https://observatory.global/industries/infrastructure/construction-sites/) [Specialized field Structural health of major structuresVibration, strain, movement and wind on long-span bridges, towers, stadium roofs and tall buildings in service, on fibre and an industrial network, so engineers see how a structure behaves between inspections.The full field →](https://observatory.global/industries/infrastructure/structural-health/) [Specialized field Levees and coastal defencesPore pressure and seepage, settlement, water levels, waves and overtopping on levees, dikes and sea walls, on LoRaWAN and microwave, so defence managers see weak sections before the flood finds them.The full field →](https://observatory.global/industries/infrastructure/levees-coastal/) [Specialized field Heritage buildingsCrack and tilt movement, vibration from traffic and works, and indoor climate for collections in historic buildings in use, on LoRaWAN with nothing drilled that does not have to be, so conservation decisions rest on evidence.The full field →](https://observatory.global/industries/infrastructure/heritage-buildings/) ### 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/)**Infrastructure** . Assets that report their own condition.[Talk to us](https://observatory.global/contact/) Infrastructure - [Overview](https://observatory.global/industries/infrastructure/) - [Explainer](https://observatory.global/industries/infrastructure/explainer/) - [Specialized fields](https://observatory.global/industries/infrastructure/fields/) - [Use cases](https://observatory.global/industries/infrastructure/use-cases/) - [Solutions](https://observatory.global/industries/infrastructure/solutions/) - [Platforms](https://observatory.global/industries/infrastructure/platforms/) - [Resources](https://observatory.global/industries/infrastructure/resources/) - [Contact](https://observatory.global/industries/infrastructure/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/) - [Open governance](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/)