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

20040614: 20040610: dcnexr2



Jimmy,

Gpnexr2 is supposed to used the %SITE% string to guess at the station when
the station ID isn't found in the data, but you will see warning messages 
to alert you that the station ID is being guessed at, and not found in the 
data:
 MAP      = 2/1/1+31/1/2
 GAREA    = dset
 PROJ     = rad
 RADFIL   = NEXRII|KDMX
 LATLON   = 0
 PANEL    = 0
 TITLE    = 1/-1
 TEXT     = 1/21/1/hw
 CLEAR    = y
 DEVICE   = xw
 LUTFIL   = default
 IMCBAR   = 1
 TILT     = .5
 RADPARM  = dz
 RADTIM   = last
 GEMPAK-GPNEXR2>
Can't read station ID from file, using KDMX

If you use TILT=list, you will get an addition wsr88d error, similar to
what you have, but you will be able to proceed with an elevation angle tilt.

Your NCDC data file should look like:

% od -c KDMX_20040615_1910 | head -2
0000000   A   R   C   H   I   V   E   2   .   2   2   9  \0  \0   1   )
0000020 004 035   `   R  \0  \0  \0  \0  \0  \0

If the "ARCHIVE2." string is not at the beginning of your data, then
the data is not in NCDC tape archive format.

The station ID KDMX can be added to bytes 21-24 of the archive2 format
NCDC files (which is what dcnexr2 does in addition to un-bzipping).

This would be ammended with the station ID like:

% od -c KDMX_20040615_1910 | head -2
0000000   A   R   C   H   I   V   E   2   .   2   2   9  \0  \0   1   )
0000020 004 035   `   R   K   D   M   X  \0  \0


Steve Chiswell
Unidata User Support





>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200406150159.i5F1x6tK000745

>Steve-
>
>Ok. Thanks. It appears however, that I can not simply view the data. I 
>have changed my datatype.tbl file to reflect where my file is and also 
>to tell it what site I am looking for (at least I believe I am telling 
>gpnexr2 what site I am looking at. It appears that wsr88d_to_radar is 
>failing because it doesnt have a site name...
>wsr88d_to_radar: No valid site ID info found.
>[IM -3] Image file /lesh2/jimmyc/KDMX/KDMX_20030610_0452 not a supported 
>format
>[GEMPLT -15] NIPROJ - Invalid projection specified.
>[GG -7] No map drawn.
>
>etc..
>
>I used this format for my radfil name in datatype.tbl
>NEXRII  /lesh2/jimmyc/%SITE% %SITE%_YYYYMMDD_HHNN  etc.
>
>in gpnexr2:
>NEXRII|KDMX
>
>Is something that needs to be fixed or am I missing a detail somewhere?
>Again, Thanks for all the help!
>jimmyc
>
>
>On Fri, 11 Jun 2004, Unidata 
>Support wrote:
>
>>
>>Jimmy,
>>
>>The NCDC data is not bz2'd (unlike the CRAFT idd feed data) so there is no 
>>need to unbzip with dcnerx2. The IRAS cannot view bz2 data, but I added the 
>>ability for GEMPAK to view either bz2 or the uncompressed form that you will 
>>find on NCDC.
>>
>>Steve Chiswell
>>Unidata User Support
>>
>>
>>>From: address@hidden
>>>Organization: UCAR/Unidata
>>>Keywords: 200406101728.i5AHSqtK022510
>>
>>>Hi-
>>>I have data from the NCDC level 2 radar archive. I tried pushing it 
>>>through dcnexr2 to no avail:
>>>[28490] 040610/1005 [DC 3]  Starting up. Version 5.7.2p2
>>>[28490] 040610/1005 [DCNEXR2 0] STID set to KDMX
>>>[28490] 040610/1005 [DCNEXR2 0] read block size 0
>>>[28490] 040610/1005 [DCNEXR2 -7] Expanding input buffer to 159385984
>>>[28490] 040610/1005 [DCNEXR2 0] read block size 159385984
>>>[28490] 040610/1005 [DCNEXR2 -5] Short block read
>>>[28490] 040610/1005 [DC 5]  Normal termination.
>>>[28490] 040610/1005 [DC 2]  Number of bulletins read and processed: 1
>>>[28490] 040610/1005 [DC 6]  Shutting down.
>>>
>>>the file was originally tarred - so I untarred it.
>>>Then it was compressed with a .Z so i gunzipped it.
>>>
>>>I can view the file in JAVA IRAS just fine...
>>>
>>>I used the following command to push it through
>>>dcnexr2 -c 030610/0452 -v 4 -s KDMX KDMX_030610_0452 < 
>>>radar/KDMX20030610_0452
>>>
>>>any idea how I can use gpnexr2 to plot this data?
>>>Thanks for the help!
>>>
>>>
>>>-- 
>>>James Correia Jr.
>>>Ph.D. Candidate in Agricultural Meteorology
>>>President (Dictator) of the ISU Graduate Meteorology Club
>>>Dept. of Agronomy, Iowa State University
>>>*********************************************
>>>Email: address@hidden
>>>Phone: 515-294-5587
>>>Web: http://www.mesoscale.iastate.edu/jimmyc/
>>>ISU GMC: http://www.stuorg.iastate.edu/gmc/
>>>*********************************************
>>>"Imagination is more important than knowledge."
>>>-Einstein
>>>
>>>"There is a difference between knowing the path and walking the path"
>>>-"Morpheus"
>>>
>>>
>>--
>>**************************************************************************** 
>>Unidata User Support                                    UCAR Unidata Program 
>>(303)497-8643                                                  P.O. Box 3000 
>>address@hidden                                   Boulder, CO 80307 
>>---------------------------------------------------------------------------- 
>>Unidata WWW Service              http://my.unidata.ucar.edu/content/support  
>>---------------------------------------------------------------------------- 
>>NOTE: All email exchanges with Unidata User Support are recorded in the
>>Unidata inquiry tracking system and then made publically 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.
>>
>
>-- 
>James Correia Jr.
>Ph.D. Candidate in Agricultural Meteorology
>President (Dictator) of the ISU Graduate Meteorology Club
>Dept. of Agronomy, Iowa State University
>*********************************************
>Email: address@hidden
>Phone: 515-294-5587
>Web: http://www.mesoscale.iastate.edu/jimmyc/
>ISU GMC: http://www.stuorg.iastate.edu/gmc/
>*********************************************
>"Imagination is more important than knowledge."
>-Einstein
>
>"There is a difference between knowing the path and walking the path"
>-"Morpheus"
>
>
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.