NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
On Thu, Nov 6, 2014 at 12:57 PM, Gus Correa <gus@xxxxxxxxxxxxxxxxx> wrote: > PS - Yes, I do understand the initial thread was about > NetCDF3 vs NetCDF4, which is a separate discussion in itself. > Bringing it back --- One of the main reasons users don't use netcdf4 is that it's substantially harder to build (and more heavy weight). As (at least for the c libs) the netcdf4 libs fully support netcdf3, there really isn't any reason for all client code to use the netcdf4 libraries, regardless of whether they are actually using netcdf4 files. So anything Unidata can do to make it easier for end users to use netcdf4 will really help: Easier to build Good binary distributions (for Window and probably OS-X anyway) ??? -Chris > > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@xxxxxxxx
netcdfgroup archives: