Along the same lines, does anyone know why the RFCs at Peachtree City and
Tulsa
have two source identifiers? I haven't checked recently, but I believe one
is used
in a product's WMO header and the other is used in the second line AWIPS
code.
KALR and KATR for Peachtree City
KTUA and KTUR for Tulsa
All other RFCs use one identifier.
Boris
On Fri, Aug 4, 2017 at 9:43 AM, Rodger R. Getz <rgetz@xxxxxxxx> wrote:
> Daryl-
>
> Yes, we care too! We’ve always seen these sort issues over the years and
> usually report it to the offending office. Since we are private sector, we
> usually are ignored. We end up having to put in extra code in our
> scripts/programs to handle these sort of exceptions. If you want to get
> really frustrated, let’s talk about SHEF coded products! That’s been around
> since the mid 1980s and they still can’t get it right.
>
> Rodger
>
> Rodger R. Getz, President and CEO
> AWIS Weather Services
> 1735 East University Drive, Suite 101
> Auburn, AL 36830-5204
>
> Website: http://www.awis.com
> Facebook: https://www.facebook.com/AWISWeatherServices
> Twitter: https://twitter.com/AWISweather
> Phone: (334) 826-2149 ext 1004 <(334)%20826-2149>
> Toll-free: (888) 798-9955 ext 1004 <(888)%20798-9955>
> Toll-free Fax: (888) 374-8027
>
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and/or legally
> privileged
> material. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited.
>
> If you received this in error, please contact the sender and delete the
> material from any computer.
>
>
> On Aug 3, 2017, at 9:52 AM, daryl herzmann <akrherz@xxxxxxxxxxx> wrote:
>
> Greetings,
>
> I have a strange fixation for 100% fidelity of parsing text products found
> on NOAAPort/SBN. As a part of that process, I attempt to properly
> associate a text product with its issuance center. I base the issuance
> center on the 4-character code used within the WMO header found with each
> product. Each day, I have a process email me a listing of 4-character
> codes that are 'unknown' to my database. For example, here's a product
> from yesterday from KFAT
>
> CSUS46 KFAT 021943
> HYMHNX
>
> MONTHLY PRECIPITATION FOR THE SAN JOAQUIN VALLEY AND THE SOUTHERN SIERRA
> JULY 2017
>
> .BR HNX 0731 P DH24/PPM
>
> ASHC1 M : ASH MOUNTAIN
> ...snipped...
>
> In a previous lifetime as a NOAA contractor, I provided NWS HQ Data
> Management with a listing of incorrect WMO source codes used within
> products and what I believe the correct code should be. In this example,
> it should be KHNX. Anyway, it took two years and a gigantic effort just to
> get a handful of Alaska climate products corrected and a hurricane center
> product coming from KMIA removed, so I don't have much hope that the others
> will be corrected.
>
> Does anybody else here care about this situation? hehe, perhaps I should
> just 'get a life' as the kids like to say these days. :)
>
> daryl
>
>
> --
> /**
> * daryl herzmann
> * Systems Analyst III -- Iowa Environmental Mesonet
> * https://mesonet.agron.iastate.edu
> */
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
> Data-curation mailing list
> Data-curation@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
>
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
> Data-curation mailing list
> Data-curation@xxxxxxxxxxxxxxxx
> For list information, to unsubscribe, or change your membership options,
> visit: http://www.unidata.ucar.edu/mailing_lists/
>
>
