Umweltwissenschaften FR Geowissenschaften Professur f Geoinformationssysteme WPS 2

WPS 1. 0 • Has gained some attention • Recently also in the environmental

WPS 2. 0 – Components • • • Conceptual Model - Core (Native) Process

WPS 2. 0 – The core • Is a conceptual model • Formulates minimal

WPS 2. 0 – The core Castellón, June 2014 WPS 2. 0 Folie 5

WPS 2. 0 – The core • Requirements around • Service discovery • Service

WPS 2. 0 – Process Model • Process interface / signature • Descriptive elements

Process Model WPS 1. 0 Dataset A Input 1 Dataset B Dataset C Y=

Process Model WPS 2. 0 Ø Process (@Identifier, @Title, @Abstract, @keywords) Ø Input[0. .

Process Model WPS 2. 0 Castellón, June 2014 WPS 2. 0 Folie 10

Process Model WPS 2. 0 • More symmetry for inputs and outputs • Documentation

Data model for Process I/O generic Castellón, June 2014 pre-defined WPS 2. 0 Folie

Alien process models https: //openclipart. org/image/800 px/svg_to_png/184642/cyborg _alien_green. png (alien : = <not defined

Foreign process models • Idea triggered by Sensor. ML change request • Pupose: WPS

Common service operations • • • Castellón, June 2014 Get. Capabilities Describe. Process Execute

Status. Info • • • Castellón, June 2014 Job. ID Status (Running, Succ) Estimated

The scope for Process Profiles • Align the interfaces of different implementations • Align

Fundamental difference: Planar vs geodesic buffering Castellón, June 2014 WPS 2. 0 Folie 18

Concept What means „buffer“? OGC ® Copyright © 2013 Open Geospatial Consortium

Concept • ISO 19107 – Terms and definitions: buffer geometric object that contains all

(Be aware of alternate Bufffer concepts!) • Minkowski sum of a given set of

Workflow metadata and lineage Concept Roads Concept Buff‘d roads Buffer Intersection Affected parcels Parcels

Summary • Align the interfaces of different implementations • Align the behaviour of different

Slides: 30

Download presentation

Umweltwissenschaften, FR Geowissenschaften, Professur f. Geoinformationssysteme WPS 2. 0 developments and proposed features Matthias Müller Castellón, June 2014

WPS 1. 0 • Has gained some attention • Recently also in the environmental modeling domain • Long due overhaul (dates back to 2007) • Lot's of change requests accumulated • Lacks support for process cataloguing • … Castellón, June 2014 WPS 2. 0 Folie 2

WPS 2. 0 – Components • • • Conceptual Model - Core (Native) Process model / data model Support foreign process models Common Service operations Process profiles Castellón, June 2014 WPS 2. 0 Folie 3

WPS 2. 0 – The core • Is a conceptual model • Formulates minimal platform-independent requirements for a WPS • Can relized in many Distributed Computing Platforms / Architectures (SOA, REST, …) • (we lack an an abstract specification that describes basic concepts for data processing services) Castellón, June 2014 WPS 2. 0 Folie 4

WPS 2. 0 – The core Castellón, June 2014 WPS 2. 0 Folie 5

WPS 2. 0 – The core • Requirements around • Service discovery • Service capabilities • Abstract process model • Job control • Process execution • Data transmission by value / by reference • Job monitoring Castellón, June 2014 WPS 2. 0 Folie 6

WPS 2. 0 – Process Model • Process interface / signature • Descriptive elements • Data types Castellón, June 2014 WPS 2. 0 Folie 7

Process Model WPS 1. 0 Dataset A Input 1 Dataset B Dataset C Y= f(X) Output 1 Dataset G Output n Dataset H Input 2 Dataset D Dataset E Input n Dataset F Castellón, June 2014 WPS 2. 0 Folie 8

Process Model WPS 2. 0 Ø Process (@Identifier, @Title, @Abstract, @keywords) Ø Input[0. . *] Ø … Ø… Ø Output[1] Ø Output[1. . *] Ø … Ø Output[1] Castellón, June 2014 WPS 2. 0 Folie 9

Process Model WPS 2. 0 Castellón, June 2014 WPS 2. 0 Folie 10

Process Model WPS 2. 0 • More symmetry for inputs and outputs • Documentation links in metadata elements <ows: Metadata xlink: role="http: //www. opengis. net/spec/wps/2. 0/def/process/description/documentation" xlink: href="http: //my. wps. server/processes/proximity/Planar-Buffer. html#input_geometry"/> <ows: Metadata xlink: role="http: //www. opengis. net/spec/wps/2. 0/def/process/description/documentation" xlink: href="http: //some. host/profileregistry/implementation/Planar-GML-Buffer. html"/> Castellón, June 2014 WPS 2. 0 Folie 11

Data model for Process I/O generic Castellón, June 2014 pre-defined WPS 2. 0 Folie 12

Alien process models https: //openclipart. org/image/800 px/svg_to_png/184642/cyborg _alien_green. png (alien : = <not defined by WPS standard>)

Foreign process models • Idea triggered by Sensor. ML change request • Pupose: WPS protocol shall support other process models that have their own descriptive model and data types • Solution: Abstract minimum requirements for process models that shall be used in conjuction with WPS • Identifiers for processes, inputs, outputs • Well-defined data types • Cardinality contraints • … Castellón, June 2014 WPS 2. 0 Folie 14

Common service operations • • • Castellón, June 2014 Get. Capabilities Describe. Process Execute (mode=sync|async) Get. Status (async) Get. Result (async) Dismiss (extension) • Cancel / release running job • Release server-stored results WPS 2. 0 Folie 15

Status. Info • • • Castellón, June 2014 Job. ID Status (Running, Succ) Estimated completion Next. Poll Expiration date Percent completed WPS 2. 0 Folie 16

The scope for Process Profiles • Align the interfaces of different implementations • Align the behaviour of different implementations the signature (or interface) à Defines what goes in and comes out … Refers to the process mechanics The behaviour … Describes how the outputs are derived from the inputs … Defines the result quality Castellón, June 2014 WPS 2. 0 Folie 17

Fundamental difference: Planar vs geodesic buffering Castellón, June 2014 WPS 2. 0 Folie 18

Hierarchical profiling approach (Buffer) Concept Buffer Generic Profile Geodesic. Buffer Implementation Profile Geodesic. Buffer on Geo. JSON Process Implementation http: //my. process. geodesic-buffer OGC ® Copyright © 2013 Open Geospatial Consortium

Concept • ISO 19107 – Terms and definitions: buffer geometric object that contains all direct positions whose distance from a specified geometric object is less than or equal to a given distance • Put that definition & description on web location and assign HTTP-URI OGC ® Copyright © 2013 Open Geospatial Consortium

Generic Profile • Simple Planar Buffer Returns a geometry that represents all points whose distance from this Geometry is less than or equal to distance. Computations are performed in the coordinate system of this Geometry. Generic Profile Geodesic Buffer + Source. Geometry : 2 DGeometry + Distance: Double + Buffered. Geometry: 2 DGeometry OGC ® Copyright © 2013 Open Geospatial Consortium

Generic Profile • Simple Geodesic Buffer Returns a geometry that represents all points whose distance from this Geometry is less than or equal to distance. Calculations are always performed on the Spatial Reference System’s ellipsoid of this Geometry. Generic Profile Geodesic Buffer + Source. Geometry : 2 DGeometry + Distance: Linear Unit + Buffered. Geometry: 2 DGeometry OGC Similar interface except for the Linear Unit in <Distance> ® Copyright © 2013 Open Geospatial Consortium

Implementation Profile: data types Implementation Profile Geodesic. Buffer Geo. JSON + Source. Geometry: 2 DGeometry {Complex. Data; mimetype=application/json; schema=geojson} + Distance: Linear Unit {Literal. Data} + Buffered. Geometry: 2 DGeometry {Complex. Data; mimetype=application/json; schema=geojson} Implementation Profile Geodesic. Buffer Open. Street. Map + Source. Geometry: 2 DGeometry {Complex. Data; application/protobuf; schema=Osm. Schema-V 0. 6} + Distance: Linear Unit {Literal. Data} + Buffered. Geometry: 2 DGeometry {Complex. Data; application/protobuf; schema=Osm. Schema-V 0. 6} OGC ® Copyright © 2013 Open Geospatial Consortium

Implementation (and Extension) Implementation Profile Geodesic. Buffer Geo. JSON + Source. Geometry: 2 DGeometry {Complex. Data; mimetype=application/json; schema=geojson} + Distance: Linear Unit {Literal. Data} + Buffered. Geometry: 2 DGeometry {Complex. Data; mimetype=application/json; schema=geojson} Implementation Profile Geodesic. Buffer Open. Street. Map Extension A: implement multiple formats + Source. Geometry: 2 DGeometry {Complex. Data; application/protobuf; schema=Osm. Schema-V 0. 6} + Distance: Linear Unit {Literal. Data} + Buffered. Geometry: 2 DGeometry {Complex. Data; application/protobuf; schema=Osm. Schema-V 0. 6} Process Implementation http: //my. wps. process. geodesic-buffer + capstyle[0. . 1]: String {Literal. Data} Extension B: add optional parameters OGC ® Copyright © 2013 Open Geospatial Consortium

Workflow metadata and lineage Concept Roads Concept Buff‘d roads Buffer Intersection Affected parcels Parcels Dist. Generic Profile Planar Buffer Contract Document Planar Buffer Implementation Profile Planar. Buffer Geo. JSON Generally not required Process Implementation http: //my. wps. process. planar-buffer OGC ® Copyright © 2013 Open Geospatial Consortium

Summary • Align the interfaces of different implementations • Align the behaviour of different implementations • Provide a framework that addresses different levels of process similarity • Support cataloguing, search and retrieval tasks • Support lineage creation and handling OGC ® Copyright © 2013 Open Geospatial Consortium