| | 1 | {{{ |
| | 2 | #!html |
| | 3 | |
| | 4 | <div class="zoo-default"> |
| | 5 | <div class="container"> |
| | 6 | <div class="col-xs-12 col-sm-2 col-lg-2 text-center"> |
| | 7 | <span class="zoo-title "><i class="fa fa-cogs bfs"></i></span> |
| | 8 | </div> |
| | 9 | <div class="col-xs-12 col-sm-12 col-lg-10 text-center"> |
| | 10 | <h1 class="section-heading">What is WPS ?</h1> |
| | 11 | <h2 class="sub-heading">Web Processing Service</h2> |
| | 12 | <div class="well well well-heading"> |
| | 13 | <p class="intnp">The <a href="http://opengeospatial.org" |
| | 14 | target="_blank">OpenGIS®</a> Web Processing Service |
| | 15 | (<a href="http://www.opengeospatial.org/standards/wps" target="_blank">WPS</a>) |
| | 16 | Interface Standard provides rules for standardizing inputs |
| | 17 | and outputs (requests and responses) for geospatial processing |
| | 18 | services. The standard also defines how a client can request the execution of a process, and how the output from the process is handled.</p> |
| | 19 | </div> |
| | 20 | </div> |
| | 21 | </div> |
| | 22 | </div> |
| | 23 | |
| | 24 | <div class="zoo-content"> |
| | 25 | <div class="container"> |
| | 26 | <div class="col-xs-12 col-sm-8 col-lg-8"> |
| | 27 | <h2 class="st">Overview</h2> |
| | 28 | <p class="sp"><b>WPS</b> defines a standardized interface that facilitates the |
| | 29 | publishing of geospatial processes, and the discovery and binding |
| | 30 | to those processes by client applications. 'Processes' include any algorithm, |
| | 31 | calculation or model that operates on spatially referenced |
| | 32 | data. 'Publishing' means making available machine readable binding |
| | 33 | information as well as human readable metadata that allows service |
| | 34 | discovery and use. </p> |
| | 35 | <p class="sp"><b>WPS</b> can be configured to offer any sort of GIS functionality to clients across a |
| | 36 | network, including access to pre-programmed calculations and/or computation models |
| | 37 | that operate on spatially referenced data. A WPS may offer calculations as simple as |
| | 38 | subtracting one set of spatially referenced numbers from another, or as complicated as an |
| | 39 | environnemntal model. The data required by the WPS can be delivered across a |
| | 40 | network, or available at the server.</p> |
| | 41 | |
| | 42 | <h2 class="st">OpenGIS® WPS 1.0.0 specification</h2> |
| | 43 | |
| | 44 | <p class="sp"> The <b>WPS</b> interface specification provides mechanisms to identify the spatially referenced data |
| | 45 | required by the calculation, initiate the calculation, and manage the output from the |
| | 46 | calculation so that the client can access it. This Web Processing Service is targeted at |
| | 47 | processing both vector and raster data.</p> |
| | 48 | <p class="sp"> The <b>WPS</b> specification is designed to allow a service provider to expose a web accessible |
| | 49 | process in a way that allows clients to input data and |
| | 50 | execute the process with no specialized knowledge of the underlying physical process |
| | 51 | interface or API. The WPS interface standardizes the way processes and their |
| | 52 | inputs/outputs are described, how a client can request the execution of a process, and how |
| | 53 | the output from a process is handled.</p> |
| | 54 | </div> |
| | 55 | |
| | 56 | <div class="col-xs-12 col-sm-4 col-lg-4"> |
| | 57 | <h2 class="ht">Resources</h2> |
| | 58 | <ul class="list-group list-group"> |
| | 59 | <li class="list-group-item list-group-item3"><a |
| | 60 | href="http://portal.opengeospatial.org/files/?artifact_id=24151" |
| | 61 | target="_blank"> |
| | 62 | <i class="fa fa-external-link"></i> OpenGIS® WPS 1.0.0 specification</a></li> |
| | 63 | <li class="list-group-item list-group-item3"><a href="http://schemas.opengis.net/wps/1.0.0/" |
| | 64 | target="_blank"><i class="fa fa-external-link"></i> WPS 1.0.0 schemas</a></li> |
| | 65 | <li class="list-group-item list-group-item3">Morbi leo risus</li> |
| | 66 | <li class="list-group-item list-group-item3">Porta ac consectetur ac</li> |
| | 67 | <li class="list-group-item list-group-item3">Vestibulum at eros</li> |
| | 68 | </ul> |
| | 69 | |
| | 70 | <div class="well well well-cont"> |
| | 71 | <img class="img-responsive" src="/img/zoo-landscape.png" /> |
| | 72 | </div> |
| | 73 | </div> |
| | 74 | |
| | 75 | |
| | 76 | </div> |
| | 77 | </div> |
| | 78 | |
| | 79 | <div class="bblock"> |
| | 80 | <h1 class="stw">WPS operations</h2> |
| | 81 | |
| | 82 | <div class="container"> |
| | 83 | <div class="col-xs-12 col-sm-4 col-lg-4 text-center"> |
| | 84 | <h2><i class="fa fa-list fa-1x"></i> GetCapabilities</h2> |
| | 85 | <div class="well well well-cont"> |
| | 86 | <p class="intnp">The <b>GetCapabilities</b> operation returns |
| | 87 | service-level metadata information.It provides the list of |
| | 88 | available processing services.</p> |
| | 89 | </div> |
| | 90 | <a href="#" class="btn btn-warning btn-lg">View example</a> |
| | 91 | </div> |
| | 92 | <div class="col-xs-12 col-sm-4 col-lg-4 text-center"> |
| | 93 | <h2><i class="fa fa-cog fa-1x"></i> DescribeProcess</h2> |
| | 94 | <div class="well well well-cont"> |
| | 95 | <p class="intnp">The <b>DescribeProcess</b> operation |
| | 96 | returns a description of a process, including its supported inputs and outputs</p> |
| | 97 | </div> |
| | 98 | <a href="#" class="btn btn-warning btn-lg">View example</a> |
| | 99 | </div> |
| | 100 | <div class="col-xs-12 col-sm-4 col-lg-4 text-center"> |
| | 101 | <h2><i class="fa fa-rocket fa-1x"></i> Execute</h2> |
| | 102 | <div class="well well well-cont"> |
| | 103 | <p class="intnp"> The <b>Execute</b> operation return the |
| | 104 | outputs produced by a process</p> |
| | 105 | </div> |
| | 106 | <a href="#" class="btn btn-warning btn-lg">View example</a> |
| | 107 | </div> |
| | 108 | </div> |
| | 109 | </div> |
| | 110 | |
| | 111 | }}} |