Changeset 679 for branches/PublicaMundi_David-devel/docs/kernel/what.rst
- Timestamp:
- Jun 22, 2015, 10:07:47 AM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/PublicaMundi_David-devel/docs/kernel/what.rst
r663 r679 9 9 ZOO-Kernel is the heart of the `ZOO-Project <http://zoo-project.org>`_ WPS platform. It is a WPS compliant implementation written in C language which provides a powerful and extensible WPS server. 10 10 11 ZOO-Kernel implements and complies with the `WPS 1.0.0 <http://www.opengeospatial.org/standards/wps/>`_ standard edited by the `Open Geospatial Consortium <http://www.opengeospatial.org/>`_. It is able to perform the WPS operations as indicated in the OpenGIS |reg| specification, as listed bellow: 11 ZOO-Kernel is an extensible WPS server that makes your system more powerful. It provides a full-featured processing engine which runs on Linux, Mac OSX |trade| and Windows |trade| operating 12 systems. ZOO-Kernel is a CGI program which works on common web servers (namely `Apache <http://httpd.apache.org/>`_ or `IIS <http://www.iis.net/>`_ |trade|). It can be seamlessly integrated to new or existing web platforms. 13 14 ZOO-Kernel lets you process geospatial or non geospatial data using well formed WPS requests. The WPS server is able to manage and chain WPS Services (see ZOO-Services for examples) by loading dynamic libraries and source code written in different programming languages. 15 16 First class WPS server 17 ----------------------- 18 19 Compliant 20 ........................................................ 21 22 ZOO-Kernel implements and complies with the `WPS 1.0.0 <http://www.opengeospatial.org/standards/wps/>`_ and the `WPS 2.0.0 <http://www.opengeospatial.org/standards/wps/>`_ standards edited by the `Open Geospatial Consortium <http://www.opengeospatial.org/>`_. It is able to perform the WPS operations as indicated in the OpenGIS |reg| specification, as listed bellow: 12 23 13 24 * **GetCapablities**: Returns service-level metadata information.It provides the list of available processing services. … … 15 26 * **Execute**: Launches computation and returns the output produced by a particular process. 16 27 28 ZOO-Kernel compliancy can be tested using tools such as the WPS Test Suite provided by the `OGC compliancy program <http://cite.opengeospatial.org/>`_ or `XMLint <http://xmlsoft.org/xmllint.html/>`_. 17 29 18 First class WPS server 19 ----------------------- 20 21 ZOO-Kernel is an extensible WPS server that makes your system more powerful. It provides a full-featured processing engine which runs on Linux, Mac OSX |trade| and Windows |trade| operating systems. ZOO-Kernel is a CGI program which works on common web servers (namely `Apache <http://httpd.apache.org/>`_ or `IIS <http://www.iis.net/>`_ |trade|). It can be seamlessly integrated to new or existing web platforms. 22 23 ZOO-Kernel lets you process geospatial or non geospatial data using well formed WPS requests. The WPS server is able to manage and chain WPS Services (see ZOO-Services for examples) by loading dynamic libraries and source code written in different programming languages. 24 25 Supported programming languages 30 Polyglot 26 31 ........................................................ 27 32 28 ZOO-Kernel is a **polyglot**. The software is written in a valid form of multiple programming languages, which performs the same operations independent of the programming language used to compile or interpret it. 29 33 ZOO-Kernel is a **polyglot**. The software is written in a valid form 34 of multiple programming languages, which performs the same operations 35 independent of the programming language used to compile or interpret 36 it. The supported programming languages are listed bellow: 30 37 31 38 ============ =================== ========================= ============ … … 49 56 50 57 58 Scalable 59 ........................................................ 51 60 61 ZOO-Kernel can **scale** to large infrastructures involving high 62 numbers of (concurrent) WPS requests and/or huge amounts of 63 input/output. 52 64 65 ... 66 . 53 67
Note: See TracChangeset
for help on using the changeset viewer.