Page History

...

• General enable/configure/test Main service per Datasets
  • Trajectory Subsetter - mostly pre-configured for SMAP & ICESat-2
  • HOSS - Minor updates for SMAP, ICESat-2 special cases (e.g., TRT-290 - HOSS support for SMAP L3)
    • Missing CF (configuration files already accommodate, mostly)
    • Lower-Left Orientation
    • Edge aligned dimension scales
  • SMAP to GeoTIFF - Special case in Trajectory Subsetter for SMAP data, enabling existing code for In-Cloud deployment
• Harmony-GDAL-Formatter - GeoTIFF/COG - ICESat-2 & SMAP (L3/L4 Formats)
  (Note e.g., HOSS (OPeNDAP) produces NetCDF-4 output, even for HDF-5 inputs, but .nc4 is built upon .h5.  Likely .nc4 is default and preference over .h5 in all cases and .h5 is not available).
  
  • 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, Custom code exists, GDAL?)
  • NetCDF (Custom upgrade .h5 to .nc4 with CF support, port to in-cloud)
  • ASCII (CSV, Tabular, other? - Custom code exists, GDAL?)
  • kml, kmz (GDAL + custom front-end?)
• (Possible Trajectory Subsetter rewrite - Python - 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)
  • See HGA Roadmap
• Swath-Projector for Trajectory Data (e.g. 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, OPeNDAP?)
  
  

...