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.
Mark, The 2 byte entries for GOES 12 may or may not be in your imgtyp.tbl file depending on what version of GEMPAK you have. The entries would look similar to: GOES12 VIS 0 30240 78 1 2 GRAY GOES12 IR2 0 255 78 2 2 GRAY GOES12 IR3 0 255 78 4 2 watvap.tbl GOES12 IR4 0 255 78 8 2 GRAY GOES12 IR5 0 255 78 16 2 GRAY GOES12 IR6 0 255 78 32 2 GRAY GOES12 IR4 0 255 78 128 2 GRAY Also, depending on whether or not your files have the expected calibration information, you may get an all black image (which I have created a fix for in the display drivers). If you get that, we'll have to update your distribution. The 2 numbers that specify the data range are dependent on how the values are found in your files. For example, the range of 0 to 30240 for visible is based upon the raw values in the data files- but yours may be different. Steve CHiswell >From: Mark Tucker <address@hidden> >Organization: UCAR/Unidata >Keywords: 200401201533.i0KFXFp2019276 > >We've retrieved some area files from SSEC and are trying to use them with >GPMAP. When executed, gpmap gives the following error: > >No image type entry for file goes12_1_2003_162_0045.area > >satfil is set to the correct filename from the data we've retrieved. The >output from the strings command on the area file shows the following >header info: > >RT GVAR >GVARRAW > >GVARK003 >MOREGVAR >MOREGVAR >MOREGVAR >MOREGVAR > > >The download from ssec had the option of obtaining the files with 1 byte >per pixel or 2 bytes per pixel. The data we have has 2bytes per pixel. > >I received a response from someone on the gembud mailing list that >directed me to the $GEMPAK/tables/sat/imgtyp.tbl. I've looked the file >over but cannot determine what I should put in as the "SAT ID", "SAT ID >NUBMER" or "IMGTYPE NUMBER" fields. I'm not sure if this is the fix I'm >looking for but it seems to make sense. I could not find any references >to this problem in the support archives. > >All of our regular area files we ingest with the LDM work perfectly with >the gempak applications. > > >Mark Tucker >Meteorology Dept. Systems Administrator >Lyndon State College >http://apollo.lsc.vsc.edu >address@hidden >(802)-626-6328 > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publically 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.