20030504: Gempak - solaris? - Gempak's SFLIST output for PIREP data (dcacft)

Mike,

UNV is State College, PA  where the report was transmitted through.
PSB is Phillipsburg PA, the point of reference for the phenomena.

Steve Chiswell
Unidata User Support



>From: "mike richards" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200305050508.h4558ddO024893

>Institution: San Francisco State University (student)
>Package Version: ?
>Operating System: solaris?
>Hardware Information: ?
>Inquiry: Hello...
>
>I am having a problem when using Gempak's "sflist" program to veiw PIREP data 
> which has been decoded using "dcacft".  Using "sflist" and viewing the text f
> orm of the pilot reports, it gives the reports in the following format:
>
>ATL UA /OV ATL 005040/TM 0017/FL120/TP AT72/TA 5C/IC LGT RIME/RM CWSU
>ZTL
>
>UNV UA /OV PSB270035/TM 0044/FL060/TP C208/SK BTWN LYRS/TA 06/TB
>NEG/RM LYR BLW THN BKN
>
>I have never seen this format before.  There is a three-digit identifier at th
> e beginning of the PIREPs that I am unfamiliar with and am having a hard time
>  locating helpful documentation.  In the first, ATL is the approximate locati
> on of the aircraft (OV ATL), and it is also this "mystery identifier".  In th
> e second report, UNV is the "mystery identifier" with a different location (P
> SB).  There are many reports with "mystery identifiers" much different from t
> he aircraft's reported location.
>
>Then when using "sflist" to view the different parameters, the parameter "stat
> ion" is given as this "mystery identifier" and not the location of the aircra
> ft.
>
>Is this the place to which the PIREPS are reported to?  Is this some type of r
> elay station in the general area of the aircraft??
>
>Any help would be greatly appreciated.  Thank you...Mike (mikeventure55@hotmai
> l.com)
>
>
>