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

20030804: Zlib compression of NOAAPORT GINI images in NIMAGE stream (cont.)

>From: "Paul L. Sirvatka" <address@hidden>
>Organization: College of DuPage
>Keywords: 200307301619.h6UGJWLd013737 ldm-mcidas NIMAGE pngg2gini zlibg2gi


>On Wed, 30 Jul 2003, Unidata Support wrote:
>> to:
>> #
>> # PNG compressed NOAAPORT GINI images
>> NIMAGE       ^sat/ch[0-9]/.*/(.*)/([12][0-9])([0-9][0-9])([01][0-9])([0-3][0
> -9]) ([0-2][0-9])([0-5][0-9])/(.*)/(.*km)/
>>      PIPE    -close
>>      decoders/pngg2gini -vl logs/ldm-mcidas.log
>>      data/pub/raw/gini/\8/\9/\1/\1_\2\3\4\5_\6\7
>> #
>> # Zlib compressed NOAAOPRT GOES-East GINI images
>> NIMAGE       ^satz/ch[0-9]/.*/(.*)/([12][0-9])([0-9][0-9])([01][0-9])([0-3][
> 0-9]) ([0-2][0-9])([0-5][0-9])/(.*)/(.*km)/
>>      PIPE    -close
>>      decoders/zlibg2gini -vl logs/ldm-mcidas.log
>>      data/pub/raw/gini/\8/\9/\1/\1_\2\3\4\5_\6\7

>You have this twice?

The headers in these two actions are different.  The first one starts
with 'sat' and the second one starts with 'satz'; they are mutually
exclusive.  The first action was for the PNG compressed images we were
sending before the NWS switched to the Zlib compression technique; the
second action is for the Zlib compressed images now being sent in the
IDD NIMAGE datastream.

>Am I getting rid of the pngg2gini altogether or do I want both?

I recommend keeping both patterns just in case the NWS backs away from
the Zlib compression for any reason.

>Also...I assume I need this for all the images, not just GOES
>East.  Does it work for the SUPER images sent as well? It seems that the
>NWS said it would be for EAST and WEST imaes.

You are misinterpreting my 'GOES-East' and 'GOES-West' comments to mean
the EAST-CONUS and WEST-CONUS images; they don't.  The comments were
about _all_ of the NOAAPORT GINI images from GOES-East (all those in
NOAAPORT channel 1) and all of the NOAAPORT GINI images from GOES-West
(all of those in NOAAPORT channel 2).

>Also, if I use the reception of these images to kick off other products, I
>assume that I need to change sat to satz ... correct?

If you do have pqact.conf actions for the NIMAGE stream that are used
to kick off other processing based upon receipt of NIMAGE products,
then yes, you will need to use 'satz' instead of 'sat' in the product
header pattern.


No worries.


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.