Skip to content
Canopulse

Technical Archive

Previous releases preserved for reproducibility.

Archived artifacts support verification of previously generated reports and signed packages. They are not used by the current Explorer, reports, downloads, APIs, or CanoProof analyses.

Previous release, CA_2026.07_CES5

July 2026 California release

This release used NLCD tree canopy 2021, NLCD impervious surface 2021, a single-scene Landsat summer 2023 heat composite, CDC/ATSDR SVI 2022, and the CalEnviroScreen 5.0 Pollution Burden percentile. It was the current public model from July 20, 2026 until the October 2026 release. Its signed verification bundle is preserved unchanged so reports generated in that period can still be verified and reproduced. It is not used by current workflows.

Previous pollution-burden release, CA_v2.0

CalEnviroScreen 4.0-based California release

This historical release used the CalEnviroScreen 4.0 Pollution Burden percentile. Its tract records, checksums, metadata, and signed verification bundle remain unchanged so earlier outputs can be reproduced. It is not a current public model.

Los Angeles County baseline, UCRI LA v1.0

May 2026 Los Angeles County release

The first UCRI release covered Los Angeles County only, with county-wide percentiles and the overall CalEnviroScreen 4.0 percentile as its environmental component. LA v1.0 is preserved unchanged as a frozen release for reproducibility. Its definition is recorded in the historical model registry above; it is not the current model.

How to verify an archived bundle

  1. Download the bundle JSON and its .sig.json signature file.
  2. Download the CanoProof public key (canoproof-signing-key.pub).
  3. Compute the SHA-256 of the bundle file and check that it equals bundleSha256 in the .sig.json.
  4. Verify the Ed25519 signature in the .sig.json over those 32 digest bytes with the public key, using OpenSSL or any Ed25519 library. A match shows the bundle is the one Canopulse published; it does not validate the method.

Previous Canopulse releases are preserved separately for reproducibility and are not used in current reports. Superseded data files are served with a superseded notice; the current release is in the reproducibility package.