20031125: V5D files.

>From: Bernard Mendiburu <address@hidden>
>Organization: UCLA
>Keywords: 200311191822.hAJIMROb008058 IDV Vis5D

Hi Bernard-

The problem with the Vis5D file using the Linear coordinates is that
the vertical dimension does not get mapped to Altitude. In the IDV, the
main display has mappings that are basically Latitude to Y, Longitude
to X and Altitude to Z. In a Vis5D file, you basically have (row, col,
height) as the 3 dimensions. The Vis5DForm which creates a VisAD object
out of this data usually adds in a CoordinateSystem such that (row, col,
height) ==> (latitude, longitude, altitude). However, with type 0, it
ends up as (row, col, height) ==> (latitude, longitude, GENERIC_REAL) so
there is no mapping to Altitude. If you use the OmniControl in the IDV,
then you can see the data because you can map GENERIC_REAL to Z. In the
IDV's main window, you don't have that type of control since it is meant
to handle only georeferenced data.

I'm discussing this issue with Bill Hibbard (Vis5D, VisAD creator) and
trying to get it so we have the correct mappings.

For now, I would say use something other than type 0 if you can until we
can (hopefully) get this fixed.

Don Murray
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
303 497 8643                                                  P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata WWW Service              http://my.unidata.ucar.edu/content/support
****************************************************************************

Date:    Tue, 25 Nov 2003 12:58:39 PST
To:      "'Unidata Support'" <address@hidden>
From:    Bernard Mendiburu <address@hidden>
Subject: RE: 20031125: V5D files. 

That doesn't make a big problem for me.
It was mainly a bug follow-up.
I just wonder if sometimes next year, we'll have defomations in the display
because of the "cylindrical" parameter.
Anyway, i'll do my best to add IMG file handling in visAD.
It's much more efficent in the long-term than convert in vis5D.

Thank for all.