Describes the public technical work of the UN Office for the Coordination of Humanitarian Affairs on data: the Humanitarian Data Exchange (HDX) and HDX HAPI, ReliefWeb, the Financial Tracking Service, common operational datasets including administrative boundaries, HXL, the Centre for Humanitarian Data's data responsibility and anticipatory action work, with INFORM and GDACS as named peers, and what Nexus profiles could contribute. A section of the Humanitarian Action and Development subsite. Every artifact of the area carries a UNI (Unique Nexus Identifier), which identifies and never certifies.
Context entry PROPOSED for the Nexus Standards registry.
Nexus Standards (2026). OCHA and humanitarian data: area brief, Humanitarian Action and Development (PROPOSED). https://nexustandards.com/humanitarian/ocha-and-humanitarian-data/. Last reviewed 2026-10-17.
Files carry the credits and the licence line; they are generated in your browser and nothing is sent. Downloads need script.
The multilateral and institutional technical areas section of Humanitarian Action and Development. Scope as the area context entry states it (PROPOSED).
In scope 4
Out of scope 3
Jurisdictions No jurisdiction note is recorded for this area yet; jurisdiction narrows what applies and never implies that a Nexus profile satisfies a law.
Sources the area reads or proposes. Delivery follows GRIx first; a source is shown live only after an owner decision admits it for public pages.
No legal register row admits any of these sources for live display on public pages yet, so nothing is read from them here. A register row that exists records the source for the governed GRIx path; admission for public pages is a separate owner decision.
GDACS event alertspending admission
European Commission JRC and OCHA · real time
European Commission reuse policy via GDACS terms (CC BY 4.0 for EC content)
GRIx governed readregister row exists
INFORM Risk Index datapending admission
European Commission Joint Research Centre · annual with mid-year update
CC BY 4.0
GRIx governed readregister row exists
HDX HAPI (Humanitarian API)pending admission
OCHA Centre for Humanitarian Data · daily
Per source dataset as stated on HDX
GRIx governed readproposed register row
ReliefWeb APIpending admission
OCHA · continuous
ReliefWeb terms; content rights remain with the original sources
browser-direct readproposed register row
Relations are register entries (NS-14), never conformance or equivalence statements; hover or focus a relation for its meaning. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here.
Indicator names and codes as their stewards publish them; values appear only from a governed GRIx source, never typed into a page.
Each coupling names the mechanism that links this area to another; select a card on the canvas to trace it. Mechanisms are stated in the context bank (PROPOSED).
Fig.RUNNING marks the area you are reading; DONE an area in the same subsite, QUEUED an area elsewhere and GATE a subsite reached. Tags give reading order only, never a status. Design, not a record.
The Nexus Standards the area context entry lists. Every one is proposed or specified; none is adopted by an authority.
Status proposed · 0 rules stated. Read NS-3
Status proposed · 7 rules stated. Read NS-10
Status proposed · 6 rules stated. Read NS-11
GCRI Canada decides under its own evidence rules whether humanitarian data records are usable; describing OCHA services is not acceptance.
The Global Risks Forum (GRF) decides under its own rules how humanitarian data work features in its programmes; this section implies no recognition.
The Global Risks Alliance (GRA) decides capital readiness under its own criteria; humanitarian records only inform its reviewers.
Each institution decides under its own rules what it reads as evidence; no pathway is an approval, a readiness statement or investment advice.
Version and feed state per standard; every row reads source feed pending admission until a register row admits a feed.
Today · in your browserPick a sector, hazard family, capability and artifact type; the registry routes the standards and says why.
A console computes from the registry and shows its reasons; it never decides, approves or certifies.
Describe OCHA's data services accurately and develop licence-aware profiles that consume them.
No working group is chartered yet; a community may charter this one under NS-13 through a docket.
Closed or paywalled standards appear by name and link only; any compatibility profile of one is built on simulated data and kept on protected pages until an institutional arrangement with the issuing body is recorded. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
The working group may name closed standards later; they would be listed here by name and link only.
Hazards and threats 0
No hazard or threat is listed for this area; it reads the hazards of the areas it couples with.
Sectors 0
No sector is listed for this area; it serves every sector through the areas it couples with.
Peer-reviewed sources and published statistics on the publishers' own domains, as the context entry cites them. No Risk Academy faculty pathway is linked to this area yet; one is linked when a faculty publishes a pathway that fits.
Risk Academy disciplines that teach OCHA and humanitarian data, with their courses; the GCRI Canada, The Global Risks Forum (GRF) and The Global Risks Alliance (GRA) subsites that carry those disciplines; and the Nexus Foundry systems the standards name. Mappings are proposed for review (Risk Academy standards map, 2026-10-17); a link says a page on the same subject exists, never an endorsement or a conformance statement; framework names in course titles are named and linked, never reproduced.
Propose a change, join the working group or name a source. Area entries are PROPOSED content for the Nexus Standards registry; a UNI identifies and never certifies, and nothing on this site is a certification, an approval or a readiness statement.
Nexus Standards documents CC BY 4.0 · tooling Apache-2.0 · counsel review pending (DEC-2026-10-16-NEXUS-STANDARDS-OPEN-LICENCE). External standards are named and linked under their own licences; a UNI (Unique Nexus Identifier) identifies, it never certifies. · Generated from the Nexus Standards corpus at commit 437ae044c5cb (2026-10-17); proposed and open.