Skip to content

Commit 349f9d7

Browse files
Release v0.6.3
1 parent fb36fce commit 349f9d7

2 files changed

Lines changed: 8 additions & 2 deletions

File tree

‎DESCRIPTION‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
Package: cd
22
Title: Climate Departure Analysis from ERA5-Land Reanalysis
3-
Version: 0.6.2
4-
Date: 2026-10-09
3+
Version: 0.6.3
4+
Date: 2026-10-10
55
Authors@R: c(
66
person("Allan", "Irvine", , "al@newgraphenvironment.com", role = c("aut", "cre"),
77
comment = c(ORCID = "0000-0002-3495-2128")),

‎NEWS.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
# cd 0.6.3 (2026-10-10)
2+
3+
* Every published COG now carries a **checksum and the run that made it**. Each catalog item's `data` asset has `file:checksum` (a sha256 multihash) and `file:size` (STAC file extension v2.1.0), and the item's properties carry `cd:version`, `cd:sha`, `cd:run_time` and `cd:run_id`, read from GDAL tags written into the COG itself. The daily cube, which is not in the catalog, gets the same per file in `s3://stac-era5-land/daily/manifest.json`. So a changed checksum means changed bytes, and an analysis can record which build it read. A checksum identifies a **build**, not values: the run time is in the bytes, so a rebuild of unchanged data changes it. Every published file is republished once to carry them, so caches validated by ETag download each file again once; if you set `options(cd.cache_revalidate = FALSE)`, run `cd_cache_clear()`. ([#124](https://github.com/NewGraphEnvironment/cd/issues/124), [#127](https://github.com/NewGraphEnvironment/cd/pull/127))
4+
* `cd_cog_write()` gains `tags =`, written into the file as dataset metadata; any `CD_*` tag the input carries is dropped first. `cd_s3_push()` no longer syncs `--size-only` by default (`size_only = FALSE`), so a rebuilt file of unchanged size is uploaded. cd now imports `openssl` and needs `terra (>= 1.8-54)`.
5+
* Producer side, every publish recomputes the hashes and refuses an untagged or undescribed file; after the sync it checks each object's ETag against its file before the catalog or manifest goes up, and a live publish needs a commit on `main`. Checksums and provenance in `cd_catalog()` and the extract functions are [#126](https://github.com/NewGraphEnvironment/cd/issues/126).
6+
17
# cd 0.6.2 (2026-10-09)
28

39
* The published layers now reach **60° N and 140° W**. The ERA5-Land store holds its coordinates with a tiny rounding error (60.0 N is `60.00000000000142`), so the slice that cut British Columbia out of it dropped the top row and the west column: every product was 120 × 260 cells and stopped at 59.95 N, and stations along the Yukon and NWT border, such as 10DA001, got no air temperature. The daily cube and all 59 monthly COGs are rebuilt and republished on 121 × 261 cells (47.95–60.05 N, 140.05–113.95 W). Values in the old cells are unchanged, except the 2025 band of `prcp_annual`, `prcp_winter` and `snowfall_fraction`, where EDH has since revised its daily 2025 precipitation. **Every `cell` number from `cd_extract_daily()` changes**, since the grid gained a row and a column. Cached files refresh by ETag; if you set `options(cd.cache_revalidate = FALSE)`, run `cd_cache_clear()`. ([#123](https://github.com/NewGraphEnvironment/cd/issues/123), [#125](https://github.com/NewGraphEnvironment/cd/pull/125))

0 commit comments

Comments
 (0)