Catalog NEX-GDDP-CMIP6 timeseries_mean_month aggregates (A + new trends B) in STAC / CDH

[peetmate]

@bjyberg — two domain=climate/.../processing=timeseries_mean_month/timeframe=3months/ parquet aggregates are now live on S3 but not in the STAC catalog (the catalog currently holds the per-year processing=analysis-ready .tif rasters under climate/nex-gddp-cmip6-hazards, not these admin-aggregated parquets). Flagging for cataloging + a steer on the CDH path.

A — ensemble_season_timeseries (republished 2026-06-12, CR-119)

• Keys: …/period={1995-2014,2021-2040,2041-2060,2061-2080,2081-2100}/baseline=1995-2014/variable=ensemble_season_timeseries.parquet
• Pruned to the notebook read-set + iso3-first sorted/prunable; restored CR-060 q17/q83(_anomaly) + n_models.
• Schema: iso3, admin0_name, admin1_name, scenario, timeframe, year, hazard, season, baseline_name, mean, sd, q17, q83, n_models, mean_anomaly, sd_anomaly, q17_anomaly, q83_anomaly
• Prior objects backed up to .preFix-20260612-125412.bak.

B — ensemble_season_trends (new, 2026-06-12, CR-117)

• Keys: …/period={2021-2040,2041-2060,2061-2080,2081-2100}/baseline=1995-2014/variable=ensemble_season_trends.parquet (~8 MB each)
• Schema: iso3, admin0_name, admin1_name, scenario, timeframe, season, hazard, stat, mean, sd, stat ∈ {value_slope, value_decade}
• Per-GCM Theil–Sen then ensembled (mean/sd). Significance deferred (AR6 agreement metric, CR-117).

CDH metadata

Drafted a CDH v0.0.1 record for B against your standard: metadata/cdh/ensemble_season_trends.cdh.yaml (TODOs: license, citation, confirm Africa bbox). Can do a parallel one for A.

Questions

1. Right path to catalog these — author CDH YAML → your stac/ build, or a direct collection under climate/? New collection (e.g. nex-gddp-cmip6-hazard-timeseries) vs items under the existing nex-gddp-cmip6-hazards?
2. Item granularity — one item per period? per period×variable? (non-geo admin tables → continental Africa bbox, parquet asset.)
3. Does the CDH record format/fields look right for v0.0.1, or adjust before I template the rest?
4. License + citation to use (the YAML TODOs)?

Filed from hazards_prototype (CR-119 / CR-117).

[peetmate]

FYI on two adjacent STAC freshness gaps (NOT asking for action yet — both sit downstream of producer state you/others already own):

1. exposure_catalog version-stale — cataloged collections are mapspam2017 + GLW3_livestock, but the live canonical domain=exposure is spam2020v1r2 + glw4 (published late-2025). Pending the exposure-producer-drift triage (atlas_notebooks/.../2026-05-26_exposure-producer-drift.md).
2. hazard_risk_vop_* collections are empty stubs (0 items) despite VoP data on S3. The current domain=hazard_exposure/source=nex-gddp-cmip6 canonical is minimal (3 files, 2026-05/06) with CR-068 findings still open.

Logging here so the cataloging gap is visible; will follow up once those producer issues close.

[peetmate]

Third aggregate now live (CR-120) — same timeseries_mean_month/timeframe=3months tree, please include in the cataloging steer:

C — ensemble_season_variability (2026-06-15) — per-GCM interannual variability, ensembled.

• Keys: …/period={1995-2014,2021-2040,2041-2060,2061-2080,2081-2100}/baseline=1995-2014/variable=ensemble_season_variability.parquet
• Schema: iso3, admin0_name, admin1_name, scenario, timeframe, season, hazard, stat, mean, sd, pct_gcms_increase, stat ∈ {iav_sd, iav_delta}.
• iso3-first sorted + prunable (null-stat=0). Baseline file carries absolute iav_sd only; futures add iav_delta + pct_gcms_increase (NDD hazard has no historical baseline → its Δ/agreement are null by design).

So the cataloging question now spans three variables under that tree: ensemble_season_timeseries (A), ensemble_season_trends (B), ensemble_season_variability (C).

[peetmate]

@bjyberg — a third dataset of the same class (admin-aggregate parquet, region=africa, not in STAC) is now live, same questions as A/B above.

C — hazard_change (new, 2026-06-24, CR-093)

Whole-period change + inter-model spread products from R/2.2_haz_change.R, published to canonical CDH-style keys:

• s3://digital-atlas/domain=climate/type=hazard-indices/source=nex-gddp-cmip6/region=africa/processing=hazard-change/timeframe=annual/variable=<name>.parquet
• 10 objects (by-model + ensemble) covering: PTOT % area change + Δmm (ptot_change, ptot_diff), THI livestock heat % area (thi_perc_area), NTx crop heat % area (ntx_perc_area), NDWS/NDWL0 drought/wet frequency (haz_freq).
• Keyed iso3, admin0_name, admin1_name, admin2_name, scenario, timeframe, … + payload (mean/min/max/sd on ensembles). iso3-first sorted/prunable; non-finite → NULL; validated 10/10; prior objects backed up before republish.
• Methods note (2026-06-24): PTOT relative %-change is masked where the 20-yr historic baseline PTOT < 100 mm/yr (hyper-arid denominator → spurious %); absolute Δmm reported everywhere. Rationale + sources captured in the hazard_change record in metadata/data.json (hazards_prototype@develop).

Same Qs 1-4 as above apply to C — new collection vs items under existing, granularity, CDH v0.0.1 fields, license/citation. Happy to template CDH YAML for A + C once you steer the path.

Filed from hazards_prototype (CR-093).