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

WPS 1.0 WPS 2.0Folie 2 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 – Components Folie 3 Conceptual Model - Core (Native) Process model / data model Support for foreign process models Common Service operations Process profiles WPS 2.0Castellón, June 2014

WPS 2.0 – The core Folie 4 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) WPS 2.0Castellón, June 2014

WPS 2.0 – The core Folie 5WPS 2.0Castellón, June 2014

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

WPS 2.0 – Process Model Folie 7 Process interface / signature Descriptive elements Data types WPS 2.0Castellón, June 2014

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

Process Model WPS 2.0 Folie 9 @keywords)  Input[0..*]  …  Output[1]  Output[1..*]  …  Output[1] WPS 2.0Castellón, June 2014

Process Model WPS 2.0 Folie 10WPS 2.0Castellón, June 2014

Process Model WPS 2.0 Folie 11 More symmetry for inputs and outputs Documentation links in metadata elements WPS 2.0Castellón, June 2014

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

Alien process models _alien_green.png (alien := )

Foreign process models Folie 14 Idea triggered by SensorML 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 … WPS 2.0Castellón, June 2014

Common service operations Folie 15 GetCapabilities DescribeProcess Execute (mode=sync|async) GetStatus (async) GetResult (async) Dismiss (extension) Cancel / release running job Release server-stored results WPS 2.0Castellón, June 2014

StatusInfo Folie 16 JobID Status (Running, Succ) Estimated completion NextPoll Expiration date Percent completed WPS 2.0Castellón, June 2014

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

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

OGC ® Hierarchical profiling approach (Buffer) Copyright © 2013 Open Geospatial Consortium Concept Buffer Generic Profile GeodesicBuffer Implementation Profile GeodesicBuffer on GeoJSON Process Implementation

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

OGC ® Concept Copyright © 2013 Open Geospatial Consortium ISO – 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 ® (Be aware of alternate Bufffer concepts!) Minkowski sum of a given set of points with a disc-shaped (in 3D: spherical) point set. Copyright © 2013 Open Geospatial Consortium

OGC ® Generic Profile Copyright © 2013 Open Geospatial Consortium What is a suitable „buffer“ function for my analysis task?

OGC ® 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. Copyright © 2013 Open Geospatial Consortium Generic Profile Geodesic Buffer + SourceGeometry : 2DGeometry + Distance: Double + BufferedGeometry: 2DGeometry

OGC ® 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. Copyright © 2013 Open Geospatial Consortium Generic Profile Geodesic Buffer + SourceGeometry : 2DGeometry + Distance: Linear Unit + BufferedGeometry: 2DGeometry Similar interface except for the Linear Unit in

OGC ® Implementation Profile Copyright © 2013 Open Geospatial Consortium Buffer my OSM data!

OGC ® Implementation Profile: data types Copyright © 2013 Open Geospatial Consortium Implementation Profile GeodesicBuffer GeoJSON + SourceGeometry: 2DGeometry {ComplexData; mimetype=application/json; schema=geojson} + Distance: Linear Unit {LiteralData} + BufferedGeometry: 2DGeometry {ComplexData; mimetype=application/json; schema=geojson} Implementation Profile GeodesicBuffer OpenStreetMap + SourceGeometry: 2DGeometry {ComplexData; application/application/protobuf; schema=OsmSchema-V0.6} + Distance: Linear Unit {LiteralData} + BufferedGeometry: 2DGeometry {ComplexData; application/application/protobuf; schema=OsmSchema-V0.6}

OGC ® Implementation (and Extension) Copyright © 2013 Open Geospatial Consortium Process Implementation + capstyle[0..1]: String {LiteralData} Extension B: add optional parameters Implementation Profile GeodesicBuffer GeoJSON + SourceGeometry: 2DGeometry {ComplexData; mimetype=application/json; schema=geojson} + Distance: Linear Unit {LiteralData} + BufferedGeometry: 2DGeometry {ComplexData; mimetype=application/json; schema=geojson} Implementation Profile GeodesicBuffer OpenStreetMap + SourceGeometry: 2DGeometry {ComplexData; application/application/protobuf; schema=OsmSchema-V0.6} + Distance: Linear Unit {LiteralData} + BufferedGeometry: 2DGeometry {ComplexData; application/application/protobuf; schema=OsmSchema-V0.6} Extension A: implement multiple formats

OGC ® Workflow metadata and lineage Copyright © 2013 Open Geospatial Consortium Concept Buffer Roads Buff‘d roads Concept Intersection Affected parcels Contract Document Planar Buffer Generic Profile Planar Buffer Implementation Profile PlanarBuffer GeoJSON Process Implementation Generally not required Parcels Dist.

OGC ® 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 Copyright © 2013 Open Geospatial Consortium