[IDV #LQD-222418]: GTSPP data and NetCDF

Greetings Murray!

It looks like the new file format uses the CF-1.6 specification, which isn't 
yet supported in the IDV. We are currently integrating the latest release of 
netCDF-Java (4.3), which will handle CF-1.6, so at that point the IDV should be 
good to go. We have an issue ticket open on our tracking site regarding the 
transition (if you'd like to follow along):

https://mcidasv.ssec.wisc.edu/issues/11

but it hasn't been updated in quite some time. I'll see if I can find out the 
latest today and get that updated.

Cheers!

Sean

> Murray,
> 
> Thanks for the attachments. We will take a closer look as soon as we can.
> 
> Best,
> 
> Unidata IDV Support
> 
> > Here's an example they just sent me of GTSPP5 (the big file) and 4 smaller
> > ones of the old type.  Good luck and thanks.
> >
> > Murray
> >
> >
> > ----- Original Message -----
> > From: "Unidata IDV Support" <address@hidden>
> > To: <address@hidden>
> > Cc: <address@hidden>
> > Sent: Tuesday, June 12, 2012 2:42 PM
> > Subject: [IDV #LQD-222418]: GTSPP data and NetCDF
> >
> >
> > > Dear Murray,
> > >
> > > Thanks for your inquiry. The IDV development team is somewhat for short
> > > staffed at this very moment because several of us are on travel. At any
> > > rate, we will try to make some progress. Would it be possible to have a an
> > > example of both the GTSPP 4 and GTSPP 5 file formats?
> > >
> > > If these files are voluminous, please upload them to RAMADDA
> > > (http://motherlode.ucar.edu/repository/alias/idvupload) or some equivalent
> > > service like dropbox. And let us know where the GTSPP files are located.
> > >
> > > Best Wishes,
> > >
> > > Unidata IDV Support
> > >
> > >> Dear Folks,
> > >>
> > >> I recently spent some time figuring out how to get the NC formatted GTSPP
> > >> data (from the US NODC) into IDV.  So far so good.  Then, merely weeks
> > >> later, they upgraded from single-station-per-file (what they called GTSPP
> > >> 4) to multiple stations per file (GTSPP 5).  Happily I jumped in and
> > >> tried out a new file in IDV.  Nothing.  It seems they have adopted an
> > >> entirely new approach to NetCDF.  In their words:  "GTSPP4 uses four
> > >> dimensions, i.e. t,z,y,x , but GTSPP5 uses two dimensions, t and z, as
> > >> suggested by the CF-conventions....most likely, every single netCDF
> > >> visualization software needs to be modified to read and interpret  netCDF
> > >> format files correctly."  Am I at the tail end of something everybody
> > >> already knows about, or is a misinterpretation in effect?  This, for
> > >> oceanographers, is no trivial matter because the GTSPP data flow is huge,
> > >> and becoming a keystone of operational oceanography.
> > >>
> > >> Murray Brown
> > >>
> > >>
> > >> Dear Folks,
> > >>
> > >> I recently spent some time figuring out how to get the NC formatted GTSPP
> > >> data (from the US NODC) into IDV.  So far so good.  Then, merely weeks
> > >> later, they upgraded from single-station-per-file (what they called GTSPP
> > >> 4) to multiple stations per file (GTSPP 5).  Happily I jumped in and
> > >> tried out a new file in IDV.  Nothing.  It seems they have adopted an
> > >> entirely new approach to NetCDF.  In their words:  "GTSPP4 uses four
> > >> dimensions, i.e. t,z,y,x , but GTSPP5 uses two dimensions, t and z, as
> > >> suggested by the CF-conventions....most likely, every single netCDF
> > >> visualization software needs to be modified to read and interpret  netCDF
> > >> format files correctly."  Am I at the tail end of something everybody
> > >> already knows about, or is a misinterpretation in effect?  This, for
> > >> oceanographers, is no trivial matter because the GTSPP data flow is huge,
> > >> and becoming a keystone of operational oceanography.
> > >>
> > >> Murray Brown
> > >>
> > >>
> > >> Dear Folks,
> > >>
> > >> I recently spent some time figuring out how to get the NC formatted GTSPP
> > >> data (from the US NODC) into IDV.  So far so good.  Then, merely weeks
> > >> later, they upgraded from single-station-per-file (what they called GTSPP
> > >> 4) to multiple stations per file (GTSPP 5).  Happily I jumped in and
> > >> tried out a new file in IDV.  Nothing.  It seems they have adopted an
> > >> entirely new approach to NetCDF.  In their words:  "GTSPP4 uses four
> > >> dimensions, i.e. t,z,y,x , but GTSPP5 uses two dimensions, t and z, as
> > >> suggested by the CF-conventions....most likely, every single netCDF
> > >> visualization software needs to be modified to read and interpret  netCDF
> > >> format files correctly."  Am I at the tail end of something everybody
> > >> already knows about, or is a misinterpretation in effect?  This, for
> > >> oceanographers, is no trivial matter because the GTSPP data flow is huge,
> > >> and becoming a keystone of operational oceanography.
> > >>
> > >> Murray Brown
> > >>
> > >>
> > >> Dear Folks,
> > >>
> > >> I recently spent some time figuring out how to get the NC formatted GTSPP
> > >> data (from the US NODC) into IDV.  So far so good.  Then, merely weeks
> > >> later, they upgraded from single-station-per-file (what they called GTSPP
> > >> 4) to multiple stations per file (GTSPP 5).  Happily I jumped in and
> > >> tried out a new file in IDV.  Nothing.  It seems they have adopted an
> > >> entirely new approach to NetCDF.  In their words:  "GTSPP4 uses four
> > >> dimensions, i.e. t,z,y,x , but GTSPP5 uses two dimensions, t and z, as
> > >> suggested by the CF-conventions....most likely, every single netCDF
> > >> visualization software needs to be modified to read and interpret  netCDF
> > >> format files correctly."  Am I at the tail end of something everybody
> > >> already knows about, or is a misinterpretation in effect?  This, for
> > >> oceanographers, is no trivial matter because the GTSPP data flow is huge,
> > >> and becoming a keystone of operational oceanography.
> > >>
> > >> Murray Brown
> > >>
> > >>
> > >
> > >
> > > Ticket Details
> > > ===================
> > > Ticket ID: LQD-222418
> > > Department: Support IDV
> > > Priority: Normal
> > > Status: Open
> > >
> >
> >
> 


Ticket Details
===================
Ticket ID: LQD-222418
Department: Support IDV
Priority: Normal
Status: Open