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.
If the functions in a tuple of functions have the same domain sampling (including units and coordinate systems) then it is generally better to merge them into a function whose range is the merged tuple of ranges. Of course, if some range components define a coordinate system, then they should be grouped into a sub-tuple. The exception to this occurs when the merging of functions would greatly increase size by forcing the use of FieldImpls instead of FlatFields, but this should not be too common with proper range merging. FlatField ranges may not include Text values, which might be a reason not to merge Text and Real values. But of course, Text in functions ranges probably won't be common. In a tuple of functions, the system generally does not know that the range values are linked, whereas in the merged function, the system does know about the linkage. ---------------------------------------------------------- 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: