Changes between Version 41 and Version 42 of NetCDF_exportUpdateChanges
- Timestamp:
- Oct 16, 2011, 10:23:47 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NetCDF_exportUpdateChanges
v41 v42 148 148 However, on importing data the driver will continue to use the full GDAL WKT specification in the 'spatial_ref' attribute where present (as described in 3.2). This is because the CF-1.5 conventions still don't include provision for saving full Datum information, such as the name and authority of the datum, which is needed for precise transformations. The CF-1 ellipsoid attributes will only be used as a fallback when the full WKT isn't present. 149 149 150 {{{ 151 #!comment 152 ((?? pds: Should we add anything here about special import behaviour, e.g. whether to auto-detect datum on import based on ellipsoid values?? Or should there be an option for this?)) 150 An open question: if the CF metadata includes datum information (but no named datum), should we try to match the spheroid to well known GeogCS (such as WGS84)? This can cause datum errors in some cases (one spheroid can be used in many named datums), as discussed in this thread http://lists.osgeo.org/pipermail/gdal-dev/2011-October/030374.html. 153 151 154 -> etienne: we could look into that for most common datums, but specify that there is no guarantee that a specific datum will be checked for.155 156 }}}157 152 158 153 '''Rationale''':