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

[IDV #CUC-588449]: load satellite image with ISL from ADDE server

Hi David.

The problem is that the scriptability of the ISL is fairly limited, as far as I 
can tell. In your use case you are requiring greater programmatic control which 
I am not sure the ISL can offer you.

You may also want to take a look a Jython support within the IDV. Jython is a 
complete programming language that will allow for the sort programability that 
you may be looking for.


-Julien

> Hi Julien - As a follow up,
> Here's my next email from Russ (address@hidden) about IDV and
> McIDAS.  Apparently their image servers can only serve one image at a
> time.  One must query the adde server for a list of images and then
> request each one individually.  I looked for an example of how to do
> this in ISL, but came up short.
> 
> According to various documentation I found online, there are 2 types of
> requests: ADIR and AGET.  ADIR lists the images and AGET gets one.  I
> probably need to use ADIR first, then AGET, but I how to do it in ISL? I
> can't find any examples .
> 
> --Dave
> 
> 
> David,
> 
> Sorry about the delay in answering. I was trying to find
> someone that knows the correct format for an IDV transaction
> request. In "normal" McIDAS command line syntax the command would
> look something like this.
> 
> IMGLIST AGOES13/NH.ALL DAY=2010229 TIME=9:15 11:15
> 
> This command generates a LIST of images matching these
> constraints. You must then scan the list to request each image (1 at
> a time) to be fetched from the server. Unfortunately, the ADDE image
> servers can only return 1 image per request.
> 
> Russ
> 
> 
> 
> 
> On 12/28/2010 01:56 PM, Unidata IDV Support wrote:
> > There are a few different issues concerning parameterization of the time 
> > and time range:
> >
> > #1 Apparently, the adde protocol supports a "time" range. See here for 
> > documentation.
> >
> > http://www.ssec.wisc.edu/visad-docs/javadoc/edu/wisc/ssec/mcidas/adde/AddeImageURL.html
> >
> > However, I cannot get it to work. When I try to load the URL in the IDV, 
> > the image time stamp is always the end time in the time range which I find 
> > strange. Perhaps it would be worth pinging the ADDE team, and see what they 
> > think.
> >
> > At any rate, get this adde URL working in the IDV before trying it an ISL 
> > script.
> >
> > #2 You can also set a time property. See here for a template:
> >
> > http://www.unidata.ucar.edu/software/idv/docs/userguide/isl/datasource.isl
> >
> > However, setting a time property does not work either. The IDV does not 
> > support time ranges for the ADDE image server perhaps because of #1
> >
> > -Julien
> >
> >
> >
> >> Hi Julien,
> >> I think so.  I only can get it to download one image at a time even if I
> >> specify a time range.  It always picks the last image in the time range.
> >>
> >>
> >> dave
> >>
> >>
> >> On 12/27/2010 11:25 AM, Unidata IDV Support wrote:
> >>> Hi David.
> >>>
> >>> I am not sure this will answer your question, but have you looked how to 
> >>> specify time ranges:
> >>>
> >>> http://www.unidata.ucar.edu/software/idv/docs/userguide/isl/DataAndDisplays.html
> >>>
> >>> -Julien
> >>>
> >>>
> >>>
> >>>> Full Name: David ahijevych
> >>>> Email Address: address@hidden
> >>>> Organization: ncar
> >>>> Package Version:
> >>>> Operating System:
> >>>> Hardware:
> >>>> Description of problem: In the attached .isl file I try to load a 
> >>>> sequence of satellite images from an adde server. Instead of grouping 
> >>>> them so I can animate or save them locally as a single entity, idv 
> >>>> creates two separate data sources.  Can I download them as a group? I 
> >>>> would like to be able to animate them or save them locally in one step. 
> >>>> I tried using the times= tag for<datasource>, but it only grabs the 
> >>>> final time in the time range.  I got the idea from searching the 
> >>>> documentation and idv support archives that the adde GET request can 
> >>>> only grab 1 image at a time.
> >>>>
> >>>>
> >>> Ticket Details
> >>> ===================
> >>> Ticket ID: CUC-588449
> >>> Department: Support IDV
> >>> Priority: Normal
> >>> Status: Closed
> >>>
> >>
> >
> > Ticket Details
> > ===================
> > Ticket ID: CUC-588449
> > Department: Support IDV
> > Priority: Normal
> > Status: Closed
> >
> 
> 
> 


Ticket Details
===================
Ticket ID: CUC-588449
Department: Support IDV
Priority: Normal
Status: Closed