Hi Justin, re: > The IMGLIST is the following: > > IMGLIST LRIT/MET7 FORM=ALL > Image file directory listing for:LRIT/MET7 > Pos Satellite/ Date Time Center Res (km) Image_Size > sensor Lat Lon Lat Lon > --- ------------- ------------ -------- ---- ---- ----- ----- ------------ > 1 METEOSAT7 18 APR 16109 03:30:00 0 -57 > Band: 8 11.5 um IR Surface/Cloud-top Temp 4.52 4.49 2500 x 2500 > proj: 0 created: 2016109 33000 memo: FSD data from XRIT > type:MSAT cal type:RAW > offsets: data= 832 navigation= 256 calibration= 768 auxiliary= 0 > doc length: 0 cal length: 0 lev length: 0 PREFIX= 0 > valcod: 0 zcor: 0 avg-smp: A > start yyddd: 2016109 start time: 33000 start scan: 0 > lcor: 2 ecor: 2 bytes per pixel: 1 ss: 58 > Resolution Factors (base=1): Line= 2.0 Element= 2.0 > IMGLIST: done OK, I get the same thing. re: > Here is the DSSERVE taken from the RESOLV.SRV list > > N1=LRIT,N2=MET7,TYPE=IMAGE,RT=N,K=FSDX,R1=1,R2=999999,MASK=/home/awips/Desktop/mcidas/L-000* > > I have not specifically found a command on the McIDAS-X, but I did find it > for McIDAS-V which specifies to use FSDX for the format and MET7 for the > descriptor. Thanks for this info. Using it allowed me to create the ADDE dataset in McIDAS-X, and the resulting IMGLIST output matches what you sent along. re: > I also noted on the latest changes for 2015.2, that SSEC > mentions a bit about LRIT for Meteosat-7 saying, "The FSDX LRIT servers now > support data from Meteosat-7" > https://www.ssec.wisc.edu/mcidas/software/x/fastrack2015.2_changes.txt. I had read that, but I didn't recall it. Thanks for the reminder. Here are the weird things that I found: - the IMGLIST output suggests that the image has only one band OK, no worries. - an IMGDISP, however, complains that BAND= needs to be specified for a multi-banded image: IMGLIST LRIT/MET7 FORM=ALL Image file directory listing for:LRIT/MET7 Pos Satellite/ Date Time Center Res (km) Image_Size sensor Lat Lon Lat Lon --- ------------- ------------ -------- ---- ---- ----- ----- ------------ 1 METEOSAT7 15 APR 16106 15:00:00 0 -57 Band: 8 11.5 um IR Surface/Cloud-top Temp 4.52 4.49 2500 x 2500 proj: 0 created: 2016106 150000 memo: FSD data from XRIT type:MSAT cal type:RAW offsets: data= 832 navigation= 256 calibration= 768 auxiliary= 0 doc length: 0 cal length: 0 lev length: 0 PREFIX= 0 valcod: 0 zcor: 0 avg-smp: A start yyddd: 2016106 start time:150000 start scan: 0 lcor: 2 ecor: 2 bytes per pixel: 1 ss: 58 Resolution Factors (base=1): Line= 2.0 Element= 2.0 IMGLIST: done IMGDISP LRIT/MET7 IMGDISP: Band required for multi-banded image IMGDISP: done IMGDISP failed, RC=2 These contradictory results might help pinpoint where the serving problem likes if, in fact, the problem is on the serving side and not in the data itself. Also: IMGDISP LRIT/MET7 BAND=8 Beginning Image Data transfer, bytes= 1130592 IMGDISP: loaded frame 21 IMGDISP: done results in a blank display, just as you reported originally. Now the question is why there is a discrepancy in IMGLIST's and IMGDISP's interpretation of the bandedness of the image, and if this discrepancy is somehow related to the blank display from IMGDISP. This will take a bit of code diving to figure out... Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: PVX-650315 Department: Support McIDAS Priority: Normal Status: Closed
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.