Re: Combining disparate VisADGeometry types

• To: Bill Hibbard <hibbard@xxxxxxxxxxxxxxxxx>
• Subject: Re: Combining disparate VisADGeometry types
• From: Don Murray <dmurray@xxxxxxxxxxxxxxxx>
• Date: Thu, 27 Jun 2002 10:44:08 -0600

Thus spaketh Bill Hibbard:
> 
> You need at least a different ScalarMap to Shape for each
> different subclass of VisADGeometryArray, just because
> different subclasses can't be merged.

If I had a VisADGeometryArray[] vga for each location (where the
vga.length could be >=0 depending on the number of subclasses of
VisADGeometryArray), couldn't I create a new Field of

  index -> ((original_ob), Station_Model)

where index.length would be the sum of the vga.lengths and the
value of Station_Model would be just the value of index and
the shapes would just be an array comprised of the individual
vga elements?

Don
*************************************************************
Don Murray                               UCAR Unidata Program
dmurray@xxxxxxxxxxxxxxxx                        P.O. Box 3000
(303) 497-8628                              Boulder, CO 80307
http://www.unidata.ucar.edu/staff/donm
*************************************************************

• Follow-Ups:
  • Re: Combining disparate VisADGeometry types
    • From: Bill Hibbard

• References:
  • Combining disparate VisADGeometry types
    • From: Don Murray
  • Re: Combining disparate VisADGeometry types
    • From: Bill Hibbard