I tried both solutions and neither worked. The QuantityDB I construct
seems to be completely ignored by the Plain constructed with it. That
is, if I construct a Plain with a custom QuantityDB using the code
mentioned earlier, and then I save my data with that Plain, and then I
open it right back up with an InputNetcdf, I find the things have
changed back to "Altitude" instead of "Elevation" and Kelvin instead of
Farenheit on me.
'fraid so. Or you could try using your own Plain that uses a different
quantities database. I don't know which approach might be easier.
If I use a VisADSerialForm a little progress can be made, but it turns
out that the Spreadsheet gets confused. It seems to handle the
elevation data correctly, but it chokes on the temperature data,
treating it in some ways as Kelvin and in some ways as Farenheit, though
I can't really decipher what it's doing... Nonetheless, this isn't an
acceptable solution - even if I figure out what's going on, I'd still
like to be able to use Farenheit or Celsius data, as per the orginal
data file that I'm importing. When I override setMaps, all I can do is
explicitly pick one or the other. Furthermore, using a VisADSerialForm
is not a preferred solution, either, as all my data files will be
invalidated if/when VisAD changes.
Is there another data format I might consider that handles units
correctly, or is this just something I'll have to live with?