ODD PI 26.2 Objective 3: 🤗 Support community adoption of the technologies incubated by EODC and VEDA

[abarciauskas-bgse]

Why us?

The ODD team needs to remain aware of the latest technologies in order to keep pushing forward the envelope of what’s possible. We also need to make sure that the potential of technology that we build is fully realized. Both of these goals rely on remaining connected with the broader community.

Why now?

It takes constant effort to remain at the forefront of building solutions. Leaving off the community objective for any quarter increases the probability of our technology failing to make an impact.

Milestone

• ESIP January Meeting

Acceptance Criteria

• Host session, participate in panel, and present on VirtualiZarr at ESIP January meeting (Max, Aimee)
• Coordinate the Pangeo showcase
• Lead the GeoZarr OGC SWG (Max)
• Submit ESCO standards updates for Zarr (Max)
• Virtual stores co-working sessions (Aimee leads, Max supports)
• ESIP cloud computing cluster reboot with chunk manifest committee/working group (Aimee)
• Develop and introduce documentation for developing virtual datasets (Tyler)
• Collaborate on maintenance of the earthaccess library (Chuck)
• Services-oriented tab in https://guide.cloudnativegeo.org/ and/or Data Product Development Guide Guidance (DPDG) for compliant datasets with xarray and virtualizarr (TBD)
• Work with science support to establish cross-VEDA practice of reporting on open source contributions (https://github.com/NASA-IMPACT/veda-analytics/issues/198) (TBD)
• Support NISAR evaluation (https://github.com/NASA-IMPACT/active-maap-sprint/issues/1336) (Henry)
• Stretch: 1 blog post (Aimee: for ESIP "Are we doing cloud right?", Max: history of chunk manifest, obspec-utils)

LOE: 0.2 FTE for 4 sprints

[maxrjones]

FYI I heard feedback from the community that it'd be valuable to keep the pangeo showcases continuous, even if they're scoped down a bit. I'm hoping to organize some to start in March and find a co-organizer.