Scope remaining work on iceflow library development

[trey-stafford]

Scope the work required to support the other datasets valkyrie & the iceflow notebooks supported.

[trey-stafford]

High priority tasks (3-5 days)

I consider these tasks a high priority, as they represent functionality currently existing in valkyrie that we would like to replicate:

• Add support for and test BLATM1B v1, ILATM1B v1 and v2 #18
  • work is complete, PR is ready: 18 atm1b data #31
• Add support for ILVIS2 v1 #19
  • Branch https://github.com/nsidc/iceflow/tree/19-support-ilvis2 is a work in progress. I have implemented support to search/download and read ILVIS2 data. Remaining work is to support ITRF transformation. The ATM1B data has lat/lon/elevation fields that are used for ITRF transformation, but the ILVIS data does not (it has multiple lon/lat/elev fields; e.g., CLON, GLON, HLON are all longitude fields). Need to do some digging to figure out which lat/lon/elev fields should be used, or if we need to support transformations of different combinations.
  • remaining work on this task is probably a day or two.
• Add support for GLAH06 version 34 #21
  • Estimating 2-3 days

Medium priority (~7 days)

• Develop example showing iceflow and icepyx working together #29
  • This was not supported directly by valkyrie, but the iceflow notebooks do
    use icepyx to find and visualize ICESat2 data. The notebooks did not support
    ITRF transformations of ICESat2 data, however. For parity with the existing
    notebooks, we may want to add support for the latest version of icepyx.
  • Estimating 2-3 days for integration allowing search/download and ITRF
    transformation support.
• Add confirmation step for downloads #34
  • This issue is to add some support to notify users about especially large
    downloads, and to re-consider the API around that. Currently, the code is
    setup to download whatever matches a users' search, which could be quite
    large!
  • Estimate: 1-3 days.
• ATM1B qfit files without a header use hard-coded ITRF values #35
  • This issue is about how the source ITRF is determined for ATM1B data, and
    will likely require interfacing with PIs of the ATM1B datasets to get
    clarification. I am less certain of an estimate on this, but if we get a
    prompt response from PIs invovled with these datasets, it could only take a
    day or two to make necessary changes (if any).

Low priority (3-5 days)

• Add support for ILVIS2 v2 #20
  • valkyrie did not support ILVIS v2, so this is "low" priority. However, we
    probably want to implement this at some point. Estimate is 3-5 days.