[IDD #EFM-179238]: GOES-16/17 pqact.conf and ldmd.conf files?

Hi,

re:
> I am trying to get the GOES-16/17 feed going for gempak 7.5.1   My
> ldmd.conf entries are listed below and then my pqact.conf entry is listed
> below that.

We have not yet started distributing GOES-16/17 ABI L2 imagery that
has been stitched together from tiles distributed in NOAAPort in
the IDD.  We have a test feed that we are making available to
a handful of core university sites for testing purposes, and as soon
as they have thoroughly tested the products in the feed, we will be
making the products (all GOES-16/17 L2 products from NOAAPort)
available generally.

re:
> Do you have a pqact.conf and ldmd.conf entry that would be
> correct?

Yes, but since the feed is not yet generally available, it
would do you no good.

re:
> Am I close with what I have?

No.

re:
> When I start ldm I do see this
> -- Upstream
> LDM-6 on idd.aos.wisc.edu is willing to be a primary feeder
> and I also see this - LDM-6 desired product-class: 20190425232510.757930
> TS_ENDT {{NOTHER, "TIRE[0-1][0-9] KNES"},{NONE, "SIG=6ad2a9c
> 3013dec1f77a55527303441bb"}}.
> 
> I was under the impression that once the product comes in the directory
> structure would automatically be created for that product.

Actions in pattern-action files will create indicated output directory
structures as long as the user running the LDM (typically 'ldm') has
write permission for the directories in the hierarchy.

re:
> So despite these
> "positive" things I am seeing the bottom line is I am not seeing any
> GOES-16/17 satellite data saved or anything like that. So if you can help
> that would be great.  Thanks!

> REQUEST NOTHER "TIRC[0-1][0-9] KNES" idd.aos.wisc.edu
> REQUEST NOTHER "TIRU[0-1][0-9] KNES" idd.aos.wisc.edu
> REQUEST NOTHER "TIS.[0-1][0-9] KNES" idd.aos.wisc.edu
> REQUEST NOTHER "TIRE[0-1][0-9] KNES" idd.aos.wisc.edu

The IDD NOTHER feed contains the ABI L2 tiles that need to be stitched
together to make full scenes.  The NOTHER and HDS feeds contain other
GOES-16/17 L2 products.

re:
> ##############################################################################
> # NOAAPORT GINI Images in NIMAGE feed
> NOTHER
> ^/data/ldm/pub/native/satellite/GOES/(.*)/([^/]*)/([^/]*)/([0-9]{8})/GOES(16|17)_([^/]*)_([0-9]{8})_([0-9]{4})(..)_([^/]*).nc4
> FILE -close  /home/gempak/nawips/metdat/images/sat/\1/\2/\3/\3_\7_\8
> #################################################################################

Your extended regular expression in this action assumes that Product IDs
contain:

- /data/ldm/pub/native/GOES

- end with .nc4

- match the pattern that you include

The GOES-16/17 products (ABI tiles and other L2 products) do not match this
pattern.  After we start relaying the full scenes stitched together from
the tiles, and other L2 products that have had the NOAAPort broadcast
header and footer stripped off, then the pattern may match the Product
IDs.

My best advice is to either get the tiles and L2 products from the NOTHER
datastream and stitch together the tiles and strip off the broadcast
headers/footers yourself, or wait until the products are available in
a revamped NIMAGE datastream.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: EFM-179238
Department: Support IDD
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.