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

[LDM #OXP-765029]: Using pqinsert with -p option

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: [LDM #OXP-765029]: Using pqinsert with -p option
  • Date: Wed, 19 Sep 2018 16:20:24 -0600
Carol,

> Ah!!! So maybe LDM does support what I was explaining before.
> 
> Let's say the downstream LDM pattern in the pqact is "^Drop\.Sounding\.GTS\.".
> Would the downstream LDM be able to recieve the file if I did the following
> pqinsert?
> 
> pqinsert -v -p "Drop.Sounding.GTS.<whatever>"
> /path/Upper.Sounding.GTS.YYYYMMDD.png

I think that, without the "-f <feed>" option, that pqinsert(1) will use the EXP 
feedtype -- so if the dowstream site has subscribed to that feed with an 
appropriate pattern (e.g., ".*"), then yes, the dowsstream site will received 
the pqinsert(1)ed file.

> If this does work, would the downstream LDM still receive the file
> with Upper.Sounding.GTS.YYYYMMDD.png
> as the filename.

Nope. The product-identifier would be "Drop.Sounding.GTS.<whatever>".

> Good point about running the script with the pqinsert. Greg Stossmeister
> has been running these scripts for awhile, so I believe that is all setup.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: OXP-765029
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.