Changes between Version 39 and Version 40 of NetCDF_exportUpdateChanges

Timestamp:

10/15/11 10:10:41 (20 months ago)

Author:

etourigny

Comment:

--

NetCDF_exportUpdateChanges

@@ -89 +89 @@
 '''Related fix''': #2893 [[BR]]
 '''New -co options''': 
-  * WRITE_LONLAT=YES/NO/IFNEEDED (default: YES for geographic, IFNEEDED for projected) ->Note, this not implemented yet
+  * WRITE_LONLAT=YES/NO/IF_NEEDED (default: YES for geographic, IFNEEDED for projected) ->Note, this not implemented yet
   * TYPE_LONLAT=float/double (default: double for geographic, float for projected)
 
@@ -100 +100 @@
 We have also added a '-co' driver option listed above, that allows specification to also write 2D 'lat' and 'lon' arrays, which are specified as part of the CF-1 convention for map projections - but are not actually required for the Unidata-maintained NetCDF Java API and applications built upon them (eg ncWMS, Thredds Data Server).
 
-The 'IFNEEDED' option of WRITE_LONLAT is used in the case of exporting a projection which is not supported by the CF-1.5 standard (e.g. sinusoidal), so any CF-1.5 compliant software can locate the points on a lon/lat map.
+The WRITE_LONLAT=IF_NEEDED option is useful in the case of exporting a projection which is not supported by the CF-1.5 standard (e.g. sinusoidal), so any CF-1.5 compliant software can locate the points on a lon/lat map.
 
 '''Rationale''':
@@ -122 +122 @@
  * and individual corner coordinates (NN, SS, WE and WW).
 
-The new implementation saves the GeoTransform array only if the lon/lat values are not written to the file, and the corner coordinates are never saved as they are redundant.
+The new implementation saves the GeoTransform array only for a geographic CRS, in the specific case that lon/lat values are not written to the file. The corner coordinates are never saved as they are redundant.
 
 We propose adding a new WRITE_GDAL_TAGS driver creation option to allow the user to choose not to write these tags. However it would be set to 'YES' by default.