🤸🏻 ODD PI 26.4 Stretch Objectives

Description

This issue is a container for ODD's multiple stretch objectives. ODD has limited extra capacity, but we would like to capture these ideas in case other objectives are completed early or capacity is added to the team.

🧊 Stretch Objective 1: Apache Iceberg STAC backend: icestac

Why now?

• We have demonstrated that STAC Geoparquet is a really useful format for hosting STAC metadata and making it accessible to clients without imposing any burden on an API (just read the data from cloud storage with rustac/duckdb)
• There isn’t an existing way for an organization to deploy STAC Geoparquet in place of something like PgSTAC
  • How to serve/advertise the data?
  • Appending new records is not very simple
• Apache Iceberg is a well-established system for maintaining living/breathing parquet-backed data stores with
• ACID transactions (which is a critical feature for collections that are continually adding new data)
• We should build a system for maintaining a STAC catalog (multiple collections) in an Apache Iceberg store. This will require assessing the existing functionality around spatial data in Iceberg and duckdb.

Role/LOE

Questions

Stretch Objective 2: 📝 Cloud-Optimized Data Guidance

Why now?

Given our expertise and community involvement, we are well positioned to continue to develop cloud-optimized data guidance for NASA and the broader community.

Role/LOE

0.2 (<1 sprint)

Tasks/Acceptance Criteria

• Update diagram, addressing feedback on vision from ODD Team Leads Meeting - 2026/06/29 - Notes by Gemini
• Transition plan
• Share and get feedback and buy in during virtual stores co-working session
• Data lifecycle follow up from meeting: https://github.com/NASA-IMPACT/2026-odsi-retreat/issues/1
  Includes instruction on how to decide storage location and policies for icechunk stores
  Draft PR for Cloud-Optimized Data Decision Tree in guide.cloudnativegeo.org

Other stretch objectives

• 🏁Warped chunk caching
• ⚖️ Production ready multiscales pipeline
• 🚀Demonstration of flux with existing icechunk stores
• 🔥Iceberg for Fires data: 13. Outpacing the Flames: Fire Behavior Data, Delivered Fast; collaboration with data services
• Deck.gl-raster work: TBD if this will be to work on the disasters use case, protected bucket access, or CSDA footprint clustering.
• Create a more consumable (browsable? something more like 2i2c.org/roadmap?) zarr-python roadmap. Goal to be more transparent about zarr-python ongoing and future development activities.

This is a container for several unrelated objectives, and it names no source files or tests. Start by selecting one objective and reviewing its linked issues or documents; the cloud-optimized guidance objective has the clearest tasks and acceptance criteria. Done means completing the selected objective's stated deliverables and feedback steps.