[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AWIPS #NXH-679946]: LDM vs pqact question

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.

  • Subject: [AWIPS #NXH-679946]: LDM vs pqact question
  • Date: Thu, 12 Mar 2020 09:30:31 -0600
Hi Peter,

You're getting closer.  The pqact.conf file is looking for a name that fits 
this expression:
^SDUS[23578]. .... (..)(..)(..).*/p(...)(...)

Which means you need "SDUS[2 numbers][space][4 characters][space][7 
characters]/p[6 characters]
So using the product header you have I'd do something like:
"SDUS51 KBOX 120359 /p[whatever 6 characters]" ex: "SDUS51 KBOX 120359 p/123456"

That is the full product id that needs to be passed in with the pqinsert so 
that the pqact.conf
file will recognize the file as a NEXRAD3 product.

To answer you're questions:
1. The -p should be followed with the example I gave above
2. All necessary directories should be created automatically, you should not 
create any.

Let me know how that goes.


--Shay Carter

Software Engineer II
UCAR - Unidata

Ticket Details
===================
Ticket ID: NXH-679946
Department: Support AWIPS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.