[Data-curation] Usage of incorrect WMO source codes, does anybody care? :)

  • To: data-curation@xxxxxxxxxxxxxxxx
  • Subject: [Data-curation] Usage of incorrect WMO source codes, does anybody care? :)
  • From: daryl herzmann <akrherz@xxxxxxxxxxx>
  • Date: Thu, 3 Aug 2017 09:52:15 -0500 (CDT)
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom=akrherz@xxxxxxxxxxx;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
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
 */



  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the data-curation archives: