Mercurial > dive4elements > gnv-client
comparison doc/config-manual/generating_maps.tex @ 948:975bb59bb136
Adapted config-manual according to admin-manual
doc/trunk@1092 c6561f87-3c4e-4783-a992-168aeb5c3f6f
| author | Hans Plum <hans.plum@intevation.de> |
|---|---|
| date | Wed, 12 May 2010 11:56:36 +0000 |
| parents | 9a28846dfb9c |
| children |
comparison
equal
deleted
inserted
replaced
| 947:9a28846dfb9c | 948:975bb59bb136 |
|---|---|
| 35 \begin{enumerate} | 35 \begin{enumerate} |
| 36 \item After finishing the parameterization, the artifact-server | 36 \item After finishing the parameterization, the artifact-server |
| 37 requests the data from the database-backend and processes the data | 37 requests the data from the database-backend and processes the data |
| 38 (see above). | 38 (see above). |
| 39 | 39 |
| 40 \item By requesting a map in the GNV-WebClient, the artifact-server writes a ESRI | 40 \item By requesting a map in the GNV-WebClient, the artifact-server writes |
| 41 shapefile with (clipped) geometries, attribute data, projection | 41 a ESRI shapefile with (clipped) geometries, attribute data, projection |
| 42 information and a special file storing meta information (\texttt{ | 42 information and a special file storing meta information (\texttt{meta.xml}) |
| 43 meta.xml}) for this artifact in the a corresponding directory in the | 43 for this artifact in the a corresponding directory in the |
| 44 \texttt{shapefile-directory}. | 44 \texttt{shapefile-directory}. |
| 45 | 45 |
| 46 \item After that the so called \texttt{map-generator} | 46 \item After that the so called \texttt{map-generator} is triggered. The |
| 47 is triggered. The map-generator searches the \texttt{shape-directory} | 47 map-generator searches the \texttt{shape-directory} and its subfolders with |
| 48 and its subfolders with all existing \texttt{meta.xml} files and | 48 all existing \texttt{meta.xml} files and generates a central configuration |
| 49 generates a central configuration file for the mapserver at \texttt{ | 49 file for the mapserver at \texttt{ map-generator/mapfile@path}. Each |
| 50 map-generator/mapfile@path}. Each shapefile will be published as a WMS | 50 shapefile will be published as a WMS layer. \\ |
| 51 layer. \\ | 51 The generated mapfile is constructed out of a base template from \texttt{ |
| 52 The generated mapfile is constructed out of a base template from | 52 map-generator/templates/maptemplate} and a parameter-/layer-specific part |
| 53 \texttt{ | 53 generated from \texttt{map-generator/templates/path}. The selection of the |
| 54 map-generator/templates/maptemplate} and a parameter-/layer-specific | 54 correct file-based templates is extracted out of the |
| 55 part generated from \texttt{map-generator/templates/path}. The | 55 \texttt{meta.xml}-file. |
| 56 selection of the correct file-based templates is extracted out of | |
| 57 the \texttt{meta.xml}-file. | |
| 58 | 56 |
| 59 \item The matching between the generated geograpic data and the corresponding | 57 \item The matching between the generated geograpic data and the |
| 60 style files is been done by the artifact-server, constructing | 58 corresponding style files is been done by the artifact-server, constructing |
| 61 filenames of maptemplates out of parameter-information. For | 59 filenames of maptemplates out of parameter-information. For |
| 62 horizontal-cross-sections the schema looks like this \texttt{ | 60 horizontal-cross-sections the schema looks like this \texttt{ |
| 63 horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated | 61 horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated FIS like |
| 64 FIS like e.g. NAUTHIS and CONTIS like this \texttt{ | 62 e.g. NAUTHIS and CONTIS like this \texttt{ |
| 65 layer\_\$ID\_MAPSERVICE\_\$ID\_LAYER} e.g. | 63 layer\_\$ID\_MAPSERVICE\_\$ID\_LAYER} e.g. |
| 66 \texttt{layer\_BSH\_IMS\_CONTIS\_Resources\_2}. | 64 \texttt{layer\_BSH\_IMS\_CONTIS\_Resources\_2}. |
| 67 %% FIXME@TE: Marine Feature? Name of WMS? | 65 %% FIXME@TE: Marine Feature? Name of WMS? |
| 68 In order to set at least title, geometry-type and path to the | 66 In order to set at least title, geometry-type and path to the |
| 69 corresponding shapefile dynamically a templating language, called | 67 corresponding shapefile dynamically a templating language, called |
| 100 \begin{itemize} | 98 \begin{itemize} |
| 101 \item {\tt server}: URL of the mapserver where request can send to. | 99 \item {\tt server}: URL of the mapserver where request can send to. |
| 102 \end{itemize} | 100 \end{itemize} |
| 103 | 101 |
| 104 \paragraph*{velocity} | 102 \paragraph*{velocity} |
| 105 {\em Function}: Templating language used in the maptemplates at \texttt{ | 103 {\em Function}: Templating language used in the maptemplates at |
| 106 map-generator/templates/path} for accessing the parameters from | 104 \texttt{map-generator/templates/path} for accessing the parameters from |
| 107 dynamically generated \texttt{meta.xml}-configuration of artifacts. | 105 dynamically generated \texttt{meta.xml}-configuration of artifacts. |
| 108 | 106 |
| 109 \begin{itemize} | 107 \begin{itemize} |
| 110 \item {\tt logfile}: Setting the path to write log files. | 108 \item {\tt logfile}: Setting the path to write log files. \\ |
| 111 Preconfigured to \texttt{/var/log/artifacts/velocity.log}. {\bf Just | 109 Preconfigured to \texttt{/var/log/artifacts/velocity.log}. |
| 110 {\bf Just | |
| 112 absolute pathes are allowed here!} | 111 absolute pathes are allowed here!} |
| 113 \end{itemize} | 112 \end{itemize} |
| 114 | 113 |
| 115 \paragraph*{map-generator} | 114 \paragraph*{map-generator} |
| 116 {\em Function}: Mechanism for generating configuration for the {\tt | 115 {\em Function}: Mechanism for generating configuration for the {\tt |