[AWIPS #UXT-928462]: Surface Ob question

Hi Peter,

It's a little confusing - there are LDM and EDEX configurations that have to be 
met and they are slightly different.

LDM Side:
Your pqact.conf has a line that has to match the feedtype and filename (not 
header) being provided by your pqinsert command. The NEXRAD3 files you are 
ingesting, are already in the correct filename format, which is why you didn't 
have to worry about changing those. If it correctly matches, it will:
Write the file to /awips2/data_store/metar/
And notify EDEX the file is ready to be ingested

If it's not being stored in /awips2/data_store/metar, then nothing will appear 
in the edex logs because it never got ingested. You are correct, the default 
feedtype using pqinsert is "EXP". You can either specify the correct feedtype 
for metars when running your pqinsert command (-f IDS) or change the line in 
the pqact.conf file to say EXP - both ways work. 

EDEX Distribution:
/awips2/edex/data/utility/common_static/base/distribution/obs.xml

The distribution file above looks to match either the filename or header 
information, so this is where the header information is read.

EDEX plugin:
The obs plugin specifically requires the header information in the file in 
order to decode the file properly.

Right now, your current feedtype/file isn't matching anything in your 
pqact.conf file, so nothing is happening after you run your pqinsert command. 
My suggestion would be to update your pqact.conf file with the text below and 
use the "-f IDS" to your pqinsert command:


IDS|DDPLUS[TAB]^(S[AP].{4})_(.{4})_(..)(..)(..)
[TAB]FILE[TAB]-overwrite -close 
-edex[TAB]/awips2/data_store/metar/\1_\2_\3\4\5_(seq)

Replace [TAB] with an actual tab


Thanks,

Tiffany Meyer
AWIPS Lead Software Engineer
UCAR-Unidata

Ticket Details
===================
Ticket ID: UXT-928462
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.