Changes between Version 26 and Version 27 of NetCDF_Improvements
- Timestamp:
- Oct 26, 2011, 4:49:31 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetCDF_Improvements
v26 v27 24 24 25 25 * NetCDF created by GDAL not CF-1.0 compliant for geographical grids (issue #2129) - fixed in trunk 26 * netcdf driver does not read and write CF-1.0 coordinate system properly for projected CRS (issue #2893) 27 * support for read and write of projected coordinate values 28 * export std_parallel variables into a single standard_parallel netcdf attribute 29 * add proper datum import and export support 26 * netcdf driver does not read and write CF-1.0 coordinate system properly for projected CRS (issue #2893) - mostly fixed in trunk 27 * support for read and write of projected coordinate values - fixed 28 * export std_parallel variables into a single standard_parallel netcdf attribute - fixed 29 * add proper datum import and export support - fixed 30 30 * issues with specific projections: 31 31 * rotated_pole (#4285 and #4251) 32 32 * Stereographic vs. Oblique_Stereographic (#4267) 33 * others not assigned a bug report 33 * others not assigned a bug report - wiki:NetCDF_ProjectionTestingStatus 34 34 * add CF compliance checker to the autotests (issue #4233) - fixed 35 * support "coordinates" attribute for projections which are not supported by GDAL/PROJ.4 (i.e rotated pole) (issue #4251)35 * support "coordinates" attribute for projections which are not supported by GDAL/PROJ.4 (i.e rotated pole) (issues #4285 and #4251) 36 36 37 37 … … 42 42 === Issues with the current implementation === 43 43 * The import process does not use the Conventions attribute and does not consider different possible Conventions (COARDS, CF-1.0, CF-1.5, etc.) 44 * netcdf history global attribute should be updated. Does GDAL offer a history mechanism? 45 * CF-version of file read could be kept in an internal variable, as well as CF-version for file creation 44 * netcdf history global attribute should be updated. Does GDAL offer a history mechanism? - needs new function in gdal.h 45 * 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 46 46 47 47 === Issues that have been resolved (in trunk) === … … 58 58 59 59 * Which datum should be set when there is no datum information at all in a netcdf file? WGS84 or none? 60 * How to export datum information that is present in a GDAL file, in a way that it can be restored later? 61 * Import should correctly set appropriate CRS/datum information (e.g. WGS84) from the information in the netcdf file, when sufficient information is available. 60 * 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 61 * 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. 62 62 63 63 … … 72 72 * Support Create() method so that gdalwarp can be used on a netcdf file - #4221 73 73 * ~~Fix access to different netcdf file types: nc (classic), nc2 (64-bit) and nc4 (NetCDF4 with HDF5 support) - #3890 and #2379~~ 74 * Add option for file type (nc,nc2,nc4) at export (#3166) -> fixed in trunk, but needs Win32 support and autotests (nc4/nc2, import conflict w/HDF)75 * Support compressed netcdf data (szip, zip)76 * fix the y-axis for import and export (issues #4251 and #4284) 77 * support packed data (with add_offset and scale_factor) transparently (see bug #3797) 74 * Add option for file type (nc,nc2,nc4) at export (#3166) -> fixed in trunk, but needs Win32 support and autotests 75 * Support compressed netcdf (DEFLATE with NC4 or NC4C) 76 * fix the y-axis for import and export (issues #4251 and #4284) - in trunk option for bottom-up 77 * support packed data (with add_offset and scale_factor) transparently (see bug #3797) - will not implement as no sufficient need 78 78 79 79 References: