GCRI · Foundry
Foundry
Public gateway to the technical work environment while keeping project permissions and privileged services within Foundry. Foundry is an established platform of The Global Centre for Risk and Innovation.
- STEM methods
- 6
- Canonical methods this field applies
- Topics
- 8
- Subject pages in the field
- Counterparts
- 1
- Platforms in shared fields across the network
- Report series
- 1
- Reports series it contributes to
The workspace for foundry.
Workspace and job console
Project space 12 · Cluster east · Example interface, not a record
- Jobs running34Active
- Queue wait, p505minNormal
- Runs today33111
- Quota used, % this month44Watch
Jobs
| J-81914 | Flood model ensemble | Project owner | 00:50:12 | Running |
| J-26094 | Tile render, zoom 0 to 12 | GIS workspace | 00:03:40 | Running |
| J-78537 | Evidence export | Model steward | 00:00:25 | Done |
| J-72519 | Agent tool call batch | Agent sandbox | 00:01:19 | Policy block |
Policy events
- 10:22GateAgent call needs human approval
- 10:27InfoRun record sealed
- 11:15WarnQuota at 80 pct for project
Foundry · Workspace and job console. Workspace and job console: example names and illustrative values, not a record.
What Foundry does.
A risk modelling environment is the combination of compute, data pipelines, models, access controls and records in which risk analyses are built and run. Foundry is designed as that environment for national risk models and digital twins, and its pages set out the risks inside such work, from silent data transformation to permission drift, overreaching agents and compute that fails when needed.
Its community
Engineers; model builders; researchers; technology operators; project owners.
Its methods
System specifications; APIs; geospatial model workflows; authorisation.
Its outputs
Capability catalogue; installation guidance; public technical examples.
A cascade through interdependent networks.
A hazard footprint takes out co-located assets in every layer; fragmentation, dependency between layers and overload of the survivors then spread the failure. The 3D view separates the layers by depth. Teaching model with stated illustrative values, not a prediction.
Controls
- Assets per layer
- 18
- Hazard footprint
- 8% of area
- Assets that depend on another layer
- 60%
- Spare capacity (tolerance)
- 30%
Readouts
- Assets hit by the hazard
- 11%
- Assets still working
- 26%
- Amplification of the initial damage
- 6.7 times
- Steps to settle
- 3
Numbers, methods and sources
| Step | Data centres working (%) | Networks working (%) | Power working (%) |
|---|---|---|---|
| 0 | 94 | 83 | 89 |
| 1 | 78 | 44 | 39 |
| 2 | 56 | 33 | 22 |
| 3 | 56 | 17 | 6 |
Methods
- Interdependent networks Buldyrev and others (2010), Catastrophic cascade of failures in interdependent networks, Nature 464
- Overload cascades Motter and Lai (2002), Physical Review E 66
- Betweenness load Brandes (2001), Journal of Mathematical Sociology 25
- Multilayer networks Kivela and others (2014), Journal of Complex Networks 2
- Infrastructure interdependencies Rinaldi, Peerenboom and Kelly (2001), IEEE Control Systems 21(6)
- Uncertainty fan (parameter Monte Carlo) Spiegelhalter, Pearson and Short (2011), Visualising uncertainty about the future, Science 333
- One-at-a-time sensitivity (tornado) Saltelli and others (2008), Global Sensitivity Analysis: The Primer, Wiley
Data
The model runs on the teaching values set by the controls. To calibrate it for a place, read it against these admitted layers and series, which this page’s map can draw:
- Major roads Natural Earth
- Railways Natural Earth
- Seaports Natural Earth
- Airports Natural Earth
- Urban extents Natural Earth
- Night lights tonight, outages (VIIRS Day/Night Band) NASA/NOAA VIIRS (Suomi NPP) · register nasa.gibs.context-live-layers
- Natural events (NASA EONET) NASA EONET · register nasa.eonet.events
Across the six pillars, led by Nexus Consortium
- Experiments Labs
- Built in Foundry in Foundry
- Tested at Foundry in Universe
- Codified in Data and Evidence in Standards
- Published in Foundry in Reports
- Taught in Faculty of Technology and Digital Systems in Academy
The questions this field works on.
Project workstations
Project onboarding, persistent context and permissions.
TopicTwenty technical systems
Canonical Foundry system inventory.
TopicMaps and GIS
Approved geospatial public views.
TopicGrix evidence
Data, ontology, Chronotopes and lineage.
TopicModelling and simulation
Workloads, reproducibility and limits.
TopicAgents and automation
AI tools, authority and risk controls.
TopicCompute and edge
Cloud, local nodes and edge technical capacity.
TopicUsage metering, quotas and cost transparency
Service units, credits, quotas and tenant charges.
How foundry is modelled, measured and tested.
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.
Model, equations and assumptions
The model structure used for foundry, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)hazard, exposure, vulnerability and coping capacityEAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| Assumption | Why it is made | How it is tested |
|---|---|---|
| Hazard and exposure are independent within an event | Keeps the loss integral tractable | Compare with a copula fit on joint records |
| Couplings are linear near the operating point | Lets shocks propagate through A | Perturb beyond the linear range and compare |
| Vulnerability curves transfer between places | Local curves are rarely available | Validate against observed losses where they exist |
- Inputs
- versioned datasets with provenance
- Outputs
- distributions, never single numbers
- Code
- released with the model card and tests
- Reproduction
- same data, code, environment and seed
Datasets and provenance
The data classes behind foundry 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 |
- Lineage
- W3C PROV record from source to figure
- Principles
- FAIR: findable, accessible, interoperable, reusable
- Gaps
- shown as missing, never filled silently
What Foundry is for, and what its descriptions do not claim.
Foundry is the shared work environment designed for national teams to build and run risk models, data pipelines and decision tools on their own data, under their own authority. GCRI Canada is the contracting party for the service under a not-for-profit mandate; technology and infrastructure providers work at arm’s length and hold no control over governance, research or data.
Descriptions of the twenty Foundry systems state their purpose, not observed operation; information and enquiries are open today. Screens shown are illustrative interfaces with example values, never output from a live service.
One environment, five domains coupled in each national model.
- WaterHow this field couples to itBasin water balances and flood models run alongside the grid and the farm models that depend on them.
- EnergyHow this field couples to itGrid adequacy and restoration models share the asset layers water and health studies need.
- FoodHow this field couples to itCrop and market models draw on the same weather and soil inputs as water models.
- HealthHow this field couples to itHealth system continuity models read power, water and supply dependencies from the shared layers.
- BiodiversityHow this field couples to itEcosystem extent and condition layers feed water, food and health models as inputs with their own labels.
From Foundry work to Reports, under the proposed standards.
Readiness of Foundry capabilities is designed to be reported in the Foundry Build and Readiness series, and analyses built there in the country series. Software, models and datasets used in Foundry are designed to carry bills of materials, model cards and metadata under NS-12 and NS-3b of the proposed Nexus Standards.
- Research software engineers can review code and reproducibility practice.
- National teams can propose the first questions their Foundry workspace should answer.
- Security researchers can report a vulnerability to the security address.
Why risk analysis needs an environment, not just tools.
Systemic risk is studied across water, energy, food, health, finance and infrastructure at once, and the analysis that supports a decision usually passes through many hands: a hydrologist’s flood model, a utility’s asset register, a satellite product, a household survey, an economist’s loss estimate. Each step transforms data, and each transformation carries assumptions. When those steps sit in personal folders, unversioned scripts and email attachments, three failures follow. Results cannot be reproduced, because nobody can say which data cut and which model version produced them. Permissions leak, because sensitive layers travel further than their owners agreed. And errors cascade, because a correction to an upstream source never reaches the products built on it.
These are engineering problems as much as scientific ones. Distributed computing, data stewardship, geospatial processing, machine learning and safety-critical software engineering each have mature practices for traceability, access control and verification. Foundry brings those practices into one environment designed for risk work, so that a figure in a published brief can be traced back to its sources, licences, transformations and model runs, and so that the people who own data keep control of it throughout.
One environment, scoped by project, for the whole cycle of work.
All work in Foundry is designed to happen inside a project: a bounded workspace with a question, an accountable owner, data terms, a review plan and an openness profile. Authentication proves who someone is; authorisation, decided request by request by the NXS-NSF (trust, authorisation and assurance) Sovereignty Framework, decides what they may do.
Persistent context
Workspaces keep data, models, maps, decisions and programme memory together across the year, with permissions set by the project rather than by the room.
Traceable records
The Global Risks Index (NXS-GRX) registers sources with their owners and licences, keeps originals unchanged and binds every risk record to place, time and scenario.
Cloud, local and edge
NXS-COR (compute, nodes and runtimes) is designed to schedule workloads across cloud, private infrastructure and edge nodes, so analysis can run where data is allowed to sit.
One policy spine
Identity, mandate, policy gates and receipts work the same way for people, applications and AI agents.
Foundry is for engineers, model builders, researchers, technology operators and project owners working on authorised projects. No system is open to the public by default, and a membership, payment or infrastructure offer is not an allocation.
Grounded in engineering, connected across three institutions.
The platform applies six methods from the STEM Commons: high-performance, cloud and edge computing, data engineering, interoperability and stewardship, geospatial information systems, artificial intelligence and machine learning, systems engineering and software and safety-critical systems engineering. Each method page says how the method is used here and links to its canonical description.
Every platform in the network names, on its own Foundry page, the systems it relies on, and Foundry serves all 63 platforms of the three institutions. Its closest counterpart is Actuarial and Quantitative Risk at The Global Risks Alliance (GRA), which shares the methods and modelling field and works on the validation of quantitative models. Governance questions about programme gates are convened by The Global Risks Forum (GRF) through the Governance Nexus. Build readiness is reported in the Foundry Build and Readiness series, and the build is exercised in the Universe through the edition Core build theme.
Foundry is operated at national and regional level by Nexus Consortiums through their host and lead organisations, within a multilateral programme led by three pillar not-for-profit institutions, GCRI, GRF and GRA, on a public-private-planet partnership.
The areas of data and compute this platform takes on.
Foundry is the compute and methods environment where national risk models, data pipelines and digital twins are built and run. It studies the risks inside that work: models that fit the past for the wrong reasons, pipelines that transform data silently, permissions that drift, agents that overreach and compute that fails when it is needed. Its pages set out the engineering, the data, the methods and the decisions for each part, with every value labelled by its evidence.
Data pipelines and lineage
Ingestion, validation, standardisation and provenance, from the source passport to the published figure.
Models and simulation
Ensembles, coupling, calibration, validation and reproducible runs for physical, statistical and agent-based models.
Geospatial infrastructure
Coordinate reference, catalogues, OGC and STAC services, and the public-safe release of maps.
Compute and edge
Cloud, private infrastructure and edge nodes scheduled as one capacity, with placement by data location and policy.
AI and agents
Machine learning models and tool-using agents, their evaluation, authority records and human review.
Identity and authority
Projects, roles, mandates and policy gates that deny by default and record a receipt for every consequential action.
Software assurance
Contracts, software bills of materials, build provenance, testing and the evidence that a release is what it claims to be.
Metering and accountability
Service units, quotas and credits attributed to projects and kept independent of scientific state.
Built on named science, technology, engineering and mathematics.
Every claim on Foundry rests on methods with a canonical page in the STEM Commons, so readers can see what a finding depends on and where its limits lie.
How work moves in this field.
A question becomes evidence, a governed build, an organised community, a controlled test, a reviewed publication and, finally, a decision taken by the competent authority under its own rules.
- Question Universe National, regional or institutional priority. Question in Foundry
- Evidence Foundry STEM foundation of the platform. Evidence in Foundry
- Build Foundry Foundry. Build in Foundry
- Organise Universe Nexus ecosystem. Organise in Foundry
- Test Universe Universe (independent site). Test in Foundry
- Publish Reports Reports. Publish in Foundry
- Decide Competent authority Competent authorities and institutions, through NXS-RLS (participants, agreements and handoffs). Decide in Foundry
- Renew Universe Corrections and the next annual agenda. Renew in Foundry
Each step of the cycle in the pillar it runs in; the decision stays with the competent authority, outside the programme.
- Labs
- Foundry
- Universe
- Nexus Standards
- Reports
- Risk Academy
- Competent authority (outside the programme)
How this works across the six pillars.
Foundry works through six pillars of one annual programme, led by the Nexus Consortium, with GCRI, GRF and GRA each contributing in its role: explore, experiment and prototype in Labs, build, simulate and prepare in Foundry, convene and test in Universe, codify, correct and apply in Nexus Standards, publish in every format in Reports, teach in the open in Risk Academy.
handoff in playrecorded handoffno direct handoff
Programme yearAll phases
Route
The whole programme
Every pillar hands its work to another; together they close the year’s feedback loops.
L · F · U · S · R · A
- Pillars
- 6 of 6
- Handoffs
- 18 of 18
- Loops
- 17 closed
Handoffs in play
- F01Universe → Foundry · Admitted mission becomes a cycle project with a decision caseReadiness preparation
- F02Foundry → Universe · Core Build Report and go or no-go evidenceControlled build
- F03Foundry → Reports · Sealed observations and indicator series behind a profileCloseout
- F04Universe → Reports · After-action and scenario findings for chapters 10 and 13After-action review
and 14 more
- LabsWhere questions become experiments and prototypes: new methods, data and tools are tried in the open, with their limits on record, before the Foundry builds them, under the Nexus Consortium.Labs
- FoundryWhere methods, data and models become reproducible builds, each run with its inputs, version and limits on record.Foundry in FoundryFoundry
- UniverseWhere a build is tested under controlled conditions with independent evaluators, so a method’s skill is measured, not assumed.Foundry in Universeuniverse.nexus
- Nexus StandardsWhere methods, identifiers and data schemas are codified in the open and corrected when a test finds a fault.Data and Evidence in Standardsnexustandards.com
- ReportsWhere findings are published with their method, uncertainty and evidence class, and corrected as new versions.Foundry in ReportsReports
- Risk AcademyWhere methods and systems are taught on real data and real places, by working the case, on Risk Academy.Faculty of Technology and Digital Systems in Academyrisksacademy.com
What the work is read against.
The platform does not set standards. It reads its evidence against the frameworks that competent bodies have adopted, so a finding can be placed where a decision-maker already works.
| Framework or standard | Body | What it sets |
|---|---|---|
| ISO/IEC 25010 and ISO/IEC 27001 | ISO and IEC | A product quality model for software and systems, and requirements for an information security management system and its controls |
| NIST AI Risk Management Framework | US National Institute of Standards and Technology | Functions to govern, map, measure and manage risks from AI systems across their life cycle |
| ISO/IEC 42001 artificial intelligence management system | ISO and IEC | Requirements for establishing, operating and improving an organisation’s management of AI |
| OGC API standards and the SpatioTemporal Asset Catalog | Open Geospatial Consortium, STAC community | Interoperable web access to features, maps, tiles and gridded coverage data, and searchable catalogues of imagery and derived rasters |
| Climate and Forecast (CF) metadata conventions | CF conventions community | Standard names, units and coordinate descriptions for gridded scientific data in netCDF |
| FAIR guiding principles | FORCE11 and GO FAIR | Findable, accessible, interoperable and reusable data and metadata, for machines as well as people |
| SLSA and software bill of materials practice | OpenSSF; SPDX (ISO/IEC 5962) and OWASP CycloneDX | Levels of build provenance and integrity, and standard inventories of software components and licences |
| Model cards and datasheets for datasets | Research and practitioner community | Structured documentation of a model’s intended use, evaluation and limits, and of a dataset’s origin and composition |
| ISO 9001 quality management applied to models | ISO | Documented process, review, corrective action and continual improvement for model development and use |
| ACM artefact review and badging | Association for Computing Machinery | Criteria for research artefacts that are available, functional, and whose results have been reproduced by others |
The same field, seen three ways.
GCRI studies a field as science, GRF governs it and GRA builds shared financial understanding of it. Foundry links to its counterparts so that work on one side is visible on the others.
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.
- NIST AI Risk Management Framework 1.0 (2023) and Generative AI Profile (2024)
- ISO/IEC 42001:2023 Artificial intelligence management system (ISO)
- SLSA supply-chain levels for software artefacts (OpenSSF)
- Barker and others, Introducing the FAIR Principles for research software, Scientific Data 9 (2022)
- Nexus Standards, the proposed NS series (nexustandards.com)
Pages in Foundry.
Capabilities
PageTechnical systems
PageProjects and workspaces
PageGIS and geospatial
PageData and NXS-GRX
PageAI and agents
PageDevelopers and integrations
PageOperator support
PageUsage and billing
PageFoundry access and security
PagePurpose and publisher
PageSupporting methods
PageContributors and community
PagePublic outputs
PageContact and support
PageSTEM foundation of Foundry
PageHow work moves in this field
PageBuild in Foundry
PageTest in Universe
PagePublish in Reports
PageThe same field across the Consortium
PageTopics
Where this page leads across the Consortium.
Questions and answers.
Who publishes Foundry?
Is Foundry active?
How can I contribute?
Where are findings published?
Which values on this platform are real?
How do I report an error?
Can I sign up and start a project today?
Does Foundry make decisions or issue warnings?
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.
How Foundry works.
Choose a view and press Play to follow the platform’s process, its programme year, the standards it applies and how its findings are published. The outline shows how the work is designed to run, not the status of any decision.
Foundry
How Foundry works
Platforms · Programme year · Standards · Reports
A platform joins a field to named methods, labelled evidence and the outputs it publishes, without becoming the authority it serves.
01 Scope
- 01Field and familiesStart · The platform leadThe home states the field, its families and who it serves.
- 02Topic dossiersRecord · Platform authorsTopics explain the subject with labelled evidence.
02 Evidence
- 03Evidence labelsRecord · GCRIEach value is labelled: observed, published statistics, estimated, modelled, scenario or unknown.
- 04MethodsStep · Method ownersMethods come from the STEM Commons, each with one canonical page.
03 Work
- 05Scenarios on the systemsModel · Foundry pillarScenarios run on the Nexus systems, labelled as scenario.
- 06Standards that applyRecord · Nexus StandardsThe platform names the standards that apply. A validator report is evidence for review.
04 Publish
- 07EditionsRecord · ReportsFindings are published through Reports with their limits.
- 08Authority decidesOutcome · The competent authorityDecisions and execution stay with the government, operator or licensed institution.
Foundry home · Platforms · Shared methodsAn outline of how the work is designed to run; it does not report the status of any decision or record.
Take part in Foundry.
Start from who you are. Answer an open call. Or form and lead a competence cell on the Foundry platform.
National institutions
Ministries, statistics offices and agencies: a national desk and chapter, and a seat in the working groups. National chapters
Sectors and professions
Operators, regulators, banks, insurers and professional bodies whose work touches Foundry. Participate
Learning
Courses and practice, with a record of every course completed. Free to study. Open learning
Standards
Draft, review and adopt the methods and data standards with the working groups. Working groups
Communities and research
Universities, civil society and individual experts: projects, data and review. Write to the team
| Open call | Seeks | Closes |
|---|---|---|
| Founding call for experts to the working groups CALL-FOUNDING-EXPERTS | expert, editor, chair | 2026-12-15 |
| Open nomination for the three independent expert seats of the Global Standards Council CALL-GSC-IND | council-member | 2026-12-01 |
| Nominations of interim regional members (applies only if the transitional provision is decided) CALL-GSC-REG | council-member | 2026-12-15 |
| Review of the wave-1 risk core outlines (C1, C2, C3, C4, C8, C10, C11) CALL-REVIEW-WAVE1 | contributor | 2027-01-31 |
| Experts for the core standards of risk science: uncertainty and evidence grading, scales, structured expert judgement, tolerability, extremes and compound events, catastrophic and existential risk, ethics and equity, units and measurement (NRS-C17 to NRS-C24) CALL-CORE-SCIENCE | expert, editor, chair | 2027-01-31 |
| Independent reviewers for the families of the hazard atlas, three from at least two regions for each family (NHS2-R19), priority families first CALL-ATLAS-REVIEW | expert | 2027-03-31 |
| Members of the interim Frontier Safety Review Panel and red-team reviewers (biosafety and biosecurity, AI safety and security, critical-infrastructure security); applications treated in confidence CALL-FRONTIER-SAFETY-REVIEW | expert | 2026-11-30 |
| Experts in ontology, metrology, software verification and conformity assessment for the requirement register, the NHS-2 machine representation, the conformance test suites and the conformity assessment scheme CALL-CONFORMANCE-ONTOLOGY | expert, editor | 2027-01-31 |
Calls past their closing date are hidden automatically. Every call, proposal and route: open areas and calls.
Gather the cell
Bring together three to seven people with complementary skills: data, field practice, policy and communication.
Register it
Write to the team with the cell’s name, members, area and region. You receive a reference and a contact. Write to the team
Choose a charter
Pick one focus: research and evidence, data and maps, standards review, or community preparedness.
Learn together
Follow shared study paths at Risk Academy, with practice and a record of every course completed. Hazards and resilience
Lead and report
Hold regular sessions. Publish what the cell learns through Reports. Bring findings to the working groups. Working groups
What a national team or a local community can do on The Global Risks Index (NXS-GRX) today.
Your country’s profile
Open risk profiles for 195 countries, with sources and licences on every value. Open the Index
Correct or reply
Correct a value or reply for your country. The change is logged with its effect. Open the Index
Offer data
Offer a dataset. It enters through the licence gate, with your credit. Open the Index
Every figure on this page is indexed: hazards, climate, conflict, the world.
The Index is the Consortium’s indexing system for risk data. Every indicator, hazard, series and country profile carries its Nexus Standards identifier, its source and its licence, so what this page shows can be traced, corrected and reused.
- 01 · Sources205 registered sourcesEvery value keeps its source and licence; withheld values are counted.Data and licences
- 02 · Nexus StandardsNIS-1 and NHS-1451 indicators, 905 hazards; every record carries a UNI.Nexus Standards
- 03 · The Index54 series, 195 country profilesComputed on the standards; no value is published until an edition is released.The Global Risks Index
- 04 · This pageFoundryMaps, figures and feeds read the Index in the context of hazards, climate, conflict.Public API
Series in this context hazards, climate, conflict
- GLBGlobal SystemsThe state of interdependent global risk: the twenty domain indices aggregated to the world, the five core systems (water, energy, food, health, biodiversity) and their couplings, the global tail register and the gap…NXS-GRX-AR-000002Hazards · Climate · Conflict
- THDisaster Risk Intelligence (DRI)Signals, observations, event streams, geospatial layers and scenario packs turned into structured risk intelligence for preparedness and planning.NXS-GRX-AR-000111Hazards · Climate · Conflict
- GSGlobal CitiesUrban exposure, heat, flooding, informal settlement, service dependency and the economic weight of cities at risk.NXS-GRX-AR-000068Hazards · Infrastructure · Climate
- GSGlobal ClimateChronic and acute physical climate hazard, transition exposure, adaptation gaps and scenario pathways to 2030, 2050 and 2100.NXS-GRX-AR-000065Climate · Hazards · Finance
Country profiles the world
Every country profile carries the source and licence of each value. Correct a value or reply
Hazard domains NHS-1
- Atmosphere and weatherNXS-GRX-AR-000135
- Solid EarthNXS-GRX-AR-000138
- Systemic and compound eventsNXS-GRX-AR-000148
Geodata and API open
Open layers on an equal-area hexagon grid, shown as densities per km² or as symbols: People · GHSL 2025People · WorldPop 2025Built-up areaPortsAirportsRoadsRailwaysRivers and lake centrelines
/api/v1/public/grix · https://nexustandards.com/uni/{uni}
Developers · Data · Made with Natural Earth, Public domain; GHSL and WorldPop, CC BY 4.0
Snapshot of the Index registries pinned 2026-10-23 · 22c6eed. Research and risk-analytics information: not a rating, an official classification, a warning, a benchmark or advice.
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.