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

Add ICESat-2 Harmony subsetting guidance as new Tutorial #352

Closed
asteiker opened this issue Sep 15, 2024 · 1 comment · Fixed by #365
Closed

Add ICESat-2 Harmony subsetting guidance as new Tutorial #352

asteiker opened this issue Sep 15, 2024 · 1 comment · Fixed by #365
Assignees
Labels
enhancement New feature or request

Comments

@asteiker
Copy link
Contributor

As part of NSIDC DAAC's Earthdata Cloud migration, we are adopting Harmony transformation services and beginning with ICESat-2 subsetting support. Although basic Harmony guidance exists in our "How do I subset data granules?" How-to and our Earthdata Cloud Clinic, we would like to include an ICESat-2-specific example that focuses on these primary goals:

  • Teaching how to discover what service capabilities exist for a given collection.
    • In particular, demonstrate the harmony-py capabilities module, so that users can determine which services are available for their data set. ICESat-2 along track data, for example, do not support variable subsetting.
  • Teaching basic harmony-py commands to request a spatial and temporal subset of ICEsat-2 data
  • Teaching how to download and direct access those Harmony outputs in-region.
    • All of the notebooks I can find in our cookbook focus on direct s3 access, so it would be helpful for users to see both download and s3 options.
@asteiker
Copy link
Contributor Author

@andypbarrett I am considering my outline complete. You can grab it from the is2-harmony branch. Notebook link here: https://github.com/NASA-Openscapes/earthdata-cloud-cookbook/blob/is2-harmony/tutorials/IS2_Harmony.ipynb.

I added a few "TODO" notes in specific areas that need further written guidance, though I'd consider all of the content fair game to update, change, and expand! For example, I don't have any content written yet on explaining the output of the capabilities json (to describe what services are available) and descriptions of many of the request and access code blocks.

There is an end to end ATL03 example running in the UAT environment. I added code comments in places where we will want to update to production once we go live. You should have UAT permissions but if you can't get this code to run then let me know.

@itcarroll itcarroll added the enhancement New feature or request label Oct 17, 2024
@andypbarrett andypbarrett linked a pull request Oct 31, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants