[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050223: IDV - Reading from OPeNDAP URLs with IDV

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20050223: IDV - Reading from OPeNDAP URLs with IDV
  • Date: Wed, 23 Feb 2005 20:29:13 -0700
>From: Roland Schweitzer <address@hidden>
>Organization: NOAA
>Keywords: 200502232302.j1NN2Qv2006235 IDV OPeNDAP

Hi Roland-

>Thanks for the quick response.
>
>Here it is in pictures:

As they say, a picture is worth a thousand words. ;-)

>As you see here, the Data Source Type is set to Netcdf grid files as
>you suggested.
>
>Once the "Add source" process is completed IDV finds no fields that it
>knows how to display and no time steps in the file.
>
>When I look at the log, I see the request for the time,x and y
>dimension variables and as far as I can tell FDS thinks it has returned
>those without error.
>
>It's still possible that FDS is returning something wrong, but other
>OPeNDAP aware clients (GrADS and Ferret) can read and plot from this
>URL without any problem.

No, it's a problem with the IDV (actually the netCDF for Java
library).   It is not understanding the conventions used for
defining the georeferencing coordinate system.  I'm guessing
it's because the coordinate variables are not using standard
names like lat, lon, or alt.  The only thing that it could guess
on is the fact that the units might describe this as a lon/lat/alt
grid.  Is there any way you could have this identify itself as
a known convention type like COARDS or CF?

I was using our latest build which uses the netCDF for Java 2.2
and the problem is fixed in that.  We will be releasing the next
version IDV in mid-March which will have the fix in.

If you need something sooner, let me know.  

Don
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.