<font face="courier new,monospace">Etienne,<br>I am all for the improvements. I am a little short on time for the next 2-4 weeks, but I would like to spend some time on this. I think that the closer we get to a CF-1.x compliant file the better. That also gives us a little better specification to work towards. I hope to have some more time soon to work on this. There does seem to be more interest in the driver and the file format recently.<br>
<br>kss<br clear="all"></font><br>/**<br> *<br> * Kyle Shannon<br> * <a href="mailto:ksshannon@gmail.com" target="_blank">ksshannon@gmail.com</a><br> *<br> */<br><br><br>
<br><br><div class="gmail_quote">On Wed, Aug 24, 2011 at 14:37, Etienne Tourigny <span dir="ltr"><<a href="mailto:etiennesky@yahoo.com">etiennesky@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt"><div>Hi all,</div><br>I would like to start a discussion with those interested about fixing various issues in the NetCDF driver.<br>
<br>As it stands, it is not fully CF-1.0 compliant, and produces geographical grids that are not valid for other software.<br>Also, the infamous "up-side down" problem has been addressed for importing netcdfs, but needs to be addressed for exporting.<br>
<br>Related ticket: <a href="http://trac.osgeo.org/gdal/ticket/2129" target="_blank">http://trac.osgeo.org/gdal/ticket/2129</a><br>I have been submitting patches for some time to fix the related issues.<br><br>I have identified a number of issues, of which the following have been fixed partially in my proposed patch.<br>
<br>1- conform to the cf-1.0 standard for geographical grids (creating lat and lon dimensions and variables)<br>2- make netcdf grids "bottom-up" by default, as all software out there uses that
convention<br>3- fix problems related to floating-point / string conversions (also reported in issue #4200 )<br>4- fix metadata handling and duplication (as reported in issue #4204), and keep band (variable) metadata outside of the global metadata<br>
<br>Pending issues:<br><br>5- how to deal with netcdfs which have no datum? Can we assume WGS84?<br>
These files are extremely common, and CF-1.0 has provisions for identifying the key variables, but no Proj/Wkt codes. <br>6- fix proper export of projected CRS (this is not fully necessary though) with lat/lon values respecting CF-1.0<br>
7- handle time axis properly (at least when creating a netcdf) - that would be great for import/export of netcdf<br><br>Regards,<br><font color="#888888">Etienne<br></font></div></div><br>_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></blockquote></div><br>