> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/systems/nxs-eop.md). # NXS-EOP NXS-EOP, the earth observation, imagery, terrain and observational digital twins system of the Nexus ecosystem: purpose, rooms, inputs and outputs, areas, standards and boundaries. {% hint style="info" %} This page is generated from the twenty-system charters, the system profiles, the interface and authority registers, the room register, the areas of work, the systems article of the constitution set and the programme spine. Do not edit it in GitBook: change the source and export again. {% endhint %} **NXS-EOP** is one of the twenty systems of the Nexus ecosystem: the earth observation, imagery, terrain and observational digital twins system. It is described here as a system of the ecosystem, with its purpose, its rooms, what it receives and provides, the areas it serves, the standards that apply and its boundaries. ## Purpose and context Earth-observation pipelines and hazard layers. Its domain is Earth observation, acquisition, geospatial processing and observational products. A typical setting is an agricultural and flood-monitoring area observed by multiple satellite products. ## What it is the authority for | Record | What the system must keep | | ------------------- | ------------------------------------------------------------------------ | | aoi | Preserve CRS, polygon validity and observation support. | | acquisition window | Distinguish requested, planned and delivered acquisitions. | | sensor product spec | Declare bands, processing level, resolution, orbit and nodata semantics. | | quality mask | Carry cloud, shadow, coverage and registration uncertainty. | | processing recipe | Record parameters, calibration, inputs and output lineage. | ## Rooms and areas of work Every system has ten rooms: eight shared rooms, which work the same way across systems with this system's domain, and two specialist rooms. | Room | Kind | Purpose | | ----------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | Station | Shared | The system's home: posture of the system's own records, freshness, refusals and next actions; never a summary of another system's truth | | Mission | Shared | Mission and task work for the system's domain, linked to Universe missions and Project OS plans | | Builder | Shared | Composition of the system's artifacts and configurations from admitted packages (NXS-STU, NXS-FAC and NXS-NXQ boundaries apply) | | Maps | Shared | Spatial views of the system's records and NXS-GRX products, under the boundary licence gate | | Data | Shared | The system's datasets, sources and lineage as NXS-GRX products or system-owned records | | Commons | Shared | Shared methods, standards, templates and reusable artifacts, including Nexus Standards (NXS, a programme of the Nexus Consortium) participation | | Reports | Shared | Reports and editions built from the system's evidence, with cutoffs and correction history | | Knowledge | Shared | Institutional knowledge, records, runbooks and learning linked to NXS-HUB | | Acquisition | Specialist | Records: observation requirement, acquisition plan, acquisition order, observation delivery | | Change | Specialist | Records: change study, preprocessing record, change detection run, change feature, change product | **Kinds of work it carries:** AOI monitoring; EO product pipelines; Imagery Product; Change Detection; Terrain/Surface Product; EO Hazard Product; Observational Twin Layer; AOI monitoring programmes; Imagery archives; Tasking campaigns; Urban growth watches; Asset footprint watches; Linear corridor watches; Ground deformation watches; Mine site monitorings; Shoreline and coastal asset watches; Land change audits; Deforestation-free sourcing watches; Crop condition watches; Reservoir and surface water watches; Protected area watches; Flood mapping services; Wildfire and burned area watches; Drought stress monitors; Post-event damage assessments; Terrain and surface models; Observational twin layers. **This system in the Nexus model.** Generated from the Nexus Standards index and the programme spine; statuses are registry statuses, never adoption or certification. | | | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Descriptor | Earth observation, imagery, terrain and observational digital twins | | In the programme | Built, simulated and prepared in the [Foundry pillar](/organization/programme/foundry.md); its records serve the other pillars through the handoffs of [the programme year](/organization/programme/the-programme-year.md), and the competent authority decides outside the programme. | | System profile | [NRS-S7](https://nexustandards.com/standards/nrs/#nrs-s7): NXS-EOP (Earth observation and digital twins) (status OPEN) | | Nexus Risk Standards that apply | 11 in 5 series: core: [NRS-C3](https://nexustandards.com/standards/nrs/#nrs-c3); nexus-stream: [NRS-N1](https://nexustandards.com/standards/nrs/#nrs-n1), [NRS-N3](https://nexustandards.com/standards/nrs/#nrs-n3), [NRS-N5](https://nexustandards.com/standards/nrs/#nrs-n5); system: [NRS-S7](https://nexustandards.com/standards/nrs/#nrs-s7); technology: [NRS-T3](https://nexustandards.com/standards/nrs/#nrs-t3), [NRS-T6](https://nexustandards.com/standards/nrs/#nrs-t6); cross-cutting: [NRS-X1](https://nexustandards.com/standards/nrs/#nrs-x1), [NRS-X3](https://nexustandards.com/standards/nrs/#nrs-x3), [NRS-X5](https://nexustandards.com/standards/nrs/#nrs-x5), [NRS-X12](https://nexustandards.com/standards/nrs/#nrs-x12) | | Nexus Reports technology streams | GSP Earth observation and space; DTW Digital twins and simulation | ## Inputs What it receives, and from whom. Each interface carries its context (estate, tenant, workspace, purpose, jurisdiction, time and place) and is checked under the policy authority. | From | What it receives | | ------------------------------------------- | -------------------------------- | | [NXS-GRX](/organization/systems/nxs-grx.md) | admitted source/context products | ## Outputs What it provides, and to whom. Consumers read projections; the system stays the authority for its own records and their corrections. | To | What it provides | | ------------------------------------------- | --------------------------------------- | | [NXS-GRX](/organization/systems/nxs-grx.md) | EO-derived products | | [NXS-EWS](/organization/systems/nxs-ews.md) | hazard/EO features | | [NXS-NSF](/organization/systems/nxs-nsf.md) | authorization/policy evaluation request | | the evidence fabric | append consequential receipt/evidence | ## Interfaces with other systems Beyond its interfaces, it relies on fact families owned elsewhere: context history root (the time-and-place context fabric). ## Areas it serves | Area | Category | What the area covers | | ------------------------------------------------------ | ----------- | --------------------------------------------------------------- | | [Early warning](/organization/systems/areas.md) | Management | From forecast to early action, for every hazard | | [Risk assessment](/organization/systems/areas.md) | Research | Multi-hazard national baselines, dependencies and evidence gaps | | [Earth observation](/organization/systems/areas.md) | Technology | Satellite and geospatial evidence for risk decisions | | [Insurance resilience](/organization/systems/areas.md) | Finance | Protection gaps and risk transfer questions | | [Sustainable finance](/organization/systems/areas.md) | Finance | Disclosure, taxonomies and resilience investment evidence | | [Resilient recovery](/organization/systems/areas.md) | Development | Loss and damage, recovery and building back better | ## Standards that apply Every record of the system is identified through the UNI identifier fabric of Nexus Standards (NS-1), and its public name follows the Nexus Standards naming rules. The areas it serves reference these external standards; naming a standard records where it is referenced and is not a claim of certification, accreditation, conformance or endorsement. | Standard | Issuer | Year | Use | | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | ---- | ----------------------------------------------------- | | Sendai Framework 2015-2030, Global Target G | UNDRR | 2015 | Availability of and access to early warning | | Early Warnings for All initiative | United Nations Secretary-General with WMO, UNDRR, ITU and IFRC | 2022 | Four pillars of people-centred early warning, to 2027 | | Common Alerting Protocol (CAP) 1.2 | OASIS, adopted as ITU-T X.1303 | 2010 | Interoperable alert message format | | Multi-Hazard Early Warning Systems: A Checklist | World Meteorological Organization (WMO) | 2018 | Structured readiness review | | IEC 31010 Risk management, Risk assessment techniques | International Electrotechnical Commission and ISO (IEC/ISO) | 2019 | Choosing assessment techniques | | IPCC Sixth Assessment Report, Working Group II | Intergovernmental Panel on Climate Change (IPCC) | 2022 | Risk as hazard, exposure, vulnerability and response | | Words into Action: National Disaster Risk Assessment | UNDRR | 2017 | National assessment process | | SpatioTemporal Asset Catalog (STAC) 1.0 | STAC community, an Open Geospatial Consortium community standard | 2021 | Searchable geospatial catalogues | | OGC API, Features, Part 1: Core | Open Geospatial Consortium (OGC) | 2019 | Web access to geospatial features | | CEOS Analysis Ready Data (CEOS-ARD) | Committee on Earth Observation Satellites (CEOS) | 2017 | Analysis-ready product specifications | | Insurance Core Principles | International Association of Insurance Supervisors (IAIS) | 2019 | Supervisory context for insurance markets | | Application Paper on the Supervision of Climate-related Risks in the Insurance Sector | IAIS | 2021 | Climate risk in insurance supervision | | Insurance Development Forum | Public-private partnership of insurers and international organisations | 2015 | Comparator for protection-gap collaboration | | IFRS S1 and IFRS S2 Sustainability and climate-related disclosures | International Sustainability Standards Board (ISSB) | 2023 | Global baseline for disclosure | | Recommendations of the Taskforce on Nature-related Financial Disclosures | Taskforce on Nature-related Financial Disclosures (TNFD) | 2023 | Nature-related risk disclosure | | Taxonomy Regulation, Regulation (EU) 2020/852 | European Union | 2020 | Classification of sustainable activities | | Recommendations of the Task Force on Climate-related Financial Disclosures | Financial Stability Board (FSB) | 2017 | Foundation of climate disclosure | | Post-Disaster Needs Assessment guidelines | European Union, United Nations and World Bank | 2013 | Joint assessment methodology | | Fund for responding to Loss and Damage, operationalised | UNFCCC, COP28 | 2023 | Loss and damage finance architecture | | Santiago network for averting, minimizing and addressing loss and damage | UNFCCC | 2019 | Technical assistance for loss and damage | | Sendai Framework 2015-2030, Priority 4 (Build Back Better) | UNDRR | 2015 | Safer recovery and reconstruction | ## Governance boundaries Policy authority for the system sits with [NXS-NSF](/organization/systems/nxs-nsf.md); identifiers come from the UNI identifier fabric. The system exports read projections and commands through typed contracts, and no other system writes its records. It does not own, and never stands in for: * warnings (NXS-EWS) * risk methodology (NXS-NXS-GRX) **Method boundary.** Change assessment requires spatial co-registration, comparable measurements, uncertainty and validation. Cloud cover and missing scenes must not be interpreted as no change. Do not mistake registration error, missing data or cloud contamination for physical change. [All twenty systems](/organization/systems.md) ยท [Areas](/organization/systems/areas.md) *** *Generated page. It records names, roles and design for reading, not readiness: release is on hold, and nothing here is presented as ready, certified or official.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.therisk.global/organization/systems/nxs-eop.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.