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.
Jim, Last phone call you mentioned that you received the FOS from Alden feed as a back up. I was wondering if you could check to see if the avn-x type products have the "before" or "now" sequence of chars described below falling the 7777 sequence. The products coming on NOAAport have the "now" sequence on some of the GRIB products but no all. I think the sequence will be the "before" sequence but I want to confirm it. Thanks for your time, Robb... Date: Fri, 20 Aug 1999 10:17:14 -0600 From: Russ Rew <address@hidden> To: Dan Vietor <address@hidden> Subject: HRS on NOAAPORT Hi Dan, In a message to the ldm-users mailing list back on 12 Jul 1999, you wrote: > Oh, one other thing. Back on April 27th, NWS changed how it sent out > HRS on NOAAPORT. There are non-conforming characters trailing the GRIB > products which can throw some decoders off. For example a hexdump of > end of product: > > before: > 37 37 37 37 0D 0D 0A 03 01 0D 0D 0A > > now: > 37 37 37 37 03 00 0D 0D 0A 03 01 0D 0D 0A I was looking for some documentation of this change or the reason for it, and I couldn't find anything. For example, the NWS notices at http://www.nws.noaa.gov/oso/notices/notices.shtml make no mention of it, as far as I can tell. Do you know whether the NWS ever announced this change or why it was made? I would ask Chiz, but he's on vacation right now ... --Russ