20100512 Workflow Ramage


Published on

High level presentation for the workshop on workflow and earth observation at OSGIS 2010 at the University of Nottingham

  • Be the first to comment

  • Be the first to like this

20100512 Workflow Ramage

  1. 1. Workshop on Workflows on Earth Observation Steven Ramage, OGC [email_address] 21 June 2010, Sir Clive Granger Building, University of Nottingham
  2. 2. The importance of workflow <ul><li>Workflows are important because real jobs rarely involve few, simple tasks. Creating value in almost any area of endeavor requires the sequencing and organisation of human efforts, or of digital or mechanical processes, e.g. </li></ul><ul><ul><li>Supply chain manufacturing </li></ul></ul><ul><ul><li>Insurance claims processing </li></ul></ul><ul><ul><li>Building design </li></ul></ul><ul><li>All can be studied as workflows. </li></ul><ul><li>The geospatial realm is no different. Image processing and spatial modeling can also be characterized as workflows. </li></ul>
  3. 3. Description of workflow <ul><li>In information systems workflows are a series of coordinated analytical and information processing steps </li></ul><ul><li>Typically to transform data into information or knowledge </li></ul><ul><li>Workflows could be described as Web-based scripts or macros that automate serial information tasks. </li></ul>
  4. 4. OGC Interoperability Program <ul><li>Collaborative, standards-based interoperability initiatives </li></ul><ul><li>Sponsors define operational issues where standards can help and initiatives are created </li></ul><ul><li>Technology providers come together to prototype solutions to tackle sponsors’ interoperability problems. </li></ul><ul><li>OGC Web Services (OWS) initiatives underway for years </li></ul><ul><li>OWS-5 had geospatial workflows as a primary focus, a detailed video report is available at: </li></ul><ul><li>http://www.opengeospatial.org/projects/initiatives/ows-5 </li></ul>
  5. 5. OGC Web Services standards <ul><li>OGC has four main OGC Web services standards for geospatial data sharing and processing: </li></ul><ul><li>OGC Web Mapping Service Interface Standard (WMS) defines a Web API for requesting a picture of data, such as a PNG, JPEG, or GIF. </li></ul><ul><li>OGC Web Feature Service Interface Standard (WFS) defines a Web API for accessing raw vector data in formats such as GML, KML or GeoRSS and adding, updating and deleting data. </li></ul>
  6. 6. OGC Web Services standards <ul><li>OGC has four main OGC Web services standards for geospatial data sharing and processing: </li></ul><ul><li>OGC Web Coverage Service Interface Standard (WCS) defines a web API for accessing raster data in formats such as GeoTIFF, JPEG2000, or HDF WCS also supports adding, updating and deleting data. </li></ul><ul><li>OGC Web Processing Service Interface Standard (WPS) defines a web API for running an algorithm or model, specifying data inputs and outputs </li></ul>
  7. 7. “ Chaining” Web Services for decision support … WCS WPS – Classification WPS - WCTS WFS Internet Web servers OGC Interfaces Service chaining creates value-added products Decision Support Client Geoprocessing worklow developed in OGC testbeds since 2004 Assess Wildfire Activity
  8. 8. BPEL workflow in OWS-5 Participants chained combinations of services together to address the requirements of geospatial data conflation and image processing. It also addressed an important gap, which was the lack of SOAP (Simple Object Access Protocol) and WSDL (Web Service Description Language) descriptions for those APIs.
  9. 9. BPEL workflow in OWS-5 Both W3C standards are critical for creating and managing workflows using industry standards such as OASIS’s BPEL (Business Process Execution Language). BPEL is the workflow description language used in many end-user service chaining tools such as Oracle BPEL Designer and George Mason University’s BPEL Power.
  10. 10. Conflation workflow architecture
  11. 11. Conflation workflow architecture The OWS-5 geo-processing workflow thread bound together WFS and WPS services in BPEL scripts to model data conflation in a consistent, repeatable fashion. This successful prototype signaled the utility of this approach for a host of geospatial tasks that require the combination of many different geospatial services and operations. Fusion activities developed in OWS-7 and will have more focus in this area for OWS-8.
  12. 12. OGC Web Processing Service (WPS) WPS GetCapabilities Execute DescribeProcess Algorithms Repository … … Algorithm 1 Data Handler Repository … … Data Handler A Communication over the web using HTTP WPS-client Web Processing Service
  13. 13. REST-oriented workflow in OWS-5 The SOAP/WSDL/BPEL approach to chaining Web services is one of the most widely used ways to implement service oriented architectures (SOA). However, other approaches, notably REST (Representational State Transfer) services, are also used to implement services in an enterprise. Some feel that Web services do not need the extra layer of description provided by SOAP and WSDL to build reliable workflows.
  14. 14. REST-oriented workflow in OWS-5 REST uses HTTP and other parts of the basic Web platform. In the SWE (Sensor Web Enablement) thread of OWS-5, participants used a REST-based architecture and WfXML to create workflows that allowed raw earth observation data to be acquired from assets, such as the EO-1 satellite, and then utilized by different WPS. Relevant data were then published and distributed to end-users in formats such as GeoAtom (Atom with GeoRSS extensions) and KML.
  15. 15. Integrating smoke WPS into WfXML-R workflow GMU GRASS SOAP/WSDL GRASS Image Algebra EO-1 SOS Google Earth Execute <ul><li>Inputs: </li></ul><ul><li>URL Grid 1 </li></ul><ul><li>URL Grid 2 </li></ul><ul><li>OutputType </li></ul>EO Sensor Web Workflow GMU WCS-T GetCapabilities DescribeProcess NGC EO-1 Smoke WPS Calculated smoke geotiff Classified smoke geotiff Call calculation Call classifier <ul><li>Processes: </li></ul><ul><li>FineSmoke </li></ul><ul><li>CoarseSmoke </li></ul><ul><li>Inputs: </li></ul><ul><li>URL Grid 1 </li></ul><ul><li>URL Grid 2 </li></ul><ul><li>OutputType </li></ul><ul><li>Output: </li></ul><ul><li>URL Grid 3 </li></ul>
  16. 16. OWS-6 WPS Grid Processing <ul><li>Bastian Baranski and Bastian Schäffer, Univ. Muenster Institute for Geoinformatics (IfGI) and 52° North, Germany </li></ul><ul><li>Andrew Woolf, Science and Technology Facilities Council (STFC), UK </li></ul><ul><li>Lan-Kun Chung, GIS Center, Feng Chia University, Taiwan </li></ul>
  17. 17. OWS-6 WPS grid processing <ul><li>Grid processing profiles of WPS - specification </li></ul><ul><ul><li>WPS grid processing profile integrated with grid computing infrastructure: </li></ul></ul><ul><ul><ul><li>Job Submission Description Language (JSDL) </li></ul></ul></ul><ul><ul><ul><li>High Performance Computing (HPC) Basic Profile (HPC-BP) </li></ul></ul></ul><ul><ul><ul><li>Simple API for Grid Applications (SAGA) </li></ul></ul></ul><ul><ul><ul><li>Data Access and Integration set of specifications (WS-DAI-*) </li></ul></ul></ul><ul><ul><ul><li>Web Services Resource Framework (WSRF) </li></ul></ul></ul>
  18. 18. OWS-6 WPS grid processing <ul><li>OGF enabled WPS - implementation </li></ul><ul><ul><li>WPS to benefit from and integrate with distributed computing resources and technologies </li></ul></ul><ul><ul><li>Two potential ways to make use of OGF specifications, concepts and their implementations where identified </li></ul></ul><ul><ul><ul><li>encapsulating other resources </li></ul></ul></ul><ul><ul><ul><li>integration alongside other services </li></ul></ul></ul>
  19. 19. Grid-enabled WPS implementations <ul><li>Airport Scenario </li></ul><ul><ul><li>Trajectory Service (WPS JSDL Profile) </li></ul></ul><ul><ul><ul><li>Science and Technology Facilities Council (STFC), UK </li></ul></ul></ul><ul><ul><li>Plume Rendering Service (WPS JSDL Profile) </li></ul></ul><ul><ul><ul><li>Institute for Geoinformatics (IfGI), University of Münster, Germany </li></ul></ul></ul>
  20. 20. Grid-enabled WPS implementations <ul><li>Debris Flow Scenario </li></ul><ul><ul><li>Rainfall Data Interpolation (WPS HPC Basic Profile) </li></ul></ul><ul><ul><ul><li>Institute for Geoinformatics (IfGI), University of Münster, </li></ul></ul></ul><ul><ul><ul><li>Geographic Information Systems (GIS) Research Center, Feng Chia University (FCU), Taiwan </li></ul></ul></ul><ul><ul><li>Geophone Data Analysis (WPS HPC Basic Profile) </li></ul></ul><ul><ul><ul><li>Institute for Geoinformatics (IfGI), University of Münster, Germany </li></ul></ul></ul><ul><ul><ul><li>Geographic Information Systems (GIS) Research Center, Feng Chia University (FCU), Taiwan </li></ul></ul></ul>
  21. 21. OGC online resources <ul><li>OWS-6 Geoprocessing Workflow Architecture </li></ul><ul><li>Engineering Report   </li></ul><ul><li>0.3.0  09-053r5   </li></ul><ul><li>Bastian Schäffer  2009-10-09 </li></ul><ul><li>This document covers geo-processing workflow </li></ul><ul><li>best practices and methods in a SOA environment. </li></ul>
  22. 22. Debris Flow Monitoring System
  23. 23. Debris flow – scenario <ul><li>A debris flow is a fast moving mass of unconsolidated, </li></ul><ul><li>saturated debris that looks like flowing concrete. </li></ul><ul><li>Based on existing debris flow monitoring system </li></ul><ul><li>(proprietary and monolithic software infrastructure) </li></ul><ul><li>in Taiwan (running since 2003). </li></ul><ul><li>Develop and implement open (OGC) standards-based </li></ul><ul><li>service oriented architecture (SOA) for debris flow </li></ul><ul><li>monitoring. </li></ul>
  24. 24. Debris flow - scenario
  25. 25. Debris flow – sensors and geo-processing <ul><li>Landslides and flooding are a threat on the mountainous </li></ul><ul><li>island of Taiwan, due to typhoons and earthquakes. </li></ul><ul><li>The Geographic Information Systems Research Center, </li></ul><ul><li>Feng Chia University (GIS.FCU) in Taiwan has implemented </li></ul><ul><li>OGC services for use in workflow, detecting and analyzing </li></ul><ul><li>sensor data for emergency response. </li></ul><ul><li>There is a demonstration showing the working network of </li></ul><ul><li>debris flow sensors and examples of distributed services </li></ul><ul><li>performing analysis and processing the sensor data. </li></ul>
  26. 26. Debris flow monitoring system
  27. 27. Debris flow monitoring system
  28. 28. Debris flow monitoring system
  29. 29. Debris flow monitoring system
  30. 30. Debris flow operational scenario
  31. 31. Grid-enabled WPS from IfGI
  32. 32. Encapsulation vs. integration Integration requires a WSRF binding for WPS
  33. 33. Encapsulation vs. Integration
  34. 34. GEOSS AIP-2 flood prediction and response Led by NASA, Spot Image, Northrop Grumman, ERDAS From portal select desired theme and area of interest Wizard picks appropriate workflow for desired result Wizard Mozambique Disaster Management Information System (DMIS) Workflows Estimated rainfall accumulation and flood prediction model Flood Model Selected workflow automatically activates needed assets and models Baseline water level, flood waters and predicted flooding
  35. 35. GEOSS AIP-2 biodiversity & climate change Led by CNR, Univ of Colorado, GBIF IP3 Client & Workflow engine IP3 Distributed Community Catalog/Mediator WCS - T Other Non-OGC Services GBIF Non-OGC Services OGC WPS Access to Model CSW GEOSS Portal WCS WFS req req req resp resp resp req req resp resp req resp req resp req resp Broker Research Scientist req resp
  36. 36. SWE and geo-processing workflow SOS ! SAS Sensor Net Mission Control Center Access & Processing Node WPS CSW Register Measurement Types SPS CSW SAS SOS
  37. 37. The power of workflow Workflows can be formally described as programmes that invoke Web services that invoke other Web services that invoke other Web services. Analytical models, decision support tools and other complex resources can quickly deliver results in this way and optionally, provide documentation of the steps. There is an OGC Workflow Domain Working Group: this is a forum for describing, discussing and providing best practice guidance related to geospatial workflows using existing IT workflow standards.
  38. 38. Contact me
  39. 39. Thanks for your attention