...
- General enable/configure/test Main service per Datasets
- Trajectory Subsetter - mostly pre-configured for SMAP & ICESat-2
- HOSS - Special cases for SMAP, ICESat-2 (TRT-290 - HOSS support for SMAP L3)
- SMAP to GeoTIFF - Special case for SMAP data, enabling existing code for In-Cloud deployment
- HGF-COG - 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 (11st), NetCDF source (22nd)
- See HGA Roadmap
- HGA-Reprojection (SMAP focus, currently GDAL based)
- Swath-Projector for Trajectory Data
- 1D vs 2D inputs
- SMAP special cases (spiraling trajectory, but already gridded, and ICESat-2 ?)
- L1/L2 Formats (mostly custom):
- Shapefile (Vector, Custom, GDAL?)
- NetCDF
- ASCII (CSV, Tabular, other?)
- kml, kmz (GDAL)
- L3/L4 Reprojection - PyResample based?
- HGA-Reprojection? (SMAP focus, currently GDAL based, but not clear if GDAL specific option is best path)
- Swath-Projector for Trajectory Data (e.g. ICESat-2) ?
- Minor fix for 1D vs 2D inputs
- Legacy HDF-4 file handling (HDF-4 to NetCDF, OPeNDAP?)
...
- L1/L2 - Trajectory Subsetter - SMAP special case - Gridded outputs
- Enable in existing code base for Cloud deployment
- Gridded outputs to .h5 (Cropped grid, Revive un-merged branch? Not-GeoTIFF as is currenton-prem)
- GeoTIFF formatter (COG, HGA) - chaining. (Alternative is enabling existing on-prem Gridding to GeoTIFF functionality).
- Reprojection special case? (HGA?, chaining)
- L1/L2 - Trajectory Subsetter + general chaining for formats (ICESat-2, SMAP, other?) √
- Projection - use Swath-Projector (minor updates likely, 1D inputs)?
- Potential use cases for Oblique Equal-Area, Oblique Mercator, or Oblique EquiDistance projections
- Note SMAP is spiraling trajectory and is already "gridded" with CEA row/col data
- Not an existing on-prem feature
- Reformat: Vector Data: Shapefile, KML, NetCDF, multi-file: file ASCII
- as micro services, lifted mostly from on-prem implementations (or port/rewrite)- (Note size constraints, e.g., ICESat-2 files)
- NetCDF: CF, metadata upgrade from .h5 h5 (on-prem implementation)
- ShapeFile, KML format output (.shp, .kml, .kmz)
- ASCII format output? - rewrite to Python, chaining - single file per variable
- CSV
- Choice of delimiters? (Comma, tab)
- “Row of vars” per time-stamp? (see Tabular ASCII)
- “Time, Name, Value” format
or “Time, Value” per variable, separate files (variable name as filename?)? - GDAL standard?
- “Tabular-ASCII” - lifted from on-prem, or rewritten to Python
- Textual layout
- “Row of vars” per time-stamp
- Blocked per group and/or frequency (count)
- OPeNDAP / GDAL (HGA): various ASCII format choices ?
- L3/L4 - HOSS + chaining (ICESat-2, SMAP other?) √ (some reconfig, perhaps tweaks to code?)
(Note will be .nc4 output not originally scoped .h5, but hopefully not significant)- ICESat-2 has some notorious quirkiness - Lower-Left orientation, Edge-Aligned dimension scales
- Possible support for missing dimension-scales - use CF-ish config entry for grid-parameters (SMAP)
- see: GeoTagging for a Geo-Located Grid Array
- Reprojection - TBD (I suspect not HGA, rather PyResample based, Data Reprojection Wizard)
- Reformat - GeoTIFF/COG (HGA?), other standard Cloud formats, Zarr
...
{"serverDuration": 75, "requestCorrelationId": "6b22dc6c15958d98"}