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

[THREDDS #GTH-932455]: Re: [support] How to Structure a NetCDF File to Get a Specific DDS Form

Hi Steve,

The THREDDS Data Server (TDS) does not at this time support returning
DAP sequences from this type of netCDF file.

As James mentions, you might take a look at ERDDAP [1]. I know they do
a lot with this type of data including returning the data as DAP
sequences. (ERDDAP also supports a number of other response types,
e.g., JSON.) I don't know the requirements for Dapper/DChart so I'm
not sure if ERDDAP serves things in a compatible manner.

Also, are you aware that Dapper/DChart are no longer supported by
NOAA/PMEL [2]? Though it looks like the software is still available
for download [3]. If you go that route, you might look at using the
Dapper server itself [4]. Though I'm trying to remember if it uses an
RDBMS to store the data behind the scenes rather than netCDF files.

Anyway, hope this helps.

Ethan

[1] http://coastwatch.pfeg.noaa.gov/erddap/index.html
[2] http://www.epic.noaa.gov/epic/dapper_dchart/unsupported.html
[3] http://www.epic.noaa.gov/epic/dapper_dchart/index.html
[4] http://www.epic.noaa.gov/epic/software/dapper/

James Gallagher wrote:
> 
> On Aug 18, 2014, at 3:12 PM, address@hidden wrote:
> 
> > I've got a NetCDF CTD file containing profile data.  When served
> > by the THREDDS DODS server it presently manifests as the following DDS
> > structure:
> >
> > Dataset {
> >     Int16 profile;
> >     Float64 time;
> >     Float64 lat;
> >     Float64 lon;
> >     Float64 Prz[z = 5385];
> >     Float64 Tmp[z = 5385];
> >     Float64 Cod[z = 5385];
> >     Float64 Xms[z = 5385];
> >     Float64 V0[z = 5385];
> >     Float64 Flc[z = 5385];
> >     Float64 V1[z = 5385];
> >     Float64 Oxy[z = 5385];
> >     Float64 V2[z = 5385];
> >     Float64 Obs[z = 5385];
> >     Float64 V4[z = 5385];
> >     Float64 PAR[z = 5385];
> >     Float64 V5[z = 5385];
> >     Float64 Alt[z = 5385];
> >     Float64 Sal[z = 5385];
> >     Float64 Sig[z = 5385];
> >     Float64 Dep[z = 5385];
> >     Float64 Ptp[z = 5385];
> >     Float64 Des[z = 5385];
> > } ctd/PE1315T12302.nc;
> >
> >
> > I want for it to manifest itself in the following sort of DDS structure:
> >
> >    Sequence {
> >         Float64 time;
> >         Float32 longitude;
> >         Float32 latitude;
> >         Int32 _id;
> >         Sequence {
> >             Float32 depth;
> >             Float32 Prz;
> >             Float32 Tmp;
> >             Float32 Cod;
> > ...
> >         }
> >    }
> >
> > Is there any way I can restructure a NetCDF file such that a DDS file
> > with nested sequences will be created, or is that a function of the
> > NetCDF handler that is beyond my control?  My ultimate goal is to be
> > able to use CF profile feature type files in the DAPPER/DCHART servers,
> > but they require that profile files have this sort of nested sequence
> > structure.  Thank you.
> 
> I think the ERDAP software might be able to do this. We are not the
> developers of the TDS, however, and I’m CC’ing Unidata’s support
> so they can help you.
> 
> James
> 
> > Steve Baum
> > Texas A&M Department of Oceanography
> 
> --
> James Gallagher
> opendap.org


Ticket Details
===================
Ticket ID: GTH-932455
Department: Support THREDDS
Priority: Normal
Status: Closed