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.
Steve et al, The quantity database and coordinate system database sound like good ideas. There should probably be system default values that users can override. Perhaps discipline-specific databases that can be merged in multi-discipline applications. There should be no problem putting it into the core VisAD package, possibly with discipline-specific databases in discipline-specific subpackages. There should probably be some way for applications to ask the user to resolve questions like whether "wnd_spd" is wind speed. This sounds like the kind of design that ultimately must be measured by the way it works in real applications. Of course, this is true of much of the VisAD design, including the parts that have been through a half-dozen design reviews and are already implemented. The real test will be applications. It will be interesting to see a design for a quantity database. This would be a good time for anyone with thoughts about this to offer them, so that Steve can factor them into a design. Cheers, Bill ---------------------------------------------------------- Bill Hibbard, SSEC, 1225 W. Dayton St., Madison, WI 53706 whibbard@xxxxxxxxxxxxx 608-263-4427 fax: 608-263-6738 http://www.ssec.wisc.edu/~billh/vis.html
visad archives: