Changeset 904 for branches/prototype-v0/docs
- Timestamp:
- Apr 19, 2019, 4:33:36 PM (6 years ago)
- Location:
- branches/prototype-v0/docs
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/prototype-v0/docs/install/installation.rst
r809 r904 147 147 <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel/sql/schema.sql#L34>`_. 148 148 149 149 Metadata Database (Optional) 150 ***************************** 151 152 .. _zoo_create_metadb: 153 154 It is possible to use a PostgreSQL database to store metadata 155 information about WPS Services. This support is optional and require 156 to be activated by using the ``--with-metadb=yes`` option. 157 158 To create the database for storing the metadata informations about the 159 WPS Services, you may use the following command: 160 161 .. code:: 162 163 createdb zoo_metadb 164 psql zoo_metadb -f zoo-project/zoo-kernel/sql/zoo_collectiondb.sql 165 166 In case you want to convert an existing zcfg file then, you can use 167 the ``zcfg2sql`` tool from the command line. 150 168 151 169 YAML Support (Optional) … … 154 172 If ``yaml.h`` file is not found in your ``/usr/include`` directory and 155 173 ``libyaml.so`` is not found in ``/usr/lib``, a ``--with-yaml`` option 156 can be used to specify its location. For instance, if the heade er file174 can be used to specify its location. For instance, if the header file 157 175 lies in ``/usr/local/include`` and the shared library is located in 158 176 ``/usr/local/lib``, you may use the following command: -
branches/prototype-v0/docs/kernel/configuration.rst
r817 r904 94 94 service providers, e.g., shared libraries with service implementations 95 95 (the ``serviceProvider`` parameter in the service configuration (.zcfg) file). 96 * ``memory``: (Optional) can take the value ``load`` to ensure that 97 the value field of the inputs data will be filled by the ZOO-Kernel 98 or ``protected`` to have only the ``cache_file`` filled. 99 96 100 97 101 .. warning:: 98 102 The ``libPath`` parameter is currently only recognized by services implemented 99 103 in C/C++ or PHP, and may be moved to another section in future versions. 100 104 105 106 .. warning:: 107 Depending on the ``memory`` parameter the WPS Service will receive 108 different fields (``value`` or ``cache_file``). 109 101 110 In case you have activated the MapServer support, please refer to 102 111 :ref:`this specific section <kernel-mapserver-main.cfg>`. … … 264 273 hosts=localhost,127.0.0.1 265 274 275 Optionaly, you can also define the shared url(s), meaning that even if 276 the ressource requires authentication to be accessed, this 277 authentifcation won't be used to define the name for storing the 278 file. Hence, two user with different authentication will use the same 279 file as it is considerated as shared. You can find bellow a sample 280 security section containing the shared parameter. In this example, 281 every requests to access the coverage using the url defined in the 282 shared parameter (``myHost/cgi-bin/WCS_Server``) will be shared 283 between users. 284 285 .. code:: 286 287 [security] 288 attributes=Authorization,Cookie,User-Agent 289 hosts=localhost,127.0.0.1 290 shared=myHost/cgi-bin/WCS_Server 266 291 267 292 .. _zoo_activate_db_backend: … … 300 325 to setup the database. 301 326 327 328 Database section 329 ............................... 330 331 The database section allows to configure the ZOO-Kernel to access the 332 metadata information about WPS Services by using a PostgreSQL database 333 in addition to the zcfg files. 334 335 .. code-block:: guess 336 337 [metadb] 338 dbname=zoo_metadb 339 port=5432 340 user=username 341 host=127.0.0.1 342 type=PG 343 344 This will generate strings to be passed to GDAL to connect the 345 database server: 346 347 .. code-block:: guess 348 349 <type>:host=<host> port=<port> user=<user> dbname=<dbname> 350 351 352 With the previous database section, it will give the following: 353 354 .. code-block:: guess 355 356 PG:"dbname=zoo_metadb host=127.0.0.1 port=5432 user=username" 357 358 Please refer to this `section <zoo_create_metadb>`_ to learn how 359 to setup the database. 360 302 361 Include section 303 362 ............................... -
branches/prototype-v0/docs/kernel/index.rst
r725 r904 14 14 orfeotoolbox 15 15 sagagis 16 16 hpc -
branches/prototype-v0/docs/kernel/mapserver.rst
r752 r904 73 73 * `MapServer <http://mapserver/org>`__ version >= 6.0.1 74 74 75 First download the lastest zoo-kernel by checking out the svn. Use the following command from do the directory where your previously checked out (in this example we will use `` <PREV_SVN_CO>`` to design this directory).76 77 .. code-block:: guess 78 79 cd <PREV_SVN_CO>80 svn checkout http://svn.zoo-project.org/svn/trunk/zoo-kernel zoo-kernel-ms81 75 First download the lastest zoo-kernel by checking out the svn. Use the following command from do the directory where your previously checked out (in this example we will use ``$PREV_SVN_CO`` to design this directory). 76 77 .. code-block:: guess 78 79 svn checkout http://svn.zoo-project.org/svn/trunk/ $PREV_SVN_CO 80 cd $PREV_SVN_CO 81 82 82 Then uncompress the MapServer archive (ie. ``mapserver-6.0.1.tar.bz2``) into ``/tmp/zoo-ms-src``, and compile it using the following command: 83 83 … … 92 92 cp mapserv /usr/lib/cgi-bin 93 93 94 Once done, compile ZOO-Kernel with MapServer support from the `` <PREV_SVN_CO>`` directory, using the following command:95 96 .. code-block:: guess 97 98 cd zoo-kernel -ms94 Once done, compile ZOO-Kernel with MapServer support from the ``$PREV_SVN_CO`` directory, using the following command: 95 96 .. code-block:: guess 97 98 cd zoo-kernel 99 99 autoconf 100 100 ./configure --with-python --with-mapserver=/tmp/zoo-ms-src/mapserver-6.0.1 101 101 make 102 103 You can then copy the new ZOO-Kernel to ``/usr/lib/cgi-bin`` directory, as follow: 104 105 .. code-block:: guess 106 107 cp zoo_loader.cgi /usr/lib/cgi-bin 102 sudo make install 108 103 109 104 … … 119 114 dataPath = /var/www/temp/ 120 115 mapserverAddress=http://localhost/cgi-bin/mapserv 116 117 You can also add the following lines to the ``[main]`` section, in case 118 you want to use a default style for Polygon, Lines and Points vector 119 layer. 120 121 .. code-block:: guess 122 123 msStylePoly=STYLE COLOR 202 109 19 OUTLINECOLOR 105 105 105 WIDTH 3 END 124 msStyleLine=STYLE OUTLINECOLOR 202 109 19 WIDTH 3 END 125 msStylePoint=STYLE COLOR 202 109 19 OUTLINECOLOR 105 105 105 SYMBOL 0 SIZE 14 END 121 126 122 127 The ``dataPath`` directory is mandatory and must belong to the Apache user. … … 175 180 ************* 176 181 182 You have different options to define the style of the layer created 183 using the data returned by your service. 184 185 msStyle 186 +++++++ 187 177 188 The optional ``msStyle`` parameter can also be used to define a custom MapServer style block (used for vector datasource only), as follow: 178 189 … … 181 192 msStyle = STYLE COLOR 125 0 105 OUTLINECOLOR 0 0 0 WIDTH 3 END 182 193 183 If a WPS service outputs a one band raster file, then it is possible to add a ``msClassify`` parameter and set it to ``true`` in the output ComplexData ``<Default>`` or ``<Supported>`` nodes of its ``zcfg`` file. This allows ZOO-Kernel to use its own default style definitions in order to classify the raster using equivalent intervals. 184 185 .. code-block:: guess 186 187 msClassify = .... 194 msClassify 195 ++++++++++ 196 197 If a WPS service outputs a one band raster file, then it is possible 198 to add a ``msClassify`` parameter and set it to ``true`` in the output 199 ComplexData ``<Default>`` or ``<Supported>`` nodes of its zcfg 200 file. This allows ZOO-Kernel to use its own default style definitions 201 in order to classify the raster using equivalent intervals. 202 203 .. code-block:: guess 204 205 msClassify = true 206 207 208 msInclude 209 +++++++++ 210 211 In case you want to use another layer which use the result of your 212 service, for instance to produce a `heatmap 213 <https://mapserver.org/output/kerneldensity.html>`_, then you can use 214 the 215 ``msInclude`` and ``msLayer`` options in the output ``ComplexData`` 216 ``<Default>`` or ``<Supported>`` nodes of its zcfg file. You can see below an 217 example of use of this two options with the associated mapfile. 218 219 .. code-block:: guess 220 221 msInclude = /var/data/template.map 222 msLayer = heatmap 223 224 You can find below a sample ``/var/data/template.map``: 225 226 .. code-block:: guess 227 228 MAP 229 SIZE 1000 500 230 EXTENT -180 -90 180 90 231 NAME "test heat" 232 IMAGETYPE "png" 233 234 WEB 235 METADATA 236 "ows_srs" "epsg:4326 epsg:3857 epsg:900913" 237 "ows_enable_request" "*" 238 END # METADATA 239 END # WEB 240 241 PROJECTION 242 "+init=epsg:4326" 243 END # PROJECTION 244 245 LAYER 246 NAME "heatmap" # Corresponding to the msLayer defined 247 TYPE raster 248 CONNECTIONTYPE kerneldensity 249 CONNECTION "Result" 250 STATUS on 251 PROCESSING "RANGE_COLORSPACE=HSL" 252 PROCESSING "KERNELDENSITY_RADIUS=20" 253 PROCESSING "KERNELDENSITY_COMPUTE_BORDERS=ON" 254 PROCESSING "KERNELDENSITY_NORMALIZATION=AUTO" 255 OFFSITE 0 0 0 256 CLASS 257 STYLE 258 COLORRANGE "#0000ff00" "#0000ffff" 259 DATARANGE 0 32 260 END # STYLE 261 STYLE 262 COLORRANGE "#0000ffff" "#ff0000ff" 263 DATARANGE 32 255 264 END # STYLE 265 END # CLASS 266 END # LAYER 267 268 LAYER 269 NAME "points" 270 STATUS on 271 TYPE POINT 272 #DATA "/Library/WebServer/cache//ef76ee6642c1ea704e847e28120ba1ca.zca" 273 END # LAYER 274 END # MAPFILE 275 276 277 188 278 189 279 Example … … 216 306 useMapserver = true 217 307 asReference = true 218 msClassify = ....308 msClassify = true 219 309 </Supported> 220 310 -
branches/prototype-v0/docs/kernel/sagagis.rst
r725 r904 4 4 ====================== 5 5 6 `SAGA GIS <http:// orfeo-toolbox.org/otb/>`_ provides a comprehensive set of geoscientific methods and spatial algorithms. The optional SAGA GIS support is available since `ZOO-Project 1.5 <http://zoo-project.org>`__. It allows to execute the `SAGA Modules <http://www.saga-gis.org/saga_module_doc/2.1.4/index.html>`_ directly as ZOO WPS Services thanks to a :ref:`kernel_index` specific internal mechanism which is detailed in this section.6 `SAGA GIS <http://www.saga-gis.org/>`_ provides a comprehensive set of geoscientific methods and spatial algorithms. The optional SAGA GIS support is available since `ZOO-Project 1.5 <http://zoo-project.org>`__. It allows to execute the `SAGA Modules <http://www.saga-gis.org/saga_module_doc/2.1.4/index.html>`_ directly as ZOO WPS Services thanks to a :ref:`kernel_index` specific internal mechanism which is detailed in this section. 7 7 8 8 .. note:: 9 9 10 |saga| `SAGA GIS <http s://www.orfeo-toolbox.org>`__ is the System for Automated Geoscientific Analyses. Learn more on official `website <http://www.saga-gis.org/en/index.html>`__.10 |saga| `SAGA GIS <http://www.saga-gis.org/>`__ is the System for Automated Geoscientific Analyses. Learn more on official `website <http://www.saga-gis.org/en/index.html>`__. 11 11 12 12 … … 27 27 28 28 * latest `ZOO-Kernel <http://zoo-project.org/trac/browser/trunk/zoo-project/zoo-kernel>`_ trunk version 29 * SAGA GIS (`SAGA-GIS 2.1.4 <http://saga-gis.org>`_ ) 30 * libLAS-1.2 (`LibLAS-1.2 <https://github.com/libLAS/libLAS-1.2>`_ ) 29 * `SAGA GIS <http://saga-gis.org>`_ (7.2.0) 31 30 32 31 Installation steps 33 32 ........................... 34 33 35 .. Note:: These installation steps were successfully tested on Ubuntu 14.4 LTS 36 37 Download lastest ZOO-Kernel code from SVN. 38 39 .. code-block:: guess 40 41 svn checkout http://svn.zoo-project.org/svn/trunk/zoo-kernel zoo-kernel 42 43 Then compile ZOO-Kernel using the needed configuration options as shown bellow: 34 Compile ZOO-Kernel using the configuration options as shown bellow: 44 35 45 36 .. code-block:: guess … … 47 38 cd zoo-kernel 48 39 autoconf 49 ./configure --with-saga=/usr/local/ 40 ./configure --with-saga=/usr/local/ --with-saga-version=7 50 41 make 51 42 52 And copy the newly created zoo_loader.cgi to ``/usr/lib/cgi-bin`` : 53 43 And copy the newly created zoo_loader.cgi to ``/usr/lib/cgi-bin``. 44 45 .. note:: 46 47 The ``--with-saga-version`` option let you set the major 48 version number of SAGA-GIS. 49 54 50 .. code-block:: guess 55 51 … … 62 58 **************************** 63 59 64 Building the `saga2zcfg 65 <http://zoo-project.org/trac/browser/trunk/thirds/otb2zcfg >`_ utility is required to activate the available SAGA-GIS Modules as WPS Services. This can be done using the following command: 60 Building the 61 `saga2zcfg <http://zoo-project.org/trac/browser/trunk/thirds/saga2zcfg>`_ 62 utility is required to activate the available SAGA-GIS Modules as WPS 63 Services. This can be done using the following command: 66 64 67 65 .. code-block:: guess
Note: See TracChangeset
for help on using the changeset viewer.