[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #HMK-805601]: Why is there an extraneous space (\040) behind the seqno for noaaport code?

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.

  • Subject: [LDM #HMK-805601]: Why is there an extraneous space (\040) behind the seqno for noaaport code?
  • Date: Mon, 08 Dec 2014 13:09:23 -0700
Hi Daryl,

My my, you're deep in the weeds. :-)

I don't know why a space is put there. I didn't write the that code and it's 
not commented. I agree that the standard <http://www.nws.noaa.gov/tg/head.php> 
doesn't call for a space.

I do know that the presence or absence of a space won't affect the pqing(1) 
program. I don't know about other programs (e.g., GEMPAK decoders, McIDAS 
decoders).

> Hi Unidata,
> 
> I am putzing on some NWSTG dissemination code and my current bogglement is
> over these two lines of code:
> 
> https://github.com/Unidata/LDM/blob/master/noaaport/productMaker.c#L754
> 
> sprintf(memheap, "\001\015\015\012%03d\040\015\015\012",
> ((int) pdh->seqno) % 1000);
> 
> https://github.com/Unidata/LDM/blob/master/noaaport/readnoaaport.c#L945
> 
> sprintf(memheap, "\001\015\015\012%03d\040\015\015\012",
> ((int) pdh->seqno) % 1000);
> 
> So the question is why there is an extra space (\040) behind the 3 digit
> sequence number?  Is there some magic going on there?
> 
> Curiosity kills the cat!  Thanks.
> 
> daryl
> 
> --
> /**
> * Daryl Herzmann
> * Assistant Scientist -- Iowa Environmental Mesonet
> * http://mesonet.agron.iastate.edu
> */

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HMK-805601
Department: Support LDM
Priority: Normal
Status: Closed