CAP in EUMETSAT and the Disaster Charter

1. CAP in EUMETSAT and the Disaster Charter Simon Elliott EUMETSAT simon.elliott@eumetsat.int

2. Outline of the presentation • EUMETSAT’s current use of CAP • EUMETSAT’s use of OID arcs for identification • CAP-EP, our CAP profile • Possible role of CAP in the support of Disaster Charter related activities

3. Distribution of satellite products EUMETSAT operates meteorological satellites Satellite data are processed to derive a range of products (images, radiance data, wind information, soil moisture, fire detection, etc.) Products are produced operationally in near real time in a variety of formats BUFR - GRIB - JPEG - ASCII - netCDF - HDF

4. Distribution mechanisms • Several mechanisms are used to distribute satellite products • Global Telecommunication System, GTS • Global network connecting NMHSs • Limited access, highly controlled, well established • EUMETCast/GEONETCast • Satellite DVB-S multi-cast service • Easy access, many users, almost global coverage • Website access • Archive access

5. Volcanic Ash Detection • Infrared image data from METEOSAT are processed to detect the presence of volcanic ash • Products could be: • GRIB or BUFR encoded for NWP community • Graphically represented (e.g. JPEG) for Volcanic Ash Advisory Centre (VAAC) or internet presentation • Described with a plain text bulletin or in XML • CAP can be used to encapsulate these formats

6. Volcanic Ash on EUMETCast Style sheet reference Graphics CAP message Text CAP message contains standard information supplemented by hyperlinks to associated information

7. Active fire detection products in CAP <?xml version="1.0" encoding="UTF-8" ?> <alert xmlns="urn:oasis:names:tc:emergency:cap:1.1"> <identifier>urn:oid:2.49.0.3.1.1.MET10</identifier> <sender>urn:oid:2.49.0.2.1</sender> <sent>2013-04-15T14:00:00-00:00</sent> <status>Actual</status> <msgType>Alert</msgType> <scope>Public</scope> <info> <category>Geo</category> <event>FIRE</event> <responseType>Assess</responseType> <responseType>Monitor</responseType> <urgency>Immediate</urgency> <severity>Moderate</severity> <certainty>Likely</certainty> <effective>2013-04-15T13:45:00-00:00</effective> <expires>2013-04-15T14:15:00-00:00</expires> <senderName>EUMETSAT</senderName> <headline>Fire detection report</headline> <description>Fire detection. This is a computer generated report and has not been reviewed by a human.</description> <web>http://oiswww.eumetsat.org/IPPS/html/MSG/PRODUCTS/FIR</web> <area> <areaDesc>List of detected fires (latitude, longitude, radius)</areaDesc> <circle>-33.728,25.048 1.991</circle> ... <circle>12.112,-12.554 1.572</circle> </area> </info> <info> <category>Geo</category> <event>FIRE</event> <responseType>Assess</responseType> <responseType>Monitor</responseType> <urgency>Immediate</urgency> <severity>Moderate</severity> <certainty>Possible</certainty> <effective>2013-04-15T13:45:00-00:00</effective> <expires>2013-04-15T14:15:00-00:00</expires> <senderName>EUMETSAT</senderName> <headline>Fire detection report</headline> <description>Fire detection. This is a computer generated report and has not been reviewed by a human.</description> <web>http://oiswww.eumetsat.org/IPPS/html/MSG/PRODUCTS/FIR</web> <area> <areaDesc>List of detected fires: latitude, longitude, radius(km)</areaDesc> <circle>-33.764,25.061 1.992</circle> ... <circle>49.996,23.522 2.545</circle> </area> </info> </alert> Sample active fire detection CAP message and display using Google’s CAP validator

8. Use of object identifiers (OIDs) • From http://oid-info.com/ • An object identifier (OID) is an extensively used identification mechanism jointly developed by ITU-T and ISO/IEC for naming any type of object, concept or "thing" with a globally unambiguous name ... • OIDs are hierarchical and allocated by a Registration Authority (for EUMETSAT CAP messages this is WMO) • As per 2009 discussions, OIDs can be used in CAP for elements <identifier> and <sender>

9. Allocation of OIDs for EUMETSAT • In July 2011, via DWD, EUMESAT was allocated OIDs: • urn.oid.2.49.0.2.1 (used for the <sender> element) • 2 = Joint ISO and ITU 49 = Alerts and alerting agencies • 0 = WMO 2 = Organizations other than countries • 1 = EUMETSAT • urn.oid.2.49.0.3.1 (used for the <identifier> element) • 2 = Joint ISO and ITU 49 = Alerts and alerting agencies • 0 = WMO 3 = Alerting messages of other orgns • 1 = EUMETSAT

10. Status of EUMETSAT and its CAP messages As EUMETSAT is supporting its Member States and is itself not an Alerting Authority, it is not listed in the WMO Registry of Alerting Authorities. CAP messages from EUMETSAT have <responseType>Assess</responseType> “Evaluate the information in this message. (This value SHOULD NOT be used in public warning applications.)”

11. CAP-EP: EUMETSAT's profile on the Common Alerting Protocol • The CAP standard caters for the representation of all types of alert messages and as such is open to some degree of flexibility and interpretation. • EUMETSAT has defined a profile [CAP-EP] which can be applied to the standard in order to define the types of CAP message which EUMETSAT produces. • Corresponding CAP profiles have been defined by • the German Weather Service, DWD [CAP-DWD Profil], • the U.S. Federal Emergency Management Agency, FEMA [IPAWS Profile], and • the Canadian Association for Public Alerting and Notification [CAP-CP]

12. International Charter “Space and Major Disasters” An International agreement among participating Space Agencies to provide space-based data and information in support of relief efforts during emergencies caused by major disasters.

13. Activations by disaster type International Charter “Space and Major Disasters” - I Fire is identified as a disaster type by the Charter. Observations from space contribute to the monitoring of ongoing fires and the analysis of the extent of burnt areas For 368 activations

14. EUMETSAT offers to the Charter • Special Imagery/Products for use by the Charter • In the event of specific Charter activations, namely: “Cyclones”, “Ocean Storms”, “Fire” and “Flooding” • EUMETSAT would make available imagery/data files available via the Charter ftp site: • Cyclone imagery • Active fire monitoring product • Files can be used to support the development of value added products and/or for inclusion in the product set provided to the Authorised/End User.

15. Special Imagery/Products • Cyclone imagery – graphic files depicting the cyclone (Hurricane, Typhoon, Tropical Storm, etc.) over the region of interest. These may be in the form of single image files (e.g. GIFF) derived from Metop AVHRR or image animation loops (e.g. MPEG) derived from Meteosat SEVIRI or MVIRI visual (VIS) or infra-red (IR) channels.

16. Special Imagery/Products • Active Fire Monitoring - fire detection product indicating the presence of fire within a pixel. The SEVIRI channel IR3.9 is sensitive to hot spots which are caused by fires. The algorithm distinguishes between potential fire and active fire. This product is available in CAP (Common Alert Protocol) format and is generated every 15-minutes. CAP is an XML format constrained by a simple schema readily be converted to KML for use with Google Earth.

17. Conclusions • EUMETSAT is using CAP for fire detection and volcanic ash messages in support of alerting authorities • OIDs are being used to uniquely identify EUMETSAT and its messages • A profile has been developed detailing the constrained use of the CAP standard by EUMETSAT • The potential role of CAP in the support of the International Charter "Space and Major Disasters"is being evaluated.