Skip to content

feat: Add CHC geotiff files as backup path when agents cant access zarr - #5

Merged
bjyberg merged 4 commits into
mainfrom
chc-backup
Nov 18, 2026
Merged

bjyberg merged 4 commits into
mainfrom
chc-backup

Conversation

@bjyberg

@bjyberg bjyberg commented Nov 18, 2026

Copy link
Copy Markdown
Member

On Alliance Claude for example, the chc website is permitted, but the others are not. This tries the zarr datasets first, if they cannot be accessed for chirps/chirts, it now falls back to the CHC hosted data

Some agent sandboxes block S3 but allow data.chc.ucsb.edu. The yearly NetCDFs there hold the same rnl product, chunked, so point reads stay small. Retries back off on the server's 429 rate limit.
Same reason as CHIRPS: data.chc.ucsb.edu is reachable where Hugging Face is not, and serves the CHIRTS-ERA5 data the Hugging Face store copies.
Otherwise check.py reports CHIRPS and CHIRTS as blocked in sandboxes where their fallback works.
@bjyberg
bjyberg merged commit 6b34395 into main Nov 18, 2026
2 checks passed
@bjyberg
bjyberg deleted the chc-backup branch November 18, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant