CGIAR Climate Data Hub — Use Cases DRAFT

GCF Preparation Facility · Climate Rationale v2 · Data review

GCF Preparation Facility — data, skills & notebook review

A structured review of the data behind the Atlas Climate Rationale v2 notebook and the CGIAR Climate Data Hub’s plan to serve Green Climate Fund proposal writers — organised around the nine notebook sections in the GCF data-requirements memo, and mapped to the GCF Concept Note (v3.1) sections each one feeds.

Where this sits. This use-case is a deliverable of CACC2 — the CGIAR Climate Data & Innovations Hub, the Climate Action capability that builds shared, quality-assured climate-data infrastructure. It is designed to support CACC1 — “Support the development of CGIAR’s GCF portfolio”, the capability that gives CGIAR Centers technical backstopping on climate rationale and proposal design across engagements in Togo, Benin/Nigeria, Egypt, Zambia and Kenya. In short: CACC2 provides the data and tools; CACC1 puts them to work in GCF proposals. Cesare Scartozzi (CACC1) is the champion and first user; Peter Steward (CACC2) coordinates.
Who this is for

The use-case task group (champion, CACC1; coordinator, CACC2; plus Brayden Youngberg and Majambo Gamoyo); the CDH technical team prioritising which datasets to bring into the Hub; and GCF proposal writers as the end users.

The goal

Compress the climate-rationale step of a GCF Concept Note / Funding Proposal from weeks to hours, while keeping methodological attribution transparent. The Togo SAT rationale (April 2025) is one illustrative example of the kind of output — a suggestion, not a prescribed standard.

How it’s organised

Four tabs: Data (this one — the nine notebook sections and their datasets), Skills (the CDH LLM-skills library and a proposed generic climate-rationale skill), Notebook (the multilateral-climate-funds pipeline idea), and GCA alignment (the Global Center on Adaptation’s parallel IFI/MDB adaptation-finance use-case and where it overlaps this one).

Decisions it informs

Which datasets the Hub catalogues first; which memo sections are in scope for v1 (August target); what to build as a reusable skill; and how to turn the climate-funds dataset into a notebook.

How we keep it honest. Section requirements are quoted verbatim from the CACC1 GCF data-requirements memo (dated 2026-01-31; filed as “2026.03”). Notebook state comes from the live climateRationale notebook and its decision log. Dataset facts come from each provider’s official page, checked live on 2026-07-07 and re-checked adversarially — logged in the evidence log. Internal meeting transcripts, chats and emails are not reproduced — only short excerpts and summaries of decisions. Anything unconfirmed is marked pending, never guessed.

The nine data themes at a glance

Each row is a theme of a GCF/IFI proposal and the datasets that serve it. The same data can be delivered two ways — through an Atlas-style geoselector notebook or an LLM skill that emits citable structured outputs — so this review is about the datasets, not one delivery surface. Every theme must be queryable at country + admin0/1/2 level. Click a theme to jump to its datasets.

Table 1 — Nine data themes for GCF/IFI proposal development. “Serves” = the GCF Concept Note (CN) / Funding Proposal (FP) sections each theme supports (key in the fold below the table). Status: IN CR already in the Climate Rationale notebook · PARTIAL partly present, needs additions · NEW not yet built · DEPRIORITISED in the memo but since parked. “Present” = what the live notebook does today; “Recommended” = target datasets.

#Notebook sectionServes (GCF proposal sections)StatusFeasibility
1Climate trends & projectionsCN C.1 · FP B.1IN CR1
2Extreme eventsCN C.1 · FP B.1, D.1IN CR1
3Crop & livestock hazard exposureCN C.1, C.2 · FP B.1, D.1PARTIAL2–3
4Vulnerability & socioeconomic contextCN Exec Summary · FP D.4PARTIAL1–2
5NDC & NAP alignmentCN A.16 · FP D.5DEPRIORITISED3
6Impact potential & beneficiariesCN A.6–A.7 · FP D.1, E.3NEW2–4
7Theory of change & GCF portfolioFP B.2, D.2NEW2–3
8Safeguards & gender screeningCN C.4 · FP G.1–G.2NEW2
9Financial context & justificationCN D.1–D.4 · FP B.5, C.1NEW2

Feasibility 1 = easy (public, mostly integration) to 5 = hard (per-country acquisition, NLP, or new modelling). Memo priority actions: (a) extend Sections 3–4; (b) build Section 7 (GCF portfolio); (c) build the remaining NEW sections on public global datasets; (d) standardise all outputs to a common schema.

Key — what the “CN” / “FP” section codes mean

GCF applications come in two stages, each a standard template. The codes are section references within them:

  • CN — Concept Note (template v3.1): the short first-stage pitch. Its sections include Exec Summary (the problem + solution), C.1 Climate change context, C.2 Proposed project/programme, C.4 Indicative safeguards profile, A.6–A.7 Estimated mitigation / adaptation outcomes, A.16 Alignment with country NDCs & NAPs, and D.1–D.4 Financing information & justification.
  • FP — Funding Proposal: the full second-stage document that follows a successful Concept Note. Its section letters cover the same themes in more depth — broadly B climate rationale & theory of change, D expected performance / financing, E logic & results, G safeguards annexes (exact subsection titles per the GCF Funding Proposal template).

So e.g. “CN C.1 · FP B.1” means the section supplies the climate-context narrative needed for Concept Note section C.1 and Funding Proposal section B.1. Codes trace to the memo’s section-to-GCF mapping.

