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

20020122: 20020118: Source of AIREP data

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: 20020122: 20020118: Source of AIREP data
Date: Tue, 22 Jan 2002 16:38:05 -0700

Pat,

I have the last 30 days of the NOAAPORT products from the DDPLUS
data stream.

I can see if it is possible for me to figure out what report
I have that is comparable to your report.

In looking at the data, it appears that the obs that are 
from flight numbers look to be in lat/lon groups. EG,
ARP KAL002 38N 140W 2105 F340 MS54 010/027KT=

The UB.. reports look to use the waypoints.

Steve Chiswell
Unidata User Support




>From: "Pauley, Dr. Pat" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200201222304.g0MN4xx11503

>Steve,
>
>If I give you some recent obs as I see them, could you 
>find the original (undecoded) reports and send them
>to me? Id so, how recent would these have to be?
>
>Thanks!
>Pat
>
>
>Patricia M. Pauley
>Meteorologist, Data Assimilation Group
>Naval Research Laboratory              Phone: (831) 656-4802
>7 Grace Hopper Avenue                  Fax: (831) 656-4769             
>Monterey, CA  93943-5502               email: address@hidden
>
>
>-----Original Message-----
>From: Unidata Support [mailto:address@hidden]
>Sent: Tuesday, January 22, 2002 3:02 PM
>To: Pauley, Dr. Pat
>Cc: 'address@hidden'; address@hidden
>Subject: 20020118: Source of AIREP data 
>
>
>
>Pat,
>
>It looks like the AIREP data on NOAAPORT can be either lat/lon
>or waypoints. The UB.. look to be more of the latter.
>
>GEMPAK 5.6 does have a decoder for the AIREP/AMDARs carried on NOAAPORT.
>These are the data that Bob Creasy would be obtaining from our IDD.
>So, if he can store the in files for you that is what I could give you.
>
>My decoder pattern looks like:
>#
># Decoder for Aircraft Observations
>DDPLUS|IDS      (^U[ABDR].... ....|^XRXX84 KAWN|^YIXX84 KAWN)
>([0-3][0-9])([0-2][0-9])
>        PIPE    decoders/dcacft -e GEMTBL=/home/gempak/NAWIPS/gempak/tables
>        -d data/gempak/logs/dcacft.log
>        data/gempak/acft/YYYYMMDDHH_acf.gem
>
>The GEMPAK decoder does use a AIREP waypoints translation table as well as a
>PIREP navaids table. The waypoints table is:
>$GEMTBL/stns/airep_waypnts.tbl
>
>From a bulletin "UBUS1 KNKA 222058" which contains the report:
>
>ADQ UA /OV ADQ-ODK270021/TM 2008/FL130/TP C130/SK OVC001/TOPS130/WX
> FV01 SN/TB NEG/IC NEG=
>
>I get the following decoder output:
>
>[7642600] 020122/1519 [DCACFT 1]  035     UBUS1   KNKA    222058
>[7642600] 020122/1519 [GEMPAK 1] ADQ UA /OV ADQ-ODK270021/TM 2008/FL130/TP
>[7642600] 020122/1519 [GEMPAK 1] C130/SK OVC001/TOPS130/WX FV01 SN/TB NEG/IC
>[7642600] 020122/1519 [GEMPAK 1] NEG
>[7642600] 020122/1519 [AF 1]  <-----BEGIN INTERFACE OUTPUT----->
>[7642600] 020122/1519 [DC 2]  ACTP    :  C130
>[7642600] 020122/1519 [DC 2]  RSID    :  ADQ
>[7642600] 020122/1519 [DC 2]    SLAT      SLON      FLVL      VSBY      YEAR
>[7642600] 020122/1519 [DC 2]       57.76   -152.74  13000.00      1.00
>2002.00
>[7642600] 020122/1519 [DC 2]    MNTH      DAYS      HOUR      MINU
>[7642600] 020122/1519 [DC 2]        1.00     22.00     20.00      8.00
>[7642600] 020122/1519 [AF 1]    NTRB      DGOT      HBOT      HTOT      FQOT
>TPOT
>[7642600] 020122/1519 [AF 1]        1.00      0.00  13000.00  13000.00
>-9999.00  -9999.00
>[7642600] 020122/1519 [AF 1]    NICG      AFIC      HBOI      HTOI      TPOI
>[7642600] 020122/1519 [AF 1]        1.00      0.00  13000.00  13000.00
>-9999.00
>[7642600] 020122/1519 [AF 1]    NPWX      WCOD      HBWX      HTWX
>[7642600] 020122/1519 [AF 1]        1.00  SN        -9999.00  -9999.00
>[7642600] 020122/1519 [AF 1]    NCLD      CLAM      CLTP      HCBF      HCTF
>[7642600] 020122/1519 [AF 1]        2.00      8.00  -9999.00    100.00
>-9999.00
>[7642600] 020122/1519 [AF 1]              -9999.00  -9999.00  -9999.00
>13000.00
>[7642600] 020122/1519 [AF 1]  <-----END INTERFACE OUTPUT----->
>
>
>Like I said, I find some bulletins that look give latlons:
>UAPA01 KWBC 222058^M
>ARP PAL102 48N 180 2047 F350 MS58 320/085KT=^M
>ARP AAH441 2433N 15351W 2046 F400 MS62 214/075KT TB SMTH=^M
>ARP AAL253 2650N 14412W 2048 F260 MS32 283/025KT=^M
>ARP AAL31 2650N 14412W 2047 F320 MS45 275/045KT TB CONT LGT CHOP=^M
>ARP JAZ57 2332N 16135W 2048 F360 MS47 290/060KT=^M
>ARP KAL024 3801N 12642W 2050 F310 MS51 350/100KT=^M
>ARP PAL105 16N 130E 2050 F390 MS52 240/015KT=^M
>ARP AAL5 3038N 13340W 2044 F320 MS49 307/038KT TB CONT LGT=^M
>
>
>And some that are use waypoints:
>UBKS90 KWBC 222136^M
>^^KS 222136^M
>SLN UA /OV SLN270020/TM 2132/FL045/TP C172/TB OCNL LGT=^M
>^M
>^C^A^M
>505 ^M
>UBNC90 KWBC 222136^M
>^^NC 222136^M
>CLT UA /OV CLT314055/TM 2123/FL130/TP BE30/IC MOD RIME 160-130/RM^M
>    CWSU ZTL=^M
>^M
>^C^A^M
>507 ^M
>UBNE90 KWBC 222136^M
>^^NE 222136^M
>MCK UA /OV HCT/TM 2132/FL310/TP BE40/TA M40/WV 23096/TB NEG=^M
>^M
>^C^A^M
>508 ^M
>UBWA90 KWBC 222136^M
>^^WA 222136^M
>EAT UA /OV EAT160015/TM 2131/FL065/TP PA44/TB MOD-SEV=^M
>^M
>^C^A^M
>516 ^M
>UBUS31 KWBC 222136^M
>PRCUS^M
>BFL UA /OV TSP-BFL/TM 2133/FL125/TP C310/SK TOPS 100 O/TSP MTNS/TB^M
>    LGT IN OCNL 700 FPM UDDFS=^M
>CLT UA /OV CLT314055/TM 2123/FL130/TP BE30/IC MOD RIME 160-130/RM^M
>    CWSU ZTL=^M
>EAT UA /OV EAT160015/TM 2131/FL065/TP PA44/TB MOD-SEV=^M
>GSH UA /OV GSH360010/TM 2127/FL045/TP C172/TA 02/TB SMTH /LGT BLO^M
>    035=^M
>MCK UA /OV HCT/TM 2132/FL310/TP BE40/TA M40/WV 23096/TB NEG=^M
>SLN UA /OV SLN270020/TM 2132/FL045/TP C172/TB OCNL LGT=^M
>TTW UA /OV 10 S TTW/TM 2132/FL048/TP BH06/RM HAZY OTRW CAVU=^M
>
>
>
>Steve Chiswell
>Unidata User Support
>
>
>>From: "Pauley, Dr. Pat" <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200201182251.g0IMp4x11213
>
>>I am trying to figure out a problem with duplicate voice AIREPs 
>>with position discrepancies in the Sout Pacific.  The data I 
>>look at are from FNMOC, who gets them from the Air Force.
>>Tinker AFB does the decode from waypoint names to latitude-
>>longitude locations.  One of my colleagues at FNMOC has
>>been unsuccessful in getting the original AIREPs to compare
>>with the decoded reports.  I just spoke with Bob Creasey
>>who found some of the reports in question in the ACARS
>>file that he gets from you folks.  He uses the following to
>>get this data:
>>
>>UNIDATA Feed PQACT.conf line 
>>
>>DDPLUS        ^U[AB].* .... ([0-3][0-9])([0-2][0-9])  FILE
>>data/weather/(\1:yy)(\1:mm)\1\2.ACARS
>>
>>My question for you is, do you do receive the raw AIREPs
>>with named waypoints given for locations rather than the
>>translated latitude-longitude locations?  (You would have to
>>do the location translation if you do!)  If so, can I get some
>>of the raw data to compare with the data I get from FNMOC?
>>
>>Thanks,
>>Pat Pauley
>>
>>
>>Patricia M. Pauley
>>Meteorologist, Data Assimilation Group
>>Naval Research Laboratory             Phone: (831) 656-4802
>>7 Grace Hopper Avenue                 Fax: (831) 656-4769             
>>Monterey, CA  93943-5502              email: address@hidden
>>
>
>****************************************************************************
><
>Unidata User Support                                    UCAR Unidata Program
><
>(303)497-8644                                                  P.O. Box 3000
><
>address@hidden                                   Boulder, CO 80307
><
>----------------------------------------------------------------------------
><
>Unidata WWW Service                        http://www.unidata.ucar.edu/
><
>****************************************************************************
><
>

Prev by Date: Re: 20020121: radar feed from IDD for ERAU
Next by Date: 20020122: 20020118: Source of AIREP data
Previous by thread: Re: 20020121: radar feed from IDD for ERAU
Next by thread: 20020122: 20020118: Source of AIREP data
Index(es):
- Date
- Thread