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.

Re: automatic type conversion issues: future development

NOTE: The netcdf-hdf mailing list is no longer active. The list archives are made available for historical reasons.

> Ed Hartnett <ed@xxxxxxxxxxxxxxxx> writes:
> 
> > There is an obvious combination of the code I posted, and the
> > "odometer algorithm" in the original netcdf code. I haven't yet
> > combined these, but when I do it will fix a number of bugs, and also
> > give me support for the mapping functions as well. (And I still don't
> > understand how those are meant to be used!)
> 
> Just one more elaboration...
> 
> I realize that the range check and conversion should be done on the
> same pass through the data, I've just kept them separate until now so
> that I could get a better handle on the problem...
    Yes, the HDF5 library does them in one pass.

        Quincey

  • 2003 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the netcdf-hdf archives: