Mercurial > dive4elements > gnv-client

comparison doc/config-manual/generating_maps.tex @ 947:9a28846dfb9c

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Final QS for V1.0 doc/trunk@1091 c6561f87-3c4e-4783-a992-168aeb5c3f6f
author Hans Plum <hans.plum@intevation.de>
date Wed, 12 May 2010 11:35:25 +0000
parents dd6102eae823
children 975bb59bb136
comparison
equal deleted inserted replaced
946:dd6102eae823 947:9a28846dfb9c
23 \item Clipping the datasets along the passed polygon 23 \item Clipping the datasets along the passed polygon
24 \item Matching processed object data to the corresponding style 24 \item Matching processed object data to the corresponding style
25 \item Rendering requested map 25 \item Rendering requested map
26 \end{enumerate} 26 \end{enumerate}
27 27
28 %% FIXME: box it
29 In order to understand the configuration facilities for generating maps 28 In order to understand the configuration facilities for generating maps
30 in more detail, the internal 29 in more detail, the internal
31 interaction of the artifact-server and the mapserver is described below 30 interaction of the artifact-server and the mapserver is described below
32 for the use case when a user parameterizes a horizontal-cross-section 31 for the use case when a user parameterizes a horizontal-cross-section
33 profile and visualizes it as a map (without regarding the caching 32 profile and visualizes it as a map (without regarding the caching
38 requests the data from the database-backend and processes the data 37 requests the data from the database-backend and processes the data
39 (see above). 38 (see above).
40 39
41 \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 a ESRI
42 shapefile with (clipped) geometries, attribute data, projection 41 shapefile with (clipped) geometries, attribute data, projection
43 information and a special file storing meta information ({\tt 42 information and a special file storing meta information (\texttt{
44 meta.xml}) for this artifact in the a corresponding directory in the 43 meta.xml}) for this artifact in the a corresponding directory in the
45 {\tt shapefile-directory}. 44 \texttt{shapefile-directory}.
46 45
47 \item After that the so called {\tt map-generator} 46 \item After that the so called \texttt{map-generator}
48 is triggered. The map-generator searches the {\tt shape-directory} 47 is triggered. The map-generator searches the \texttt{shape-directory}
49 and its subfolders with all existing {\tt meta.xml} files and 48 and its subfolders with all existing \texttt{meta.xml} files and
50 generates a central configuration file for the mapserver at {\tt 49 generates a central configuration file for the mapserver at \texttt{
51 map-generator/mapfile@path}. Each shapefile will be published as a WMS 50 map-generator/mapfile@path}. Each shapefile will be published as a WMS
52 layer. \\ 51 layer. \\
53 The generated mapfile is constructed out of a base template from {\tt 52 The generated mapfile is constructed out of a base template from
53 \texttt{
54 map-generator/templates/maptemplate} and a parameter-/layer-specific 54 map-generator/templates/maptemplate} and a parameter-/layer-specific
55 part generated from {\tt map-generator/templates/path}. The 55 part generated from \texttt{map-generator/templates/path}. The
56 selection of the correct file-based templates is extracted out of 56 selection of the correct file-based templates is extracted out of
57 the {\tt meta.xml}-file. 57 the \texttt{meta.xml}-file.
58 58
59 \item The matching between the generated geograpic data and the corresponding 59 \item The matching between the generated geograpic data and the corresponding
60 style files is been done by the artifact-server, constructing 60 style files is been done by the artifact-server, constructing
61 filenames of maptemplates out of parameter-information. For 61 filenames of maptemplates out of parameter-information. For
62 horizontal-cross-sections the schema looks like this {\tt 62 horizontal-cross-sections the schema looks like this \texttt{
63 horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated 63 horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated
64 FIS like e.g. NAUTHIS and CONTIS like this {\tt 64 FIS like e.g. NAUTHIS and CONTIS like this \texttt{
65 layer\_\$ID\_MAPSERVICE\_\$ID\_LAYER} e.g. 65 layer\_\$ID\_MAPSERVICE\_\$ID\_LAYER} e.g.
66 {\tt layer\_BSH\_IMS\_CONTIS\_Resources\_2}. 66 \texttt{layer\_BSH\_IMS\_CONTIS\_Resources\_2}.
67 %% FIXME@TE: Marine Feature? Name of WMS? 67 %% FIXME@TE: Marine Feature? Name of WMS?
68 In order to set at least title, geometry-type and path to the 68 In order to set at least title, geometry-type and path to the
69 corresponding shapefile dynamically a templating language, called 69 corresponding shapefile dynamically a templating language, called
70 {\tt velocity} is used. 70 \texttt{velocity} is used.
71 71
72 \item The corresponding subfolder of an artifact in {\tt 72 \item The corresponding subfolder of an artifact in \texttt{
73 shape-directory} with their shapefiles 73 shape-directory} with their shapefiles
74 and {\tt meta.xml}-document will be deleted after the time of 74 and \texttt{meta.xml}-document will be deleted after the time of
75 expiry. By triggering the {\tt map-generator} the next time, the 75 expiry. By triggering the \texttt{map-generator} the next time, the
76 geographic data and the central configuration of the mapserver will 76 geographic data and the central configuration of the mapserver will
77 be updated. 77 be updated.
78 78
79 \end{enumerate} 79 \end{enumerate}
80 80
100 \begin{itemize} 100 \begin{itemize}
101 \item {\tt server}: URL of the mapserver where request can send to. 101 \item {\tt server}: URL of the mapserver where request can send to.
102 \end{itemize} 102 \end{itemize}
103 103
104 \paragraph*{velocity} 104 \paragraph*{velocity}
105 {\em Function}: Templating language used in the maptemplates at {\tt 105 {\em Function}: Templating language used in the maptemplates at \texttt{
106 map-generator/templates/path} for accessing the parameters from 106 map-generator/templates/path} for accessing the parameters from
107 dynamically generated {\tt meta.xml}-configuration of artifacts 107 dynamically generated \texttt{meta.xml}-configuration of artifacts.
108 108
109 \begin{itemize} 109 \begin{itemize}
110 \item {\tt logfile}: Setting the path to write log files. 110 \item {\tt logfile}: Setting the path to write log files.
111 Preconfigured to {\tt /var/log/artifacts/velocity.log}. {\bf Just 111 Preconfigured to \texttt{/var/log/artifacts/velocity.log}. {\bf Just
112 absolute pathes are allowed here!} 112 absolute pathes are allowed here!}
113 \end{itemize} 113 \end{itemize}
114 114
115 \paragraph*{map-generator} 115 \paragraph*{map-generator}
116 {\em Function}: Mechanism for generating configuration for the {\tt 116 {\em Function}: Mechanism for generating configuration for the {\tt
145 \item {\tt sample}: The attribute {\tt number} sets the number of 145 \item {\tt sample}: The attribute {\tt number} sets the number of
146 steps for the interpolation grid. 146 steps for the interpolation grid.
147 \item {\tt ground}: {\tt interpolation} method for calculating the 147 \item {\tt ground}: {\tt interpolation} method for calculating the
148 interpolation from the last measured value in meshes against the seafloor. 148 interpolation from the last measured value in meshes against the seafloor.
149 Available methods are {\tt nearest-neighbor | bilinear | bicubic}. 149 Available methods are {\tt nearest-neighbor | bilinear | bicubic}.
150 %% FIXME: Could not find nn and bicubic in the code ...
151 \end{itemize} 150 \end{itemize}
http://dive4elements.wald.intevation.org