Changes between Version 9 and Version 10 of NetCDF_exportUpdateChanges
- Timestamp:
- Sep 21, 2011, 10:40:03 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetCDF_exportUpdateChanges
v9 v10 27 27 === Change to a default south-up orientation for NetCDF data === 28 28 29 '' Related tix'': #4251[[BR]]29 '''Related tix''': #4251[[BR]] 30 30 31 '' New -co options'': ?? Should we include an option to allow force assume south-regular?31 '''New -co options''': ?? Should we include an option to allow force assume south-regular? 32 32 33 '' Has back-compat impact?'': Yes - since affects default import and export NetCDF behaviour.33 '''Has back-compat impact?''': Yes - since affects default import and export NetCDF behaviour. 34 34 35 '' Description'':35 '''Description''': 36 36 37 37 When GDAL exports to NetCDF, translate the data so that it is in "south up" orientation, i.e. invert the data from the GDAL default. Likewise upon import from CF-1, assume the data is in "south up" orientation, and translate the y values by default. 38 38 39 39 40 '' Rationale'':40 '''Rationale''': 41 41 42 42 CF-1's default orientation is south-up, and all known current CF-1 -compliant applications expect this. … … 45 45 === Continue saving NetCDF custom attribute tags by default, but add option not to save === 46 46 47 '' Related tix'': N/A [[BR]]48 '' New -co options'': -co WRITEGDALTAGS (yes/no, defaults to yes)[[BR]]49 '' Has back-compat impact?'': No47 '''Related tix''': N/A [[BR]] 48 '''New -co options''': -co WRITEGDALTAGS (yes/no, defaults to yes)[[BR]] 49 '''Has back-compat impact?''': No 50 50 51 51 ''Change'': … … 57 57 The WRITEGDALTAGS driver creation option would allow the user to choose not to write these tags. However it would be set to 'YES' by default. 58 58 59 '' Rationale'':59 '''Rationale''': 60 60 61 61 We assume by default that if users export to a NetCDF file from GDAL, then they may wish to import into GDAL again and retain full information. Currently, the CF-1 convention doesn't allow saving all the projection information that GDAL can manipulate via a WKT (such as named Datums, and EPSG authorities). … … 65 65 === When exporting to NetCDF map projections via GDAL, save projection coordinate variables. Optionally, also save lat and lon mapping variables. === 66 66 67 '' Related tix'': #2893 [[BR]]68 '' New -co options'':67 '''Related tix''': #2893 [[BR]] 68 '''New -co options''': 69 69 * WRITELONLAT=yes/no (default: yes for geographic, no for projected) 70 70 * TYPELONLAT=float/double (default: double for geographic, float for projected) 71 71 72 '' Has back-compat impact?'': No72 '''Has back-compat impact?''': No 73 73 74 '' Change'':74 '''Change''': 75 75 76 76 When exporting rasters to NetCDF, save Coordinate Variables for the projected SRS, as required by the CF-1 convention, normally saved as "x" and "y". … … 78 78 Optionally using -co options listed above, also write 2D 'lat' and 'lon' arrays, which are specified as part of the CF-1 convention for map projections. 79 79 80 '' Rationale'':80 '''Rationale''': 81 81 82 82 The CF-1 conventions specify these coordinate variables as necessary for grids, see [[http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.5/ch05s06.html ch5.6]] and [[http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.5/apf.html App F]] in the document.