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-35) Area Type Designation

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

Mike Gerber commented on EMERGENCY-35:

I would compare/contrast this paradigm with others.  For example, NWS plans to add a motion description parameter for storms (and perhaps other weather related events) which includes a lat/lon pair (or pairs) demarking the storm location as well as the speed and direction of movement.  This is in addition to the alert area  polygon we already include in the CAP message.  

> Area Type Designation
> ---------------------
>                 Key: EMERGENCY-35
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-35
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tomer Petel
> The <area> block in CAP may either:
> Refer to the area where the incident is taking place or affecting
>  - or - 
> It may refer to an area where there are people that we want to notify about the incident (Essentially a targeting area) 
>  - or- 
> It may refer to both (often times the same area we want to target is also the area of the incident)
> It would be important for the processing system to know which it is, so as to take the proper action (for example system may target the people in the targeting area and send them a map of where the incident is taking place, and the two may be different)

This message was sent by Atlassian JIRA

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