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

[IDV #CHZ-651099]: our sea glider data won't open in IDV (using "Trajectory Sounding files")

> address@hidden> wrote:
> > > Full Name: John Maurer
> > > Email Address: address@hidden
> > > Organization: Pacific Islands Ocean Observing System (PacIOOS),
> > University of Hawaii at Manoa
> > > Package Version: 4.0 build date:2013-03-07 17:58 UTC
> > > Operating System: Mac OS X
> > > Hardware: Java: home:
> > /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home version:
> > 1.6.0_43 j3d:1.3.1
> > > Description of problem: Problem opening file:
> > http://oos.soest.hawaii.edu/thredds/dodsC/hioos/glider/sg523_3_aggjava.lang.NullPointerException
> > > java.lang.NullPointerException
> > >
> > > Hi IDV folks,
> > > We're having difficulty tracking down what is preventing us from
> > importing/viewing our sea glider data in IDV (error message above). These
> > are autonomous underwater vehicles (AUV) with X/Y/Z/T dimensions. Our
> > NetCDF files define them with a single time dimension, with additional
> > variables for recording longitude, latitude, and depth. We have used CF and
> > CDM standards, but perhaps we have missed something? None of the glider
> > data open in IDV in the following THREDDS Data Server (TDS) top catalog:
> > >
> > > http://oos.soest.hawaii.edu/thredds/idd/glide.html
> > >
> > > Each glider mission is provided in two catalogs: individual files per
> > dive (datasetScan in TDS) and also time-aggregated for all dives in a
> > mission (NcML aggregation along the time dimension in TDS). I'd appreciate
> > if you could give this a look and provide any insights on what might be
> > tripping things up in IDV.
> > > Many thanks!,
> > > John Maurer
> > > Pacific Islands Ocean Observing System (PacIOOS)
> > > University of Hawaii at Manoa
> >
> > Hi John,
> >        I checked out these glider datasets, and I cann't get them to
> > display in the IDV. There are several issues you need to know, first, the
> > dataset doesn't follow the CF convention, it need some modifications. But
> > even with the modifications, the IDV side need to have a new adapter to
> > load this kind of CF trajectory data type. Another option is to modify
> > these dataset with an ncml to make it displayable in the IDV, but they are
> > not the CF compliant netcdf.
> >
> > What do you think? I do plan to add the new adapter in a few months.
> >
> > Yuan
> >
> Thanks, Yuan. By CF, are you specifically referring to the relatively new
> CF-1.6 discrete sampling geometries (DSG)? We plan to convert our NetCDF
> glider format to DSG in the near future, but have been relying on the
> current setup for quite some time now. What we can't figure out is why our
> files don't load into IDV but other places with very similar glider files
> do. For instance, IMOS:
> http://opendap-vpac.arcs.org.au/thredds/catalog/IMOS/ANFOG/seaglider/SOTS20110420/catalog.html

Actually, the dataset from this catalog follows CF-1.6 (DSG). This is a very 
simple case for the trajectory sounding feature type and the IDV is able to 
handle this. If you can use the similar structure for your dataset, the IDV 
should work.

> Their setup does not comply with DSG yet either, but the glider OPeNDAP can
> be imported into IDV as Trajectory Sounding files. Can you determine why
> the IMOS glider ingests but ours do not? The data structure and attributes
> are nearly identical. However, if nothing obvious leaps out at you, no
> worries since we will transition to DSG eventually and hopefully IDV will
> handle that by then.
> Thanks!,
> John

The biggest problem is that there are three time dimensions in your dataset, 
and the unit and _CoordinateAxisType are not defined (bad units) in your 

> > >

Ticket Details
Ticket ID: CHZ-651099
Department: Support IDV
Priority: Normal
Status: Open

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.