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.
Hi Tiffany - no luck here and are the details 1. Noted the pqact.conf file that came with the install contains the corresponding entry: LIGHTNING USPLN1EX FILE -close -edex /awips2/data_store/lightning/%Y%m%d%H%M.uspln Which implies we need a feedtype LIGHTNING and perhaps a header USPLN1EX 2. So we copied line 277 from https://github.com/Unidata/awips2/blob/unidata_18.2.1/edexOsgi/com.raytheon.edex.plugin.textlightning/src/com/raytheon/edex/plugin/textlightning/impl/TextLightningParser.java into a file named LIGHTNING and containing then modifying the line so it has todays date results in a one-line file containing (no header) 2021-09-28T14:02:46.884,30.6349741,-88.3066673,-27.10,0.25,0.25,8 3. Submitted the file "LIGHTNING" with pqinsert -v -l ./log.log -f LIGHTNING ./LIGHTNING and log.log contains the following 20210928T140344.593533Z pqinsert[21906] pqinsert.c:main:439 INFO 66 20210928140344.593252 LIGHTNING 000 ./LIGHTNING 4. edex-ingest-unrecognized-files-20210928.log contains WARN 2021-09-28 14:03:59,991 1215 [external.dropbox-5] RouteFailedLog: ./LIGHTNING So we thought maybe we need some headers -- but the same result occurs (entry in the unrecognized file log) when we do the following... a. Add a header USPLN1EX as the first line of the file b. Changed the header to USPLN per line 88 in the github file -- it was a little ambiguous if this was a comment in the parser or it was intended to mean that should be the header (first line of the file being submitted) c. Changed the header to LIGHTNING-USPLN1EX per line 314 When none of these worked, we tried again each iteration but with the file named USPLN1EX instead of LIGHTNING. But the same results occur -- all iterations results in a RouteFailedLog entry in the unrecognized files log. We feel we are close, but am out of permutations we believe to try. Can you tell if we are missing something? Pete -----Original Message----- From: Unidata AWIPS Support <address@hidden> Sent: Monday, September 27, 2021 2:54 PM To: Manousos, Peter C <address@hidden> Subject: [EXTERNAL] [AWIPS #MOM-689702]: Lightning data from local feed >> Ok with that then - technically if I get this working via pqinsert >> following the pqact format, data should decode and be available in the >> USLPN menu in CAVE >> then - correct? > > Well, only if you match to that string pattern. In the textlightning plugin > that I shared, there are 4 separate patterns. Two of the patterns set the > lightning source to "UNKN", one to "USPLN", and another sets it to "WWLLN". > > So if you wanted the lightning source to be "USPLN" then you need to match > to that pattern (there are two examples in line 89 and line 277) > > 2015-06-22T22:26:56.988,20.0405176,-83.8311105,-117.00,1.50,0.25,28 > 2015-06-22T23:04:46.884,30.6349741,-88.3066673,-27.10,0.25,0.25,8 > > The last three numbers (0.25,0.25,8) aren't used and can be a default dummy > string. > >