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

[IDV #RAI-544646]: help: Handling CMA file (.ta extension) from a server

> Would you fix this problem with IDV 2.8 release?
> 
> The problem: The time animation toolbar disappears
> The data: 4000 vertical levels
> 
> Thank you,
> Howard

Howard,
     I got the fix checked in today, you should update the IDV next week to see 
the changes.


Yuan
> 
> Howard Soh wrote:
> > 1. CMA is working now.
> > 2. It supports the minute by passing "HH-mm".
> >
> > So far, so good.
> >
> >
> > But I have several problems with the CMA format sounding data. You can
> > reproduce the problems I have by using the attached CMA file.
> >
> > The attached file is generated from the database.
> > - The number of vertical levels is about 4000.
> > - There are 6 timestamps
> > - There are three stations (two timestamps for each station)
> >
> > Step 1. Open the attachment by
> >         RAOB --> Sounding:Local tab --> Select FIle...
> >         I see 6 timestamps and three stations by zooming
> > Step 2. Choose all available times and stations
> >    - Problem 1: The selected soundings are 5 timestamps.
> >      One timestamp is missing.
> >      (2009-11-04 18:52 the last one from the available times)
> > Step 3. Click "Add Source" button
> > Step 4. Create Display ("Sket-T")
> > Step 5. Check Map View
> >    - There are five texts with station id & timestamp
> >    - Problem 2: There are five 1060824832
> >      They are the same except the color
> > Step 6. Back to Dashboard
> >    - There are two timestamps
> > Step 7. Pick 1060871488 or 1060918144 from Station dropdown box (above
> > the time animation toolbar)
> >    - Problem 3: The time animation toolbar disappears, and can not bring
> > it back.
> >
> > Thank you.
> > Howard
> >
> > Unidata IDV Support wrote:
> >>> 1. Different Exception from NetcdfSoundingAdapter
> >>>
> >>> The logic for the sounding data (with "RAOB" data source) is:
> >>> 1) apply Netcdf format
> >>> 2) apply CMA format if netcdf format fails
> >>>
> >>> This logic does not work if NullPointException happened instead of
> >>> IllegalArgumentException from NetcdfSoundingAdapter.
> >>>
> >>> SO the problem will be fixed if CMASoundingAdapter is applied for any
> >>> exception.
> >>>
> >> This is fixed now and will be in tonight's nightly build.
> >>
> >>> 2. Need supporting minute with CMA.
> >>>
> >>> The CMA format supports yyyy mm dd hh only. Our sounding data requires
> >>> minute, too. The sounding data is coolected every 36 monite than 00
> >>> minute. Could you support minutes too (yyyy mm dd hh MM or we need to
> >>> define format to avoid 5 column VS. six column data)
> >>>
> >>
> >> I now iterate on the formats:
> >>   private static final String []DATE_FORMATS =
> >> {"yyyy-MM-dd-HH-mm","yyyy-MM-dd-HH"};
> >> when trying to parse the dates. is "HH-mm" what you use?
> >>
> >> -Jeff
> >>
> >>
> >> Ticket Details
> >> ===================
> >> Ticket ID: RAI-544646
> >> Department: Support IDV
> >> Priority: Urgent
> >> Status: Closed
> 
> 


Ticket Details
===================
Ticket ID: RAI-544646
Department: Support IDV
Priority: Urgent
Status: Closed