Daryl,
You're are correct that WMO headers are regularly incorrect. Sometimes they
don't even get assigned. I can only comment from the point of view of HADS,
but it's a source of frustration for us. We do have action item to address
this. Hopefully it'll propagate through other data systems when we finally
can address it. Here is our action item:
NESDIS and Raw Data (2.3)
NESDIS has struggled with understanding the rules of WMO headers. The HADS
team also has struggled. There needs to be a task that involves HADS from
the Office of Dissemination to gain an understanding of how these WMO
headers should be set and then work with NESDIS to automate this in their
DADDS system. This is important because of the backup data feed. If no
WMO header is associated with a DCP or the WMO header is incorrect, it can
impact whether NESDIS pushes that DCP’s raw data to the NWS (
tgftp.ncep.noaa.gov). If the LRGS should fail to acquire data and HADS
fails over to the backup raw data feed, a number of DCPs may not decode due
to no raw data available. Simple solution is to request NESDIS to default
to SXXX50 or SXXX20 for all sites that do not have a WMO header.
Stakeholders Requesting: MADIS/HADS Team
Stakeholders Benefiting: WFOs, RFCs, NCEP, NCEI, DCP Owners, MADIS Team,
General Public.
Benefits: Reduces or eliminates risks of missing raw data when MADIS HADS
fails over to the backup feed. The MADIS HADS team no longer would need to
try to find sites that have no WMO header and request NESDIS add the
appropriate WMO header to DADDS.
Paul
On Thu, Aug 3, 2017 at 10: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/
>
--
Paul Fajman301-427-9547
Physical Scientist
Hydrometeorological Automated Data System (HADS)
