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.
>From: Scott Gennari <address@hidden> >Organization: University of Hawaii >Keywords: 200109070136.f871aZ103355 McIDAS-X AXFORM Scott, In your last email (attached below) you noted: >I'll put together a tarball of our GVAR processing this weekend and make >it available to you. Thank you for helping out! >Do you prefer email or ftp? I much prefer FTP. I can either FTP it from you, or you can upload it to our passworded McIDAS FTP account as follows: machine: ftp.unidata.ucar.edu user: umcidas pass: XXXXXX directory: incoming/source Thanks again for the help! Tom >> You should be able to get this _if_ the raw values are getting put into >> the AREA you are creating from your HDF files. > >Ah, I think our code that generate the HDF data pads the >counts by 6 bits (for each 2 byte integer) as we are >seeing values between 2000 and 18000 for a typical scene around hawaii. >McIDAS appears to be able to properly calibrate the HDF data as the >radiance/temp/albedo values all appear reasonable. > >> On another topic, you may have gotten some email from Darren Gallant of >> UCAR/JOSS regarding conversion of TeraScan-produced HDF imagery to >> McIDAS AREA format. We (JOSS and Unidata) are very interested in being > >> Are you or have you been involved in the development of the software >> that converts the HDF images into AREAs? > >Sort of, I maintain processing systems but did not write any of the >code that generates the HDF data. The programmer who did is long gone. >We do have the source code and I have received permission to release >the code. > >If so, would it be possible >> to get the code from you so I can take a look? If yes, is there any >> documentation on what the TeraScan "navigation" parameters mean? > >We have no ties or experience with anything to do with SeaSpace and >what they produce (TDF?). Our data is simply ripped from the raw GVAR >files we receive in Hawaii (GOES-10) and GSFC (GOES-8) using standard >HDF libraries. The ancilliary ascii files we produce are ripped from >the DOC sector of a said GVAR file. It is the combination our or >HDF and ancialliary DOC files (ascii) that Anthony Gillory's group >at NASA/MSFC use to generate the McIDAS area file from our data. >At one point, we allowed the group at MSFC to modify our DOC code >to generate more information from the DOC sectors (Block 0)in order to >make their HDF->Mcidas converter to work. > >> If you were not involved in the development of the software, can you >> point me to the appropriate person to talk to? I know that the JOSS >> folks have already been in touch with Anthony Guillory (I know Anthony) >> and have gotten some code from him, but do not have any documentation >> on what the TeraScan HDF and ancillary ASCII file values mean. > >Most of the data in our DOC ascii file are taken from the Block 0 section >of each GVAR transmission. We received doumentation from the makers of the >GVAR instrument;Space Systems/Loral. > >OPERATIONS GROUND EQUIPTMENT (OGE) INTERFACE SPECIFICATION >DRL 504-02-1 PART I >GOES IJK/LM > >I'll put together a tarball of our GVAR processing this weekend and make >it available to you. Do you prefer email or ftp? > >Thanks, >Scott