Hi Stephan:
I agree strongly with you, having seen similar issues from the POV of the
netcdf-java library. It seems to be very common to confuse the reference
library with the specification, whether it be file format, web service, OTW
protocol, etc. Its so easy to fix something in the library. Im sure Ive
done it myself. ;^(
Anyway, no sign it will happen here, but good reminder.
John
On Thu, Apr 21, 2016 at 10:43 PM, Stephan Hoyer <shoyer at gmail.com> wrote:
> A custom attribute to identify netCDF4 files sounds perfectly reasonable
> as an iteration on the netCDF4 spec.
>
> But I'd like emphasize that it's important to continue to treat netCDF4 as
> a specification rather than merely whatever libnetcdf knows how to read and
> write. Doing so keeps you honest and forces more careful design.
>
> My project h5netcdf (https://github.com/shoyer/h5netcdf) is one such
> reimplementation of netCDF4 on top of an HDF5 API, which has exposed a
> number of bugs and edge cases in the netCDF-C and Python netCDF4 libraries.
>
> Cheers,
> Stephan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20160423/27ccacaa/attachment.html>
Received on Sat Apr 23 2016 - 18:09:55 BST
