Re: Combining disparate VisADGeometry types

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?