disaster lifecycle i

Disaster Lifecycle IPublished on Commons (https://commons.esipfed.org)

Disaster Lifecycle I [1] Submitted by Elaw on Mon, 2014-10-06 16:25 Thursday, January 8, 2015 - 08:30 to 10:00Event: Winter Meeting 2015 [2]Session Type: Breakout [3]Expertise Level: Beginner [4]Collaboration Area: Cloud Computing [5]Decisions [6]Discovery [7]Earth Science Collaboratory [8]Energy and Climate [9]Products and Services [10]Semantic Web [11]Visualization [12]Abstract/Agenda: ESIP Disaster Lifecyle Cluster is to facilitate connections and coordinate efforts among dataproviders, managers and developers of disaster response systems and tools, and end-usercommunities within ESIP. We are establishing a testbed called Collaborative Common OperatingPicture (C-COP) to facilitate sharing and validation of data products and tools that will benefit everyphase of disaster lifecyle. This session will give an overview of the testbed, demonstrate use ofexample products and tools shared on the platform, and describe how products and tools can becontributed to C-COP. We will also hear more about the GEOSS Architecture Implementation Pilot andactivities involving the GEOSS Disasters Societal Benefit area, and we can discuss opportunities forfuture collaborations.

Draft Agenda 8:30 – 9:30 am ET Collaborative Common Operating Picture (C-COP) Testbed: concept, status, and way forward

Dave Jones/StormCenter Inc.

Maggi Glasscoe/NASA JPL

Discussion on the new ESIP sponsored testbed: concept, status, initial experience on how the testbedworks, followed by discussion on testbed activities for 2015.

9:30 – 9:50 am ET The GEOSS Architecture Implementation Pilot (AIP) program: background, recent results,opportunities in future

Bart De Lathouwer/OGC

Discussion on related architecture pilot activities for GEOSS and the Disasters Societal Benefit area Note: George Percivall/OGC will discuss the overall GEOSS Architecture Implementation Pilot (AIP)an an agile development process for the GEOSS Information System, on Tuesday at 16:00 in theFoggy Bottom Room. This session is intended to explore the disasters domain in more detail. 9:50 – 10:00 am ET

Testbed wrap up discussion for 2015 plans

Emily Law/NASA JPL, Karen Moe/NASA ESTO, and all

of 6

https://commons.esipfed.org/node/2698


Notes:

<Sean Barberie's Notes>Disasters Lifecycle I

· Introduction by Dave Jones

· Established a platform to access and share geospatial data

· Accelerate a collaborative approach to reviewing and testing geospatial products within ESIP

· Establish Test Folders

· Identify Partner Datasets (e.g. E-Decider, NOAA, U of Alabama Huntsville)

o What are the characteristics for the types of data sets we want for this platform?

· Test datasets for display

· Apply successful datasets to “ESIP Trusted Data” Folder

o Vision: have ESIP Trusted Data available to emergency response organizations any time andquickly available after a disaster.

· On-Line help available for adding datasets.

o Need to determine initial credentialed leaders.

· Conducts prototype product evaluation session on telecons.

· Q: How do we establish criteria for evaluating different data sets when determining what isESIP Trusted Data?

· A: The disaster lifecycle cluster will come up with the criteria that we will use to determinewhether a data set is ESIP Trusted Data. We can use different levels to display a seal of approval fora given data set: i.e. Trusted Data Level 1, Trusted Data Level 2, etc.

· Anne Rosinski comment: thinks we’re on the right track but wants to push us to go further. GISdata: in a disaster, geospatial data is not the only data that is important for disaster management.Each organization builds its own operational picture using their own platform (e.g. EPA uses theirown system). We need two-way information exchange between the systems. It is important to takedata from multiple sources and use it to build our own custom tool and to give our users the abilityto build their own product. Described Exchange Core disaster management software as an example.

· Dave Jones: the disaster lifecycle group is primarily to evaluate and prototype data productsand not to necessarily produce a final end-user product.

· Ken UAH: It is possible that terms that we are using are causing some confusion. The focus ison the common operating data and not necessarily on the common operation picture. Since thefocus of the disasters lifecycle is data availability.

of 6


· Begin presentation: Margaret Glasscoe

· E-Decider is a decision support platform that uses remote sensing and geospatial data tocreate products for decision makers.

· Geogateway is a analysis gateway for scientific discovery and disaster response.

· Web-based and map-enabled.

· Can incorporate NASA UAV SAR for surface deformation (from the look of the maps this mighthave been InSAR).

· This was tested during the Napa Earthquake in California.

· Work with CA Earthquake Clearinghouse

· Dave Jones

· Showing what the interface will look like for the Disaster Lifecycle testbed.

· Karen: Exciting developments. But we may need to know a little bit more about the criteriaused by the end-users to evaluate the data and the needs of the customers.

· Bart De Lathouwer: Open Geospatial Consortium

· Presentation on Architecture Implementation Pilots (AIP)

· AIP is an agile, evolutionary development process, that proves the maturity of theinfrastructure components.

· AIP phase 7.

· Jan 27th will be the call for participation for AIP-8 with a meeting in Virginia on March 23rd inNorfolk VA.

· See slide figure for societal benefit areas (SBAs)

· Focus on using open standards.

· AIP-7 Results: GEOSS Water Services, 24 hour flood prediction. In collaboration with theDisaster Management and Agriculture SBAs. World-wide participation. WaterML2.

· Crowd sourcing for disasters management: Open GeoSocial API (NASA)

· How can the GEOSS portal interact with community portals?

o Can this be a two-way street where both portals build off each other?

· AIP-8 is focused on mobile apps and web applications.

<Ken Keiser's Notes> Disaster Lifecycle (Emily leading)

local

of 6


Maggie GlascoeEmilyBill TengSean Barbarie - student internChris Mattmanseveral others...

online

Dave JonesAnne Rosiniski - earthquake clearinghouseBart De LathouwerKaren MoeDan KeyesKevin WardSean BarberleStu FryeSvetla Hirstova-Veleva

Dave Jones - collaborative common operating picture testbed

current constraints

isolated datacomplex toolslimited interaction

GeoCollaborate integrates

platformspeopledata

Real-time Decision Support for

crisis managementplanning/traininglogistics/operations

Approach

establish a platform to access and share geospatial dataaccelerate collaborative approachestablish test foldersidentify partner datasets (Edecider, NOAA, UAH, others…)test datasets for displayapply successful “trusted" datasets

Questions

Emily - what are the requirements to turn a test product into a “trusted”dataset? - up to the group at this point to make those decisions andeventually engaging customers/communities to give that feedback, working todefine a “seal of approval” approach that can be assigned to the trusteddatasetsAnne - pointing out that geospatial data is not the only data important fordecisions, need to have general COP datasets that multiple systems canaccess and utilize - requesting that the focus be on COP “data” as opposed toapplication - making the data interoperable. - Dave agrees that common datais the goal.

Maggie Glascoe - JPL E-Decider and GeoGateway

note that Marlon Pierce at Indiana is involved with this projectEarthquake response case studies

of 6


? how are event notifications received?questions

Bill - question about resolution of data Ken - question about event notifications - using USGS earthquake notificationsfor event trigger

Dave Jones - demonstration of “GeoSync” - GeoCollaborate level 1

using E-Decider example of earthquake in CAdemo Storm Centers GeoCollaborate COP toolhttp://esip.geocollaborate.com/ [13]

has concept of “leader” who is doing workand “followers” who can watch/monitor what the leader is doingmaster-slave display concept

Questions

Karen - look at how the cluster can evaluate this functionality - how to getmore common data products in to the system(email question to Dave) is this an open source tool? - No, but can beavailable for testing

Bart De Lathouwer - OGC (in Dublin) - Architecture Implementation Pilots (AIP)

pilots for GEOSS Common Infrastructure (GCI)

uses in-kind contributionspreparing for AIP phase 8 - call in January 2015

disaster areas

water (drought / flood)others

SPS - sensor planning service - sensor tasking - ISERV?AIP 7 was focused on water services - flooding primarily

used crowd sourcing in situ for disaster management

Open GeoSocial API (NASA - Stu?)SSO (single sign-on) was important to facilitate usersexplored moving functionality to data in the web

AIP 8 - focus on light, web or mobile apps using GEOSS resourcesQuestions

Emily - clarifying that AIP 8 is focusing on web and mobile appsBill - question about whether social media input is participatory or beingharvested - some of both. Bill comment that geolocation is hard whenharvesting.

Attachments/Presentations: OGC AIP Intro and relevant for DM C Smaller.ppt [14]

Glasscoe_DLC1.pptx [15]Session Leads: Name: Emily Law [16]

Organization(s): JPL [17]

Name: Karen Moe [18]Organization(s): NASA ESTO [19]Email: [email protected] [20]

Presenters: Name: Emily Law [16]

of 6


Organization(s): JPL [17]

Name: Karen Moe [18]Organization(s): NASA ESTO [19]Email: [email protected] [20]

Notes takers: Name: Sean Barberie [21]Organization(s): University of AlaskaFairbanks [22]Email: [email protected] [23]

Name: Ken Keiser [24]Organization(s): University of Alabama inHuntsville [25]Email: [email protected] [26]

Creative Common License: Creative Commons Attribution 3.0 LicenseTeaser: Working toward a common information architecture/model to faciliate consistentmanagement of data products useful for disaster life cycleAccepted: Source URL: https://commons.esipfed.org/node/2698

Links[1] https://commons.esipfed.org/node/2698[2] https://commons.esipfed.org/2015WinterMeeting[3] https://commons.esipfed.org/session-type/breakout[4] https://commons.esipfed.org/taxonomy/term/260[5] https://commons.esipfed.org/collaboration-area/cloud-computing[6] https://commons.esipfed.org/collaboration-area/decisions[7] https://commons.esipfed.org/collaboration-area/discovery[8] https://commons.esipfed.org/collaboration-area/earth-science-collaboratory[9] https://commons.esipfed.org/collaboration-area/energy-and-climate[10] https://commons.esipfed.org/collaboration-area/products-and-services[11] https://commons.esipfed.org/collaboration-area/semantic-web[12] https://commons.esipfed.org/collaboration-area/visualization[13] http://esip.geocollaborate.com/[14] https://commons.esipfed.org/sites/default/files/OGC%20AIP%20Intro%20and%20relevant%20for%20DM%20C%20Smaller.ppt[15] https://commons.esipfed.org/sites/default/files/Glasscoe_DLC1.pptx[16] https://commons.esipfed.org/node/1811[17] https://commons.esipfed.org/taxonomy/term/1106[18] https://commons.esipfed.org/node/1178[19] https://commons.esipfed.org/taxonomy/term/214[20] mailto:[email protected][21] https://commons.esipfed.org/node/7880[22] https://commons.esipfed.org/taxonomy/term/943[23] mailto:[email protected][24] https://commons.esipfed.org/node/1051[25] https://commons.esipfed.org/taxonomy/term/186[26] mailto:[email protected]

of 6

disaster lifecycle i

Documents