Changes between Version 2 and Version 3 of NetCDF_Improvements
- Timestamp:
- Aug 31, 2011, 1:10:01 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetCDF_Improvements
v2 v3 10 10 = Topics = 11 11 12 == 1 -UNIDATA NetCDF Conventions ==12 == UNIDATA NetCDF Conventions == 13 13 14 14 UNIDATA recommends the use of the CF Conventions (NetCDF Climate and Forecast (CF) Metadata Conventions) where applicable.[[BR]] … … 19 19 * [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.5/cf-conventions.html CF-1.5 - NetCDF Climate and Forecast (CF) Metadata Conventions] 20 20 * [http://ferret.wrc.noaa.gov/noaa_coop/coop_cdf_profile.html COARDS conventions (1995 standard that CF Conventions extends and generalizes)] 21 * [http://cf-pcmdi.llnl.gov/conformance/compliance-checker/ CF compliance checker] [http://pypi.python.org/pypi/cfchecker/2.0.2 (python script)] 21 22 22 23 === Issues with the current implementation === 23 24 * NetCDF created by GDAL not CF-1.0 compliant for geographical grids (issue #2129) - patch submitted 24 * netcdf driver does not read CF-1.0 coordinate system properly(issue #2893)25 * support packed data (with add_offset and scale_factor) 25 * netcdf driver does not read and write CF-1.0 coordinate system properly for projected CRS (issue #2893) 26 * support packed data (with add_offset and scale_factor) properly - I don't see where they are used, must be tested 26 27 27 == 2 -Metadata ==28 == Metadata == 28 29 29 30 GDAL and NetCDF support metadata in different ways, which should be harmonised. … … 39 40 40 41 41 == 3 -Datum issues ==42 == Datum issues == 42 43 43 44 CF supports Datum information but does not specify how datum ids (such as those found in EPSG codes) should be stored in the netcdf file … … 48 49 49 50 50 == 4 -Dimension issues ==51 == Dimension issues == 51 52 52 The driver should handle properly a time and Z-axis in a way t aht they they are not lost when importing and exporting.53 The driver should handle properly a time and Z-axis in a way that they they are not lost when importing and exporting. 53 54 54 55 55 == 5 -I/O issues ==56 == I/O issues == 56 57 57 * Fix access to different netcdf file types: nc (classic), nc2 (64-bit) and nc4 (NetCDF4 with HDF5 support) - #3890 and #2379 58 * Add option for file type at export 58 * Support Create() method so that gdalwarp can be used on a netcdf file 59 * Fix access to different netcdf file types: nc (classic), nc2 (64-bit) and nc4 (NetCDF4 with HDF5 support) - #3890 and #2379 - patch submitted 60 * Add option for file type (nc,nc2,nc4) at export 59 61 * Support compressed netcdf data (szip, zip) and CF-1 packed data 60 62 61 == 6 -Compatibility with other software ==63 == Compatibility with other software == 62 64 63 65 The driver should be compatible for import and/or export (with proper visualisation) with at least the following software: 64 66 65 67 * ncdump from UNIDATA netcdf 66 * ncview (http://meteora.ucsd.edu/~pierce/ncview_home_page.html) 67 * GrADS - Grid Analysis and Display System (http://www.iges.org/grads) 68 * CDO - Climate Data Operator (https://code.zmaw.de/projects/cdo) 69 * NCO - netCDF Operators (http://nco.sourceforge.net) 68 * [http://cf-pcmdi.llnl.gov/conformance/compliance-checker/ CF compliance checker] 69 * [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview] 70 * [http://www.iges.org/grads GrADS] - Grid Analysis and Display System 71 * [https://code.zmaw.de/projects/cdo CDO] - Climate Data Operator 72 * [http://nco.sourceforge.net NCO] - netCDF Operators 70 73 * others to come... 71 74 72 == 7 -Test files ==75 == Test files == 73 76 74 77 A place should be set up to store NetCDF sample files, provided they are free under the terms of http://download.osgeo.org/gdal/data/COPYING . [[BR]] … … 77 80 78 81 79 == 8 -Contribution ==82 == Contribution == 80 83 81 84 * Contributors are welcome and could be identified here in 3 categories: Ideas/reporting, testing, and/or development.
