Problem
The cd package now ships tmax/tmin on STAC (unified EDH-derived grid, 1950-2025) but the current vignette only narrates tmean and soil_moisture. tmax/tmin carry distinctive climate signals that tmean hides:
- Overnight lows (tmin) warm faster than daytime highs (tmax) under climate change — one of the clearest regional fingerprints
- Diurnal range (tmax - tmin) is a separate trend affecting evapotranspiration, fire weather, and ecosystem stress
- Specific thresholds tied to biology use tmax/tmin directly (frost days, growing-degree days, heat-stress days)
Proposed content
One or two additional sections/chunks in vignettes/climate-departure.Rmd:
- tmin warming figure: annual tmin anomaly for the AOI, compared side-by-side with tmean. Commentary on "nights are warming faster than days" as a clear departure signal.
- Diurnal range trend: compute
tmax - tmin per year, plot trend. Brief commentary.
- Optional: threshold-based derived metric — frost days (tmin < 0°C), heat days (tmax > 30°C), or growing-degree days for a biologically relevant AOI.
Keep it short — the vignette is long enough. Goal is to showcase that the package carries and supports tmax/tmin as first-class citizens, not to duplicate every analysis twice.
Out of scope
- Adding new cd functions (existing
cd_extract / cd_anomaly / cd_compare already handle tmax/tmin once the data is in the catalog, which it now is).
- Deeper narrative restructuring.
Tracking
Depends on #36 (EDH migration) landing so the tmax/tmin COGs are on S3 before the vignette references them. Once merged, this issue can be picked up any time.
Relates to #36
Relates to NewGraphEnvironment/sred-2025-2026#23
Problem
The cd package now ships tmax/tmin on STAC (unified EDH-derived grid, 1950-2025) but the current vignette only narrates
tmeanandsoil_moisture. tmax/tmin carry distinctive climate signals that tmean hides:Proposed content
One or two additional sections/chunks in
vignettes/climate-departure.Rmd:tmax - tminper year, plot trend. Brief commentary.Keep it short — the vignette is long enough. Goal is to showcase that the package carries and supports tmax/tmin as first-class citizens, not to duplicate every analysis twice.
Out of scope
cd_extract/cd_anomaly/cd_comparealready handle tmax/tmin once the data is in the catalog, which it now is).Tracking
Depends on #36 (EDH migration) landing so the tmax/tmin COGs are on S3 before the vignette references them. Once merged, this issue can be picked up any time.
Relates to #36
Relates to NewGraphEnvironment/sred-2025-2026#23