OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EMERGENCY-16) Support CAP event location and movement

    [ https://issues.oasis-open.org/browse/EMERGENCY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41749#comment-41749 ] 

Doug Allport commented on EMERGENCY-16:

A few key points:
1. Emergency officials affected by an event often (if not more often than not) receive their situational awareness at the same time as the public, from a the public alert. Communications between officials is far from good! 
2. Emergency officials are presenting alerts on maps as situational awareness. They want to know where the event is located in addition to what the public has been told to do, often in this order, given so few of them play a communications role. 
3. Use cases such as a chemical fire with a large notification area, wildfire with a large evacuation area, protest route with a buffer notification area, etc. have two distinct areas to be communicated: Event area and notification. 
4. Canada, and others, have had to deal with the ongoing challenge of distinguishing subject even and alert area, event duration and message expiry, etc. The introduction of a elements, blocks, etc. can help put the ongoing issues behind us, given that all stakeholders will be discussing specific elements and not <parameter> variables. E.g. This morning I learned that a key stakeholder has introduced an event location <parameter> to help overcome their challenge, when Canada has already adopted a documented <parameter> solution they should be using. 

> Support CAP event location and movement
> ---------------------------------------
>                 Key: EMERGENCY-16
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-16
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Should a new CAP element be added that describes the current event location, speed and direction of movement?
> Also: Is there a need for describing motion? Ideas include multiple info blocks with own effective time/location or a new movingArea structure. Scenarios? Specifics?

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]