Versions Compared

Old Version 21

changes.mady.by.user David Auty

Saved on

compared with

New Version 22

changes.mady.by.user David Auty

Saved on

Key

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

...

  • General enable/configure/test Main service per Datasets
    • Trajectory Subsetter - Available as a cloud data service and mostly pre-configured for SMAP & ICESat-2.  Should only require metadata connections.
    • HOSS - Minor updates for SMAP, ICESat-2 special cases (e.g., TRT-290 - HOSS support for SMAP L3)
      • Missing CF for SMAP (configuration files already accommodate, mostly)
      • Note e.g., HOSS (OPeNDAP) produces NetCDF-4 output, even for HDF-5 inputs, but .nc4 is built upon .h5.  Likely we will end up with .nc4 is as default and preference over output format, and as a preferred format over "plain" .h5 in all cases and . "plainPlain" .h5 (native) for processed outputs is not available.
      • Lower-Left Orientation - is a known issue, not currently supported in HOSS.
      • Edge aligned dimension scales - also a known issue.
    • SMAP to GeoTIFF - Special case in Trajectory Subsetter for SMAP data,
      • Generally, just needs enabling existing code for In-Cloud deployment
      • However, recommending revised implementation - SMAP to Gridded HDF-5 format + Common HDF-5 to GeoTIFF/other (see following)
  • Harmony-GDAL-Formatter - GeoTIFF/COG - ICESat-2 & SMAP (L3/L4 Formats)
    • Refactor HGA - split archive, 2 or 3 separate services - HGF, HGA, HGAgg, (TRT-213 - Images for GITC?)
    • COG formatter - GeoTIFF source (1st?), NetCDF source (2nd?)
    • See HGA Roadmap
  • L1/L2 Formats (mostly custom - port on-prem code to in-cloud):
    • Shapefile (Vector data, ESRI-based file format, Custom code exists, GDAL?)
    • NetCDF (Custom upgrade .h5 to .nc4 with CF support, L1/L2, port to in-cloud)
    • ASCII (CSV, Tabular, other? - Custom code exists, GDAL?)
    • kml, kmz (GDAL + custom front-end) - requirements?
  • (Possible Trajectory Subsetter rewrite - Python - as a maintenance issue)
  • L3/L4 Reprojection - PyResample based?
  • HGA-Reprojection? (SMAP focus, currently GDAL based, but not clear if GDAL specific option is best path)
  • Projection Gridding for Trajectory Data (based on Swath-Projector, e.g. for ICESat-2) ?
    • Minor fix for 1D vs 2D inputs
    • Not specifically an on-prem feature, but from use-case analysis - an opportunity
  • Legacy HDF-4 file handling (HDF-4 to NetCDF/CF converter as pre-step, OPeNDAP?)

...