How to read the dataset tables (Themes 3–9). Each theme below unpacks its datasets for the Hub technical team — what each one is, its format, the transformation to reach admin0/1/2, its IP/licence, and a concrete CDH integration route (mirror-host the raw data, federate to a live API, or derive-then-host a computed product). Every dataset is tagged by source: HAVE already held · CACC1 recommended in Cesare's memo · CACC2 additional, from this review's own deep research (beyond the memo). Each table also carries a Priority (P1/P2/P3): a rough rubric ranking each recommended dataset by value to GCF proposals × ease of integration (open licence + live API = easiest) × coverage × non-redundancy. P1 = do first (high value, open/API, broad, not redundant); P2 = next (valuable but harder — non-commercial, bulk, or narrower); P3 = later / optional (niche, heavily restricted, redundant, or heavy NLP / per-country). Held datasets show “—”. Themes 1–2 are already in the notebook, so they keep the short summary; Theme 5 is deprioritised but its sources are still unpacked so the dev team can see how they'd connect. Screenshots: the comment box here is a plain Markdown field and can't upload an image directly — to include one, paste a hosted image URL (![](url)), or open the thread on GitHub (click a comment's timestamp) and drag the image into GitHub's own editor there, or use the 💬 Feedback button (its form takes file uploads). Handy for suggesting an output format or flagging an issue.
💬 Comment / discuss “Sections at a glance”

Ingestion shortlist — the P1 datasets to bring in first

One consolidated do-first list for the CDH data-ingestion team: every P1 dataset across the nine themes, pulled into a single view. Quick wins (open licence + a live API or cloud-optimised endpoint) can be federated / mirrored with little work; the rest are P1 but need a licence decision or a derive-then-host step first. P2 / P3 datasets stay in each theme's table. Themes 1–2 are already held; Theme 5 is deprioritised.

Table 2 — P1 ingestion shortlist. Source: CACC1 Cesare's memo · CACC2 added by this review. Start = quick win (open + API/cloud) or resolve first (licence / derive step).

DatasetThemeSourceLicenceFirst move (integration route)Start
INFORM Risk4 · VulnerabilityCACC1open — CC BY 4.0Federate the JRC JSON APIquick win
FEWS NET4 · VulnerabilityCACC2open (USAID)Federate FDW API + mirror admin2 / livelihood-zone boundariesquick win
DHS (aggregate)4 · VulnerabilityCACC1open (aggregate API)Federate the DHS Indicator API (not the restricted microdata)quick win
ESA WorldCover6 · ImpactCACC2open — CC BY 4.0Federate the GEE / AWS COG; on-the-fly zonal statsquick win
EDGAR / FAOSTAT emissions6 · ImpactCACC2open — CC BY 4.0Federate the FAOSTAT API (country totals) / EDGAR bulk gridquick win
World Bank IEG7 · PortfolioCACC1open — CC BY 4.0Federate the DDH OpenAPIquick win
OECD DAC CRS9 · FinanceCACC1open — CC BY 4.0Federate the OECD SDMX-REST endpointquick win
OECD CRDF (Rio markers)7 & 9CACC2open — CC BY 4.0Federate via the same OECD SDMX client as CRSquick win
IATI Datastore7 · PortfolioCACC2openFederate the Datastore API (pulls AF / IFAD / WB at once)quick win
Global Forest Watch8 · SafeguardsCACC2open — CC BY 4.0Federate GFW API / GEE, or mirror the derived zonal statsquick win
WRI Aqueduct 4.03 · Crop/livestockCACC1open — CC BY 4.0Mirror the bulk ZIP, or derive an admin-joined bws/bwd parquetquick win
AQUASTAT GMIA v53 · Crop/livestockCACC2open (cite-as)Mirror the bulk raster; pairs with Aqueductquick win
IMF fiscal9 · FinanceCACC1open via WB Data360 (CC BY)Federate the Data360 mirror (avoid IMF's own bulk)quick win
Meta RWI4 · VulnerabilityCACC2CC0Derive an admin table (pop-weighted zonal) then hostresolve first — derive step
GDL SHDI4 · VulnerabilityCACC2NCDerive-then-host, keyed to GDLCODEresolve first — NC
IPC / Cadre Harmonisé4 · VulnerabilityCACC1NC — CC BY-NC-SAFederate the API; host derived products only (ShareAlike)resolve first — NC
WDPA / Protected Planet8 · SafeguardsCACC1NC, no-redistributeHost the derived overlay stat only — never the raw layerresolve first — NC
CSPD / CSPDxCF8 · SafeguardsCACC1NC — CC BY-NCFederate + derive the country risk tier (CGIAR sibling — coordinate with CSO)resolve first — NC
IPCC EFDB6 · ImpactCACC1unclearDerive a curated emission-factor lookup; confirm terms firstresolve first — licence
FAO EX-ACT6 · ImpactCACC1tool (no data licence)Wire as a computation engine, not a hosted datasetresolve first — it's a tool

Reads across the theme tables below; priorities and routes are this review's assessment, open to the team's correction. Start top-down: the quick wins are the fastest path to a populated Hub.

💬 Comment / discuss “Ingestion shortlist”

1 · Climate trends & projections IN CR

Serves CN C.1 · FP B.1. Every GCF proposal opens with the climate context — a defensible account of how the climate has already shifted in the project area and how it is projected to change, from historical timeseries and future projections at admin level. The datasets must answer: what is the temperature and rainfall baseline and trajectory here, by season and scenario?

Memo requirement (verbatim)
Historical timeseries (TAVG, PTOT, by season); future projections (SSP1-2.6 through SSP5-8.5, periods 2021–2040 to 2080–2100); anomalies; warming stripes. All at administrative level.GCF Data Notebook Memo, Section 1
Present — in the notebook today
Historical
CHIRPS v3 (PTOT) + CHIRTS-ERA5 (TAVG/TMAX/TMIN) + SPEI-03/12; 0.05°; adm0 + adm1; baseline 1991–2020 (WMO); anomaly toggle
Future
NEX-GDDP-CMIP6, 18-GCM ensemble; adm1 only; 4 periods 2021–2100; 4 SSPs (1-2.6 → 5-8.5); baseline 1995–2014; 17–83% inter-model range
Coverage
served products are region = Africa (both obs & projections) — not global; the pipeline could extend but hasn't published beyond Africa

Verified against the Atlas CR data audit, 2026-07-09. Two trend/variability products (Theil-Sen slope; interannual variability) are produced but not yet wired into the production notebook.

Recommended — memo target
Sources
NEX-GDDP-CMIP6 / CORDEX; ERA5; CHIRPS / CHIRTS
Scenarios
SSP1-2.6 → SSP5-8.5; periods 2021–2040 to 2080–2100
Outputs
anomalies + warming stripes, admin-level, with pre-computed sentence fragments

Verdict. Core capability exists and is the notebook’s strongest section. Gap is breadth of SSP/period coverage in the exposed outputs, not the underlying data.

💬 Comment / discuss “Climate trends & projections”

2 · Extreme events IN CR

Serves CN C.1 · FP B.1, D.1. A proposal must show the acute hazard is real and rising — that damaging extremes (drought, heat, heavy rain) already occur and intensify under future scenarios. The datasets must answer: how often do unusual / extreme events hit, historically versus projected, and is the frequency climbing?

Memo requirement (verbatim)
Z-score classification of unusual/extreme temperature and precipitation events; historical vs. projected frequency by scenario. All at administrative level.GCF Data Notebook Memo, Section 2
Present — in the notebook today
Method
Z-score categorisation; tails-aware (PTOT both tails, others high-only); per-hazard threshold rows
Derivation
computed in-notebook (client-side) from the Section 1 projections parquet; z-score vs 1995–2014; ensemble-mean only — no per-GCM classification, so tail models are masked (audit 2026-07-09)
Recommended — memo target
Source
derived from Section 1
Add
historical vs projected frequency by scenario; per-GCM classification for uncertainty bands (open pipeline item)

Verdict. Matches the Togo SAT z-score approach (Fig. 5 rainfall anomalies). Note the Togo document’s own Z=1 / Z=2 labelling is internally inconsistent with its annex — resolve the threshold labels when this feeds a template.

💬 Comment / discuss “Extreme events”

3 · Crop & livestock hazard exposure PARTIAL

Serves CN C.1, C.2 · FP B.1, D.1. The crux of the adaptation rationale: what is at stake — the value of agricultural production and livelihoods exposed to the hazard, valued in USD (in the style of the Togo SAT Table 5 example). The datasets must answer: how much crop and livestock production value is exposed to compound hazards, where, and under which scenario?

Memo requirement (verbatim)
Production value by crop (MapSpam); crop and livestock hazard exposure (drought, heat, waterlogging combos) valued in USD by scenario. Add if possible: fisheries/aquaculture exposure, water-demand stress on irrigated systems.GCF Data Notebook Memo, Section 3
Present — in CDH / Atlas
  • MapSPAM 2020 · crop value
  • FAOSTAT · production, prices
  • GLW4 · livestock numbers
CACC1 — Cesare's memo
  • FAO GLEAM · emission intensity
  • WRI Aqueduct · water stress
  • FAO FishStat · aquaculture value
CACC2 — added by this review
  • AQUASTAT GMIA v5 · irrigation extent
  • Sea Around Us · marine catch value

Present in the notebook (verified against the Atlas CR data audit, 2026-07-09): MapSPAM 2020 v1r2 production value × GLW4-2020 livestock (a combined crop + livestock exposure parquet — livestock is present, not partial) × the hazard indices; Ecocrop-default thresholds. Scope: Sub-Saharan Africa only, adm1 only (the champion's "biggest limitation"); fisheries / aquaculture absent. Only the severe severity tier is live (moderate / extreme pending). Valued in nominal 2021 USD, not constant dollars.

Data-plumbing flag (for the dev team). The audit found the hazard-exposure product the notebook reads and the one the pipeline writes sit on different S3 paths — 4 of 6 partition keys diverge (source nex-gddp-cmip6 vs atlas_cmip6; variable vop_nominal-usd21 vs vop_intld15/usd15; model ENSEMBLEmean vs ENSEMBLE/historic; interaction filename). The constant-dollar currency fix prepped in hazards_prototype ships to keys the live notebook doesn't read. Not yet S3-verified — needs an aws s3 ls on both prefixes to confirm it's a real gap vs a stale notebook path.

Table 3 — Theme 3 datasets: crop & livestock hazard exposure. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & resolution→ adminIP / licenceCDH integration route
MapSPAM 2020HAVECrop physical area / production / value by crop & systemGeoTIFF raster, ~10 kmzonal sumopen — CC BY 4.0already held (in CR) — but the run is SSA only; global MapSPAM must be run to extend coverage beyond Africa
FAOSTATHAVENational production, area, producer pricestabular, ISO3 × yearISO3 joinNC — CC BY-NC-SA 3.0 IGOalready held
FAO GLEAM v3CACC1 P3Livestock emission intensity (+ numbers/production) — a supporting/weighting layer, not USD value or exposureraster ~10 km + WMS/WMTSzonal mean/sumrestricted-use — FAO application + user agreement; NC, no redistributionFederate WMS/WMTS only (data.apps.fao.org); no mirror; a derived parquet is licence-blocked pending FAO permission
WRI Aqueduct 4.0CACC1 P1Baseline water stress (bws) + water depletion (bwd) — the water-demand-stress signal for irrigated systemsvector polygons (basin+province+aquifer composite) + CSVattribute join on gid_0/1; overlay onto irrigated areaopen — CC BY 4.0Mirror-host raw ZIP, or derive an admin-joined bws/bwd parquet
FAO FishStat — aquaculture valueCACC1 P2Aquaculture value of production (1000 USD), 1984–2021, by country (memo's "add fisheries/aquaculture")tabular CSV, ISO3ISO3 join → admin0 (national only)NC — CC BY-NC-SA 3.0 IGODerive-then-host parquet (normalise to ISO3+year+value)
FAO GLW4HAVEGridded livestock density (head/km²) by species, 2020 — open animal-numbers layerGeoTIFF raster, ~10 kmzonal sum → head/admin; × FAOSTAT price → value exposedopen — CC BY 4.0already held — gives open gridded animal numbers (so GLEAM isn't needed for numbers)
AQUASTAT GMIA v5CACC2 P1% area equipped for irrigation — locates irrigated systems under water stressraster 5 arc-min + shapefilezonal sum irrigated area; multiply by Aqueduct bwsopen (cite-as, Siebert et al. 2013)Mirror-host raw; pairs directly with Aqueduct
Sea Around UsCACC2 P3Reconstructed marine catch tonnage + landed value (sub-national / EEZ detail FishStat lacks)0.5° grid + EEZ polygons + APIcell → EEZ → coastal ISO3NC — CC BY-NC 4.0Federate API / derive-then-host — only if coastal/marine sub-national detail is needed

Verdict. Highest-value theme — the hazard-exposure matrix in the style of the Togo SAT Table 5 example (see Example target output). Priorities: water-stress additions and coverage. We already hold the open GLW4 gridded animal-numbers layer, so GLEAM isn't needed to count livestock; pair Aqueduct bws with GMIA to resolve stress onto irrigated cropland. The open coverage call: served data is SSA + adm1 only (Atlas audit 2026-07-09), but the active GCF pipeline spans non-African countries (Syria, Iraq, Sri Lanka, Egypt) — so the team must decide the minimum v1 coverage, and whether to run global MapSPAM or signpost an external global product where GCF prefers one.

Overlaps → GLW4 (open animal numbers, held) supersedes GLEAM for counting livestock — GLEAM only adds emission intensity, so it belongs in Theme 6, not here. Sea Around Us overlaps FishStat — add only if sub-national/marine detail is needed beyond FishStat's national totals.

Open question — for Cesare (CACC1): We already hold GLW4 (open gridded livestock numbers), and GLEAM is restricted-use and provides emission intensity (kg CO₂eq/kg product), not animal numbers or USD exposure. What does GLEAM add here — is it for the mitigation / enteric-CH₄ side (Theme 6), and is its restricted licence worth pursuing?
💬 Comment / discuss “Crop & livestock exposure”

4 · Vulnerability & socioeconomic context PARTIAL

Serves CN Exec Summary · FP D.4. The executive summary and needs case must establish who is vulnerable and why concessional GCF finance is warranted — poverty, food insecurity, water access, gender. The datasets must answer: how vulnerable are the people in the project area, on composite indices and sectoral measures?

Memo requirement (verbatim)
CR has poverty rates, GDP by sector, land use. Add if possible: composite vulnerability indices (ND-GAIN, INFORM Risk); food insecurity prevalence (IPC/CH); water stress and WASH access; gender-disaggregated vulnerability; population projections; HDI.GCF Data Notebook Memo, Section 4
Present — in CDH / Atlas
  • World Bank WDI · poverty, GDP
  • WorldPop · population
CACC1 — Cesare's memo
  • ND-GAIN
  • INFORM Risk (+ Subnational)
  • IPC / Cadre Harmonisé
  • WHO/UNICEF JMP
  • DHS · UNICEF MICS
  • UNDP HDI
CACC2 — added by this review
  • GDL SHDI · subnational HDI
  • Meta RWI · 2.4 km, CC0
  • FEWS NET · admin2 food security

Present in the notebook: World Bank indicators (poverty rates, GDP by sector, land use) in Key Facts — national only.

The crux of this theme: most memo datasets are national-only (admin0) — they can only shade a whole country. Genuine subnational granularity comes from DHS, IPC/CH, INFORM-Subnational (regional coverage only), and the CACC2 additions (GDL SHDI, Meta RWI, FEWS NET).

Table 4 — Theme 4 datasets: vulnerability & socioeconomic context. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & finest admin→ adminIP / licenceCDH integration route
ND-GAINCACC1 P2Climate vulnerability + readiness compositetabular, admin0 onlyISO3 joinunclear — "free/open" but no CC text found; verify (ndgain@nd.edu)Mirror-host (small yearly CSV)
INFORM Risk (global)CACC1 P1Crisis/disaster risk composite (hazard·exposure·vuln·coping)XLSX + JSON API, admin0ISO3 joinopen — CC BY 4.0Federate JRC API, or mirror the annual XLSX
INFORM SubnationalCACC1 P2Same model at admin1/2 — select regions only, not globalXLSX + HDX + boundaries, admin1/2admin-code joinopen — CC BY 4.0Mirror per-region; flag coverage gaps (null outside covered regions)
IPC / Cadre HarmoniséCACC1 P1Acute food-insecurity phase (1–5) + population by phaseREST API → GeoJSON / vector tiles, subnationalarea join to admin1/2 (geometry native)NC — CC BY-NC-SA 3.0 IGOFederate API (key) or mirror HDX CSV
WHO/UNICEF JMPCACC1 P2Water / sanitation / hygiene coverage since 2000SDMX API, admin0 (urban/rural = category)ISO3 joinNC — CC BY 3.0 IGOFederate UNICEF SDMX, or mirror the estimates file
DHS ProgramCACC1 P1Demographic & health surveys, 1500+ indicators, 90 countriesopen Indicator API (JSON/geoJSON), subnational; microdata + GPS separatebreakdown=subnational → region values; join SDR boundariesaggregate API open; microdata/GPS no-redistributeFederate API for aggregates + mirror SDR boundaries; never mirror microdata
UNICEF MICSCACC1 P3Child/woman wellbeing surveys (complements DHS)SPSS microdata only, no API; region tablesderive from microdata → admin1restricted — no redistributionDerive-then-host aggregate indicators only (manual pipeline)
UNDP HDICACC1 P2Human Development Index (health/education/income)XLSX, admin0ISO3 joinopen — CC BY 3.0 IGO (commercial OK)Mirror the annual XLSX
GDL SHDI / Area DBCACC2 P1The subnational HDI + ~130 indicators — the subnational upgrade of UNDP HDICSV + R API + GDLCODE shapefiles, admin1(+)GDLCODE joinNC — non-commercial + attributionDerive-then-host SHDI keyed to GDLCODE + ship GDL shapefiles. Fills the HDI subnational gap
Meta Relative Wealth IndexCACC2 P1ML-predicted relative wealth, 93 LMICsgridded CSV, 2.4 km → any adminpop-weighted zonal mean (via WorldPop) → admin0/1/2CC0 — public domainDerive-then-host admin table + keep grid. Finest granularity, cleanest licence
FEWS NETCACC2 P1Acute food-insecurity classifications + livelihood zones (IPC-compatible)FDW REST API + GeoJSON, admin2 + livelihood zonesadmin2 / LZ join (geometry native)open (USAID; attribution)Federate FDW API + mirror admin2/LZ boundaries — open subnational reach IPC/CH misses

Verdict. Additions are mostly public, low-risk integrations (memo action a) — good early Hub wins. The real design decision is subnational coverage: add the CACC2 trio (GDL SHDI, Meta RWI, FEWS NET) so admin1/2 mode is more than a single country colour. Non-commercial flags on IPC, JMP, GDL are fine for GCF/non-profit use but must ride through to any LLM-skill citation.

Overlaps → GDL SHDI is the subnational version of UNDP HDI (promote GDL for admin1/2, keep HDI for the national headline); FEWS NET and IPC/Cadre Harmonisé both classify acute food insecurity (FEWS adds livelihood zones + open licence + reaches gaps IPC misses); ND-GAIN and INFORM Risk are both national composite indices — one may suffice.

💬 Comment / discuss “Vulnerability & socioeconomic”

5 · NDC & NAP alignment DEPRIORITISED

Serves CN A.16 · FP D.5. A proposal must show it aligns with the country's own climate commitments — NDC targets and NAP priorities — to demonstrate country ownership. The datasets must answer: what has the country pledged for agriculture, land use and water, and does this project deliver on it?

Memo requirement (verbatim)
Country NDC targets for agriculture, forestry, land use, water; NAP priority actions; LT-LEDS commitments; GCF country programme priorities.GCF Data Notebook Memo, Section 5
Present — in CDH / Atlas
  • none
CACC1 — Cesare's memo
  • UNFCCC NDC Registry
  • NAP Central
  • Climate Watch
  • GCF country programmes
CACC2 — added by this review
  • none new needed — the gap here is NLP text-extraction from PDFs, not more datasets; Climate Watch already structures NDC targets via API

Deprioritised — but unpacked for the dev team. The memo named this the highest-priority new section, but on 2026-04-29 the champion withdrew the automation ask (the NAP/NDC corpus — roughly a dozen documents a year — is too small to justify text-extraction automation; at most a metadata page that links out). We record the conflict rather than silently picking one. Still, if it is ever revisited, here is how each source would connect: three of the four are PDF document registries that need NLP text-extraction; only Climate Watch exposes structured NDC content via an API, so it is the pragmatic connect route.

Table 5 — Theme 5 datasets: NDC & NAP alignment. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & granularity→ connectIP / licenceCDH integration route
UNFCCC NDC RegistryCACC1 P3Official NDC submissions — country targets for agriculture, forestry, land use, waterPDF documents per Party + registry metadata; no structured target APIdownload PDF → NLP-extract targetsUNFCCC terms — free download, no open licenceFederate / link; NLP extraction (non-trivial)
NAP CentralCACC1 P3National Adaptation Plans + priority actionsPDF per countrydownload → NLP-extract priority actions© UNFCCC termsFederate / link; NLP extraction
Climate WatchCACC1 P2Structured NDC content (NDC Explorer) + GHG + pathways — the same targets, already parsedREST API + CSV, country-structuredAPI query by country → structured NDC targetsopen — CC BY 4.0 (Climate-Watch data)Federate API — the structured shortcut that avoids most NLP
GCF country programmesCACC1 P3Country programme prioritiesPDF operational documents, per countryfilter operational-docs by country → linkGCF terms — no open licenceFederate / link; scrape

Verdict. Stays deprioritised (champion withdrew automation; corpus is small). If revisited, start with Climate Watch's API — it already structures NDC targets, so most of the NDC side needs no text-extraction; reserve NLP for the NAP PDFs. A metadata/signpost page linking out is the low-effort interim.

💬 Comment / discuss “NDC & NAP alignment”

6 · Impact potential & beneficiary estimates NEW

Serves CN A.6–A.7 · FP D.1, E.3. A proposal must estimate its impact — how many beneficiaries are reached and, for mitigation, how much GHG is avoided. The datasets and tools must answer: how many people benefit, and what is the tCO₂e mitigation impact?

Memo requirement (verbatim)
List of useful datasets and methods to calculate beneficiaries.GCF Data Notebook Memo, Section 6
Present — in CDH / Atlas
  • GLW4 · livestock activity data
CACC1 — Cesare's memo
  • IPCC EFDB · emission factors
  • FAO EX-ACT · C-balance tool
  • GYGA · yield gaps
  • WOCAT · SLM practices
  • national census
CACC2 — added by this review
  • ESA WorldCover · 10 m land cover
  • EDGAR / FAOSTAT · baseline GHG

Present in the notebook: none (WorldPop population comes via Section 4).

Read this theme as two layers: EX-ACT and the IPCC EFDB are accounting machinery, not spatial datasets — other layers supply activity data per admin unit (land-cover areas, livestock heads, holdings), which the factors/tools convert to tCO₂e for the CN A.6 mitigation claim.

Table 6 — Theme 6 datasets: impact potential & beneficiary estimates. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & resolution→ admin / useIP / licenceCDH integration route
IPCC EFDBCACC1 P1Methodology/DB, not spatial. Tier-1 default emission factors by IPCC category & gasweb DB + Excel exportfactor lookup × activity data → tCO₂e/adminunclear — IPCC copyright, non-commercial defaultDerive-then-host a curated EF lookup (factors + category codes)
FAO EX-ACTCACC1 P1Tool/model, not spatial. Ex-ante carbon-balance appraisal for AFOLU + value chainExcel + online, registrationconsumes admin activity data → project tCO₂efree; no explicit OSS licence statedFederate as a computation engine (or reimplement its coefficients); not hosted as data
GYGA / YPYGACACC1 P2Actual vs attainable yield + yield gap — the adaptation "close-the-gap" impact basistabular, by climate zone / TED (not admin)zone→admin area-weighted crosswalk (state the caveat)NC — CC BY-NC-SA 4.0Derive-then-host yield-gap figures crosswalked to admin (NC-safe evidence table)
WOCATCACC1 P22,400+ documented SLM practices — qualitative adaptation/resilience evidenceQCAT case-study records, site-levelfilter practices by country/region (don't rasterise)NC — CC BY-NC-SA 4.0 (notify wocat.cde)Federate QCAT API, or derive a country-indexed subset
National censusCACC1 P3Ground-truth activity + beneficiary denominators (holdings, heads, population)no common format — per-country PDF/xlsx/portalper-country ETL → common admin schema (GAUL/GADM)per-country; variesDerive-then-host per country — recurring manual onboarding cost, no federation. The weak link
FAO GLW4HAVEGridded livestock density by species (2020) — livestock beneficiaries + enteric-CH₄ baselineGeoTIFF ~10 kmzonal sum → head/admin (× EF)open — CC BY 4.0already held — supplies the animal-numbers activity data for enteric-CH₄ accounting
ESA WorldCoverCACC2 P110 m land cover, 11 classes — AFOLU activity-data + land-use-change baselineCOG 10 m (GEE / AWS)zonal area (ha) per class per adminopen — CC BY 4.0Federate GEE / AWS COG — no mirror needed (heavy); on-the-fly zonal stats
EDGAR / FAOSTAT emissionsCACC2 P1Baseline GHG accounting (additionality) — anthropogenic + agri/land-use emissionsEDGAR grid 0.1° + country XLSX; FAOSTAT tabular + APIzonal / ISO3 join → baseline tCO₂e by sectoropen — CC BY 4.0 (avoid the IEA-EDGAR CO₂ subset)Federate FAOSTAT API (country totals) / EDGAR bulk grid

Verdict. Mitigation accounting (EX-ACT, IPCC EFs) is new territory — CGIAR's prior GCF work is adaptation-only, so the L2 mitigation focal point must be engaged. Build EX-ACT/EFDB as a computation layer, not a tile service. Prefer the open CACC2 trio (GLW4, ESA WorldCover, EDGAR/FAOSTAT — all CC BY 4.0) for activity data; note GYGA and GAEZ v4 are both non-commercial (derive-and-cite only). National census is the recurring manual cost — budget it.

Overlaps → GYGA and GAEZ v4 both give attainable yield / yield-gap and are both non-commercial — pick one, don't ingest both. GLW4 (held) and national census both supply livestock/holding activity data — census only where finer ground-truth is essential.

Open question — for Cesare (CACC1): EX-ACT and the IPCC EFDB are accounting machinery, not spatial datasets. How does he imagine these integrated into a pipeline? Options: (a) the notebook/skill emits admin-level activity data (areas, heads) and a human runs EX-ACT separately; (b) reimplement the relevant EX-ACT / IPCC Tier-1 coefficients inside the pipeline to emit tCO₂e directly; (c) EX-ACT as an external computation service the pipeline calls. Which fits the GCF workflow?
💬 Comment / discuss “Impact & beneficiaries”

7 · Theory of change & GCF portfolio evidence NEW

Serves FP B.2, D.2 (memo action (b)). A proposal must justify its theory of change with evidence and show it is not duplicating what other funders already back. The datasets must answer: what interventions are shown to work here, and what comparable food / land / water projects have the funds already financed?

Memo requirement (verbatim)
Database of approved GCF projects in food/land/water result areas (T4, T5, T6) with structured fields.GCF Data Notebook Memo, Section 7
Present — in CDH / Atlas
  • CACC1 MCF dataset · 5,115 GEF/GCF/AF projects (seed/spine)
CACC1 — Cesare's memo
  • GCF project DB
  • GEF projects DB
  • Adaptation Fund DB
  • CGIAR evidence maps
  • World Bank IEG
  • IFAD IOE
CACC2 — added by this review
  • OECD CRDF · Rio markers
  • IATI Datastore · multi-funder feed
  • GAMI · adaptation evidence

Present: the CACC1 MCF project-level dataset (5,115 GEF/GCF/AF records) is the seed/spine — see the Notebook tab.

Geometry note (all rows): these carry country as a text/ISO attribute only — no sub-national geometry, many regional/global records. For the geoselector they are admin0-after-ISO3-join; this theme is better served by the LLM-skill / citable-output route than by mapping. Keep two functions separate: comparable-projects (funds DBs) vs evidence (EGM/GAMI, feeding FP B.2/D.2 narrative).

Table 7 — Theme 7 datasets: theory of change & GCF portfolio. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & granularity→ countryIP / licenceCDH integration route
GCF project DBCACC1 P2Approved activities: financing, disbursed, results areas, entityOpen Data Library + REST API, project-levelcountry field → ISO3; result-area codes → ToClicence NOT stated (flag ARR until GCF confirms)Federate API (key) or derive CSV — pin licence before hosting
GEF projects DBCACC1 P3All GEF projects: focal area, agency, grant + cofinanceweb DB + CSV export, no APIcountry/regional → ISO3© all rights reservedScrape-export → derive; seek permission or link-out + cite
Adaptation Fund DBCACC1 P2AF projects: country, entity, amounts, sectorweb DB + CSV; also published to IATIcountry → ISO3© ARR; IATI copy openFederate via IATI Datastore (preferred); CSV fallback
CGIAR evidence mapsCACC1 P3Evidence-and-gap maps — study corpus coded intervention × outcome (evidence, not projects)EGM platform + CGSpace recordsstudy→country tags (uneven)3ie EGM CC BY-NC-SA; CGSpace mostly CC BYDerive study metadata for citations (respect NC/SA); harvest CGSpace OAI-PMH / REST
World Bank IEGCACC1 P1Project performance ratings + lessons, ~11,300 assessmentsData Catalog + DDH OpenAPI, project-level ratingscountry field → ISO3; ratings evidence ToCopen — CC BY 4.0 (+ WB attribution terms)Federate DDH OpenAPI — cleanest licence of the set
IFAD IOECACC1 P3Independent evaluation ratings, ~315 projects, 6-point scaleExcel, annual, no APIcountry field → ISO3no explicit CC (verify with IOE)Scrape-export → derive; cross-check IFAD IATI feed
OECD CRDF (Rio markers)CACC2 P1Climate finance by provider × recipient × sector × adaptation/mitigation markerExcel + SDMX API, activity-levelrecipient → ISO3; Rio markers + CRS sector codesopen — CC BY 4.0 (from Jul 2024)Federate SDMX. Best single CACC2 pick for comparables across all funders
IATI Registry / DatastoreCACC2 P1Superset of activity data from many funders (AF, IFAD, WB, UNDP)Datastore API (CSV/JSON/XML), activity-levelrecipient-country query → ISO3; some point locationsopen (per-publisher, generally open)Federate Datastore — one endpoint pulls several CACC1 funds at once
GAMICACC2 P2Global Adaptation Mapping Initiative — 1,682 coded adaptation-evidence articlesZenodo CSV (DOI), literature corpuscountry coded per article → ISO3open — CC BY 4.0Derive-then-host coded CSV; cite per article — the CC-BY evidence complement to CGIAR EGMs

Verdict. Strongly overlaps the Notebook tab — the MCF dataset is the natural engine; sequence them together. Licences are not uniformly open: IEG, OECD CRDF, GAMI and the IATI feeds are clean CC BY; GCF (unstated), GEF and AF (all-rights-reserved), IFAD (unstated) and CGIAR 3ie EGMs (NC-SA) need link-out-and-cite or written permission — don't silently derive-and-host. Use OECD CRDF + IATI as the open comparable-projects backbone.

Overlaps → heavy — the held MCF dataset already unifies GEF/GCF/AF projects, and OECD CRDF + IATI supersede pulling each fund's own DB (demote the individual GCF/GEF/AF DBs to source-of-record / drill-down); CGIAR evidence maps and GAMI are both evidence corpora (GAMI is CC-BY, cleaner); WB IEG and IFAD IOE both supply project-evaluation ratings.

💬 Comment / discuss “Theory of change & portfolio”

8 · Safeguards & gender screening NEW

Serves CN C.4 · FP G.1–G.2. A proposal must pass environmental & social safeguards and gender screening — protected areas, biodiversity, indigenous lands, land tenure, SEAH risk. The datasets must answer: what environmental, social and gender risks does the project zone carry?

Memo requirement (verbatim)
Protected areas and biodiversity hotspots in project zones; indigenous territories; gender gap indices for agriculture; land tenure; SEAH risk indicators by country, Climate Security Programming Dashboard for Climate Finance (CSO).GCF Data Notebook Memo, Section 8
Present — in CDH / Atlas
  • none
CACC1 — Cesare's memo
  • WDPA / Protected Planet
  • IUCN Red List
  • FAO SDG 5.a.x + Land Portal · replaces defunct GLRD
  • OECD SIGI
  • World Bank CPIA
  • CSPD / CSPDxCF · GCF module
CACC2 — added by this review
  • Key Biodiversity Areas
  • LandMark · indigenous lands
  • Global Forest Watch

Present in the notebook: none.

Two delivery routes here: polygon/raster layers (WDPA, IUCN, KBA, LandMark, GFW) drive project-zone overlays in the notebook; tabular-by-country layers (SIGI, CPIA, FAO 5.a.x, CSPD tier) suit the LLM skill (ISO3 join → cited sentence). Split the portfolio by licence, not theme: rehost the CC-BY ones; derive-then-host the non-commercial ones (host the computed overlay stat, never the raw layer).

Table 8 — Theme 8 datasets: safeguards & gender screening. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & geometry→ admin / zoneIP / licenceCDH integration route
WDPA / Protected PlanetCACC1 P1Global protected-areas inventoryvector polygons, site-leveloverlay → % of zone protected, PA countNC, no-redistribute (commercial via IBAT)Derive-then-host the overlay stat only; federate raw to Protected Planet
IUCN Red List (spatial)CACC1 P2Threatened-species range maps + assessmentsshapefile polygons + tabularintersect → threatened-spp count in zoneNC, no-redistribute (IBAT for business)Derive-then-host the count/flag; never mirror ranges
FAO SDG 5.a.1/5.a.2 + Land PortalCACC1 P2Gender land-tenure statistics + legal profiles — the live replacements for the defunct FAO GLRDtabular by country (5.a.x) + country profiles (Land Portal)ISO3 join → admin0FAO open termsFederate SDG portal / Land Portal — do not target the dead GLRD URL
OECD SIGICACC1 P2Gender-discrimination index incl. restricted access to land/resourcestabular, admin0, SDMXISO3 joinopen — CC BY 4.0 (from Jul 2024)Federate OECD SDMX, or mirror the small score table
World Bank CPIACACC1 P2Policy/institutional scores incl. Criterion 8 Gender Equalitytabular admin0, scores 1–6ISO3 joinopen — CC BY 4.0 (IDA countries only)Mirror the score table, or federate WB Data360
CSPD / CSPDxCFCACC1 P1Climate-security / conflict-sensitivity screening; ships a GCF module; ingests INFORM + ACLEDweb tool, country-level, no APIISO3 → risk tier + SEAH contextNC — CC BY-NC 4.0Federate (link to its GCF module) + derive country tier. Sibling CGIAR product — coordinate with CSO
Key Biodiversity AreasCACC2 P2Biodiversity-significant sites — captures unprotected sites WDPA missesvector polygons + GEEoverlay → % of zone in KBA, trigger-species flagrequest-gated, NCDerive-then-host overlay; federate raw via GEE / KBA request
LandMarkCACC2 P2Global map of Indigenous & community lands — the layer that directly answers "indigenous territories"vector polygons + national tenure %overlay → Indigenous-land flag/area in AOIattribution + FPIC / data-sharing conditionsDerive-then-host the flag; respect per-source FPIC terms before mirroring community polygons
Global Forest WatchCACC2 P1Tree-cover loss / deforestation alerts — biodiversity/land-degradation pressure proxyraster 30 m + REST/GEEzonal stats → ha / % loss in zoneopen — CC BY 4.0Mirror derived zonal stats, or federate GFW API / GEE — cleanest licence, safe to rehost derivatives

Verdict. Public global layers, largely project-zone overlay work — good once Sections 3–4 land. Licence split is the rule: rehost the CC-BY set (GFW, CPIA, FAO 5.a.x, SIGI); derive-then-host the non-commercial set (WDPA, IUCN, KBA, CSPD) — computed stat only, federate users to source. LandMark fills the indigenous-territories gap but carries FPIC conditions. ACLED intentionally omitted — its conflict/SEAH signal already rides through the CACC1 CSPDxCF.

Overlaps → WDPA (protected areas) and KBA (biodiversity-significant sites, incl. unprotected) overlap but are complementary — KBA fills what WDPA misses; IUCN Red List ranges feed the same biodiversity screen. Promote the open GFW / CPIA / FAO 5.a.x; the NC layers (WDPA / IUCN / KBA) all share the derive-then-host pattern.

💬 Comment / discuss “Safeguards & gender”

9 · Financial context & justification NEW

Serves CN D.1–D.4 · FP B.5, C.1. A proposal must justify its funding request and additionality — the climate-finance landscape, the adaptation-finance gap, fiscal space and co-financing. The datasets must answer: why is GCF finance needed and additional, and what do comparable approved projects cost?

Memo requirement (verbatim)
Climate finance flows to country/sector; adaptation finance gap; co-financing landscape (MDB, bilateral, domestic); fiscal space indicators; GCF funding benchmarks from comparable approved projects.GCF Data Notebook Memo, Section 9
Present — in CDH / Atlas
  • CACC1 MCF dataset · project financing fields
CACC1 — Cesare's memo
  • OECD DAC CRS
  • CPI Global Landscape · regional only
  • IMF fiscal (Fiscal Monitor / GFS)
CACC2 — added by this review
  • OECD CRDF · Rio markers
  • World Bank IDS · debt / creditors

Present: the CACC1 MCF dataset carries project financing fields (project value, GCF financing, co-financing).

One client covers most of this theme: a single SDMX/Data360 client pulls OECD CRS + CRDF and the IMF/World Bank finance series — all natively country-year, so they drop straight into the geoselector and self-cite (deterministic query URL = citation).

Table 9 — Theme 9 datasets: financial context & justification. Source: HAVE in CDH/Atlas · CACC1 Cesare's memo · CACC2 added by this review. Priority: P1 do first · P2 next · P3 later (rubric above).

DatasetSourceWhat it isFormat & granularity→ countryIP / licenceCDH integration route
OECD DAC CRSCACC1 P1Activity-level ODA + official flows — the canonical "who funded what, where" ledgerSDMX API + CSV; donor × recipient × sector × yearfilter RECIPIENT=ISO, aggregate by purpose code / Rio markeropen — CC BY 4.0 (from Jul 2024; excludes third-party)Federate SDMX-REST (sdmx.oecd.org/public/rest/)
CPI Global LandscapeCACC1 P3Best global estimate of tracked climate finance by source/instrument/use — mostly regional, NOT countryreport + dashboard CSVregional aggregates only (weak country fit)© all rights reserved — no CC grantDerive regional aggregates + cite as a benchmark; do not federate; legal check before republishing figures
IMF fiscal (Fiscal Monitor / GFS)CACC1 P1Fiscal-space evidence: debt, balances, revenue, expenditure (% GDP) + forecastsSDMX API + DataMapper; country × indicator × yearISO/IMF code + indicator (e.g. GGXWDG_NGDP)IMF terms (attribution; automated bulk banned)Federate via World Bank Data360 mirror (clean, un-WAF'd, no bulk ban); avoid IMF's own bulk
OECD CRDF (Rio markers)CACC2 P1Climate-tagged view of CRS — bilateral + multilateral, split adaptation/mitigationExcel + SDMX; provider × recipient × sector × markerfilter recipient ISO; split by markeropen — CC BY 4.0Federate SDMX (same OECD endpoint as CRS). Best CACC2 pick — climate lens, country-native
World Bank IDS (Data360)CACC2 P2External debt stocks / service / creditor composition — the debt-sustainability half of fiscal contextREST API + bulk CSV; country × indicator × creditor × yearquery WB_IDS by ISO3 + indicatoropen — CC BY 4.0 (cleanest of the set)Federate Data360 API (data360.worldbank.org/en/api)

Verdict. Bundle with Section 7 (both lean on the MCF dataset). Ingest CRS + CRDF from one OECD SDMX endpoint (CRDF is the climate view of CRS — not a separate pipeline); route IMF through Data360 to stay within terms. CPI is regional, not country — the biggest surprise; keep it as a citable benchmark only and clear its all-rights-reserved terms before republishing any figure. Dropped: IMF Climate Dashboard (repackages CRDF) and Climate Funds Update (overlaps MCF, no API/licence).

Overlaps → OECD CRDF is the climate-tagged subset of OECD CRS — ingest from one SDMX endpoint, don't treat them as two pipelines; the held MCF dataset overlaps the multilateral-fund flows (use it for GCF/GEF/AF, CRS/CRDF for the wider donor picture); CPI is regional so it duplicates nothing but can't serve as a country layer.

💬 Comment / discuss “Financial context”

Example target output — the Togo SAT hazard-exposure matrix

One illustrative example of a target output is the Togo Sustainable Agricultural Transformation rapid climate-risk assessment (Global Center on Adaptation + Alliance Bioversity-CIAT, April 2025) — a suggestion of the kind of table Theme 3 could produce, not a prescribed standard. Its Table 5 shows crop production value exposed to compound hazards, by region × crop × scenario, with the share of regional crop value in parentheses.

Togo SAT report Table 5 — projected value of crop production exposed to severe climate hazards, by region, crop, and SSP scenario
Togo SAT report, Table 5 (p.19). Rows = region × hazard combination (Dry only / Heat only / Dry and Heat); columns = crop (maize / soybean / rice) × scenario (SSP245 / SSP585); cells = exposed value of production in constant 2015 US$ with the % of that region’s crop value in parentheses. Built from MapSPAM (Togo agricultural census 2012–14) crossed with African Adaptation Atlas hazard layers — the exact pipeline the Climate Rationale notebook runs. A companion Table 6 shows the same in harvested hectares. Reproduced from the source report for reference; note the source header typo “SS245” in the rice column.
Methods used in the Togo example (Annex 2), for reference. CHIRPS + AgERA5 historical (1981–2022); 5-GCM CMIP6 ensemble (ACCESS-ESM1-5, MPI-ESM1-2-HR, EC-Earth3, INM-CM5-0, MRI-ESM2-0); SSP245 & SSP585; baseline 1995–2014; 0.05° resolution; hazard indices NTx35 (crop heat), NDWS (drought), NDWL0 (waterlogging), HSH (human heat) with the thresholds in the report’s Annex Table A.1.
💬 Comment / discuss “Target output”

Data licensing — what the Hub can host

Why this matters before anything is built: a dataset’s licence decides whether the CGIAR Climate Data Hub may legally host a copy of it, only link to it, or use it at all. Get this wrong and the Hub can’t publish the result. It is as much a gating factor as whether the data is technically useful — so it is worth stating plainly for everyone, not just lawyers.

Two separate rights. Hosting the raw data and publishing derived admin1/admin2 products (summaries, maps, tables) are governed differently — and the notebook is almost entirely the second. Good news: even where we can’t host the raw data, we can nearly always compute and publish the derived summaries for non-commercial use.
  • Open licence → the Hub can mirror-host the raw data. Free to copy and redistribute with attribution: NEX-GDDP-CMIP6, ERA5/AgERA5, CHIRPS/CHIRTS, MapSPAM, FAOSTAT, Aqueduct, World Bank WDI/CPIA, WorldPop, HDI, Climate Watch.
  • Non-commercial → federate or link the raw data, don’t copy it. ACLED, DHS, MICS, WDPA, IUCN Red List, IPC, WHO/UNICEF JMP, GYGA, WOCAT, CPI. For our non-commercial research use, all of them still permit computing and publishing derived admin-level stats and maps — the notebook’s actual output — verified per-licence in the evidence log.
  • Unclear licence → resolve before cataloguing. FAO GLEAM, ND-GAIN, INFORM, IPCC EFDB, EX-ACT, and the OECD / IMF series don’t state a clear reuse licence; confirm terms first.

Three conditions attach to the derived products from the non-commercial sets: (1) ShareAlike cascade — IPC, JMP, GYGA, WOCAT and CPI are CC BY-NC-SA, so a derived (or combined) export must itself carry that licence; (2) ACLED outputs must be genuinely transformative (coarse aggregates, not a reorganised dump); (3) publish the statistics, not the raw layer — for WDPA, IUCN, DHS, MICS the source data stays with the provider and we expose derived numbers/maps that link back. Full per-dataset URLs, licences and verification dates: evidence log.

💬 Comment / discuss “Data licensing”

Delivering the data — geoselection & AI-skill access

Two practical questions the review has to answer: under an Atlas-style country/admin geoselector, how does each dataset get summarised? And could an AI skill reach the data — by federating to a live endpoint, or by rehosting? The answer turns on the dataset’s native form (raster / vector / point / tabular) and, for hosting, its licence.

By data type — how a geoselection is summarised

Table 10 — how a geoselection is summarised, by data type.

Data typeDatasetsNative form & accessGeoselection summary → outputAI-skill route
Gridded climate raster NEX-GDDP-CMIP6, ERA5, AgERA5, CHIRPS, CHIRTS NetCDF/GeoTIFF/COG, 0.05–0.25°. NEX-GDDP COGs on public AWS S3; CHIRPS has a COG dir; ERA5/AgERA5 gated behind the Copernicus CDS API (key + async queue); CHIRTS bulk. Zonal statistics (mean / sum) within the selected admin0/1/2 polygon → per-admin timeseries, anomalies, warming stripes. Federate NEX-GDDP / CHIRPS COGs; but the practical route is rehost a precomputed admin-indexed parquet (what hazards_prototype already does). CDS is not real-time — pre-compute.
Gridded exposure raster MapSPAM 2020, WorldPop GeoTIFF. MapSPAM = Dataverse bulk (~10 km); WorldPop = REST API (`worldpop.org/rest/data`) → GeoTIFF (100 m/1 km). Zonal sum within admin × hazard mask → value / population exposed (e.g. the Togo Table 5 example). WorldPop federates via REST; MapSPAM bulk-download-then-host. Exposure product is a derived parquet either way.
Vector polygons WDPA / Protected Planet, IUCN ranges, Aqueduct (HydroBASINS) Polygons. WDPA = global GDB bulk + per-country API; IUCN ranges = spatial download (API is attributes only); Aqueduct = bulk zip, sub-basin level. Spatial overlay / intersection with the admin unit or project zone → area or count within the selection (e.g. % of project zone under protection). Bulk-download-then-host the geometry; derive the admin/zone overlay. ⚠ non-commercial — host the derived stat, not the raw polygons.
Point / event ACLED Point events (lat/lon) + admin1/2/3 fields, event_date. REST API (OAuth token). Spatial join / admin-field aggregation → event count or rate per admin unit over time. Federate via API for ingest; ⚠ NC + transformative rule — host only coarse admin aggregates that can’t reconstruct events.
National tabular (admin0) World Bank WDI, FAOSTAT, ND-GAIN, INFORM, HDI, WHO/UNICEF JMP, CPIA, OECD CRS/SIGI, IMF, CPI One row per country-year. Live APIs: WDI, FAOSTAT, INFORM (JRC), OECD & IMF (SDMX). Bulk-only: ND-GAIN, HDI, JMP, CPI. Row filter / join by ISO3 → national value(s) for the selected country; trivially "geoselected". Federate to the provider API where one exists (WDI, FAOSTAT, INFORM, OECD, IMF); bulk-then-host the rest.
Subnational tabular IPC / Cadre Harmonisé Subnational phase areas as GeoJSON + vector tiles; REST API (`api.ipcinfo.org`, key). The only source here that natively serves subnational polygons via API. Join by admin1/2 unit-of-analysis → food-insecurity phase for the selected sub-area. Federate via API. ⚠ CC BY-NC-SA — derived product carries the same licence.
Project databases (admin0 attribute) GCF, GEF, Adaptation Fund, the CACC1 MCF dataset Project-level rows; country is an attribute, no geometry. GCF = Open Data API; AF = via IATI Registry; GEF = export/scrape; MCF = the delivered CSV. Filter by selected country, join country → admin0 boundary to map → aggregate financing / counts (the CACC1 pipeline notebook). Federate GCF / AF (IATI); scrape GEF; host the MCF dataset as a CDH parquet (its metadata-standard pilot).

Access modes verified live 2026-07-07/08 (see evidence log). ⚠ marks datasets where licence limits what can be hosted — see the licence note above.

Can an AI skill access this — federate or rehost?

Yes — all of it, through one pattern. The skill (or MCP) queries a CDH-hosted, admin-indexed derived layer via a stable metadata URL — the federation-by-metadata design Brayden is building, where the URL never changes and the Hub swaps the backing S3 path underneath. Behind that URL, each dataset takes one of two routes:

Federate — skill hits a live endpoint
When
the provider has a live API/cloud endpoint and the licence allows
Datasets
WDI, FAOSTAT, INFORM, IPC, ACLED, WorldPop, OECD, IMF, GCF, Adaptation Fund (IATI), Climate Watch, GAUL (WFS), NEX-GDDP / CHIRPS COGs
Good for
national tabular (fast, always current); no storage burden
Rehost a derived product — Hub stores it
When
bulk-only, or heavy raster needing zonal stats, or non-commercial data where only the derived product may be hosted
Datasets
MapSPAM, CHIRTS, ND-GAIN, HDI, JMP, WDPA, IUCN, Aqueduct, GEF, the MCF dataset — plus the climate hazards already in hazards_prototype
Good for
performance (~1 s admin queries) and the only lawful route for the NC datasets
The one architecture serves both. Because the Hub hosts the derived admin-indexed layer — not the raw source — the same skill endpoint works for open and non-commercial data alike (deriving + publishing admin summaries is permitted even for the NC sets; see the licence note). Federation is the default where a live API exists and the licence permits; rehosting-the-derived-product covers everything else. Caveats: ERA5/AgERA5 is API-gated (key + async queue — pre-compute, don’t federate live); ACLED aggregates must be coarse enough to be non-reverse-engineerable; ShareAlike (IPC, JMP, GYGA, WOCAT, CPI) propagates to the hosted derivative.
💬 Comment / discuss “Delivering the data”

Feedback

Two ways to respond. With a GitHub account: expand the “💬 Comment / discuss” box under any section — comments post to GitHub Discussions on the use-cases repo. Without one: use the floating 💬 Feedback button (bottom-right), which opens a short form; submissions become tracked issues the coordinator triages.

Draft for task-group review. Facts sourced from the GCF data-requirements memo, the live Climate Rationale notebook, and dataset providers’ official pages (evidence log linked above). Not for external circulation until the champion confirms it is public-safe.

💬 Feedback