Changes between Version 12 and Version 13 of NetCDF_Improvements
- Timestamp:
- Sep 11, 2011, 6:48:26 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetCDF_Improvements
v12 v13 22 22 23 23 === Issues with the current implementation === 24 * NetCDF created by GDAL not CF-1.0 compliant for geographical grids (issue #2129) - patch submitted24 * NetCDF created by GDAL not CF-1.0 compliant for geographical grids (issue #2129) - fixed in trunk 25 25 * netcdf driver does not read and write CF-1.0 coordinate system properly for projected CRS (issue #2893) 26 26 * support for read and write of projected coordinate values … … 28 28 * add proper datum import and export support (being discussed on the mailing list) 29 29 * fix the y-axis for projected CRS, because currently the driver (GDAL) expects top-down for projected crs but netCDF is bottom-up approach. This issue need to be addressed for projected crs so that the resulting file in geotiff -> netcdf conversion (and vice versa netcdf -> geotiff) will not be upside-down when viewed in both gdal and netcdf software. 30 * add CF compliance checker to the autotests (issue #4233) 30 * add CF compliance checker to the autotests (issue #4233) - added in trunk, needs tests for projected CRS 31 31 * support packed data (with add_offset and scale_factor) properly - I don't see where they are used, must be tested 32 32 … … 37 37 === Issues with the current implementation === 38 38 * The import process does not use the Conventions attribute and does not consider different possible Conventions (COARDS, CF-1.0, CF-1.5, etc.) 39 * netcdf history global attribute should be updated. Does GDAL offer a history mechanism? 40 * GDAL version should be recorded in a GDAL global attribute 41 * CF-version of file read could be kept in an internal variable, and default CF-version of output also 39 42 40 43 === Issues for which a patch has been submitted ===