Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hi Ugo, > Our data set consists of M x N height points, each with an attribute > value. So we'd have 2 x L x M x N points (where L is the number of > layers) each with its own attribute: soil type, etc. I'm sorry to say this is a bit confusing. 'M x N height points' suggests that height is a function of latitude and longitude and you are interested in surface attributes, but '2 x L x M x N points' suggests that you are interested in attributes at L different depths below the surface. Are you only interested in the earth's surface, or are you interested in soil type and other attributes at many different depths below the surface? What values of M, N and L are you using? Do your data come from a simulation, or from observations? I am am interested in the size and organization of your raw data, before it comes into VisAD. > The point is, I can only set one RealType to Display.ZAxis. > Ideal would be to be able to set many RealTypes to Z... > Is there a workaround? Actually, you can use Display.ZAxisOffset as a workaround, but first I'd like to figure out the nature of your data. Then it will be easier to think about display mappings. If you want, send me code (in Java, C or ?) that describes the declaration of your data, before you have done any processing on it. 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: