Issue #45 stubbed out the geometry section of the UMM-G output with hard-coded values. Add the necessary logic to pull geospatial information from a netCDF file and add it to the UMM-G output. The goal is to handle the geospatial metadata generation automatically, not with an override file created by the operator.
Acceptance criteria:
A Gpolygon should be added to the UMM-G output. (Simple polygon, no holes)
Ensure spatial metadata is in the correct order—umm-g metadata spatial information for gpolygon spatial representation must list vertex order counter-clockwise.
Existing NSIDC-0081 metadata can serve as a reference for the expected Gpolygon. The existing metadata was created using MetGen, using the override in which the operator created a .spo file (MetGen did no "thinking").
afitzgerrell
commented
1 week ago
Issue #45 stubbed out the geometry section of the UMM-G output with hard-coded values. Add the necessary logic to pull geospatial information from a netCDF file and add it to the UMM-G output. The goal is to handle the geospatial metadata generation automatically, not with an override file created by the operator.
Acceptance criteria: