[netCDFJava #ERN-943149]: Issue with glider (autonomous underwater vehicle) data and NetCDF-Java library.

The next release of netcdf-java (in a few days) will handle this file with the 
following mods:

<?xml version="1.0" encoding="UTF-8"?>
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2"; 
location="rt_20090512_willy2.nc">
  <variable name="conductivity" shape="time" type="float">
    <attribute name="coordinates" value="time latitude longitude" />
  </variable>
  
  <attribute name="Conventions" value="CF-1.5" />  
  <attribute name="CF:featureType" value="trajectory" />

</netcdf>

it will take a while before this new functionality gets into the IDV, however 
you can test in the FeatureTypes/PointFeatureType tab in the ToolsUI app. 
feedback would be appreciated.

thanks

 .
> 
> > Guys,
> >
> > I verified that this file:
> >
> > <http://dataserver.imedea.uib-csic.es:8080/thredds/catalog/Glider/2009/catalog.html?dataset=Glider/2009/rt_20090512_willy2.nc>
> >
> > had the problem Kristian described.   If you bring it up in toolsUI
> > with Feature Type trajectory, it works, but if you change the variable
> > name to "depth" (using NcML)
> >
> > <variable name="depth" orgName="altitude" shape="time" type="float">
> >
> > it fails, saying
> >
> > Failed to find Datatype Factory...   datatype=trajectory
> >
> > -Rich
> >
> >
> > On Tue, Sep 15, 2009 at 10:32 AM, Unidata netCDF Java Support
> > <address@hidden> wrote:
> > > Hi Kristian :
> > >
> > > Can you send us an example file, or a URL to one? thanks
> > >
> > >> Hello,
> > >>
> > >> I am Kristian from OceanBit and we want to ask you about the resolution 
> > >> of
> > >> a weak problem with NetCDF-Java library, CF-1.0 and the NetCDF CF-1.0
> > >> compliant file for glider  trajectories. The problem is, for the NetCDF 
> > >> file
> > >> we have to define the z coordinate with "altitude" name (it should be
> > >> depth), to display the glider trajectory data in IDV. That's because the
> > >> NetCDF-Java library check that there is an "altitude" variable, and the
> > >> CF-1.0 compliant don't say nothing about define an "altitude" variable 
> > >> for
> > >> trajectories.
> > >>
> > >> We solve the problem renamed "depth" variable to "altitude", but we 
> > >> think is
> > >> a temporal solution. Possible solution is modify the NetCDF-Java library 
> > >> to
> > >> support underwater vehicles trajectories, adding new types of 
> > >> trajectories
> > >> or change the checker trajectory to support "depth" variable.
> > >>
> > >> Before I contact with you I got in touch with Richard Signell in 
> > >> reference
> > >> with to this issue.
> > >>
> > >> Thanks!
> > >>
> > >> --
> > >>
> > >> Kristian Sebastián Blalid
> > >> Coastal Ocean Observing and Forecast System, Balearic Islands ICTS
> > >> Parc Bit, Naorte, Bloc A 2ºplanta, puerta 3
> > >> 07121 Palma (Mallorca)
> > >> NIF: Q0700535H
> > >>
> > >>
> > >
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: ERN-943149
> > > Department: Support netCDF Java
> > > Priority: Normal
> > > Status: Open
> > >
> > >
> >
> >
> >
> > --
> > Dr. Richard P. Signell   (508) 457-2229
> > USGS, 384 Woods Hole Rd.
> > Woods Hole, MA 02543-1598
> >
> >
> 


Ticket Details
===================
Ticket ID: ERN-943149
Department: Support netCDF Java
Priority: Critical
Status: Closed