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.
=============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ =============================================================================== ---------- Forwarded message ---------- Date: Sun, 22 Aug 1999 21:01:33 -0600 From: Russ Rew <address@hidden> To: address@hidden Subject: "Dan Vietor": RE: HRS on NOAAPORT Robb, Here's Dan's reply on the NOAAPORT HRS end-of-product stuff ... --Russ ------- Forwarded Message Date: Sun, 22 Aug 1999 03:00:07 -0400 From: "Dan Vietor" <address@hidden> To: <address@hidden> Subject: RE: HRS on NOAAPORT I haven't looked into this much since I started seeing it. There have been a few subtle changes to the NOAAPORT feed this summer. This worries me that there still might be some glitches in the feed. This problem only affects certain programs but as far as I know it doesn't affect most software packages don't worry about what is at the end of a product... ________________________________________________________ Daniel Vietor Mail: address@hidden Unisys Corp Title: Engineer/Meteorologist 221 Gale Lane Phone: 610-444-2407 Kennett Square PA 19348 Fax: 610-444-2420 > -----Original Message----- > From: Russ Rew [mailto:address@hidden] > Sent: Friday, August 20, 1999 12:17 PM > To: Dan Vietor > Cc: 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 ------- End of Forwarded Message