Changes between Version 23 and Version 24 of NetCDF_exportUpdateChanges


Ignore:
Timestamp:
Oct 12, 2011, 9:40:29 PM (13 years ago)
Author:
pds
Comment:

Minor update to rationale: remove the bullet point about overriding CF-1 conventions on export.

Legend:

Unmodified
Added
Removed
Modified

  • NetCDF_exportUpdateChanges

    v23 v24  
    1515
    1616(1) The NetCDF view of rasters created by GDAL should conform to CF-1 conventions :- and work for key operations with common NetCDF tools such as creating a WMS or WCS display from a NetCDF raster (eg displaying a WMS using ncWMS, or a WCS using Thredds Data Server).
    17   - If the user wishes to go against NetCDF conventions when exporting, they should use a -co option to specifically request this.
    18 (2) Given (1), the driver should use the CF-1 conventions for storing needed metadata where at all possible, but where necessary add extra metadata so the file can be readable back into GDAL with no loss of information or translation error. A specific example of this is named Datum and EPSG codes, which GDAL needs to supplement CF-1.
    19   - Again, if the user doesn't wish to supplement the files with GDAL metadata, they should specifically disable this using the appropriate -co option.
     17(2) Given (1), the driver should use the CF-1 conventions for storing needed metadata where at all possible, but where necessary add extra metadata so the file can be readable back into GDAL with no loss of information or translation error. A specific example of this is named Datum and EPSG codes, which the current CF convention (CF-1.5) do not include a standard for recording. Therefore, GDAL should by default supplement CF-1 with this information.
     18  - If the user doesn't wish to supplement the files with GDAL metadata, they should specifically disable this using an appropriate '-co' option to the gdal command used.
    2019(3) Given (2), when importing from NetCDF files, the driver will first read from CF-1 conventions, then read supplementary data from GDAL-added attributes. If the two sources conflict, we should report this and consider the CF-1 encoded info as authoritative, which assumes a user has modified the data with a non-GDAL program. 
    2120