DisasterResponse telecon 2014-02-18

< Back to the Disasters Homepage
Telecon info: Tuesday February 18, 2014, 10-11 am Pacific (1-2 pm Eastern)

• Call-in toll-free number (US/Canada): 1-877-668-4493
• Attendee access code: 23138379#

Agenda:

1. Discuss and finalize cluster objective, mission statement (Draft: ESIP Disaster Cluster is to facilitate connections and coordinate efforts among data providers, managers and developers of disaster response systems and tools, and end-user communities within ESIP.)
2. Discuss goals and potential activities the group plan to accomplish by Summer ESIP, possible activities include:

• Classify disaster types for assessment with the cluster, and identify those within scope
• Capture use cases, potentially contribute to next GEOSS Architecture Implementation Pilot opportunity (e.g., AIP-7 in 2014)
• Gather insights from organizations addressing disasters like GEOSS, USGEO, OSTP, CEOS, OGC (complementary, not duplicate effort)
• Collect information from ESIP members involved in disaster response/risk reduction such as what data are being used now (list of derived products) and map data sources to consumers (probably by hazard type)
• Identify commonality and major gaps
• Develop a webinar or exhibit on the use of EO for disasters to engage end users and better understand their needs

Notes
Attendees - Karen Moe, Emily Law, Carol Meyer, Erin Robinson, How? (Taiwan), Ken Keiser, Bob Chen, Bob Downs, Don Sullivan, David Arctur, Oleg Auvlov, Hook Hua, Joan Aron

1. Discuss and finalize cluster objective, mission statement (Draft: ESIP Disaster Cluster is to facilitate connections and coordinate efforts among data providers, managers and developers of disaster response systems and tools, and end-user communities within ESIP.)

   The discussion about the mission statement framed by three questions raised by Emily Law and Karen Moe - (1) Part of the mission is to connect stakeholders, do we also extend that to other disaster platforms? (2) There was significant exchange on ESIP-all about disaster definition. What do we include as disasters? (3) There was also significant discussion about the disaster life cycle. Are we focused solely on response or do we extend to mitigation and prediction?

   The group agreed that disasters are multidimensional - life cycle is one dimension, type is another and geography could be a third. The group also stressed multiple times the necessity to identify focused objectives, stakeholders and purpose of the group is and specifically, how is it different from other groups working on disaster already around. Hook Hua described ESIP's niche as being able to see commonalities across domains or dimensions of disasters. This niche supports the initial purpose of the cluster across disaster types to find commonalities over the entire life cycle. Don Sullivan also suggested that this cluster may be a glue support - to provide the 'last mile' creating crucial connections.

   The group discussed that success might be identifying gaps in current system, to identify common architecture patterns; The audience is data providers. These are people that are working closely with end users like re-insurers; It has taken a long time to work with the users to identify specific products or places where remotely sensed data can be used.

2. Discuss goals and potential activities the group plan to accomplish by Summer ESIP, possible activities include:

• Classify disaster types for assessment with the cluster, and identify those within scope
  • Create a wiki subpage to collect definitions of Disaster/Hazard Types and allow ESIP participants to add to the list as well as identify what areas they are interested in analyzing (or have relevant background) for the cluster
  • Create a wiki subpage to capture Disaster Life Cycle views, also allow inputs on content and a way to indicate which phases to analyze within the cluster (as for hazard types)
  • Create a wiki area to contribute links to relevant organizations addressing our topics; site could help track relevant meetings/ conferences (but separate from a cluster calendar that Emily suggested)
• Capture use cases, potentially contribute to next GEOSS Architecture Implementation Pilot opportunity (e.g., AIP-7 in 2014)
  • The group decided they weren't ready to contribute to GEOSS AIP-7 yet.
• Gather insights from organizations addressing disasters like GEOSS, USGEO, OSTP, CEOS, OGC (complementary, not duplicate effort)
  • It was suggested that this group connect with the OGC Emergency Management & Disaster Response - focused on standards, but some overlap. The group has members that participate in both group