1 / 33

PGIST CyberGIS Integration Strategy

PGIST CyberGIS Integration Strategy. Timothy Nyerges , Mary Roderick University of Washington November 10, 2011. About PGIST. Collection of participatory deliberation tools: BCT/CCT/CST Brainstorm Concerns / Categorize Concerns / Concerns Synthesis.

astra
Download Presentation

PGIST CyberGIS Integration Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PGIST CyberGIS Integration Strategy Timothy Nyerges, Mary Roderick University of Washington November 10, 2011

  2. About PGIST Collection of participatory deliberation tools: BCT/CCT/CST Brainstorm Concerns / Categorize Concerns / Concerns Synthesis Enables large-scale, asynchronous participation of a diverse group of actors in a decision making process. Delphi and Technology of Participation heavily influence both processes. • Structured deliberation, consensus-building & decision-making • Open, transparent decision repository • Participation metrics for reporting Typical Workflow:

  3. PGIST Architecture Web-based application, user-interface needed for deliberation BCT/CCT/CST are composed of DWR agents, Struts action classes, Hibernate persistence objects

  4. CyberGIS & PGIST Integration • Two-fold Purpose: • Enable structured discussion about Gateway integration Discuss Discuss Not Bug Tracking! Deliberative framework to advance GIScience.

  5. CyberGIS All-Hands Meeting CyberGIS & PGIST Integration • Two-fold Purpose: • Support collaborative domain science research and problem-solving

  6. CyberGIS & PGIST Architecture PGIST Server IFrame • Single sign-on via Token Service • Custom web interface for CyberGIS

  7. 1st Deliberation Topic Evaluation and development of metrics for: CyberGIS Gateway Integrated Software Elements Background: VCC (the specific PGIST application being integrated into the Gateway) is useful for synthesizing open dialog into a definitive set of topics/indicators/metrics through a mix of automated text mining, user interaction, and group decision making. Why Participatory Metrics Development? We want to know about people’s experience with CyberGIS and need a systematic way of structuring that information. Through participatory metrics development we achieve both. From CyberGIS Proposal, pg. C-6: “Evaluation of the CyberGIS framework will be based on rigorous metrics and driven by the same participatory approach developed to capture evolving community requirements.”

  8. CyberGIS Metrics Overview

  9. Example CyberGISCollaboratory

  10. Example Proposed Agenda: One week per step Agenda is generic. Instructions for each step will provide specific details about metric development. Brainstorm = free form input from each user, for which key words are generated that will later be used to develop metric categories and assign measurement units Assess = provide comments on others’ feedback and vote to move forward to metric category development

  11. Example CyberGISCollaboratory Write about your experience using CyberGIS in the box on the right and select or write your own keywords and keyphrases. Be specific. Try to use keywords and keyphrases that describe your experience in terms of how you used CyberGIS and any issues or difficulties you encountered. Of course, praise is welcome too! We will use these keywords and key phrases to develop evaluation metrics in the next step.

  12. Example CyberGISCollaboratory

  13. Example

  14. Example CyberGISCollaboratory

  15. Example

  16. Example

  17. Example CyberGISCollaboratory Explore other participants’ metric categories for keywords and keyphrases. Make comments and discuss how well they capture your experience with using CyberGIS. Vote on moving forward to Step 3 when satisfied.

  18. Example

  19. Requirements Analysis Review & Update

  20. Requirements Overview 4 Broad Areas of Participatory Requirements Business The character of geospatial problem solving. System Capabilities to address geospatial problem solving. Component Software design for implementing capabilities. Application Packaging the components into solutions to address scientific problem solving requirements. Use Cases Web Survey CyberGIS Integration Requirements

  21. End Users Devices Portals Applications Business Requirements Service Providers Model Standards Service Consumers Tech Standards System, Component, Application Requirements Spatial Middleware Service Registry Integration Requirements Generic CyberInfrastructure

  22. Use Case Overview

  23. Use Case Overview

  24. Requirements Synthesis Example EM.BUC.1 Wildfire Evacuation Triggers • Yan’s Comment: • This table is a good starting point, but it only lists what current system use cases claim to have. To enrich this section: • Find more details of each existing software to make the list more complete. • Ask each software provider to check what they have, will have, would like to have in CyberGIS project. I believe we have most of capabilities, but the challenge is on integration.

  25. What have we learned? • Range of use cases represents the diversity of research CyberGIS can support and need for on-going contributions. • Business use cases should be supported by one or more system use cases. Due to the distributed and voluntary nature of the participatory requirements process and SE contributions, this 1:1 or 1:M relationship is not given at this time. • Identification of missing functionality important to drive future requirements and prioritize software element integration. • Gaps between the emergency management and software element use cases also indicate the need for both a top-down, domain science driven and a bottom-up, interoperability- focused integration strategy.

  26. Next Steps • Top Down Strategy: • Selection of one domain science UC • (UW suggests flooding vulnerability) • Creation of baseline UC • Mapping between baseline • and CyberGIS • Bottom Up Strategy: • Pairwise integration with Gateway • Documentation of best practices: • SEs and Gateway in action. • Integration across SEs

  27. Flooding is the most severe hazard – causing both the largest loss of life and most physical damage. It is both an acute emergency management and climate change issue.

  28. Social Media

  29. How can social media enhance CyberGIS? “for broad-based communication functionalities and are used to develop affinity groups among colleagues, fostering social topic awareness and allowing for rapid communication” CyberGIS Proposal, pg. C-7 How can CyberGIS support social media-oriented research? See Wilson Center webcast: Social Media in Emergency Management: Transforming the Response Enterprise How does Social Media differ from PGIST & CyberGIS WIKI? What are the synergies? What is the integration potential?

  30. Example: Add social media derived content to maps, ie. live info feeds from disaster sites.

  31. Example: Create maps and share via a range of social media outlets

  32. Example: Create special interest groups and integrate popular social media tools

  33. Example: Add twitter feed to Gateway (can already follow GISolve on twitter)

More Related