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: address@hidden >Organization: NMT >Keywords: 200510212351.j9LNpI7s028398 McIDAS MYDATA Hi Mekonnen, >My problem on the the GOES timing issue is now solved. The scan duration >is about 10 minutes, and this information is good enough for me. OK. I just heard back from SSEC on this. If the images are of type RAW, then IMGPROBE lists back the Scan Time for the pixel being interrogated. If it is not of type RAW, a application sent out with Unidata McIDAS-X but not built by default can list the Scan Time _IF_ the image (AREA) was created so that the DOC section was included. Since none of the images in the Unidata-Wisconsin datastream are created with the DOC section (would require the DOC=YES keyword when the images were originally IMGCOPYed), this data is not available for them. The question would be where you got your images? If they have the DOC section, then you could build the application I am referring to and use it: <as 'mcidas'> cd ~mcidas/mcidas2005/src make gvarinfo.k gvarinfo.hlp ln gvarinfo.k ~/bin ln gvarinfo.hlp ~/help help.k GVARINFO If the images are of type RAW, you can use IMGPROBE directly. >Have a great week, You too. >p.s. Most people think the same thing regarding my name. OK, so I have company "out in left field" :-) Cheers, Tom -- 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.