Michael, I have the MODIS AREA files displaying with gpmap using the following line in imgtyp.tbl: MODIS IR 0 255 111 2**30 1 GRAY and I've attached my imgtyp.tbl If you find problems with this, you might try replacing 2**30 with the full band number 1073741824 to check. Michael James Unidata > Michael, > > Thank you for the initial guidance -- I'm relieved to realize that I was on > the right track! I have uploaded an example AREA file to our ftp site for > you to take a look at: ftp://ftp.nsstc.org/outgoing/molthan/area/AREA1111 . > Based upon the header dump from "arinfo", I attempted to make an entry to > imgtyp.tbl based on the following: > > The reported band number is 1073741824 (or 2^30), and the "sensor source > number" is 111. These are one byte values, so the min and max are 0 to 255. > The actual data stored in the image is actually a calculation slightly > different from a single band imagery, but we have displayed the image in > AWIPS and it looks correct there. Therefore, the "band number" in the AREA > file was retained from one of the channels used in the differencing, although > the stored data isn't a single channel -- so if the image displays, I do > expect it to look a bit messed up on the first try. I plan to add a separate > enhancement table as well, once I can get an AREA file displayed in GPMAP, > etc. > > So, based upon the above, here is the entry I attempted to add to IMGTYP.TBL: > > MODIS IR 0 255 111 2**31 1 GRAY > > I thought that my interpretation of the 2**(n-1) might be off, so I've also > tried replacing 2**31 with 2**30, 2**29 but no luck. > The resulting error message is: [IM 1] No entry in the image type table, > imgtyp.tbl, for file AREA1111 > > Perhaps there is something I am misinterpreting between the AREA file header > and the IMGTYP.TBL entries? > If you happen to have luck with my IMGTYP.TBL line, this might also tell me > that our local system is finding another copy of IMGTYP.TBL and ignoring all > of my efforts. I hope not! > > Thank you! MSFC really appreciates Unidata's quick response and assistance! > > Andrew > > > > > -----Original Message----- > From: Unidata GEMPAK Support [mailto:address@hidden] > Sent: Thursday, October 14, 2010 4:02 PM > To: Molthan, Andrew L. (MSFC-VP61) > Cc: address@hidden > Subject: [GEMPAK #DMR-506008]: Adding New Entries to IMGTYP.TBL > > Hi Andrew, > > Tom forwarded your ticket for me to handle. You're going to need to add an > entry to $GEMTBL/sat/imgtyp.tbl for the AREA file you wish to view, complete > with min and max image pixel values, satellite ID and image channel (defined > as 2**(n-1) where n is the channel number). > > entries for imgtyp.tbl look like: > > ! |IMG | | |SAT ID|IMGTYP| PIXEL| DEFAULT > | > !SAT ID |TYP | MIN| MAX|NUMBER|NUMBER| DEPTH| LUT FILE > | > !(20) |(8) | (6)| (6)| (6)| (6)| (6)| (14) > | > ! | | | | | | | > | > !------------------------------------------------------------------------------ > SOUNDER CTP 0 255 71 2**26 1 ctp_upc.tbl > SOUNDER PW 0 255 71 2**27 1 pw_upc.tbl > > > I'm assuming that you have this information available from the header of the > AREA file. > > Take a look at this table for more examples. If you run into trouble, let me > know if I can get a copy of one of the AREA files to work with, but like you > said: you may need to remap these MODIS images if you have projection issues. > > Best, > > Michael James > Unidata > > > > > > > > Tom, > > > > I've recently been struggling with the issue of viewing some new McIDAS > > AREA formatted files in GEMPAK using routines such as SFMAP and GPMAP. > > I passed along a question to the gembud distribution, and a separate email > > to my "GEMPAK mentor" from my days at the University of Nebraska, Clint > > Rowe. I apologize for emailing you directly, but I haven't been able > > to get anywhere, and Clint suggested that you might be able to assist. > > > > Here is a rundown of what I'm trying to do... > > > > We have some McIDAS AREA files here at Marshall Space Flight Center > > that contain MODIS data, obtained from the University of Wisconsin and > > other providers, and some other files that we produce locally. I would > > like to use these files for display within GEMPAK routines, but when I > > put their file names into GPMAP, such as "SATFIL=AREA0001", I receive > > an error that there is no entry for data type AREA0001 within the file > > "IMGTYP.TBL". My understanding is that the IMGTYP.TBL file contains > > entries for "known" satellite types, along with the expected range of > > data and a reference to the corresponding color enhancement table. > > > > What would I need to add to the IMGTYP.TBL file in order for it to > > recognize AREA files from sources that aren't already included? I am > > speculating that there needs to be a matching number between an AREA > > file satellite identifier value and the column value in IMGTYP.TBL. > > Is this correct? > > > > Are there any settings within the AREA file data or header information > > block that I must modify to match values in IMGTYP.TBL to achieve a > > successful lookup for other values, such as projection? > > > > I also expect that I could run into some problems with the projection > > of the MODIS data within the AREA files but expect that I could fix that > > using McIDAS commands such as imgremap.k. > > > > I will appreciate any guidance you might be able to provide. I've asked > > so me of our "local GEMPAK experts" here at Marshall and no quick fixes > > have come to mind! > > > > Thank you, > > Andrew Molthan > > > > > > > Ticket Details > =================== > Ticket ID: DMR-506008 > Department: Support GEMPAK > Priority: Normal > Status: Open > > Ticket Details =================== Ticket ID: DMR-506008 Department: Support GEMPAK Priority: Normal Status: Open
Attachment:
imgtyp.tbl
Description: Binary data