Recap of your meeting with Radiant Earth Foundation

2 views

Skip to first unread message

Fathom

unread,

11:36 AM (6 hours ago) 11:36 AM

to STAC Community

Meeting Purpose Review community updates and discuss STAC implementation challenges. Key Takeaways - PySTAC v2 is in planning with a PR outlining goals: auto-generating extension classes from JSON schemas and decoupling extension code into separate packages for more flexible development. - "NoSTAC" (Knowledge Interoperable STAC), a system using a knowledge graph to semantically enhance STAC catalogs, is now live on Geoplatform, automating the publication of US Forest Service drone data. - NASA is pursuing official adoption of STAC 1.1, a key step that validates STAC as an OGC community standard and will increase its visibility. - An Archive Extension PR is blocked by a spec change causing a nested class error and a type field name conflict with Python keywords, requiring a local CI fix. Topics PySTAC v2 & Extension Strategy - Goal: Overhaul PySTAC for improved developer experience and flexibility. - Key Initiatives: - Auto-generate extension classes from JSON schemas (Julia Signell). - Rationale: Simplify extension development. - Challenge: Avoid breaking the existing PySTAC v1 extension API. - Decouple extension code from the core PySTAC package (Pete Gadomski). - Rationale: Release extensions as separate packages to enable breaking changes without affecting the core. - Related Work: - STAC Best Practices: Julia Signell is advancing a PR on storage and auth extensions. - STAC Geoprocessing (GeoproK): Pete Gadomski is continuing work to consolidate ecosystem software and improve adoption. STAC Archive Extension PR - Kameswarrao Modali's PR for the Archive Extension is blocked by two issues: - Nested Class Error: A recent spec change by Uwe created a nested archive property, causing a "forward declaration" error in the CI tests. - Keyword Conflict: The spec's type field name conflicts with a Python keyword. - Resolution: Keep the spec name; disable the local linter check. - Action: Kameswarrao must fix local formatting and run tests before the PR can be reviewed. "NoSTAC" Implementation - Project: "NoSTAC" (Knowledge Interoperable STAC), a system that uses a knowledge graph to semantically enhance STAC catalogs. - Status: Now live on Geoplatform, automating the publication of US Forest Service drone data (e.g., mosaics, LiDAR). - Architecture: The knowledge graph is the source of truth, dynamically publishing STAC catalogs. - Challenge: Modeling complex, non-spatial/temporal hierarchies from the knowledge graph in STAC. - Consensus: The STAC spec supports complex trees, but off-the-shelf tooling (e.g., API servers) often does not. NASA STAC Adoption - Pete Gadomski is working with a NASA standards group to draft text for the official adoption of STAC 1.1. - Significance: This move validates STAC as an OGC community standard, increasing its visibility and formal recognition. Next Steps - Julia Signell: Continue experiments with PySTAC v2 extension class generation. - Pete Gadomski: Continue work on PySTAC v2 decoupling and the NASA STAC 1.1 adoption text. - Kameswarrao Modali: Fix formatting and run local tests for the Archive Extension PR. - Justin Lewis: Prepare a demo of the NoSTAC system for a future meeting.