This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
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