fix(overture): resolve STAC release dynamically via /catalog.json#1063
Conversation
The hardcoded 2026-03-18.0 release has been retired (HTTP 404). Resolve the current release from /catalog.json's `latest` field at fetch time, with a hardcoded fallback (2026-05-20.0) for offline/discovery-failure cases. This stops Overture from breaking on every monthly release rotation.
There was a problem hiding this comment.
Pull request overview
This PR prevents Overture STAC downloads from breaking when older monthly releases are retired by dynamically resolving the current release from https://stac.overturemaps.org/catalog.json (latest field) at fetch time, with a pinned fallback release for discovery/offline failure cases.
Changes:
- Replaces the previously hardcoded
collections.parquetURL with a STAC root + fallback release constant. - Adds
resolve_stac_url()to discover the current release via/catalog.jsonand fall back when discovery fails. - Improves the STAC download failure message to include the resolved URL for easier debugging.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
⏱️ Benchmark run finished in 0m 58s 📈 Compared against baseline: 27s time, 900 MB memory 🟢 Generation time is unchanged. 📅 Last benchmark: 2026-05-24 00:16:20 UTC You can retrigger the benchmark by commenting |
The hardcoded 2026-03-18.0 release has been retired (HTTP 404). Resolve the current release from /catalog.json's
latestfield at fetch time, with a hardcoded fallback (2026-05-20.0) for offline/discovery-failure cases. This stops Overture from breaking on every monthly release rotation.