| 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-users bfs"></i></span> |
| 8 | </div> |
| 9 | <div class="col-xs-12 col-sm-12 col-lg-10 text-center"> |
| 10 | <h1 class="section-heading">ZOO Tribe</h1> |
| 11 | <h2 class="sub-heading">Web Processing Service</h2> |
| 12 | <div class="well well well-heading"> |
| 13 | <p class="intnp">The </p> |
| 14 | </div> |
| 15 | </div> |
| 16 | </div> |
| 17 | </div> |
| 18 | |
| 19 | <div class="zoo-content"> |
| 20 | <div class="container"> |
| 21 | <div class="col-xs-12 col-sm-8 col-lg-8"> |
| 22 | <h2 class="st">Overview</h2> |
| 23 | <p class="sp"><b>WPS</b> defines a standardized interface that facilitates the |
| 24 | publishing of geospatial processes, and the discovery and binding |
| 25 | to those processes by client applications. 'Processes' include any algorithm, |
| 26 | calculation or model that operates on spatially referenced |
| 27 | data. 'Publishing' means making available machine readable binding |
| 28 | information as well as human readable metadata that allows service |
| 29 | discovery and use. </p> |
| 30 | <p class="sp"><b>WPS</b> can be configured to offer any sort of GIS functionality to clients across a |
| 31 | network, including access to pre-programmed calculations and/or computation models |
| 32 | that operate on spatially referenced data. A WPS may offer calculations as simple as |
| 33 | subtracting one set of spatially referenced numbers from another, or as complicated as an |
| 34 | environnemntal model. The data required by the WPS can be delivered across a |
| 35 | network, or available at the server.</p> |
| 36 | |
| 37 | <h2 class="st">OpenGIS® WPS 1.0.0 specification</h2> |
| 38 | |
| 39 | <p class="sp"> The <b>WPS</b> interface specification provides mechanisms to identify the spatially referenced data |
| 40 | required by the calculation, initiate the calculation, and manage the output from the |
| 41 | calculation so that the client can access it. This Web Processing Service is targeted at |
| 42 | processing both vector and raster data.</p> |
| 43 | <p class="sp"> The <b>WPS</b> specification is designed to allow a service provider to expose a web accessible |
| 44 | process in a way that allows clients to input data and |
| 45 | execute the process with no specialized knowledge of the underlying physical process |
| 46 | interface or API. The WPS interface standardizes the way processes and their |
| 47 | inputs/outputs are described, how a client can request the execution of a process, and how |
| 48 | the output from a process is handled.</p> |
| 49 | </div> |
| 50 | |
| 51 | <div class="col-xs-12 col-sm-4 col-lg-4"> |
| 52 | <h2 class="ht">Resources</h2> |
| 53 | <ul class="list-group list-group"> |
| 54 | <li class="list-group-item list-group-item3"><a |
| 55 | href="http://portal.opengeospatial.org/files/?artifact_id=24151" |
| 56 | target="_blank"> |
| 57 | <i class="fa fa-external-link"></i> OpenGIS® WPS 1.0.0 specification</a></li> |
| 58 | <li class="list-group-item list-group-item3"><a href="http://schemas.opengis.net/wps/1.0.0/" |
| 59 | target="_blank"><i class="fa fa-external-link"></i> WPS 1.0.0 schemas</a></li> |
| 60 | <li class="list-group-item list-group-item3">Morbi leo risus</li> |
| 61 | <li class="list-group-item list-group-item3">Porta ac consectetur ac</li> |
| 62 | <li class="list-group-item list-group-item3">Vestibulum at eros</li> |
| 63 | </ul> |
| 64 | |
| 65 | <div class="well well well-cont"> |
| 66 | <img class="img-responsive" src="/img/zoo-landscape.png" /> |
| 67 | </div> |
| 68 | </div> |
| 69 | |
| 70 | |
| 71 | </div> |
| 72 | </div> |
| 73 | |
| 74 | <div class="bblock"> |
| 75 | <h1 class="stw">WPS operations</h2> |
| 76 | |
| 77 | <div class="container"> |
| 78 | <div class="col-xs-12 col-sm-4 col-lg-4 text-center"> |
| 79 | |
| 80 | </div> |
| 81 | </div> |
| 82 | </div> |
| 83 | |
| 84 | }}} |