>Date: Mon, 06 Jun 2005 12:03:05 -0700
>From: Peter Hollemans <Peter.Hollemans@xxxxxxxx>
>To: Steve Emmerson <steve@xxxxxxxxxxxxxxxx>
>Subject: Re: 20050603: Use of Java udunits package
>Keywords: 200506031601.j53G1GZu004496 netCDF-Java UDUNITS
The above message contained the following:
> I agree that it's better to insulate the user from the implementation.
> However in my case, I'm satisfied with only supporting Gaussian or
> linear conversions. The coefficients are useful to me because I already
> have a system of software in place that reads HDF data and translates
> integers into floating point by way of a scaling factor and offset.
> It's easier for me to update my implementation to convert units by
> modifying the scaling factor and offset using the unit conversion
> coefficients than it is to check for a SimpleUnit object and convert
> using that for every retrieval of a floating point value. However, I
> may still adopt the SimpleUnit.convertTo() approach, I just haven't
> considered all the ramifications yet.
Compositing transformations is problemematical if there's no general
framework in which each transformation is a particular instance. Good
At least the array-based convertTo() methods are more efficient than the
one that convert a single value.