Changes between Version 17 and Version 18 of NetCDF_ProjectionTestingStatus


Ignore:
Timestamp:
Dec 13, 2011, 1:15:25 PM (12 years ago)
Author:
etourigny
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NetCDF_ProjectionTestingStatus

    v17 v18  
    2121||M-2SP||Mercator||Yes||Yes||Yes*||18/10/11||Parameters appear correct, loads in NetCDF Java and IDV, but appears translated slightly (a few arc-minutes) from expected position||
    2222||Ortho||Orthographic||Yes||Yes||Yes||18/10/11||||
    23 ||PS||Polar stereographic||Yes*||Yes||No*||18/10/11||Believe we can translate parameters correctly, but see comments below. Translated file opens in NetCDF-Java IDV, but doesn't display as correctly georeferenced. ||
     23||PS||Polar stereographic||Yes*||Yes||No*||13/12/11||Believe we can translate parameters correctly, but see comments below. Translated file opens in NetCDF-Java IDV, but doesn't display as correctly georeferenced. ||
    2424||Rot Pole||Rotated pole||No||No||No||18/10/11||See projection comments below||
    2525||St||Stereographic||Yes||Yes||Yes||18/10/11||||
     
    3939  * For export: given the LCC-1SP can specifically include a scale_factor to control the projection (see http://www.remotesensing.org/geotiff/proj_list/lambert_conic_conformal_1sp.html), it seems this can't be directly exported to NetCDF without throwing away the scale factor.
    4040    * Perhaps the reasonable thing for now is to export the scale_factor to NetCDF, so it can at least be read back in. Otherwise, we'd have to try to translate the LCC-1SP to a LCC-2SP on the fly.
    41  * CEA : The CF-1 conventions claim this can be encoded with a 'scale_factor_at_projection_origin' alternative to standard parallel - how would this conversion be done back from OGC WKT?
    42  * PS : This projection's parameters in CF-1 are significantly different from http://www.remotesensing.org/geotiff/proj_list/polar_stereographic.html. In particular the CF-1 equivalent for 'latitude of natural origin' seems to be 'standard_parallel'. Note: we have verified the current approach we take to mapping is the same used by at least one other NetCDF CF-1 user in the UCAR NARCCAP project.
     41 * CEA : The CF-1 conventions claim this can be encoded with a 'scale_factor_at_projection_origin' alternative to standard parallel - how would this conversion be done from/to OGC WKT (which requires central_meridian and standard_parallel_1)?
     42 * PS : This projection's parameters in CF-1 are significantly different from http://www.remotesensing.org/geotiff/proj_list/polar_stereographic.html. In particular the CF-1 equivalent for 'latitude of natural origin' seems to be 'standard_parallel'.  CF-1 defines either standard_parallel or scale_factor_at_projection_origin, which is incompatible with OGC WKT (and OGR) that requires both.   Note: we have verified the current approach we take to mapping is the same used by at least one other NetCDF CF-1 user in the UCAR NARCCAP project. Current implementation (as of Dec. 13) uses the following rules:
     43    * WKT scale_factor maps to CF scale_factor_at_projection_origin
     44    * WKT central_meridian maps to CF straight_vertical_longitude_from_pole
     45    * WKT latitude_of_origin maps to WKT standard_parallel
     46    * WKT to CF: if WKT latitude_of_origin is positive then CF latitude_of_projection_origin is +90, else it is -90 (North vs. South Pole)
     47    * CF to WKT: unsupported if standard_parallel is not defined, as OGRSpatialReference::SetPS() requires both CF scale_factor_at_projection_origin
     48  and standard_parallel
    4349 * Rot pole : Not able yet to test: as seems GDAL needs support of advanced proj4 strings that can handle rotated coord systems (see bug #4285).