GCRI · Water Nexus
Data and technical methods
The public technical tools of Water Nexus: the models and data behind them, how to reproduce a view and the uncertainty it carries.
The workspace for data and technical methods.
Build workspace
Water · Data and technical methods · Run R-7518 · Example interface, not a record
Runs
same inputs, versioned
| R-3125 | Hydrology and water | v7.2 | 0.47 | Running |
| R-5152 | Water and environmental | v8.7 | 0.73 | Passed |
| R-8820 | Geospatial information | v3.4 | 0.44 | Passed |
| R-8148 | Earth observation | v7.6 | 0.61 | Passed |
Model card
- Method
- Hydrology and water science
- Inputs
- Gauge network telemetry, Reanalysis precipitation
- Validation
- held-out period, skill reported
- Label
- MODELLED
Run log
- 00:00:57InfoIngest gauge network telemetry
- 00:03:12InfoSchema and licence checks passed
- 00:06:40WarnGap filled by interpolation, flagged
- 00:16:03DoneCalibration complete
- 00:21:55GateIndependent test queued
Water Nexus · Build workspace. Build workspace: example names and illustrative values, not a record.
What is published here.
Three questions every water tool should answer about itself.
- Which basin, period and spatial resolution it represents.
- Which inputs it uses, with evidence labels, and which it lacks.
- What decision it is fit for, and what it is not fit for (for example, a regional drought map is not a well-siting tool).
Released maps carry the indicator register; model descriptions are on models and scenarios.
How the process runs.
Process
Data and technical methods: Build, sign and accept
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.
01 Request and sources
- 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
- 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
02 Build and verify
- 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
- 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
- 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
- 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
03 Sign and admit
- 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
- 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
04 Accept
- 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
- 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.
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.
Working with the tools.
Analysis runs in Foundry for authorised projects. Public pages show released views only, each with its time and space reference and its rights.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Pages in Data and technical methods.
Questions and answers.
Can I use the data?
Contribute evidence from this page.
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.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
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.
Bring a method, a dataset or a question.
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.
Legal documents.
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.