NASA-IMPACT / NASA-IMPACT/veda-odd

earthdata support for virtual icechunk stores

Open
#258 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
5
Forks
0
Avg merge
4d 19h
Merged PRs (30d)
3

Description

In the past PI we have demonstrated how to create virtual icechunk stores for nasa data in netcdf/hdf format. With that we got increased performance and potentially large savings in time and storage due to the lack of data duplication.

But with those advantages comes more frictions, mostly due to the complexity of access to both the virtual store as well as the virtual chunk locations. This Task outlines steps to contribute to earthaccess to streamline this process for NASA datasets available in CMR.

While general 'magic'/'behind the scenes' authentication to arbitrary cloud buckets is a very bad idea, we think that in the context of earthaccess this makes sense (we will always have a set of 'trusted' sources here, not an ubounded list) and will enhance the user experience and hopefully drive adoption of virtual zarr within the NASA user community.

Roadmap

  • Review existing work https://github.com/nsidc/earthaccess/pull/964 starter
  • Write concept issue and discuss collaboration of kerchunk and icechunk efforts starter
  • Decide on API (combined kerchunk/icechunk method or separate)
  • Implement
  • Test

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing work in earthaccess PR #964, then read the proposed collaboration scope for kerchunk and icechunk. Clarify whether the API should be combined or separate before implementation, and use the planned tests to verify the completed Earthdata support.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.