Re: Combining disparate VisADGeometry types

• To: Don Murray <dmurray@xxxxxxxxxxxxxxxx>
• Subject: Re: Combining disparate VisADGeometry types
• From: Bill Hibbard <hibbard@xxxxxxxxxxxxxxxxx>
• Date: Thu, 27 Jun 2002 12:15:59 -0500

That would work too.

> 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?

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