SRS satellite special NetCDF file format

[ggalibert]

Context:

• GoGoDuck is a temporal and spatial subsetting and aggregating tool, such that the result file needs to have its temporal and spatial global attributes updated according to what's actually found in the temporal and spatial coordinates.
• The IMOS NetCDF conventions makes compulsory the use of the following temporal and spatial global attributes. These are basically the global attributes that GoGoDuck needs to update:
  • time_coverage_start / end
  • geospatial_lat_min / max
  • geospatial_lon_min / max
  • geospatial_vertical_min / max

Problem: Satellite NetCDF files seem to include extra temporal and spatial global attributes such as:

• start_time / stop_time
• northernmost_latitude / southernmost_latitude
• easternmost_longitude / westernmost_longitude

See example: http://thredds.aodn.org.au/thredds/dodsC/IMOS/SRS/SST/ghrsst/L3S-1d/dn/2016/20160804092000-ABOM-L3S_GHRSST-SSTfnd-AVHRR_D-1d_dn.nc.html .

What to shall we do? 1- Enforce IMOS NetCDF conventions and get rid of redundant entries in the original files when no strong reason apply:

start_time: 20160803T202039Z
time_coverage_start: 20160803T202039Z
stop_time: 20160804T234329Z
time_coverage_end: 20160804T234329Z

2- Non IMOS compliant spatio-temporal global attributes are not included in the file output by GoGoDuck. 3- Non IMOS compliant spatio-temporal global attributes have to be updated just as the compliant ones in the file output by GoGoDuck.

[ggalibert]

@jonescc can add label question. This is either a GoGoDuck issue or a SRS data issue. @smancini FYI.