Changes between Version 51 and Version 52 of NetCDF_exportUpdateChanges

Timestamp:

Oct 18, 2011, 12:43:46 PM (13 years ago)

Author:

etourigny

Comment:

--

NetCDF_exportUpdateChanges

@@ -141 +141 @@
 The new implementation does not save the GeoTransform array, with the exception of when the GeoTransform cannot be retrieved from the netcdf file (i.e. only for a geographic CRS, in the specific case that lon/lat values are not written ). 
 
-This has the effect that in some cases, the computed pixel width and height (GT(1) and GT(5)) differs by a very small amount (e.g. for 30m pixels, <10^11, the order or a picometer) from the original values in the GDAL raster file, due to various floating-point operations and half-pixel shifts. We feel that this difference is marginal, however should a strong argument be presented, we could save the GeoTransform as before and compare with the values stored in the CF dimensions variable for conflict.
+This has the effect that in some cases, the computed pixel width and height (GT(1) and GT(5)) differs by a very small amount from the original values (e.g. for 30m pixels, < 10^-11^ - about a picometer) in the GDAL raster file, due to various floating-point operations and half-pixel shifts. We feel that this difference is marginal, however should a strong argument be presented, we could save the GeoTransform as before and compare with the values stored in the CF dimensions variable for conflict.
 
 The corner coordinates are never saved as they are redundant. When importing a CF file, if GeoTransform cannot be computed from dimension variables, GeoTransform and corner coordinates are consulted if available.