GCRI · Registry
Public recordWhat the Nexus ecosystem publishes and runs, as data
Registry
Public-safe records of programmes, evidence, publication status and correction histories, subject to owner authority. Registry is an established platform of The Global Centre for Risk and Innovation.
- Records
- 1,256
- In 12 types
- Identifiers
- 130
- Records carrying a UNI
- Snapshot
- 3.1.1
- As of 2026-10-17
- Formats
- 4
- JSON, CSV, JSON-LD, RO-Crate
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 |
|---|---|---|
| FAIR Guiding Principles | FORCE11 community, published in Scientific Data | Findability, accessibility, interoperability and reusability of data and metadata, for people and machines |
| CARE Principles for Indigenous Data Governance | Global Indigenous Data Alliance | Collective benefit, authority to control, responsibility and ethics for data about Indigenous peoples, lands and knowledge |
| TRUST Principles for digital repositories | Research Data Alliance community, published in Scientific Data | Transparency, responsibility, user focus, sustainability and technology as the basis of repository trustworthiness |
| COPE Core Practices and retraction guidelines | Committee on Publication Ethics | How editors and publishers handle allegations, corrections, retractions, expressions of concern and authorship disputes |
| PROV data model and ontology | World Wide Web Consortium (W3C) | A common vocabulary of entities, activities and agents for recording how a record was produced and changed |
| Data Catalog Vocabulary (DCAT) version 3 | World Wide Web Consortium (W3C) | How datasets, data services, distributions and their versions are described in catalogues and exchanged |
| OAIS reference model (ISO 14721) | CCSDS and the International Organization for Standardization | Functions, information packages and preservation description information for archives that keep records usable over the long term |
| ISO 19115 and ISO 19157 | ISO Technical Committee 211 | Metadata, lineage and data quality elements for geographic information, widely reused for the provenance of spatial records |
| DOI system (ISO 26324) | DOI Foundation and the International Organization for Standardization | Syntax, resolution and governance of digital object identifiers, operated through agencies such as Crossref and DataCite |
| CoreTrustSeal requirements | CoreTrustSeal Standards and Certification Board | Core requirements for trustworthy data repositories, covering organisation, digital object management and technology |
Record ledger.
The screen a team would use to follow this field: its measures, states and decisions. Names are examples and values are illustrative.
Record ledger
Registry · Ledger head 5355844
- Records registered3288
- Complete provenance, % of records96Normal
- Open corrections16Watch
- Rights holds4Info
Latest records
| NX-R-47092 | Programme status | v1 | 4258505 | Registered |
| NX-P-62248 | Publication | v2 | 9388917 | Registered |
| NX-E-95255 | Evidence record | v4 | 0174133 | Correction open |
| NX-C-49731 | Participation | v1 | 9437640 | Rights hold |
Version history
- v1NEWRegistered with sources
- v2FIXUnit corrected, reason recorded
- v3OPENCorrection requested
The questions this field works on.
Programme status
What a programme state does and does not mean.
TopicRecord provenance
Issuer, date, method and source lineage.
TopicCorrection and versioning
Superseded assertions and correction routes.
TopicPublication registrations
Publication metadata and identifiers.
TopicEvidence classes
Evidence type, reliance limits and confidence.
TopicParticipation records
Consent, recognition and programme boundaries.
TopicRights and disclosure
Publication rights, withdrawal and audience.
TopicRegistry interoperability
Stable references, exports and API semantics.
Built on named methods, read across three institutions.
The Registry applies three methods from the STEM Commons: data engineering, interoperability and stewardship, which governs schemas, lineage and exchange formats; digital identity and public digital systems, which governs how people and institutions are identified without over-collecting personal data; and cybersecurity and cryptography, which governs integrity checks, access control and tamper evidence. Each is described with its limits on the STEM foundation of Registry.
Inside Foundry, the Registry works with NXS-GRX (canonical data, provenance and risk) for risk-data lineage, NXS-NSF (trust, authorisation and assurance), NXS-RLS (participants, agreements and handoffs) and NXS-POR (public, client and partner delivery). Its methods notes are designed for the Methods and Technical report series, and in the annual Universe programme it is designed to keep the evidence records across an edition.
The same questions are governed and applied elsewhere. Research Nexus at The Global Risks Forum (GRF) and Governance Nexus at The Global Risks Forum (GRF) convene institutions on research integrity and accountable governance, while Financial Regulation Nexus at The Global Risks Alliance (GRA) builds shared industry understanding of record-keeping and supervisory evidence in finance. All counterparts are listed on counterparts across the Consortium.
What Registry does.
Research record integrity is the property of records that can be traced to who issued them, when, by what method and from which sources, and that change only through visible corrections. Registry covers programme status, provenance, correction and versioning, persistent identifiers, evidence classes, participation, rights and interoperability, with the standards that govern each.
Its community
Programme stewards; librarians; auditors; technical reviewers; contributors.
Its methods
Record schemas; reference resolution; provenance and rights; correction trails.
Its outputs
Verified public record views; record methods; status glossary.
Search the registry.
1,256 records in 12 types. Search by word, filter by type, status, scope and domain, or paste a UNI to resolve it. Without JavaScript the latest records are listed below.
The latest records of snapshot 3.1.1 are listed in the next section; every record, listed by type, is on the records page. With JavaScript this section becomes a search across all 1,256 records, with filters, a record panel and a UNI resolver.
Recently dated records.
The records with the most recent date in snapshot 3.1.1, as of 2026-10-17.
| Identifier | Record | Type | Status | Updated |
|---|---|---|---|---|
NXS-STD-DC-000010 | Governance directory index | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000011 | Nexus Standards Charter (draft target) | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000012 | National adoption, adaptation and sovereignty | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000013 | Open boundary, IPR and licensing | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000014 | Legal structure and instruments | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000015 | Disclaimers and legal language | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000016 | Security, safety and continuity measures | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000017 | Go-live readiness | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000018 | Agent guide | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000019 | Site pages: stewardship, national adoption and open boundary | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000020 | Site pages: legal notices | Artefact | draft | 2026-10-17 |
NXS-STD-DC-000021 | Nexus Risk Standards: the systemic architecture | Artefact | draft | 2026-10-17 |
1,256 records in 12 types.
Snapshot 3.1.1, as of 2026-10-17, identifier 90a6a93b18a2bf3c. Every figure on these pages is read from the snapshot when the page is built.
- Standards19RecordsStatusproposed 15, open 2, specified 2What it isA Nexus Standard (NS-0 to NS-16 and the Nexus Risk Standards) with its status in the standards index.
- Areas57RecordsStatusplanned 55, wired 2What it isA specialised area of the Nexus Standards site: a subsite arranged by domain, hazard family, sector, capability or readiness pathway.
- Artefacts114RecordsStatusdraft 114What it isA record in the NS-1 artefact catalogue: a UNI-identified standard, schema, dataset, policy or document of the standards commons.
- External standards252RecordsStatuscite 112, crosswalk 68, adopt 64, profile 8What it isAn open or third-party standard the Nexus Standards crosswalk to, named and linked, never reproduced.
- Consumers2RecordsStatuspartly wired 2What it isA system that applies the Nexus Standards, with the implementation status of each standard in it.
- Surfaces10RecordsStatusplanned 6, wired 4What it isAn NS-6 surface: a place where a UNI is shown or resolved, with how it is embedded.
- Sites101RecordsStatuslive 101What it isA WordPress site of the estate (institution, platform, Academy, Standards, Reports) with its page count and publication state.
- Editions11RecordsStatusdrafted 11What it isA Reports Baseline Edition in the 2026 edition set.
- Courses and lessons395RecordsStatusplanned 178, published 127, authoring 90What it isA Risk Academy course, or a teaching lesson (a process model with stated sources).
- Sources197RecordsStatusadmitted 111, pending 73, excluded 13What it isA data source in the legal register, with its licence class and admission state.
- Runtimes and components56RecordsStatusserved 49, pinned 7What it isA page runtime the network serves, or a pinned third-party library a runtime loads.
- Programme records42RecordsStatusopen 38, scheduled 4What it isA stream, workstream or start-up milestone of the Nexus Standards programme, with its status.
Search, read the model, download.
- Records: search all 1,256 records, filter by type, status, scope and domain, and resolve a UNI.
- Record model: the identifier grammar, the catalogue schema and the snapshot record.
- Programme state machine: the states and how a standard or a record moves between them.
- API and bulk download: JSON, CSV, JSON-LD and the RO-Crate, with digests.
- Corrections and version history: what changed between snapshots, and how to report an error.
What Registry records, and what a record does not confer.
Registry keeps the programme’s records: who asserted what, when, on what evidence and under which terms, and how each record was corrected. It is the memory of the programme, not a register of legal status. A record that an institution enquired, contributed data or completed a step is a fact about that event; it is not membership, accreditation, a licence or an approval.
Records shown on these pages are examples of structure unless marked as released. Personal data is never published, and a correction never erases the history it corrects.
Records from every domain pass through the same rules.
- WaterHow this field couples to itGauge, well and quality datasets are registered with their owner, licence and lineage before any water product uses them.
- EnergyHow this field couples to itGrid and supply datasets carry sensitivity classes, so restricted network detail is recorded without being exposed.
- FoodHow this field couples to itCrop, price and nutrition series keep the statistics office or survey as source of record.
- HealthHow this field couples to itHealth data enter only as aggregated or permitted series, with their privacy basis recorded.
- BiodiversityHow this field couples to itSpecies and ecosystem records keep rights-holders named, with CARE obligations attached where Indigenous data are involved.
How registry records support Reports and Nexus Standards.
Every figure in Reports is designed to resolve to a registry record. The proposed Nexus Standards give those records their identifiers (NS-1 and NS-3), metadata (NS-3b) and citation format (NS-2); the registry is where they are applied. Registry methods are designed for the Methods and Technical series.
- Data owners can register a dataset with its terms through the Secretariat.
- Anyone can request a correction to a record about them or their institution.
- Archivists and data stewards can review the record model against OAIS and TRUST practice.
Public trust fails when records cannot be checked.
Every claim a public programme makes rests on a record somewhere: an agreement that constituted it, a dataset behind a figure, a review that cleared a report, a decision that corrected an error. When those records are missing, scattered or silently changed, three failures follow. Readers cannot tell an estimate from an observation. A programme announced as active may never have been constituted. And a correction made in one place does not reach the copies, citations and summaries that have already spread elsewhere.
Records science, the shared ground of archivists, librarians, data engineers and auditors, treats these as structural problems rather than lapses of care. A record is trustworthy when its identity is stable, its origin can be traced, its integrity can be verified and its history is kept. Failures cascade because records are linked: a superseded dataset quietly feeds a model, the model feeds a report, and the report feeds a decision. Without lineage, no one can find which downstream records an error has touched.
Consortium programmes add a further difficulty. Work is carried out by many institutions across six regions, each with its own authority over what it produces. A shared registry cannot override that authority. It can only make each owner’s records consistent, citable and honest about their status.
A record layer for programmes, evidence and publications.
Registry is designed for programme stewards, librarians, auditors, technical reviewers and contributors who need to cite, check or maintain the records behind Consortium work.
Public-safe record views
Released records of programme states, publications, evidence and corrections, each with its validity, issuer and evidence label, published on public records.
Record methods
Versioned schemas, reference resolution, provenance and rights rules and correction trails, set out in the record model.
A shared status vocabulary
One meaning for each programme state across the three pillar institutions, set out on programme states.
No public record has been released yet. Records appear only when their owners release them and they pass review; the Registry never presents illustrative records as real.
The areas of governance and institutions this platform takes on.
Registry studies how research and programme records stay trustworthy over time: who issued an assertion, when, by what method and from which sources, how it is identified and linked, who may see it, and how it is corrected. Its pages set out the standards, identifiers, failure mechanisms, measures and decision holders for each part of the record, with every assertion labelled by its evidence and every correction kept visible.
Programme records
What a programme status asserts, who attests it, and why a stated target is not a delivered result.
Provenance and lineage
Issuer, date, method and source chain for every assertion, recorded so a reader can trace it back.
Correction and versioning
Errata, retractions, superseded versions and the routes by which corrections reach everyone who relied on a record.
Persistent identifiers
DOIs, ORCID iDs, ROR IDs and other identifiers that keep references stable when names, locations and systems change.
Evidence and confidence
Evidence classes, reliance limits and confidence statements that stop a weak source being read as a strong one.
Participation and recognition
Consent, contributor roles and programme boundaries for the people and organisations named in a record.
Rights, access and disclosure
Licences, embargoes, audience classes and withdrawal, and the balance between an open record and the duty to protect.
Interoperability and exchange
Metadata schemas, crosswalks, interfaces and export formats that let registries exchange records without losing meaning.
Built on named science, technology, engineering and mathematics.
Every claim on Registry 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 Registry
- Evidence Foundry STEM foundation of the platform. Evidence in Registry
- Build Foundry Foundry. Build in Registry
- Organise Universe Nexus ecosystem. Organise in Registry
- Test Universe Universe (independent site). Test in Registry
- Publish Reports Reports. Publish in Registry
- Decide Competent authority Competent authorities and institutions, through NXS-RLS. Decide in Registry
- Renew Universe Corrections and the next annual agenda. Renew in Registry
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.
Registry 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.Registry in FoundryFoundry
- UniverseWhere a build is tested under controlled conditions with independent evaluators, so a method’s skill is measured, not assumed.Registry in Universeuniverse.nexus
- Nexus StandardsWhere methods, identifiers and data schemas are codified in the open and corrected when a test finds a fault.Foundations and Governance in Standardsnexustandards.com
- ReportsWhere findings are published with their method, uncertainty and evidence class, and corrected as new versions.Registry in ReportsReports
- Risk AcademyWhere methods and systems are taught on real data and real places, by working the case, on Risk Academy.Faculty of Governance, Policy and International Affairs in Academyrisksacademy.com
The same field, seen three ways.
GCRI studies a field as science, GRF governs it and GRA builds shared financial understanding of it. Registry links to its counterparts so that work on one side is visible on the others.
- Research NexusInstitutionGRFShared fieldResearch and evidence, Governance and institutions
- Policy NexusInstitutionGRFShared fieldGovernance and institutions
- Governance NexusInstitutionGRFShared fieldGovernance and institutions
- Financial Regulation NexusInstitutionGRAShared fieldGovernance and institutions
- Financial Crime and Fraud RiskInstitutionGRAShared fieldGovernance and institutions
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.
- Lin and others, The TRUST Principles for digital repositories, Scientific Data 7 (2020)
- ISO 14721:2012 Open archival information system (OAIS), reference model (ISO)
- ISO 26324:2022 Digital object identifier system (ISO)
- PROV-O: the PROV ontology (W3C, 2013)
- Nexus Standards, the proposed NS series (nexustandards.com)
Pages in Registry.
Public records and status
PageData and evidence record model
PageProgramme state machine
PageProvenance and attribution
PageCorrections and version history
PageRights and visibility
PageInteroperable registries
PageSubmit and request review
PageRegistry trust and governance
PagePurpose and publisher
PageSupporting methods
PageContributors and community
PageAPI and bulk download
PageContact and support
PageSTEM foundation of Registry
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 Registry?
Is Registry active?
How can I contribute?
Where are findings published?
Which values on this platform are real?
How do I report an error?
Who publishes Registry?
Does a Registry record prove that something is true?
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 Registry 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.
Registry
How Registry 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.
Registry 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 Registry.
Start from who you are. Answer an open call. Or form and lead a competence cell on the Registry 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 Registry. 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 pageRegistryMaps, 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.