Changes between Version 37 and Version 38 of NetCDF_Improvements
- Timestamp:
- 02/14/12 11:56:58 (15 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetCDF_Improvements
v37 v38 24 24 25 25 * ~~NetCDF created by GDAL not CF-1.0 compliant for geographical grids (issue #2129)~~ 26 * netcdf driver does not read and write CF-1.0 coordinate system properly for projected CRS (issue #2893) - mostly fixed in trunk 26 * netcdf driver does not read and write CF-1.0 coordinate system properly for projected CRS (issue #2893) - mostly fixed in trunk and 1.9 27 27 * ~~support for read and write of projected coordinate values~~ 28 28 * ~~export std_parallel variables into a single standard_parallel netcdf attribute~~ … … 47 47 * implement setmetadata and setmetadataitem, tricky because other nc attributes are already written to file 48 48 49 === Issues that have been resolved (in trunk ) ===49 === Issues that have been resolved (in trunk and 1.9) === 50 50 * Duplication in Metadata when translating from NetCDF to NetCDF (issue #4204) 51 51 * metadata from a NetCDF variable should be stored inside the GDAL Band metadata, instead of a global metadata item (issue #4211) … … 53 53 * Floating-point metadata in netcdf file is converted to GDAL metadata as string without sufficient precision (issue #4211) 54 54 * GDAL version saved in GDAL global attribute 55 * CF-version of file read could be kept in an internal variable, as well as CF-version for file creation - in trunk CF-1.5 is exported to file only55 * CF-version of file read could be kept in an internal variable, as well as CF-version for file creation - in trunk and 1.9 CF-1.5 is exported to file only 56 56 57 57 … … 62 62 * Which datum should be set when there is no datum information at all in a netcdf file? WGS84 or none? 63 63 * How to export datum information that is present in a GDAL file, in a way that it can be restored later? - current codes uses spatial_ref 64 * Import should correctly set appropriate CRS/datum information (e.g. WGS84) from the information in the netcdf file, when sufficient information is available. - in trunk compares WKT and CF grid_mapping and checks for conflict. There are issues with auto-detecting named CRS/datum based on spheroid only.64 * Import should correctly set appropriate CRS/datum information (e.g. WGS84) from the information in the netcdf file, when sufficient information is available. - in trunk and 1.9 compares WKT and CF grid_mapping and checks for conflict. There are issues with auto-detecting named CRS/datum based on spheroid only. 65 65 66 66 … … 74 74 == I/O issues == 75 75 76 * Disabled PAM support, as it created incompatibilities and metadata duplication. Will re-enable once things are settled- #4244 and #424576 * ~~Disabled PAM support, as it created incompatibilities and metadata duplication. Will re-enable once things are settled~~ PAM has been re-implemented to store raster statistics only - #4244 and #4245 77 77 * ~~Support Create() method so that gdalwarp can be used on a netcdf file - #4221 (committed to trunk)~~ 78 78 * ~~Fix access to different netcdf file types: nc (classic), nc2 (64-bit) and nc4 (NetCDF4 with HDF5 support) - #3890 and #2379~~ … … 82 82 * ~~support packed data (with add_offset and scale_factor) transparently (see bug #3797) - will not implement~~ 83 83 * ~~support for signed/unsigned Byte data - #4221~~ 84 * ~~Ignore coordinate and bounds variables (CF sections 5.2, 5.6 and 7.1) as raster bands, but expose them as subdatasets - this allows to open files with projected SRS (or dimension bounds) directly, without specifying the variable as a subdataset (added in r23977)~~ 84 85 85 86 References:
