Changes between Version 9 and Version 10 of NetCDF_exportUpdateChanges


Ignore:
Timestamp:
Sep 21, 2011, 10:40:03 PM (13 years ago)
Author:
pds
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • NetCDF_exportUpdateChanges

    v9 v10  
    2727=== Change to a default south-up orientation for NetCDF data ===
    2828
    29 ''Related tix'': #4251[[BR]]
     29'''Related tix''': #4251[[BR]]
    3030
    31 ''New -co options'': ?? Should we include an option to allow force assume south-regular?
     31'''New -co options''': ?? Should we include an option to allow force assume south-regular?
    3232
    33 ''Has back-compat impact?'': Yes - since affects default import and export NetCDF behaviour.
     33'''Has back-compat impact?''': Yes - since affects default import and export NetCDF behaviour.
    3434
    35 ''Description'':
     35'''Description''':
    3636
    3737When GDAL exports to NetCDF, translate the data so that it is in "south up" orientation, i.e. invert the data from the GDAL default. Likewise upon import from CF-1, assume the data is in "south up" orientation, and translate the y values by default.
    3838
    3939
    40 ''Rationale'':
     40'''Rationale''':
    4141
    4242CF-1's default orientation is south-up, and all known current CF-1 -compliant applications expect this.
    … …  
    4545=== Continue saving NetCDF custom attribute tags by default, but add option not to save ===
    4646
    47 ''Related tix'': N/A [[BR]]
    48 ''New -co options'': -co WRITEGDALTAGS (yes/no, defaults to yes)[[BR]]
    49 ''Has back-compat impact?'': No
     47'''Related tix''': N/A [[BR]]
     48'''New -co options''': -co WRITEGDALTAGS (yes/no, defaults to yes)[[BR]]
     49'''Has back-compat impact?''': No
    5050
    5151''Change'':
    … …  
    5757The WRITEGDALTAGS driver creation option would allow the user to choose not to write these tags. However it would be set to 'YES' by default.
    5858
    59 ''Rationale'':
     59'''Rationale''':
    6060
    6161We assume by default that if users export to a NetCDF file from GDAL, then they may wish to import into GDAL again and retain full information. Currently, the CF-1 convention doesn't allow saving all the projection information that GDAL can manipulate via a WKT (such as named Datums, and EPSG authorities).
    … …  
    6565=== When exporting to NetCDF map projections via GDAL, save projection coordinate variables. Optionally, also save lat and lon mapping variables. ===
    6666
    67 ''Related tix'': #2893 [[BR]]
    68 ''New -co options'':
     67'''Related tix''': #2893 [[BR]]
     68'''New -co options''':
    6969  * WRITELONLAT=yes/no (default: yes for geographic, no for projected)
    7070  * TYPELONLAT=float/double (default: double for geographic, float for projected)
    7171
    72 ''Has back-compat impact?'': No
     72'''Has back-compat impact?''': No
    7373
    74 ''Change'':
     74'''Change''':
    7575
    7676When exporting rasters to NetCDF, save Coordinate Variables for the projected SRS, as required by the CF-1 convention, normally saved as "x" and "y".
    … …  
    7878Optionally using -co options listed above, also write 2D 'lat' and 'lon' arrays, which are specified as part of the CF-1 convention for map projections.
    7979
    80 ''Rationale'':
     80'''Rationale''':
    8181
    8282The CF-1 conventions specify these coordinate variables as necessary for grids, see [[http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.5/ch05s06.html ch5.6]] and [[http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.5/apf.html App F]] in the document.