Next. Gen Network Enabled Weather Product Formats Workshop, Boulder CO Decoder Discussion Brian Gockel NOAA/NWS Office of Science and Technology November 18, 2009
Decoder Discussion Wednesday, November 18 1. Scope of Decoder Discussion 2. What Decoder-Related Problems Should Be Anticipated? a. Based on experience b. Based on foresight [More of the same? ] 3. What Standards Apply (OFCM, WMO, …)? a. Differing standards versions b. Dealing with overlapping standards 4. Legacy Systems Transition 5. Decoder Metadata & Need for Consistency • Example: Site Identification Inconsistency 6. Rules (what is allowed, not allowed? ) • Example: METAR remarks field • Example: Concatenated messages Slide 2
Decoder Discussion - continued Wednesday, November 18 7. Local Tables 8. Other Decoder Challenges (Input from Group) 9. Governance a. b. c. d. Definition and establishment of governance Leveraging existing governance bodies Authoritative (oversight) and technical (execution) layers needed Need for ongoing interagency collaboration– a long-term activity 10. Next Steps • Very near term (e. g. , FY 10) and beyond FY 10 Slide 3
Scope of Decoder Discussion Software for encoding and decoding environmental products, such as net. CDF, GRIB, Radar, BUFR, METAR, etc. This includes the executable software as well as the configuration files (i. e. , “decoder metadata”*) upon which the encoders and decoders rely. Motivation for Discussion: maximize compatibility between dataprovider encoders and data-consumer decoders. Incompatibilities or inconsistencies prevent end users from fully decoding and/or using the desired information (even in cases where product delivery works). * Note that the term “decoder metadata, ” as used here, is different from reg-rep metadata. Slide 4
From Mike Asmussen (Skjei) slide package, NOAA/Next. Gen System of Systems Workshop. Annotations in green & red. Grid Decode Grid Encode Grid Decode Slide 5 Grid Decode
Decoder Discussion Establishing compatibility is a near-term (developmental) and a long-term (O&M) challenge. . . 1. New environmental models are developed; legacy models are eventually phased out. 2. With time, new parameters are added (e. g. , model-simulated radar reflectivity at certain heights or elevations). * 3. Stations renamed, added, subtracted & moved (e. g. , radar relocation or new airport). * * Examples in backup slides. Slide 6
Decoder Issues – METAR Example METAR – The domestic METAR code format is described in the Federal Meteorological Handbook (FMH) No. 1 "Surface Observations and Reports", (OFCM). The METAR format contains a REMARKS field… can be of 2 types: • Automated/Manual/Plain Language • Additive and Maintenance Data Example: METAR KOKC 082252 Z 14016 KT 6 SM HZ SCT 035 OVC 240 26/23 A 2957 RMK AO 2 PK WND 29031/2201 TSE 37 RAE 25 GSE 2158 GRB 2158 E 10 SLP 999 HAILSTONES>3/4 TSE MOV NE P 0075 T 02610233 From FMH #1: “Hailstone Size [coded as] (GR_[size]) [Plain Language]. At designated stations, the hailstone size shall be coded in the format, GR_[size]… Where plain language is called for, authorized contractions, abbreviations, and symbols should be used to conserve time and space. However, in no case should an essential remark, of which the observer is aware, be omitted for the lack of readily available contractions. In such cases, the only requirement is that the remark be clear. For a detailed list of authorized contractions, see FAA Order 7340 Series, Contractions. ” TSE should probably be “TS E” (thunderstorm East). “TSE” most often means “thunderstorm ended. ” From: http: //www. srh. noaa. gov/oun/storms/20030508/metarobs. php (May 8, 2003 case) Slide 7
Decoder Issues More METAR Examples Denver: KDEN 150053 Z 07013 KT 4 SM -SN BR SCT 018 OVC 036 01/M 01 A 2988 RMK AO 2 SLP 123 P 0000 T 00061011 Amsterdam: EHAM 150125 Z 24012 KT 9999 FEW 028 11/07 Q 1006 NOSIG Kiev: UKKK 150100 Z 04002 MPS 9999 SCT 010 OVC 023 04/01 Q 1022 NOSIG MPS = Meters per sec (versus KT=knots); NOSIG=No significant changes in weather since last report. Slide 8
BUFR Table B – Multiple Versions dx 3 -napo> ls -lt | grep -i bufr | grep -i tableb -rwxrwxr-x 1 fxalpha 43062 Nov 3 2008 bufr. Table. B -rwxrwxr-x 1 fxalpha 52780 Mar 14 2006 LAMPBufr. Table. B -rwxrwxr-x 1 fxalpha 14029 Jun 29 2005 GFSBufr. Table. B -rwxrwxr-x 1 fxalpha 14029 Jun 29 2005 ETABufr. Table. B -rwxrwxr-x 1 fxalpha 12028 Apr 29 2004 NGMBufr. Table. B -rwxrwxr-x 1 fxalpha 13413 Apr 24 2003 AVNBufr. Table. B -rwxrwxr-x 1 fxalpha 13337 Apr 14 2003 MRFBufr. Table. B -rwxrwxr-x 1 fxalpha 12028 Mar 2 2001 HPCBufr. Table. B -rwxrwxr-x 1 fxalpha 12028 Oct 11 2000 Mos. Bufr. Table. B dx 3 -napo> wc -l HPCBufr. Table. B Mos. Bufr. Table. B 157 HPCBufr. Table. B 157 Mos. Bufr. Table. B 314 total dx 3 -napo> diff HPCBufr. Table. B Mos. Bufr. Table. B 144 a 145, 146 > 060071|PROB. OF PCPN AMT GE. 01 INCH PAST 6 HRS |% | 0| 7 > 060072|PROB. OF PCPN AMT GE. 01 INCH PAST 12 HRS|% | 0| 7 156, 157 d 157 < 060071|UNKNOW |NUMERIC | 0| 1 < 060072|UNKNOW |NUMERIC | 0| 1 Slide 9
Decoder & Decoder Metadata Governance 1. Definition and establishment of governance – oversight body that establishes and maintains consistency in decoders and metadata; includes Next. Gen participating-system membership, is interagency, and exploits existing oversight/CM bodies. 2. Existing governance bodies: * a. NOAA Data Management Committee/DMIT (NOAA oversight) 3. b. CCBs (system-level) 3. Need for Next. Gen-related interagency collaboration (in the development and maintenance phases). How? 4. Is there a need for a Next. Gen developmental phase decoder team to work demonstration and IOC decoder issues? 5. Other questions: who should participate? how to collaborate? * adequate? ? ? Slide 10
Decoder & Decoder Metadata Proposal for a Long-Term Governance Structure NOAA DMIT FAA DOD (and other) oversight organizations(? ) ? ? Next. Gen Decoder Work Group ? ? NOAANet CCB FAA CCBs Individual-System CCBs NCEP CCB AWIPS CCB NWSTG CCB/DRG Radar/ROC CCB Slide 11 MDL CCB SPSRB (satellite) CCB/DRG JMBL CCBs
Questions & Possible Next Steps Decoder & Decoder Metadata 1. Role (charge or scope) of any new decoder working group may need more clear definition and NOAA/FAA buy in. 2. Identify participants. 3. Inform system owners. 4. Other next steps? ? ? Slide 12
Decoder Discussion - Backup Slide Addition of New Parameter* WHY CAN'T I FIND THE [Model simulated] RADAR PRODUCTS…. . Assuming you are using the nam. t. HHz. awip 12 FF. tm 00 files at ftp: //ftpprd. ncep. noaa. gov/pub/data/nccf/com/nam/prod/nam. YYYYMMDD/ where HH is the cycle time = 00, 06, 12 or 18, FF is the forecast hour = 00, 01, 02. . . 24 and YYYYMMDD is year, month & day; you are probably not seeing them because the new radar reflectivity fields are defined in NCEP GRIB parameter table version #129 (http: //www. nco. ncep. noaa. gov/pmb/docs/on 388/table 2. html#TABLE 129), and you are expecting them to be defined in the normal/default Table #2 (http: //www. nco. ncep. noaa. gov/pmb/docs/on 388/table 2. html). We had to put them in this alternative table because Table 2 had no room for new parameters to be added. According to the GRIB documentation (see http: //www. nco. ncep. noaa. gov/pmb/docs/on 388/section 1. html) you can find which Parameter Table is being used in octet 4 of the GRIB PDS (Product Definition Section). Note the kpds 5 entried above and that in Table 129, derived model reflectivity is variable #211 and composite reflectivity is variable #212. In Table 2 these would have been upward short wave and long wave flux, and this is probably what your existing processing assumed they were. * Excerpt from EMC model information page. Slide 13
Decoder Discussion - Backup Slide Station Change NWS Region email to NWS/OS&T: “…in March 2008 we had asked at the request of WFO BTV to change the Plattsburgh, NY sounding point to account for the ASOS (and TAF) relocation from KPLB to KPBG. I'm not sure if NCEP has made this change yet. ” New Location CD STATION ICAO IATA LAT LONG ELEV(m) M N V U A C NY PLATTSBURGH INTL KPBG 44 39 N 073 28 W 71 Z T 8 US Old Location NY PLATTSBURGH KPLB 44 41 N 073 32 W 106 X V A 6 US ASOS METAR TAF Slide 14 NAM Sounding
Decoder Discussion - Backup Slide Station Lists: NWS Location Identifier Database https: //ops 13 jweb. nws. noaa. gov/nwsli/liu/Approved. Stations. jsp (Requires UID & password) Slide 15
Decoder Metadata Example – Backup Slide Existing Data Format Standard (html format) http: //www. nco. ncep. noaa. gov/pmb/docs/grib 2_doc. shtml Slide 16
Скачать презентацию Next Gen Network Enabled Weather Product Formats Workshop
57e4e95e873156bc16c94b607f75842e.ppt