--- title: "Structural health of major structures | Nexus Observatory" description: "Long-span bridges, towers, stadium roofs and tall buildings move with wind, traffic, crowds and temperature every day. Accelerometers, strain sensors…" url: https://observatory.global/industries/infrastructure/structural-health/ 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/) / **Structural health of major structures** # Major structures, measured in service. Long-span bridges, towers, stadium roofs and tall buildings move with wind, traffic, crowds and temperature every day. Accelerometers, strain sensors, GNSS and weather stations report to one record that shows engineers how a structure behaves between inspections and after every storm or event. [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 · Structural health of major structures Between inspections A long-span bridge, a tower or a stadium roof is inspected on a cycle and lives through every storm, rush hour and crowd in between. Damage that starts between inspections, or behaviour that changes after an event, is invisible without measurement. Continuous evidence lets engineers see how the structure is really behaving. 2. What is measured Vibration, strain, movement and wind Accelerometers at key points record vibration and natural frequencies. Strain gauges on critical members follow load and fatigue, displacement sensors watch bearings and joints, GNSS follows towers and mid-span, and anemometers and temperature sensors record the conditions the structure answers to. InstrumentsAccelerometers · Strain gauges · Displacement sensors · GNSS · Anemometers and temperature 3. The base node Normal behaviour, learned The structure's node turns raw signals into natural frequencies, strain cycles and displacements, and compares them with the structure's normal behaviour for the temperature and load at that moment. Changes beyond normal, and storms or earthquakes, raise alerts, and every value is signed. 4. Radio and links On the structure's own fibre Major structures carry their own fibre for operations, and monitoring rides it with the bandwidth vibration needs. Points far along a span or high on a tower reach the network over a private radio, and the public cellular network is the second path to the owner. LinksFibre · Private LTE · Public cellular 5. How it works From a storm to an engineer's report A storm passes over a long-span bridge. Accelerometers and GNSS record its response, the node compares frequencies and displacements with normal behaviour, and finds them back to normal once the wind drops. The owner's engineer receives the post-event report within hours, with the evidence attached. 6. From order to operation · Order Scope the structure and the questions The scope reads the structure's design, inspection history, known concerns and the questions the owner needs answered. Nexus Observatory Inc. returns the instrument plan with the reasons for each point, the network and data design, the analysis to be delivered and a price per structure and per year. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Climb and inspect with the engineer Crews survey with the owner's structural engineer: access to decks, towers, roofs and floors, critical members for strain, points for accelerometers, sites for GNSS and anemometers at height, and routes for cables. They record the structure's own network and power at each point. 8. From order to operation · Permits Owner, operations and safety Access follows the structure's operating rules: lane closures, roof access permits, rope access plans. The owner's engineer approves every fixing to the structure, and the operator agrees when work can happen. Every approval is kept with the structure's record. Crews follow the structure’s safety rules. 9. From order to operation · Build Build for the structure Accelerometers, strain and displacement sensors, GNSS receivers, weather stations, the industrial gateway and the node are built, tested together and enrolled with their identities. Each point is configured with its location and sensitivity, and labelled for maintenance. Configurations are checked on the bench first. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install in planned closures Crews install in planned closures or by rope access: strain gauges on members, accelerometers at key points, displacement sensors at bearings and joints, GNSS and anemometers at height. Cables are routed on the structure's trays, and every point is photographed and located. 11. From order to operation · Commission Learn the structure's normal Each device proves its identity. Sensors are checked in place, the first weeks of data are analysed to find the structure's natural frequencies and normal behaviour with temperature and load, and alerts are set and tested with the owner's engineer. 12. From order to operation · Operate Engineering decisions on evidence Engineers see how the structure behaves under wind, traffic, crowds and temperature, with changes in its normal behaviour flagged. After storms and events they receive a report within hours, and inspections and assessments are planned with the record in hand. 13. From order to operation · Maintain Keep the record continuous Points are checked on schedule and at each inspection, sensors replaced when they drift, and the normal behaviour model updated after repairs or changes of use. Every change is recorded, so the long series that structural health depends on stays continuous. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For engineers, owners and operators Structural engineers receive behaviour against normal; owners and engineers receive post-event reports; assessment engineers receive fatigue and strain cycle records; operators receive comfort and serviceability indicators. Each product carries the sensors, their calibration and the normal model behind it. Reports are dated and versioned. [See the data products](https://observatory.global/data-products/) 15. Evidence Evidence for assessment Every reading, analysis, alert and report is signed and kept. Monitoring follows the international standard for condition monitoring of structures, assessment uses the basis for existing structures, and records join the structure's information model, so engineers and insurers can rely on them for decades. Drawn againstISO 16587 · ISO 4866 · ISO 13822 · 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 structural health of major structures 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 structural health of major structures. 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 contextOwners of major structures inspect them on a cycle and assess them when loads, use or condition change. Structural health monitoring adds continuous evidence: how the structure vibrates, strains and moves under real wind, traffic and crowds, and whether that changes. Assessment of existing structures has its own international basis. Hazards - Fatigue and damage developing between inspections - Excessive vibration under wind or crowds - Movement of bearings and joints - Storm and earthquake damage that must be assessed fast - Monitoring data no one can interpret **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 | | --- | --- | --- | --- | | Vibration and natural frequencies | Accelerometers at key points of decks, towers, roofs and floors | Continuous, with modal analysis | 12 | | Strain | Critical members and connections | Continuous | 1 | | Displacement | GNSS on towers and mid-span, displacement sensors at bearings and joints | Continuous | 1 | | Wind and temperature | Anemometers at height and temperature sensors on the structure | Continuous | 3 | | Assessment indicators | The whole structure | After events and on the assessment cycle | 4 | **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 measurement point: accelerometers, strain and displacement sensors on an industrial gateway with an edge node. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site A structure: every point on its fibre and network, GNSS and weather at height, with a secure link to the owner. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every monitored structure of an owner run as one fleet, with one record. [Managed offers →](https://observatory.global/industries/infrastructure/solutions/) 4. **04** Network Owners, engineers and researchers exchange structural data through open standards. [The open protocol →](https://observatory.global/protocol/) - **01** Vibration and condition monitor - **02** GNSS geodetic station - **03** Compact weather station - **04** OT gateway (OPC UA, Modbus) - **05** Edge node (Wedge) - **06** Fibre terminal Radio and links ### Fibre Major structures carry their own fibre for operations; monitoring rides it with the bandwidth that vibration needs. Radio and links ### Private LTE Points far along a span or high on a tower reach the network without new cables. Radio and links ### Public cellular A second path to the owner when the structure's own network is down. Edge computeThe structure's node computes natural frequencies, strain cycles and displacements from the raw signals, compares them with the structure's normal behaviour for the temperature and load, and raises alerts after storms, earthquakes and unusual events. PowerPoints run on the structure's power with batteries; remote points on solar where no supply reaches. **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. Structural health of major structures: data path – of 07 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 Backhaul Commit with transactional outbox andpublish, delivered at least once 05 Site Consumer inbox deduplicates and applieseach record once into governed data 06 Data store Governed product through API, map orexport, correction-aware 07 Products ISO 16587ISO 13822OPC UA 01 Vibration and condition monitor Analogue I/O · RS-485 · Ethernet Strain gauges and displacementsensors Not in the reference kit 02 GNSS geodetic station Ethernet · GNSS antenna · 1PPS/10MHz 03 Compact weather station 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 Fibre terminal Fibre · Ethernet Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Behaviour against normal Post-event reports Fatigue and strain cycle records Comfort and serviceability indicators Ethernet RS-485 · Modbus Ethernet RS-485 Ethernet · opc-ua 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 | **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 | | 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 | **Compact weather station** All-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | 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 | **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 | 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 structure and the questions The scope reads the structure's design, inspection history, known concerns and the questions the owner needs answered. Nexus Observatory Inc. returns the instrument plan with the reasons for each point, the network and data design, the analysis to be delivered and a price per structure and per year. 4 2. 02 Survey Climb and inspect with the engineer Crews survey with the owner's structural engineer: access to decks, towers, roofs and floors, critical members for strain, points for accelerometers, sites for GNSS and anemometers at height, and routes for cables. They record the structure's own network and power at each point. 3. 03 Permits Owner, operations and safety Access follows the structure's operating rules: lane closures, roof access permits, rope access plans. The owner's engineer approves every fixing to the structure, and the operator agrees when work can happen. Every approval is kept with the structure's record. Crews follow the structure’s safety rules. 4. 04 Build Build for the structure Accelerometers, strain and displacement sensors, GNSS receivers, weather stations, the industrial gateway and the node are built, tested together and enrolled with their identities. Each point is configured with its location and sensitivity, and labelled for maintenance. Configurations are checked on the bench first. 5. 05 Install Install in planned closures Crews install in planned closures or by rope access: strain gauges on members, accelerometers at key points, displacement sensors at bearings and joints, GNSS and anemometers at height. Cables are routed on the structure's trays, and every point is photographed and located. 6. 06 Commission Learn the structure's normal Each device proves its identity. Sensors are checked in place, the first weeks of data are analysed to find the structure's natural frequencies and normal behaviour with temperature and load, and alerts are set and tested with the owner's engineer. 1 7. 07 Operate Engineering decisions on evidence Engineers see how the structure behaves under wind, traffic, crowds and temperature, with changes in its normal behaviour flagged. After storms and events they receive a report within hours, and inspections and assessments are planned with the record in hand. 4 8. 08 Maintain Keep the record continuous Points are checked on schedule and at each inspection, sensors replaced when they drift, and the normal behaviour model updated after repairs or changes of use. Every change is recorded, so the long series that structural health depends on stays continuous. **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Behaviour against normal** Structural engineers - **Post-event reports** Owners and engineers - **Fatigue and strain cycle records** Assessment engineers - **Comfort and serviceability indicators** Operators Integration - **Asset management** Indicators and reports join the structure's record in the asset management system. - **Inspection planning** Findings are linked to inspection items and members. - **Digital model** Points and data are linked to the structure's information model under ISO 19650 practice. Exchanged through ISO 16587, ISO 13822, OPC UA. **07** Questions buyers ask ## Before you scope it. Does monitoring replace inspection? No. It adds continuous evidence between inspections and helps plan them. How do you tell damage from temperature? The node learns normal behaviour with temperature and load, and flags changes beyond it. How fast after a storm? A report reaches the owner within hours of the event. Can the data be used for assessment? Yes, as measured evidence under the assessment of existing structures. **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 16587: Mechanical vibration and shock, performance parameters for condition monitoring of structures](https://www.iso.org/) International Organization for Standardization 2. **2** [ISO 4866: Mechanical vibration and shock, vibration of fixed structures, guidelines for measurement](https://www.iso.org/) International Organization for Standardization 3. **3** [Guide to Instruments and Methods of Observation (WMO-No. 8)](https://library.wmo.int/) World Meteorological Organization 4. **4** [ISO 13822: Bases for design of structures, assessment of existing structures](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) [Solution Drone survey and 3D site twinsSurvey campaigns planned to the ground sample distance, photogrammetry and LiDAR, and site twins kept current.Solutions for infrastructure →](https://observatory.global/industries/infrastructure/solutions/#drone-twins) **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 Excavations and tunnellingSettlement and movement of the ground and nearby buildings, pore pressure, wall deflection and vibration during deep excavations and tunnel drives, with automatic total stations and GNSS, under the observational method.The full field →](https://observatory.global/industries/infrastructure/excavations-tunnelling/) [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/)