Changes between Version 4 and Version 5 of NetCDF_exportUpdateChanges

Timestamp:

Sep 21, 2011, 10:07:35 PM (13 years ago)

Author:

pds

Comment:

--

NetCDF_exportUpdateChanges

@@ -41 +41 @@
 
 
-=== Continue saving NetCDF "spatial_ref" attribute by default, but add option not to save ===
+=== Continue saving NetCDF custom attribute tags by default, but add option not to save ===
 
-*Related tix*: #4251 [[BR]]
-*New -co options*: -co WRITEGDALTAGS (yes/no, defaults to yes)[[BR]]
-*Rationale*: 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).
+''Related tix'': N/A [[BR]]
+''New -co options'': -co WRITEGDALTAGS (yes/no, defaults to yes)[[BR]]
+''Has back-compat impact?'': No
+
+''Change'':
+
+Currently, as well as following the CF-1 conventions to save projection metadata, the NetCDF driver also writes metadata in several custom attributes:
+ * A "spatial_ref" tag containing full OGC WKT string, including datum and EPSG codes if known
+ * A geotransform array, saved as a string (!GeoTransform).
+
+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.
+
+''Rationale'': 
+
+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).
 
 However, there is certainly a use-case to export to a NetCDF file with no intention to access again via GDAL and use purely for use by CF-1 applications, in which case we don't need to save the added metadata.