>From: address@hidden >Organization: GMU >Keywords: 200501201830.j0KIUJv2013893 McIDAS AREA GeoTIFF ADDE Hi Ying, >Thanks for your "step by step". No worries. >It seems OK when I type: >dsinfo.k IMAGE RTIMAGES > > Dataset Names of Type: IMAGE in Group: RTIMAGES > >Name NumPos Content >------------ ------ -------------------------------------- >ANTARCTIC 99999 Antarctic IR Composite >EDFLOATER-I 99999 Educational Floater >EDFLOATER-II 99999 Educational Floater II >GE-39 99999 GOES-East Hemispheric Short IR >GE-CO2 99999 GOES-East Hemispheric CO2 >GE-IR 99999 GOES-East Hemispheric IR >GE-IRTOPO 10 GOES-East IR/TOPO Composite >GE-VIS 99999 GOES-East Hemispheric VIS >GE-VISTOPO 10 GOES-East VIS/TOPO Composite >GE-WV 99999 GOES-East Hemispheric H2O >GEW-IR 10 GOES-East/West IR Composite >GEW-IRTOPO 10 GOES-East/West IR/TOPO Composite >GEW-VIS 10 GOES-East/West VIS Composite >GEW-VISTOPO 10 GOES-East/West VIS/TOPO Composite >GEW-WV 10 GOES-East/West H2O Composite >GW-12 99999 GOES-West Western Long IR >GW-39 99999 GOES-West Western Short IR >GW-IR 99999 GOES-West Western US IR >GW-IRTOPO 10 GOES-West IR/TOPO Composite >GW-VIS 99999 GOES-West Western US VIS >GW-VISTOPO 10 GOES-West VIS/TOPO Composite >GW-WV 99999 GOES-West Western US H2O >MDR 99999 Manually Digitized Radar >MDRTOPO 10 MDR/TOPO Composite >MOLL-IR 99999 Mollweide Composite IR >MOLL-IRTOPO 10 Mollweide IR/TOPO Composite >MOLL-WV 99999 Mollweide Composite H2O >RESFLOATER 99999 Research Floater > >DSINFO -- done >----------------------------------------- OK, this shows that there are definitions for the RTIMAGES ADDE dataset. The second part of the equation is making sure that the definition for the contents of the dataset are correct. >But no images showed up when I type: > >imglist.k RTIMAGES/GE-VIS.ALL >Image file directory listing for:RTIMAGES/GE-VIS >imglist.k: No images satisfy the selection criteria >imglist.k: done > >Is it because of XCDDATA? No, it is not because of XCDDATA. To figure out what is going on you should: 1) review how you are decoding the images from the UNIWISC (aka MCIDAS) IDD datastream (check your entries in ~ldm/etc/pqact.conf) 2) make sure that the images are being decoded where you expect them to be from your pqact.conf entries 3) after you know where the images are located, adjust the definitions in LSSERVE.BAT To help you out in this, I would need to look at your pqact.conf actions that decode UNIWISC images, AND I need to look at the contents of your LSSERVE.BAT file. The structure of the LSSERVE.BAT file entries for RTIMAGES dataset definition looks like: DSSERVE ADD RTIMAGES/GE-VIS AREA TYPE=IMAGE DIRFILE=/data/ldm/gempak/images/sat/GOES-12/4km/VIS/VIS_* "GOES-East Hemispheric VIS The value of the DIRFILE=keyword is a regular expression that is supposed to match the files that should comprise the particular subset of RTIMAGES (in this case, the subset that comprises the GE-VIS subset). The idea behind the regular expression is that you can use the Unix 'ls' command to see if the files will be found: ls /data/ldm/gempak/images/sat/GOES-12/4km/VIS/VIS_* If the 'ls' command gives a correct listing, the ADDE server will also. If the 'ls' command does not give a correct listing it means that the regular expression is incorrect and needs to be changed. After changing all of the entries in LSSERVE.BAT (if needed), you will need to do the dataset definitions: <as 'mcidas'> cd ~mcidas/workdata batch.k LSSERVE.BAT >Another related question came to my mind is kind of fundamental: Previously >I used LDM-McIDAS decoders so that GEMPAK can read the files. This time, can >McIDAS read and display the files already stored, like /var/data/ldm/gempak/ima > ges/sat/GOES-12/4km/VIS/VIS_20050204_0115? Yes. This listing gives me enough information to let me know how you should change your LSSERVE entry for RTIMAGES/GE-VIS: DSSERVE ADD RTIMAGES/GE-VIS AREA TYPE=IMAGE DIRFILE=/var/data/ldm/gempak/images/sat/GOES-12/4km/VIS/VIS_* "GOES-East Hemispheric VIS Make corresponding changes for the other GOES12 images and then rerun 'batch.k LSSERVE.BAT'. >Or it will only decode the steam data and store it under another folder of >its own for display? No, McIDAS can use the directory structure used/needed by GEMPAK. >Because I specified XCDDATA=/var/data/ldm and really >not sure about this... I had you define XCDDATA since it is used in the LSSERVE.BAT batch file. If it is not defined to something, the BATCH invocation will fail at the first point it is referenced. >Thanks for your help! No worries. 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.
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.