90 likes | 206 Views
Watch/Warnings in CAP NWS Partners Meeting. Bob Bunge OCIO 6/20/07. Common Alerting Protocol (CAP). Non proprietary digital message format, based on XML, that provides for Interoperability in all-hazard warning
E N D
Watch/Warnings in CAPNWS Partners Meeting Bob BungeOCIO 6/20/07
Common Alerting Protocol (CAP) • Non proprietary digital message format, based on XML, that provides for Interoperability in all-hazard warning • Compatible with current geocoding schema (e.g., NWR Specific Area Message Encoding and Emergency Alert System) • Partnership for Public Warning • Warning systems in the United States today are “a patchwork of technologies and processes.” • Need to distribute warnings consistently over all available channels.
Why CAP? • Lower cost of entry to use mission critical NWS text products • International Standard • Integration with GIS technologies • Standard format for NWS text products • Entry into cell phone text message space • Opens up use of upper/lower case • Modern electronic data format • Others • Phased and delayed effective times and expirations • Enhanced message update and cancellation features • Multilingual and multi-audience messaging • Digital encryption and signature capability • Facility for digital images, audio and video
Current Offerings • Basic CAP format offered over web started 2003 • Much interest, heavily downloaded • Many requests for better parsing • Web CAP V2 process started spring ’07 • Purposefully kept in Experimental status
OSIP SON Approach • Short term (3-6 months) • Continue current enhancment of web-based CAP feeds • Add CAP elements • Medium term (9-15 months) • Centrally generate CAP messages with WMO “envelope” to be broadcast in parallel with current WMO-formatted products over NOAAPORT and NWWS • Better quality control • Eliminate web production of CAP • Long term (2-5 years) • Native CAP generated by Next Generation Warning Tool with mixed case, expanded character set, and fully populated CAP elements • Generate WMO-formatted products from CAP messages • Disseminate both Engage Partners
Partner Feedback • Significant partner participation in CAP telecons to date. • Partners understand need to engineer and analyze, but want project to move very swiftly. • Partners grasp the issues around putting the solution in the AWIPS baseline • Short term: Want CAP feeds to be updated on web faster
The Road Ahead • Move to CAP is a journey, not an event • Finding the line between perfection and moving quickly • Short/mid term solutions will have issues • Mapping between NWS watch/warning/advisory and CAP Urgency/Certainly/Severity • Charting a course for specific CAP/NWS alert behavior(s) • Short/Mid term solutions offer a chance to test and learn for the long term • NWS will be primary provider of CAP and set examples for others to follow
CAP Summary • Journey is complex and challenging, but feasible • Strong partner support • Moves NWS text products into the 21st century • Great enhancement for the mission
Bob BungeNWS/OCIOInternet Dissemination Officer Robert.bunge@noaa.gov 301-713-1381 x140