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

[IDD #SET-184160]: GOES-W AREA Files

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: [IDD #SET-184160]: GOES-W AREA Files
  • Date: Tue, 24 Mar 2020 13:38:39 -0600
Hi Jim,

re:
> Success!

I always love to hear of successes! :-)

re:
> My McIDAS-based scripts still seem to be working and can now handle
> the new GOES-17 data without making any changes.

Excellent!  Have you had a chance to check out the various coverages for both
GOES-East/16 and GOES-West/17?  I think you will find that the Full Disk
images are fantastic.  Also, since you have now upgraded to a current
version of McIDAS, you can handle any/all of the images and products
in the SATELLITE (Goes ReBroadcast/GRB L1b images) and NIMAGE
(images reconstituted from NOAAPort-delivered tiles).

In case you are wondering about the relative volumes of the three IDD
feeds that have satellite imagery, here is a snapshot that shows the
volumes of all of the feeds we relay in the IDD:

Data Volume Summary for node1.unidata.ucar.edu

Maximum hourly volume  92621.284 M bytes/hour
Average hourly volume  59517.028 M bytes/hour

Average products per hour     480789 prods/hour

Feed                           Average             Maximum     Products
                     (M byte/hour)            (M byte/hour)   number/hour
SATELLITE             15039.078    [ 25.269%]    20094.342     6634.667
CONDUIT               11331.788    [ 19.040%]    33303.479   104051.267
NGRID                  9218.722    [ 15.489%]    13343.363    64157.911
NOTHER                 6537.393    [ 10.984%]     9903.204    11960.111
NEXRAD2                6334.127    [ 10.643%]     7497.718    85861.222
NIMAGE                 6127.990    [ 10.296%]     8941.423     5979.600
NEXRAD3                2114.903    [  3.553%]     2500.852   106645.556
HDS                    1345.628    [  2.261%]     1721.802    39804.289
UNIWISC                 871.687    [  1.465%]     1091.630      911.244
GEM                     361.814    [  0.608%]     1616.745     2204.244
FNEXRAD                 112.788    [  0.190%]      136.785      104.400
IDS|DDPLUS              110.802    [  0.186%]      130.087    51970.289
EXP                       8.906    [  0.015%]       11.943      104.356
LIGHTNING                 1.145    [  0.002%]        3.390      355.867
FSL2                      0.136    [  0.000%]        1.042       42.622
GPS                       0.122    [  0.000%]        1.289        1.044

The feeds containing satellite imagery are:

SATELLITE - GRB L1b images in netCDF4 format
NIMAGE    - NOAAPort L2 images in netCDF4 format (but different format
              than those in the SATELLITE feed)
UNIWISC   - select wavelength channels (0.64um VIS, 6.2um WV and 10.3um IR)
              that have been converted into PNG compressed McIDAS AREA
              format
NOTHER    - this is the feed from NOAAPort that contains the tiles that
               we are stitching together to form full images which we
               then send in the NIMAGE feed.  We do the work of stitching
               together the tiles so that end-users don't have to

re:
> I'd still like to be able to generate the old AREA formats for awhile
> until I can get some applications weaned off of WXP over to McIDAS.

How long do you figure that you will want/need the old GOES-East images
to be available?  We have no pressing need to turn off the creation of
the images that we are currently making, but we do want to turn them
off eventually.  What I would like to understand is if our continued
creation of the products for some stretch of time into the future would
allow you to more easily focus on making the transition to using the
newer imagery.

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: SET-184160
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.