Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

transition to Harmony API from on-prem EGI #530

Open
10 tasks
JessicaS11 opened this issue Jul 3, 2024 · 0 comments
Open
10 tasks

transition to Harmony API from on-prem EGI #530

JessicaS11 opened this issue Jul 3, 2024 · 0 comments

Comments

@JessicaS11
Copy link
Member

JessicaS11 commented Jul 3, 2024

NSIDC on-premises subsetting services for ICESat-2 data are currently handled by the EGI system. This system is being sunset in favor of the Harmony subsetter. The timeline for this transition is summer into fall 2024, with the goal to turn off EGI by the end of 2024. icepyx currently submits user data orders to EGI and must therefore be transitioned to use Harmony as well. (On a side note, we also aim to use this transition to set ourselves up for future improved integrations with earthaccess and SlideRule as part of our collective broader efforts to streamline the user experience and the way these tools interact).

Some key notes on how this transition will impact subsetting of ICESat-2 data and icepyx:

  • the two-step "search + filter" followed by "order + download with subsetting" workflow will remain unchanged
  • the search and filter step to identify granules of interest will still use CMR*
  • temporal and spatial subsetting will be available for data product Levels 2-3a; Level 3b data (ATL11, >=ATL14) will have no subsetting options available
  • variable subsetting will no longer be available.

*Harmony filters using CMR, so we could combine this into one step, but we still think the search, find services, order/download workflow is best

This parent issue aims to track specific issues required for icepyx to transition to Harmony:

Tasks:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment