>From: Mark Tucker <address@hidden>
>Organization: Lyndon State
>Keywords: 200007061904.e66J4vT23872 McIDAS-XCD RTGRIDS MRF AVN
Mark,
>Opening the request line up has killed our network. I'm really not sure
>how the headers are constructed for the HDS data but I know that we don't
>need any of the grid projections for Alaska. Is there documentation
>which explains how the headers are constructed?
The following snippit from our pqact.conf file might help you:
<snip>
# NOAAport ETA grids
# Grid #211 80km CONUS: ^[YZ].Q.*/mETA
# Grid #212 40km CONUS: ^[YZ].R.*/mETA
# Grid #215 20km CONUS: ^[YZ].U.*/mETA
# Grid #214 47.5km Alaska: ^[YZ].T.*/mETA
# Select any/all grids desired from [QRUT]
#
# RUC/MAPS model output
# Grid #211 CONUS 80km: ^[YZ].Q.*/mRUC
# Currently, only grid #211
#
# NGM model output
# Grid #211 CONUS 80km: ^[YZ].Q.*/mNGM
# Grid #207 Alaska 95km: ^[YZ].N.*/mNGM
# Grid #202 CONUS 190km: ^[YZ].I.*/mNGM
# Grid #213 CONUS 47.5km: ^[YZ].H.*/mNGM
# Select any/all grids desired from [QNIH]
HRS ^[YZ].(.)... KWB. ([0-3][0-9])([0-2][0-9]).*/m(ETA|NGM|RUC)
FILE
data/raw/hrs/model/\1/(\2:yyyy)(\2:mm)\2\3_\4.wmo
# NOAAport MRF grids
# Grid #201 N. Hemisphere 381km: ^Y.A... KWBH
# Grid #202 CONUS 190km: ^Y.I... KWBH
# Grid #203 Alaska 190km: ^Y.J... KWBH
# Grid #204 Hawaii 160km: ^Y.K... KWBH
# Grid #205 Puerto Rico 190km: ^Y.L... KWBH
# Select any/all grids desired from [AIJKL]
HRS ^[YZ].(.)... KWBH ([0-3][0-9])([0-2][0-9])
FILE
data/raw/hrs/model/\1/(\2:yyyy)(\2:mm)\2\3_MRF.wmo
# AVN model output
# Grid #201 N. Hemisphere 381km: ^Y.A... KWBC.*(/mAVN|/mSSIAVN)
# Grid #202 CONUS 190km: ^Y.I... KWBC.*(/mAVN|/mSSIAVN)
# Grid #203 Alaska 190km: ^Y.J... KWBC.*(/mAVN|/mSSIAVN)
# Grid #211 CONUS 80km: ^Y.Q... KWBC.*(/mAVN|/mSSIAVN)
# Grid #213 CONUS 95km: ^Y.H... KWBC.*(/mAVN|/mSSIAVN)
# Select any/all grids desired from [QAIJH]
HRS ^[YZ].([QAIJH])... KWB. ([0-3][0-9])([0-2][0-9]).*(/mAVN|/mSSIAVN)
FILE
data/raw/hrs/model/\1/(\2:yyyy)(\2:mm)\2\3_AVN.wmo
# Global AVN (Spectral) Thinned grids
# Grid octets I-P will be stitched togethir as a single global grid
#
HRS ^H.[I-P]... KWB. ([0-3][0-9])([0-2][0-9]).*
FILE
data/raw/hrs/model/thin/(\1:yyyy)(\1:mm)\1\2_AVN.wmo
#
# Global UKMet thinned grids
HRS ^H.[I-P]... EGRR ([0-3][0-9])([0-2][0-9]).*
FILE
data/raw/hrs/model/ukmet_wafs/(\1:yyyy)(\1:mm)\1\2_UKM.wmo
# MRF grids - Extended range grids E and F
#
HRS ^H.[EF][A-Z][0-9][0-9] KWB. ([0-3][0-9])([0-2][0-9])..
FILE
data/raw/hrs/model/extended/(\1:yyyy)(\1:mm)\1\2_MRF.wmo
# Spectral grids - grids A,B,C,D Global grid Forecasts (wind & waves, temperat
ure)
##
HRS ^H[A-Z][ABCD][A-Z][0-9][0-9] KWB. ([0-3][0-9])([0-2][0-9])..
FILE
data/raw/hrs/model/spectral/(\1:yyyy)(\1:mm)\1\2_WAVE.wmo
# Bitmap ocean
#
HRS ^H[HKLTUV][T-W][ACEIK]93 KWB. ([0-3][0-9])([0-2][0-9])
FILE
data/raw/hrs/model/ocean/(\1:yyyy)(\1:mm)\1\2_OCEAN.wmo
# ECMWF GRIB products, decode into yymmdd_ecmf#.gem (e1=global,e2=+/-35lat)
#
HRS ^H[HPT][A-L][A-Z][0-9][0-9] ECMF ([0-3][0-9])([0-2][0-9])
FILE
data/raw/hrs/model/ecmwf/(\1:yyyy)(\1:mm)\1\2_ECMWF1.wmo
HRS ^H[UV][A-L][A-Z][0-9][0-9] ECMF ([0-3][0-9])([0-2][0-9])
FILE
data/raw/hrs/model/ecmwf/(\1:yyyy)(\1:mm)\1\2_ECMWF2.wmo
<snip>
>Here is the old request
>line before the header changes were made this summer:
>
>#request HDS
># "(^[A-OQ-X])|(^[YZ].[^AHIJRU])"
># navier.meteo.psu.edu
You might want to try:
request HDS
"(^[A-OQ-X])|(^[YZ].[^AHIJLRU])"
navier.meteo.psu.edu
(the only addition is the 'L' after 'AHIJ')
I setup the University of Puerto Rico with:
request HRS "^([A-X].*|[YZ].[AIL].*)" pluto.met.fsu.edu
(HRS and HDS are the same) and they get all of the MRFs:
DATALOC ADD RTGRIDS breeze.uprm.edu
GRDLIST RTGRIDS/ALL.ALL FORM=FILE
DATASET NAME: RTGRIDS/ALL
Dataset Position Creation Date Max Grids Directory Title
---------------- ------------- --------- -------------------------------
2 2000242 5000 Misc. Grids for 29 AUG 2000
3 2000243 5000 Misc. Grids for 30 AUG 2000
52 2000242 5000 ALL 00Z NGM 0 HR<=VT<=24 HR
53 2000243 5000 ALL 00Z NGM 0 HR<=VT<=24 HR
62 2000242 5000 ALL 00Z NGM 24 HR< VT<=48 HR
63 2000243 5000 ALL 00Z NGM 24 HR< VT<=48 HR
72 2000242 5000 ALL 12Z NGM 0 HR<=VT<=24 HR
82 2000242 5000 ALL 12Z NGM 24 HR< VT<=48 HR
102 2000242 5000 ALL 00Z MRF 0 HR<=VT<=24 HR
103 2000243 5000 ALL 00Z MRF 0 HR<=VT<=24 HR
112 2000242 5000 ALL 00Z MRF 24 HR< VT<=48 HR
113 2000243 5000 ALL 00Z MRF 24 HR< VT<=48 HR
122 2000242 5000 ALL 00Z MRF 48 HR< VT<=72 HR
123 2000243 5000 ALL 00Z MRF 48 HR< VT<=72 HR
132 2000242 5000 ALL 00Z MRF 72 HR< VT<=96 HR
133 2000243 5000 ALL 00Z MRF 72 HR< VT<=96 HR
142 2000242 5000 ALL 00Z MRF > 96 HR
143 2000243 5000 ALL 00Z MRF > 96 HR
302 2000242 24 MDR data for 29 AUG 2000
303 2000243 24 MDR data for 30 AUG 2000
GRDLIST - done
>On a related note, prior to going to png compression this is the request
>line we were using for imagery:
>
>#request MCIDAS
># "^(GUNRV2.*|LWTOA3.*)"
># sunset.meteor.wisc.edu
This requested all of the delta-encoded imagery in the
Unidata-Wisconsin datastream. The GUNRV2 request has not had any
effect since July of 1999, since that is when the GRID products were
removed from the UW stream.
By the way the volume of the delta-encoded imagey was considerably more
than the volume for the same imagery that has been PNG compressed.
>but now we are using:
>
>request MCIDAS
> "^pnga2area Q[01]"
> 128.118.28.2
This requests all UW stream imagery that has been PNG compressed.
>Perhaps this could be trimmed down a bit too?
You could change the request to:
request MCIDAS
"^pnga2area Q1"
128.118.28.2
This would eliminate the CIMSS imagery that was added to the broadcast
at the end of June. I have to tell you that the bandwidth that these
images take up is miniscule in comparison to the other imagery and the
gridded HRS data.
>Any suggestions would be appreciated.
Give the HDS request modification a try and see if that gets you where
you want to be.
>Thanks.
>Mark Tucker
>Information Technology
>Lyndon State College
>address@hidden
>http://apollo.lsc.vsc.edu
Tom
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.