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

[IDV #PTP-727967]: Problems reading in CFSR data



> As I said in my last message, getting the NOMADS server upgraded will
> not happen any time soon.  Heck, it's still at 4.2, they haven't even
> upgraded to 4.3 (even though NCDC paid for the 4.3 grib development) so
> getting them to 4.5 would take an act of Congress it seems. So, that
> leaves users to download the data and try to view it in the IDV.  I
> don't understand why the problems can't be fixed on the client side.  If
> they have to be on the server, then that's a flaw in the
> netCDF-Java/grib collection design.
> 
> Don

A little more research on this one, the bug you reported actually has nothing 
to do with the above dataset error. I traced the error, and checked in
some fixes you may want to double check. Basically, there are two time 
dimensions in this dataset, and the IDV didn't do well for the subset in the 
DataSourceImpl class.
One line change can fix this, hope this change will not break anything.


Yuan
> 
> On 11/14/14 4:09 PM, Unidata IDV Support wrote:
> >>> If I read it in with IDV 5.0_u1, it has 2 fields in there (see attached
> >>> images) - the first is 1 hourly, the second is 6 hourly.
> >>>
> >>> If you read it from the OPeNDAP link, you only get one because the TDS
> >>> it's coming from is version 4.2.9.
> >>>
> >>> Don
> >>
> >> It is confusing to understand the problem when the dataset coming from 
> >> server, so
> >> I downloaded the dataset and tried locally, I saw 4 fields, and the both 1 
> >> hour and 6 hour works correctly in the IDV.
> >>
> >>
> >> Yuan
> > Don,
> >
> > I checked with John about this CFSR dataset.
> > There is some errors in the dataset itself (two group issues and gds is 
> > wrong), you can not load it into the IDV locally. The problem should be 
> > fixed once this dataset is served by the TDS server.
> >
> >
> > Yuan
> >>>
> >>> On 11/14/14 2:50 PM, Unidata IDV Support wrote:
> >>>>> Addendum to the original report.  This is a problem if you select some
> >>>>> data from the 1hour field first and then try to load data from the six
> >>>>> hourly field.
> >>>>>
> >>>>> Don
> >>>>>
> >>>>
> >>>> Don,
> >>>>        The url you provided only has  one hour dataset, what is the url 
> >>>> for the six hour dataset?
> >>>>
> >>>>
> >>>> Yuan
> >>>>> On 11/14/14 9:21 AM, Unidata IDV Support wrote:
> >>>>>>
> >>>>>> Don Murray (NOAA Affiliate),
> >>>>>>
> >>>>>> Your Ticket has been received, and a Unidata staff member will review 
> >>>>>> it and reply accordingly. Listed below are details of this new Ticket. 
> >>>>>> Please make sure the Ticket ID remains in the Subject: line on all 
> >>>>>> correspondence related to this Ticket.
> >>>>>>
> >>>>>>        Ticket ID: PTP-727967
> >>>>>>        Subject: Problems reading in CFSR data
> >>>>>>        Department: Support IDV
> >>>>>>        Priority: Normal
> >>>>>>        Status: Open
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Please let us know how we can assist you further.
> >>>>>>
> >>>>>> Unidata User Support
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> Don Murray
> >>>>> NOAA/ESRL/PSD and CU-CIRES
> >>>>> 303-497-3596
> >>>>> http://www.esrl.noaa.gov/psd/people/don.murray/
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> Ticket Details
> >>>> ===================
> >>>> Ticket ID: PTP-727967
> >>>> Department: Support IDV
> >>>> Priority: Normal
> >>>> Status: Open
> >>>>
> >>>
> >>> --
> >>> Don Murray
> >>> NOAA/ESRL/PSD and CU-CIRES
> >>> 303-497-3596
> >>> http://www.esrl.noaa.gov/psd/people/don.murray/
> >>>
> >>>
> >>
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: PTP-727967
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> >
> 
> --
> Don Murray
> NOAA/ESRL/PSD and CIRES
> 303-497-3596
> http://www.esrl.noaa.gov/psd/people/don.murray/
> 
> 


Ticket Details
===================
Ticket ID: PTP-727967
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.