Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Vision for Legacy HDF (.he4), SMAP and ICESat-2 migration to the Cloud


Some preliminary thoughts:

  • Separate support for Projection (Swath-Projection-Gridding) ?
    • Vs. Regridding (same projection)
    • Vs. Reprojection (Equal-Area to Conformal, Cartesian to Polar, others)
  • Feature expansion in Cloud Services to match on-prem
    • Less any no-longer-relevant featues (H5-EOS)
    • “Main Services”: HOSS for L3/L4, Trajectory Subsetter for L1/L2
      • For Variable and Spatial/Temporal Subsetting -  
      • BBox , and Shape/Polygon Region
    • + Formats, Projection/Reprojection
  • Back-Port to on-prem - Harmony-on-prem within SDPS ?
    • To potentially retire legacy code base for data not yet (or never) migrated
    • Open port on EIL for a localized Harmony access?
    • EDSC/CMR reconfiguration

...

  • Trajectory Subsetter √ (done)
  • GeoTIFF special case - minor adapter enablement
    • + some coding refinement
    • -or- Refactor as separate micro service (SMAP-to-GeoTIFF)?
    • -or- Gridding as an option within HDF-5 format (SMAP-to-Grid)
      • + GeoTIFF formatter (HGA) √ (preferred)
  • Reprojection (chaining): GeoTIFF/COG => HGA, HGAother?
  • .hef5 ,   NetCDF format output (.nc4) ? 
    • micro services - lifted from on-prem is possible
    • from GeoTIFF, w/ aggregation 
    • -or- aggregation vs. from HDF-5 w/ Grid & Trajectory handling?
  • ShapeFile format output (.shp) - as a micro service, 
    • lifted from on-prem is an option
  • ASCII format output? - rewrite to Python, chaining
    • CSV
      • Choice of delimiters? (Comma, tab)
      • “Row of vars” per time-stamp? (see Tabular ASCII)
      • “Time, nameName, value” formatValue” format
        or “Time, Value” per variable?
      • GDAL standard?
    • “Tabular-ASCII” - lifted from on-prem, or rewritten
      • Textual layout
      • “Row of vars” per time-stamp
      • Blocked per group and/or frequency (count)
    • OPeNDAP / GDAL formats (HGA) various choices ?


Re. ICESat-2 L1/L2 - multiple divergent data products

L1/L2 (Trajectory) -

  • Trajectory Subsetter √ (done)
  • No Gridding, Reprojection nor NetCDF format requirements
  • ShapeFile (.shp) and ASCII formats (see above), but with size constraints

...

  • HOSS - with configuration file entries, minor updates?
    • Assuming OPeNDAP updates possible/expected- not sure how feasible
  • HDF4 - NetCDF pre-processor.
  • Note .nc4 is default output .nc4 - default for HOSS (common .h5 to .nc4 “fixer”/Formatter - built-in to OPeNDAP!)
  • ?? HEG rewrite ?? (Unlikely, except possibly - to capture unique reprojection/interpolation handling)
  • Regridding/Reprojection feature (TBD)
  • GeoTIFF - HGA

...