FAIR data assessment
Datasets are assessed against the FAIR principles using published metrics, and improvements to identifiers, metadata, licences and formats are prioritised.
GCRI · Data and Compute
Data engineering, interoperability and stewardship is the second method this platform stewards. It designs how data are collected, described, stored, linked, versioned and shared, so that they can be found, trusted and reused across institutions and over time.
Data engineering, interoperability and stewardship cover the pipelines, standards and governance that make data usable and trustworthy. They determine whether information from different sectors can be combined for joint risk assessment. In data and compute and energy, sound data engineering allows hazard, exposure and financial data to be linked consistently. It supports transparent and repeatable analysis of interconnected risk. The canonical description is on the STEM Commons.
Datasets are assessed against the FAIR principles using published metrics, and improvements to identifiers, metadata, licences and formats are prioritised.
Catalogues are described with DCAT and shared vocabularies so that datasets from different agencies can be searched and combined.
Automated checks validate schema, ranges, completeness and consistency at each stage, with failures logged and reported to data owners.
Night lights, population density and true-colour imagery over the contiguous United States, from NASA GIBS. Each layer carries its own date.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
Connected activity, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
Connected activity, framed on the contiguous United States.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.
Layers and dates
Datasets and records used by data engineering, interoperability and stewardship on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Repository and catalogue metadata | FAIR assessment | OBSERVED |
| Schema and vocabulary registries | Interoperability | Published statistics |
| Validation logs | Quality | OBSERVED |
Assembled from the Nexus Standards area profile Digital, telecom and platforms: the hazards it names, the systems and sectors that carry the loss, the controls that dampen it and the data that observe it. Choose the components, pick an initiating hazard and step through the cascade. The Map view places the run on an example geography with open data. Every coupling weight is a stated assumption you can change. A teaching model, not a forecast, an assessment or a certification. To model a place of your own choosing, open the full System Builder.
Hazards
Systems and couplings
Controls
NS-0 Constitution and principlesNS-9 Contextual UNIs (deployments, instances, programme instances)NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)NS-12 Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)NRS-H86 Hazard family: Telecom and data-centre failure (NHS-1 infra.digital)NRS-H54 Hazard family: Signal and platform disruption (NHS-1 cyber.platform)NRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)NRS-H94 Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)NRS-T8 Software and supply-chain integrity riskNRS-X6 Cyber and digital security riskObservation
Example geography
Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.
| Check | How it is done |
|---|---|
| Metadata completeness | Required metadata fields are checked for every dataset |
| Identifier resolution | Persistent identifiers are tested to resolve |
| Validation coverage | Quality checks cover every critical field |
Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
The data classes behind data engineering and stewardship and what is recorded about each before it is used.
| Data class | Provenance recorded | Resolution stated | Licence checked |
|---|---|---|---|
| Satellite imagery, optical and radar | sensor, processing level, acquisition date | pixel size and revisit | per scene |
| Reanalysis and climate model output | model, experiment, member, version | grid and time step | per release |
| In-situ sensors and gauges | station, instrument, calibration record | point and sampling rate | per network |
| Population and asset exposure | method, vintage, input sources | cell size and unit | per release |
| Boundaries and reference geography | producer, edition, date | scale | per edition |
Process explorer · Process
10 steps·4 stages·2 gates
Process
An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.
The programme year · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.
Data and Compute stewards data engineering, interoperability and stewardship for the Consortium and reviews how it is applied across platforms.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.