Good morning,
I'd like to chime on the topic of "best practice for pqact entries". For the
WMO header found in products, there's a general form for the entries found:
TTAAII CCCC DDHHMI
When there's a string found in the line below the WMO header that is six or so
characters, this "PIL" is appended to LDM product name in the form like so:
TTAAII CCCC DDHHMI /pPILXXX
Summary: I *do not* trust the TTAAII value and only sparingly use it within a
pqact entry, but instead fully trust the /pPILXXX section.
In December 2015, I meet with the NWS Data Management folks expressing interest
in quality controlling the CCCC portion of the WMO header. Can you imagine
that it is sometimes wrong? Well, it has been 6+ years now, hundreds of
emails, and I'm still not done getting them to correct issues with it. As an
example of how painful the rabbit hole is, NWS Cheyenne KCYS was issuing TAFs
for 3 sites using KOAX as the CCCC. This took 8 months to fix and I am still
unsure if it is fully fixed.
I have not even attempted automated quality control of the TTAAII, nor bugging
NWS to fix it. Another story. I actually did attempt to get NWS to fix the
TTAAII in the case of a product that wasn't using 6 characters for the TTAAII,
can you imagine that it is sometimes only 5? That request was rejected.
Anyway, this value used to be more rigorously set, but is now more arbitrary
than ever. So in the original example below.
NEXRAD ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
I would only trust the SDUS and drop any checks on the other TTAAII fields.
Instead, put your limiters into the /p section.
NEXRAD ^SDUS.. ....
([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(N0Q|N0B|N0G|Nwhatever)(...)
Oh, there are examples in the TTAAII, where the AA is wrong, but I have
ranted/whined enough already.
daryl
________________________________________
From: ldm-users <ldm-users-bounces@xxxxxxxxxxxxxxxx> on behalf of Gilbert
Sebenste <gilbert@xxxxxxxxxxxxxxxx>
Sent: Friday, March 4, 2022 9:54 AM
To: Daniel Vietor - NOAA Affiliate
Cc: LDM-Users; Mike Voss
Subject: Re: [ldm-users] NEXRAD ID changes??
If you have LDM version 6.13.16, this shouldn't be happening. A bug fix was
applied to ensure that everything NEXRAD3 is supposed to be there.
Gilbert
On Mar 4, 2022, at 9:15 AM, Daniel Vietor - NOAA Affiliate via ldm-users
<ldm-users@xxxxxxxxxxxxxxxx> wrote:
I see a lot of them on the HDS feedtype. So I request both NEXRAD and HDS.
Dan.
On Fri, Mar 4, 2022 at 9:04 AM Mike Voss
<mike.voss@xxxxxxxx<mailto:mike.voss@xxxxxxxx>> wrote:
Hi All,
For me at least, some of my NEXRAD products stopped filing correctly yesterday
at 18Z using this generic pattern match:
NEXRAD ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
FILE -overwrite -close
nexrad/NIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3
as a test, when I changed to this:
NEXRAD ^SDUS66 ....
I started getting my "N0Q" products for MUX station.
Also, I stopped receiving the FNEXRAD NEXRCOMP products. Is it possible these
things are related such that the NEXRCOMP depends on the NIDS product ID's and
somehow a recent change (yesterday) cause this to break?
thanks for any insights,
-MIke
_______________________________________________
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.
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx<mailto:ldm-users@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit:
https://www.unidata.ucar.edu/mailing_lists/
--
Dan Vietor
Senior Research Meteorologist
CIRA, Colorado State Univ
Aviation Weather Center
Kansas City, MO
816.584.7211
_______________________________________________
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.
ldm-users mailing list
ldm-users@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
https://www.unidata.ucar.edu/mailing_lists/
