20050819: GeoTIFF to AREA conversion (cont.)

>From: "Valentijn Venus" <address@hidden>
>Organization: ITC
>Keywords:  200508172300.j7HN0Bjo011078 McIDAS MAKEAREA MAKNAV BSQ

Hi Valentijn.

re: use 1 km BSQ image over Africa
>As you mentioned earlier, the sectorization work has already been done
>so i went and used the Lat,Lon BSQ image for Africa.

Very good.

>This works fine using both IMGDISP and IMGCOPY, but now making this
>dataset remotely accessible poses a new problem:
>
>After i did a DSSERVE (using DSSERVE ADD MYDATA/IMAGES AREA 1 2001 "GLC
>Africa)

Just as a general comment, I would use a dataset group name of something
other than MYDATA.  This has _no_ bearing on the problem you are seeing,
however.

>i can see the data location in Raul's IDV under adde.itc.nl,

Meaning exactly what?  Since you mention below that you tried to
access the dataset through the remote ADDE interface using McIDAS,
please check let me know the results of the following commands:

DATALOC LIST MYDATA

DSINFO IMAGE MYDATA

IMGLIST MYDATA/IMAGES.2001 FORM=ALL TRACE=1

The TRACE=1 keyword should cause a file named 'trce' to be created in
the ~mcidas/mcidas/data directory.  You can then read 'trce' to
find out what is wrong.

>but when i try to access it i get the following:
>
>Inquiry: An error has occurred:
>Creating image sequence
>Problem with McIDAS AREA file: edu.wisc.ssec.mcidas.AreaFileException:
>Error opening AreaFile: edu.wisc.ssec.mcidas.adde.AddeURLException: No
>images satisfy the selection criteria

This is an IDV error that I am not familiar with.

I would first check to make sure that the permissions on the AREA file
that you created are such that the user running the remote ADDE server
code (should be 'mcadde') can read that file.

Also, it may be possible that the image you created (AREA2001 ?) is in
a directory that is not being searched by the remote ADDE server
invocation.  This would mean that the file is not in a directory in the
MCPATH specified in ~/mcidas/.mcenv, or in a REDIRECTion specified in
the file LWPATH.NAM that should be located in ~mcidas/workdata.  Also,
if, for some reason, there is a copy of LWPATH.NAM in the
~mcidas/mcidas/data directory, it could be that copy is being used for
file REDIRECTions for the remote server.

>This indicates that the requested image that does not exist.

Or is not 'findable' (or is not readable ?).

>I tried to
>reproduce the same problem, but now using McIDAS-x 2004 as client
>(running on the same machine serving data), and it also tells me the
>dataset is empty. My RESOLV.SRV shows a new line was added succesfully
>when running the DSSERVE command (existing lines prefixed with a #):
>
>#N1=TOPO,N2=TOPO,TYPE=IMAGE,RT=N,K=AREA,R1=9000,R2=9019,C=All topographic imag
> es in AREA format,
>#N1=MSG,N2=HRV,TYPE=IMAGE,RT=N,K=MSGT,R1=1,R2=999999,MASK=/home/mcidas/data/ms
> g/*,C=High resolution visible channel (band 12),
>#N1=MSG,N2=VISIR,TYPE=IMAGE,RT=N,K=MSGT,R1=1,R2=999999,MASK=/home/mcidas/data/
> msg/*,C=High resolution visible and infrared channels (bands 1-11),
>N1=MYDATA,N2=IMAGES,TYPE=IMAGE,RT=N,K=AREA,R1=1,R2=2001,C=1km GLC Africa, 

OK, this server mapping table (i.e., RESOLV.SRV) is OK.

I strongly suspect that the remote server invocation can not find the
file you created.  Where, by the way, is the file you created?

>The other data pointers i can access using both IDV as McIDAS-X 2004 as
>clients succesfully, telling us the ADDE server part itself is properly
>functioning.

OK, this is important to know.  I suspect that the file you creat ed
is not being found by the remote ADDE interface.  As I mentioned above,
I would make sure to put the file in a directory specified in the MCPATH
defined in ~mcidas/.mcenv.  I would also make sure that there is not
a REDIRECTion in effect that is telling the remote server to look
in the wrong directory for the file you created.

Cheers,

Tom
--
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.