Embed Size (px)
Citation preview
12 responsesView all responses Publish analytics
Summary
What is your name?
SHANGYU WU
Matthew Smith
Javier Soto
Czarina Jane Rosales
Nuwan Waidyanatha
Norm Paulsen
Tim Trytten
Peter Freeman
Levi Roberts
Jeremy Fee
Brian Shiro
John Carrick
[OPTIONAL] Provide an email address where we can contact you for followups.
What categories of alerts do you work with?
Edit this [email protected]
The general public 12 100%
Government officials 11 92%
Other emergency managers 11 92%
Other 3 25%
Fire, Infra, CBRNE, Other, Transport,
Geo (tsunami)
Bushfires
Meteorological mostly. A few others by definition.
earthquakes, landslides, geomag
Geo
GEO MET HEALTH RESCUE
information and broadcast intrusive (critical)
Hydrometeorology
typhoon, rainfall, earthquake, tsunami, debris flow, flood, high water, reservoir discharge,
road close, train, call of work and school
Tropical Cyclone Alerts
Fire, Bushfire, Total Fire Bans, Fire Weather warnings, Emergency alerts
Who is the audience for these alerts?
Please provide a link to an example CAP alert or the current live feed of CAPalerts.
http://gestiondelriesgo.gov.co/rss/AtomAlert.aspx
http://wcatwc.arh.noaa.gov/?page=cap
http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/2.5_week.atom
http://www.emergencyalert.alberta.ca/aeapublic/2014/2226.cap
http://demo.eden.sahanafoundation.org/eden/cap/
http://www.rfs.nsw.gov.au/feeds/majorIncidentsCAP.xml
http://rss.naadadna.pelmorex.com/
Yes (go to question 2) 12 100%
No (skip to question 3) 0 0%
https://feeds.cfs.sa.gov.au/custom/criimson/CFS_CAP_Incidents.xml
https://alerts.ncdr.nat.gov.tw/RssAtomFeed.ashx
http://ntwc.arh.noaa.gov/?page=cap
publicalerts.pagasa.dost.gov.ph/cap/feeds
CAP <parameter> usage
Do you use the CAP <parameter> element?
For each parameter valueName you specify in CAP, provide an example andindicate the purpose of the data field.
valueName: EventID value:103115 explanation:case ID for agency internal use.
valueName: EventLatLon value:22.743,121.298 0.000 explanation:Coordinate of
epicenter. valueName: EventDepth value:17.4公里 explanation: Depth of epicenter.
valueName: EventMagnitudeDescription value:芮氏規模5.2 explanation: Event Magnitude
Description in Chinese. valueName: LocalMaxIntensity value:4級;"臺東縣";Taiwan_Geocode_100;10014;;;"CAPEQ:1.0" explanation: Local Event Intensity
value. valueName: alert_title value:豪雨特報 explanation: Alert title. valueName:
severity_level value:超大豪雨 explanation: severity level of original alert. valueName:
alert_color value:紅色 explanation: recommend alert color.
Supplemental seismic information for the Geo event : Location of earthquake
<parameter> <valueName>EventLocationName</valueName> <value>5 miles SW of El
Centro, California</value> </parameter> Magnitude of Earthquake <parameter>
<valueName>EventPreliminaryMagnitude</valueName> <value>8.4</value>
</parameter> Type of magnitude (e.g., ML, MWP, MB, etc) <parameter>
<valueName>EventPreliminaryMagnitudeType</valueName> <value>Ml</value>
</parameter> Origin time of earthquake <parameter>
<valueName>EventOriginTime</valueName> <value>20120917T23:53:57
00:00</value> </parameter> Depth of earthquake <parameter>
<valueName>EventDepth</valueName> <value>6 kilometers</value> </parameter>
Lat/Lon of epicenter <parameter> <valueName>EventLatLon</valueName>
<value>32.776,115.633 0.000</value> </parameter> NWS Valid Event Time Code
<parameter> <valueName>VTEC</valueName>
<value>/T.CON.PAAQ.TS.W.0075.000000T0000Z000000T0000Z/</value>
</parameter> NWS Zones <parameter> <valueName>NWSUGC</valueName>
<value>CAZ042043040041087039034035180148</value> </parameter>
Definition of NWS Product that has been issued in response to Geo event <parameter>
<valueName>ProductDefinition</valueName> <value> Tsunami warnings mean that a
tsunami with significant widespread inundation is expected, or occurring. Warnings
indicate that widespread dangerous coastal flooding accompanied by powerful currents is
possible and may continue for several hours after the initial wave arrival. </value> WMO
Product <parameter> <valueName>WEPA41</valueName> <value> Tsunami Warnings,
Watches, and Advisories for AK, BC, and US West Coast </value> </parameter> IPAWS
<parameter> <valueName>CMAMtext</valueName> <value> Tsunami danger on the
coast. Go to high ground or move inland. Listen to local news. –NWS </value>
</parameter> Sea Level Predictions and Observations <parameter>
<valueName>predictedArrivalTime: "La Jolla, California"</valueName> <value>201209
17T17:10:0007:00</value> </parameter>
<parameter> <valueName>layer:AEA:2.0:broadcastText</valueName> <value> This is
an Alberta Emergency Alert. Municipal District of Smoky River No. 130 has issued a
Hazardous Road Condition Alert. This alert is in effect for: Smoky River #130. Due to
extremely high winds a number of powerlines and power poles have been knocked down.
Causing road closures. There may also be not yet identified areas where power lines
have gone down. Along a number of trees on the road network. If you are in the affected
area: There are hazardous road conditions. Beware there may be fallen trees downed
power poles or lines on the road network. Take all necessary precautions. Use alternate
routes. Avoid downed power lines. Report downed lines to ATCO Power 1 800 668 5506.
For details visit www.emergencyalert.alberta.ca or stay tuned to local media. </value>
</parameter>
name=priority, value=high name=windspeedkmph value=125 name=smstext
value=Flash Flood Warning in Effect for Kalutara District
We use these element for add fields/ítem that were not defiend by CAP standard, like
alert level , and use other data formats
valueName:layer:ECMSCSMC:1.0:Alert_Type value:warning explanation: The class of
Alert as per the existing "Warning, Watch, Advisory, Statement" classification of our
buisness model. valueName:layer:ECMSCSMC:1.0:Broadcast_Intrusive value:yes/no
explanation:A marker to explicity indicate the "Emergency status" of this Alert Message
as being high enough to warrent intrusive measures for alerting the public.
valueName:layer:ECMSCSMC:1.0:Parent_URI value: [some internal URI] explanation:
This is an internal index used to identify the CAP message within our own systems. Clinet
inquiries that provide the CAP message (or this value) can help us quickly diagnose any
issue. valueName:layer:ECMSCSMC:1.0:CAP_count value:64909 explanation: A
counter of the number of CAP messages isued to date this year <valueName>layer:EC
MSCSMC:1.0:Alert_Location_Status value:active explanation: A marker to indicate that
the info block is referring to a collection of locations that are one of 'active', 'ended' or
'replaced' by another alert type. valueName:layer:ECMSCSMC:1.0:Alert_Name
value:rainfall warning explanation: A string that indicates uniquely the Alert name for this
message in the language of the <info> block valueName:layer:ECMSC
SMC:1.0:Alert_Coverage value:Nova Scotia explanation: A string that indicates the full
coverage assigned to the Alert. Coverages are predefined areas of responsibilty for an
alert based on jurisdiction, issuing office etc... to which almost any alert issued is just a
subset of the coverage.
valueName: IncidentName value: YUNTA explanation: References fire name valueName:
WarningLevel value: Bushfire Emergency Warning explanation: advises level of warning
message as aligned to national 3 tiered system for warning messages valueName:
IncidentLevel value: 3 explanation: Denotes CFS incident response level 1, 2, or 3
valueName: Status value: GOING explanation: denotes status of incident valueName:
ControlAuthority value: South Australian Country Fire Service explanation: denotes which
emergency service authority is controlling the incident
<parameter> <valueName>layer:Google:Region:0.1</valueName>
<value>Luzon</value> </parameter> Short value location description name
Fuel Type type of fuel, most commonly the vegetation classification Location Address
or location of the incident FireDangerClass Class of Fire 1,2,3 Status what state the
fire is in Out of Control, Being Controlled, Under Control, Out Fireground Burnt Area
(Ha) AllocatedResources Number of appliances, firefighters ControlAuthority which
Firefighting agency has control AlertLevel Public Alert level Emergency Warning, Watch
and Act, Advice CouncilArea Local Govt Area IncidentName Name of incdent
Evactuation has an evactuation been ordered
You can see the use of the <parameter> field in the CAP feed (link provided in earlier
question). We use it to provide data as part of formal nomenclature or standards within
emergency management in Australia. This allows other emergency agencies and the
general public to hear common language, as well as allows other systems to ingest and
process the data.
EventTime, time of earthquake (same as info/onset) EventIDKey, unique identifier for
earthquake (part of info/web url) Magnitude, earthquake magnitude Depth, earthquake
depth in kilometers and miles. HorizontalError, horizontal uncertainty of center of
info/area/circle in kilometers. VerticalError, vertical uncertainty of depth in kilometers.
NumPhases, number of phases used to determine earthquake location (often not
reported). RMSTimeError, the rootmeansquare travel time residual in seconds; how
well expected seismic wave travel times match measured travel times. AzimuthalGap,
largest distance between azimuthally adjacent stations in degress; the smaller this
number the better the location.
valueName: EventLocationName value: Amukta Pass, Alaska explanation: Short text
description of where the seismic event occurred valueName: EventPreliminaryMagnitude
value: 7.1 explanation: Preliminary magnitude of the seismic event valueName:
EventPreliminaryMagnitudeType value: Mwp explanation: Type of preliminary magnitude
of the seismic event. valueName: EventOriginTime value: 20110902T10:55:5400:00
explanation: Time stamp when the seismic event was originated valueName: EventDepth
value: 39 kilometers explanation: Preliminary depth of the seismic event valueName:
EventLatLon value: 1.800,171.400 0.000 explanation: Comma separated string with
preliminary latitude and longitude of the seismic event in decimal form. Northern latitudes
are positive, southern latitudes are negative. Eastern longitudes are positive, western
longitudes are negative. Note: radius of 0.000 signifies a point. valueName: VTEC value:
/T.CON.PAAQ.TS.W.0079.110902T1545Z110902T1645Z/ explanation: The Valid Time
Event Code (VTEC) enables alert providers and vendors to automate and tailor the
product stream delivered to their clients. See http://www.weather.gov/om/vtec/ for more
info on VTEC valueName: NWSUGC value: AKZ185187021645 explanation: The
Universal Geographic Code (UGC) typically specifies: 1) The affected geographic area of
the product or product segment, typically by state, county (or parish or independent city),
or unique NWS zone (land or marine). 2) The product expiration time . See NWSI 10
1702 (www.nws.noaa.gov/directives/sym/pd01017002curr.pdf) for more details on the
Universal Geographic Code valueName: ProductDefinition value: Tsunami warnings
mean that a tsunami with significant widespread inundation is imminent, expected, or
occurring. Warnings indicate that widespread dangerous coastal flooding accompanied
by powerful currents is possible and may continue for several hours after the initial wave
arrival. explanation: Short text paragraph describing the tsunami product being issued.
valueName: ProductID value: WEPA41 explanation: Alpha/Numeric string with the
product ID valueName: predictedArrivalTime: "[location]" value: 20110902T03:29:00
0800 explanation: 1) [location] Alpha/Numeric string identifying the location of the
predicted arrival time. 2) <value> has the actual predicted time as: YYYYMM
DDTHH:MM:SShhmm. Notes: 1) The location serves as a key to link predicted arrival
time to the predicted wave height. 2) Predicted arrival times will NOT be included, if
observed values are available. valueName: predictedWaveHeight: "[location]" value:
0.750m 2.461ft explanation: 1) [location] Alpha/Numeric string identifying the location of
the predicted wave height. 2) <value> has the actual predicted wave height in both
meters and feet and takes the form: N.NNNm N.NNNft where N.NNN is the height and m
indicates height is in meters, ft indicates height is in feet. Notes: 1) The location serves as
a key to link predicted arrival time to the predicted wave height. 2) Predicted wave height
will NOT be included, if observed values are available. valueName: observedArrivalTime:
"[location]" value: 20110902T04:52:000800 explanation: 1) [location] Alpha/Numeric
Yes (go to question 2) 7 58%
No (skip to question 3) 5 42%
string identifying the location of the observed arrival time. 2) <value> has the actual
observed time as: YYYYMMDDTHH:MM:SShhmm. Notes: 1) The location serves as a
key to link observed arrival time to the observed wave height. 2) Predicted arrival time will
NOT be included, if observed values are available. valueName: observedWaveHeight: "
[location]" value: 0.750m 2.461ft explanation: 1) [location] Alpha/Numeric string
identifying the location of the observed wave height. 2) <value> has the actual observed
wave height in both meters and feet and takes the form: N.NNNm N.NNNft where N.NNN
is the height and m indicates height is in meters, ft indicates height is in feet. Notes: 1)
The location serves as a key to link observed arrival time to the observed wave height. 2)
Predicted wave height will NOT be included, if observed values are available.
valueName: CMAStext value: Tsunami danger on the coast. Go to high ground or move
inland. Check local media. NWS explanation: Short text bulletin intended for Commercial
Mobile Alert System (CMAS) dissemination. This is part of the iPAWS profile. Text length
is limited to 90 characters.
If you do not use <parameter>, please explain why.No responses yet for this question.
CAP <resource> usage
Do you use the CAP <resource> element?
For each rescource you specify in CAP, provide an example and indicate thepurpose of the resource.
resourceDesc: earthquake magnitude contour
map:http://scweb.cwb.gov.tw/webdata/drawTrace/plotContour/2014/2014123.gif
We use it at the moment to link to a map of the incident. We have been considering
If you do not use <resource>, please explain why.
Haven't got there yet. Would really like to. The operational environemnt I support does
not create any resource items to attach.
We include an info/web url which displays all currently available resources. We may
consider resources in the future if useful.
The description field is already suitable for our feeds
Not required at this time
We dont have access to a resources files, but if we have media , links or something like
that , we could use these elements
linking it to official warning messages about the alert (e.g. for us, Major Fire Update,
Emergency Alert). Thus, essentially, link the CAP alert to more information about the
emergency.
Location of supplemental Graphical Products <resource> <resourceDesc>Energy
Map</resourceDesc> <mimeType>image/jpeg</mimeType> <uri>
http://wcatwc.arh.noaa.gov/tsuPortal/events/PAAQ/2012/09/17/maiqdx/2/WEPA41/energymaiqdx.jpg
</uri> </resource> <resource> <resourceDesc>Tsunami Travel Time
Map</resourceDesc> <mimeType>image/jpeg</mimeType> <uri>
http://wcatwc.arh.noaa.gov/tsuPortal/events/PAAQ/2012/09/17/maiqdx/2/WEPA41/ttvumaiqdx
02.jpg </uri> </resource> <resource> Event Data in JSON Format <resourceDesc>Event
Data as a JSON document</resourceDesc> <mimeType>application/json</mimeType>
<uri>
http://wcatwc.arh.noaa.gov/tsuPortal/events/PAAQ/2012/09/17/maiqdx/2/WEPA41/PAAQ.json
</uri> </resource>
<cap:resource> <cap:resourceDesc>map</cap:resourceDesc>
<cap:mimeType>text/html</cap:mimeType> <cap:uri>http://www.rfs.nsw.gov.au/fire
information/firesnearme</cap:uri> </cap:resource> link to the NSW Rural Fire Service
Public Facing Map
<resource> <resourceDesc>Broadcast Audio</resourceDesc>
<mimeType>audio/mpeg</mimeType> <size>236774</size>
rescourceDesc=Dengue PHI guidelines MIME=PDF
URL=http://health.gov.lk/resources/pdf/dengue_PHI_guilde.pdf resourceDesc=Sinhala
voice alert MIME=MP3 URL=http://health.gov.lk/resources/ivr/mp3/si_ivr_20141006
001.mp3
We have not used <resource> elements in practice yet but do plan to do so in the future.
We plan to include image files and/or KMZ files of tsunami travel time and wave height
predictions.
Yes (go to the next question) 7 58%
No (skip the next question) 4 33%
Additional <area> information
Do you have additional information that you would include in a CAP <area>block if you were able to?
If so, provide an example and indicate the purpose for including thisinformation at the CAP <area> level.
While the <polygon> and <geocode> parameterizations do cover most of our needs, we
also need specific types of geocoding, such as the NWS UGC and VTEC codes for the
US/Canada and international polygon codes in the Pacific/Caribbean. In addition, the
National Tsunami Warning Center also currently parametrizes its coastlines in terms of
linear break points that define coastal line segments rather than polygons.
Would like to include sensor data applicable to the area (in our case sea level predictions
and observations) <sensorData> <typeSensorData>Seal Level
Prediction</typeSensorData> <predictedArrivalTime>20120917T17:33:00
07:00</predictedArrivalTime> <location>Alamitos Bay, California (20 miles SE of L.A.)
</location> <predictedWaveHeight> <height units="meters">0.100</height> <height
units="feet">0.328</height> </predictedWaveHeight> <sensoorID>9414750</sensorID>
<! NOS ID > </sensorData> <sensorData> <typeSensorData>Seal Level
Observation</typeSensorData> <observedArrivalTime>20120917T17:33:00
07:00</observedArrivalTime> <location>Alamitos Bay, California (20 miles SE of L.A.)
</location> <observedWaveHeight> <height units="meters">0.100</height> <height
units="feet">0.328</height> </observedWaveHeight> <sensoorID>9414750</sensorID>
<! NOS ID > </sensorData>
Need polygon with inner boundary hole support.
Emergency Alert Area or potential area that will be impacted on by fire
<area> <areaDesc>Smoky River #130</areaDesc> <polygon>
55.94150864,116.97630208 55.89851828,116.97570748 55.81178857,116.97263631
Yes (go to the next question) 5 42%
No (skip the next question) 7 58%
55.81077996,116.92167375 55.73754964,116.91958504 55.73794633,116.84523024
55.72311392,116.79326899 55.46187074,116.79265639 55.46108484,116.7675258
55.37419435,116.76991838 55.37387145,116.92093754 55.3749311,117.53865779
55.46068361,117.53930479 55.46059683,117.57034842 55.67027495,117.56874976
55.67937187,117.58425612 55.67275649,117.63055639 55.67437424,117.63910234
55.68830655,117.65260206 55.71035084,117.64051156 55.74738237,117.64293281
55.79093778,117.598759 55.79320451,117.58699612 55.78863976,117.56692717
55.78987611,117.55925119 55.83217384,117.51525563 55.85345782,117.50000001
55.90853977,117.50281539 55.93488352,117.51241859 55.94381,117.52394465
55.98059483,117.53084568 55.98547997,117.52764436 55.98482353,117.28825744
55.94124592,117.28721914 55.94150864,116.97630208 </polygon> <geocode>
<valueName>profile:CAPCP:Location:0.3</valueName> <value>4819041</value>
</geocode> <geocode> <valueName>profile:CAPCP:Location:0.3</valueName>
<value>4819048</value> </geocode> <geocode> <valueName>profile:CAP
CP:Location:0.3</valueName> <value>4819042</value> </geocode> <geocode>
<valueName>profile:CAPCP:Location:0.3</valueName> <value>4819044</value>
</geocode> <geocode> <valueName>profile:CAPCP:Location:0.3</valueName>
<value>4819046</value> </geocode> </area>
possible to include severity of the alert in color, for example a darker red for area with the
highest severity vice versa.
location uncertainty. multiple polygons for different shaking intensities.
At times, it is difficult to define an affected area for an alert message. In absence of same,
we define the area of the incident, give as much information as possible, and allow the
judgement of the consumer of the alert. In the Australia profile, we have allowed
breakdown according to the Australian Bureau of Statistics and or Addressing data
standards for Australia, so that we may define towns and localities that are meaningful to
the general public.
Do you currently include this information elsewhere in the CAP message?
Yes (go to the next question) 6 50%
No (skip the next question) 6 50%
If so, provide an example of how you currently specify this information.
Sometimes, we provide a plain English description of the location, in the description of the
incident.
location uncertainy uses parameters. multiply polygons for different intensities could
potentially be multiple info elements, but are not yet included in CAP alerts.
Series of <parameter><value> <parameter> <valueName>predictedArrivalTime:
"Langara Island, British Columbia"</valueName> <value>20121027T21:16:00
07:00</value> </parameter> <parameter> <valueName>predictedWaveHeight: "Langara
Island, British Columbia"</valueName> <value>0.100m 0.328ft</value> </parameter>
We have <parameter> elements for VTEC and UGC. In our more comprehensive
Tsunami Event XML (TEX) schema, we have other elements as well. Some of these
could be translated over to CAP if needed.
<severity>Minor</severity>
Data not in CAP
Do you have additional alerting information that would be useful todisseminate via CAP but is not currently included in your CAP messages?
If so, provide an example and indicate the purpose of this additional missinginformation.
Event Location as opposed to Alert threat area. I would see myself adding another
parameter everytime I need to add something and I see that based on the cleint
experience. If I have somehting to add I will using a parameter and and layer and I see
that list growing based on experience. So I would use the 7 provided earlier as an
example of what 'could' come along later.
We haven't gotten around to including it. 4 33%
CAP does not provide a suitable means to include it 3 25%
Other 2 17%
Fire Behaviour Analyst prediction areas
Alerts level/color , for Colombia the alerts have colors that represents a different levels of
preparation for the populations and differents actions to take in case of disaster
These items are too numerous to list, but I refer you to the latest Tsunami Event XML
(TEX) specification version 2.0.1 for a listing of elements that the tsunami warning centers
find useful to share. These elements include many parameters related to the earthquake
and tsunami events themselves, as well as derived products that we disseminate. We
have incorporated a small subset of these as the CAP <parameter> elements that I listed
earlier in this survey. One fundamental difficulty with CAP is in conveying many multiple
areas with varying tsunami alert and threat levels. It would make more sense for tsunamis
to have CAP's urgency/severity/certainty elements be subelements of <area> so that the
differing threats can be conveyed geographically. In our TEX specification, we have the
alert level (domestic) or threat level (international) elements as subelements of area for
this reason.
shaking intensity and estimated population impact. earthquake early warning.
Social Media Linkages <socialMedia> <twitter>
<URL>https://twitter.com/NWS_NTWC/status/538547374038085632</URL> </twitter>
</socialMedia>
Please explain why you do not include this additional information.
End
What other challenges do you have with CAP or changes would you like tosee to the CAP specification?
The schema needs to be truly extensible. Would be nice if there was a 'Tsunami' hazard
category
It is not well known enough by the general public. The EDXLDE standard appears not to
be much used, although we have implemented CAP within it, as advised by OASIS.
Standardise on a delivery means: is it RSS 2.0, or Atom, or ... Don't offer many choices;
these just confuse the public and ingestors of the information. We need a solution
internationally that is similar to IPAWS in the US; i.e. a place to which we publish CAP
alerts, and from which we can consume those alerts of interest.
Changing FEMA/IPAWS endpoints. We were connected for some time, but currently only
distribute CAP alerts via our ATOM feeds (to google and other saavy consumers).
CAP has seen widespread adoption by the emergency management community, but
paradoxically the fields represented by CAP seem more optimized for public consumption
rather than for use by emergency management officials. At least with regard to tsunami
hazards, CAP in its current form is not sufficient to address the informationsharing needs
of the tsunami warning system. That is why we created a new XML specification
(Tsunami Event XML: TEX) to include what we needed to adequately parametrize
tsunami messages and products. We would welcome an open dialog on the topic of
expanding CAP's flexibility and perhaps eventually finding middle ground for TEX to
change into a tsunamispecific CAP profile. Meanwhile, we also have a barebones
tsunami CAP profile called CAPTSU that we are disseminating for some messages. The
main points of contact for these schemas are John Carrick ([email protected]) at
the NTWC and Brian Shiro ([email protected]) at the PTWC.
The alert/event dichotomy is not understood and not covered off well enough in the
documentation.
Bushfires or Wildfires are very dynamic in nature as as such it is particularly hard to get
accross the potentially affected radius. For example we quite accurately have the 'burnt
area' but applying some buffer to this in an urban interface does not accurately work for
Alerting as we may be creating undue panic for residents that arean't going to be affected
by the incident.
Alerts level/color , for Colombia the alerts have colors that represents a different levels of
preparation for the populations and differents actions to take
Number of daily responses
