2005/8/18, Dominic Lowe <<a href="mailto:d.lowe@rl.ac.uk">d.lowe@rl.ac.uk</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Hi Denis,<br><br>I'd also done a "bit" of work on this, but I'll happily abandon my<br>efforts if your driver is now in the distribution.</blockquote><div><br>
I did not know somebody else worked on this. Sorry to hear that we duplicated the work.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I had a look at your code (haven't compiled it yet) but one thing I had<br>in my driver that you might like to consider adding is a check to see if
<br>the file is CF compliant (or rather, a check to see if it has the CF<br>"Conventions" attribute).<br><br>Also, if I remember rightly (it's been a few months since I wrote it)<br>this check should stop your netCDF driver picking up "GMT" grid files,
<br>which should be left to the GMT driver to deal with.</blockquote><div><br>
I can add some of your code, but some people still uses COARDS convention which is compatible with CF-etc. <br>
<br>
I notice that GMT checks for variable name "dimension" and "z".
GMT driver should then reject netcdf CF or COARDS Convention except if
these variables exists. This test seems to be good enough for the
moment. <br>
<br>
At this point, I would like the netcdf driver to try to read the data even if it is not CF or COARDS.<br>
<br>
Regards,<br>
Denis<br>
</div></div><br>