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

[IDV #AQU-558914]: IDV v5.0: MCIDAS AREA file error



> >
> > On Jan 9, 2014, at 10:10 PM, Unidata IDV Support 
> > <address@hidden<mailto:address@hidden>> wrote:
> >
> > Full Name: Dave Dempsey
> >
> > I've loaded a MCIDAS AREA file (GOES-West IR image) accessed via our 
> > RAMADDA v.1.6a server ….
> >
> > I then rubber-band a sub-domain of the image to zoom in on, which the IDV 
> > displays successfully. However, the IDV then produces the error message 
> > above.
> >
> >
> > Dave,
> > This dataset is a bit complicated. It is area file, but the IDV will 
> > process this as gridded file through the RAMADDA server. However, there is 
> > one dimension declared as z axis but storing band id information... I need 
> > to find out more information about this kind of data.
> >
> > Yuan,
> >
> > And to make sure I understand the progressive disclosure feature for 
> > satellite imagery in the IDV v.5.0 properly: it works only through an ADDE 
> > server? It won’t work on a MCIDAS AREA file accessed as a local file or 
> > through a RAMADDA server?
> >
> > — Dave
> >
> 
> Not exactly, when the area file loaded through the RAMADDA, it is processed 
> as gridded type and should be able to do the PR too, there is something in 
> the area file dimension structure I don't understand very well and it is the 
> reason you seeing the error.
> 
> 
> Yuan
> 
Dave,
   I checked with Don who wrote the IOSP for the image area file, and the 
conclusion is that we need to do some changes in the CDM iosp to make it more 
CF compliant. We can not do the PR for the area file serving by RAMADDA in the 
current release.


Yuan 

Ticket Details
===================
Ticket ID: AQU-558914
Department: Support IDV
Priority: Normal
Status: Open


pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy