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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Steve Hakusa commented on EMERGENCY-16:
---------------------------------------

I fear that whatever that it would take the committee a long time to come up with a reasonable suggestion that solves a majority of the (complex) use-cases here.  JMA tries to support location and movement in their JMX format; the result is complex and handles different event types differently.  I'd suggest speaking with someone from JMA before going too far down this route.

There is an alternative of allowing the community to use their own formats and slowly converge because alert aggregators don't want to implement and maintain many different formats.  I call out this case in http://www.wmo.int/pages/prog/amp/pwsp/documents/CAP-IW-2013-p03-10-US-Google.pdf 

> Support CAP event location and movement
> ---------------------------------------
>
>                 Key: EMERGENCY-16
>                 URL: https://tools.oasis-open.org/issues/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
(v6.2.2#6258)