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