Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-07 Thread Etienne Tourigny
On Wed, Sep 7, 2011 at 2:33 AM, Even Rouault even.roua...@mines-paris.org wrote: In case you feel like testing it, the functions needed are  OGRSpatialReference::importFromProj4() and exportToProj4(), the later which is not documented. Perhaps others can comment on the suitability of

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-07 Thread Even Rouault
How important is this information? Assuming we drop all the citation strings, or authority names and codes, but retain the important parameters of each projection (in CF and proj format), are we missing anything important numerically? In other words, are there any show-stopper issues that

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-07 Thread Etienne Tourigny
Thanks for the info Even I can see that there is not yet One standard to rule them all... Correct me if I am wrong: is WKT the preferred way GDAL stores the information? There was a proposal some time ago in the CF trac to add descriptive variables such as crs_id (EPSG code), crs_name and

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-07 Thread Even Rouault
Le mercredi 07 septembre 2011 22:49:58, Etienne Tourigny a écrit : Thanks for the info Even I can see that there is not yet One standard to rule them all... Correct me if I am wrong: is WKT the preferred way GDAL stores the information? I'd say that WKT serves as a pivot representation of

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-06 Thread Patrick Sunter
On Mon, Sep 5, 2011 at 11:23 PM, Etienne Tourigny etiennesky@gmail.com wrote: Patrick, A) your suggestion does make sense, it is imperial that basic datum information be saved as to adhere to CF-x standard.   Are those CF variables (radius, flattening etc) really sufficient for software

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-06 Thread Etienne Tourigny
On Tue, Sep 6, 2011 at 8:31 PM, Patrick Sunter patdeve...@gmail.com wrote: On Mon, Sep 5, 2011 at 11:23 PM, Etienne Tourigny etiennesky@gmail.com wrote: Patrick, A) your suggestion does make sense, it is imperial that basic datum information be saved as to adhere to CF-x standard.

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-06 Thread Even Rouault
In case you feel like testing it, the functions needed are OGRSpatialReference::importFromProj4() and exportToProj4(), the later which is not documented. Perhaps others can comment on the suitability of exporttoProj4() ??? It is documented but doxygen didn't like a macro that was

Re: [gdal-dev] NetCDF and datum handling suggestion

2011-09-05 Thread Etienne Tourigny
Patrick, A) your suggestion does make sense, it is imperial that basic datum information be saved as to adhere to CF-x standard. Are those CF variables (radius, flattening etc) really sufficient for software such as THREDDS? B) The other aspect (to save projection_ref so that GDAL can import