Mercurial > dive4elements > gnv-client
comparison doc/config-manual/model_of_transitions.tex @ 931:4615bc4dc822
Added some FIXMEs where questions arose.
doc/trunk@1071 c6561f87-3c4e-4783-a992-168aeb5c3f6f
author | Hans Plum <hans.plum@intevation.de> |
---|---|
date | Fri, 07 May 2010 06:20:41 +0000 |
parents | 63bc0044ff72 |
children | c2ce233cd9cf |
comparison
equal
deleted
inserted
replaced
930:a0c54d4edbdf | 931:4615bc4dc822 |
---|---|
72 \end{itemize} | 72 \end{itemize} |
73 | 73 |
74 Within each of these files, the steps for gathering the values for the | 74 Within each of these files, the steps for gathering the values for the |
75 parameterisation are configured by defining states, transitions and outputs | 75 parameterisation are configured by defining states, transitions and outputs |
76 (c.f. \ref{ref:config-a-product}). The definition of states, transitions and | 76 (c.f. \ref{ref:config-a-product}). The definition of states, transitions and |
77 outputs reference the actual SQL-statements via identifier. The SQL-statements | 77 outputs reference the actual SQL-statements via an identifier. The SQL-statements |
78 are gathered in the file \verb+conf/queries.txt+. | 78 are gathered in the file \verb+conf/queries.properties+. |
79 | 79 |
80 | 80 |
81 \subsection{General principle of model of transitions} | 81 \subsection{Explaining the background of the XML configuration} |
82 | 82 |
83 It is possible to configure the GNV in many ways. | 83 It is possible to configure the GNV in many ways. |
84 It is possible to add or remove FIS, add or remove Products from a FIS or | 84 It is possible to add or remove FIS, add or remove Products from a FIS or |
85 to manipulate the steps which must be gone until a product can be create | 85 to manipulate the steps which must be gone until a product can be create |
86 a diagram or generate an CSV-Export. | 86 a diagram or generate an CSV-Export. |
101 It is possible to configure several Artifactfactories. | 101 It is possible to configure several Artifactfactories. |
102 The Artifactfactories will be configured in the Section | 102 The Artifactfactories will be configured in the Section |
103 /artifact-database/artifact-factories of the Configurationfile. | 103 /artifact-database/artifact-factories of the Configurationfile. |
104 | 104 |
105 \begin{lstlisting} | 105 \begin{lstlisting} |
106 <artifact-factory name='fis\_marnet' | 106 <artifact-factory name='fis_NEWFISNAME' |
107 description='Factory to create an artifact to be used with the FIS NEWFISNAME' | 107 description='Factory to create an artifact to be used with the FIS NEWFISNAME' |
108 ttl='3600000' | 108 ttl='3600000' |
109 artifact='de.intevation.artifactdatabase.ProxyArtifact'> | 109 artifact='de.intevation.artifactdatabase.ProxyArtifact'> |
110 de.intevation.gnv.artifacts.GNVProductArtifactFactory | 110 de.intevation.gnv.artifacts.GNVProductArtifactFactory |
111 </artifact-factory> | 111 </artifact-factory> |
153 | 153 |
154 The Artifacts are configured in the Section /artifact-database/artifacts of | 154 The Artifacts are configured in the Section /artifact-database/artifacts of |
155 the Configurationfile. | 155 the Configurationfile. |
156 | 156 |
157 \begin{lstlisting} | 157 \begin{lstlisting} |
158 <artifact name='fis\_marnet'> | 158 <artifact name='fis_NEWFISNAME'> |
159 <products> | 159 <products> |
160 ... | 160 ... |
161 </products> | 161 </products> |
162 </artifact> | 162 </artifact> |
163 \end{lstlisting} | 163 \end{lstlisting} |
246 \item queryID: The ID of the Query which should be used to fetch the Data | 246 \item queryID: The ID of the Query which should be used to fetch the Data |
247 displayed in this state. All Queries are defined in the File | 247 displayed in this state. All Queries are defined in the File |
248 conf/queries.properties | 248 conf/queries.properties |
249 \item dataname: The ID of the Data which will be displayed in this State. | 249 \item dataname: The ID of the Data which will be displayed in this State. |
250 The ID will be use to localize the description of the Data. | 250 The ID will be use to localize the description of the Data. |
251 %% FIXME HP: Where are this localization files; a hint is enough | |
251 \item data-multiselect: true it is possible to select 1 or more Items. | 252 \item data-multiselect: true it is possible to select 1 or more Items. |
252 false it is possible to select only one Item. | 253 false it is possible to select only one Item. |
253 \item inputvalues: The Values which can be "feed" to this State and which | 254 \item inputvalues: The Values which can be "feed" to this State and which |
254 will be used as Values in SQL-statements. | 255 will be used as Values in SQL-statements. |
255 \end{itemize} | 256 \end{itemize} |
285 State which was visited before. | 286 State which was visited before. |
286 \item type: The type of the Value. This is required for the Validation | 287 \item type: The type of the Value. This is required for the Validation |
287 of the Value. | 288 of the Value. |
288 This might be String, Integer, Double, Date, Point, LineString, | 289 This might be String, Integer, Double, Date, Point, LineString, |
289 Polygon, Coordinate, Geometry and AttributeName. | 290 Polygon, Coordinate, Geometry and AttributeName. |
291 %% FIXME HP: Explain Coordinate, AttributeName | |
290 \item multiselect: true if more than on Value can be feed or put into the SQL-statement. | 292 \item multiselect: true if more than on Value can be feed or put into the SQL-statement. |
291 false if one on Value will be accepted. | 293 false if one on Value will be accepted. |
292 \item usedinquery: Number how often the value should be put into the SQL-Statement: | 294 \item usedinquery: Number how often the value should be put into the SQL-Statement: |
293 0: Value will not out into the Statement. | 295 0: Value will not out into the Statement. |
294 1: Value will put once into the Statement, | 296 1: Value will put once into the Statement, |
299 | 301 |
300 The next part will explain the usage of inputvalues. | 302 The next part will explain the usage of inputvalues. |
301 | 303 |
302 This SQL-statement is configured to use in the State above. | 304 This SQL-statement is configured to use in the State above. |
303 | 305 |
306 %% FIXME HP: What do we expect with this statement? Whats the result? | |
304 \begin{lstlisting} | 307 \begin{lstlisting} |
305 SELECT DISTINCT | 308 SELECT DISTINCT |
306 p.PARAMETERID KEY, | 309 p.PARAMETERID KEY, |
307 p.GERMANNAME || ' ['|| p.UNIT ||']' VALUE, | 310 p.GERMANNAME || ' ['|| p.UNIT ||']' VALUE, |
308 p.GERMANNAME | 311 p.GERMANNAME |
322 If there are put the Inputvalues in it it will look like this | 325 If there are put the Inputvalues in it it will look like this |
323 if we assume that the inputvalues has got the following values: | 326 if we assume that the inputvalues has got the following values: |
324 \begin{itemize} | 327 \begin{itemize} |
325 \item featureid: 4 (Marnet) | 328 \item featureid: 4 (Marnet) |
326 \item fisname: fis\_marnet | 329 \item fisname: fis\_marnet |
330 %% FIXME HP: Where does these values come from? Do not get the context, sense here. | |
327 \item parameterid: not set because it's the value that should be | 331 \item parameterid: not set because it's the value that should be |
328 chosen in this state. | 332 chosen in this state. |
329 \end{itemize} | 333 \end{itemize} |
330 | 334 |
331 \begin{lstlisting} | 335 \begin{lstlisting} |
362 <inputvalue name="fisname" type="String" multiselect="false" usedinquery="0"/> | 366 <inputvalue name="fisname" type="String" multiselect="false" usedinquery="0"/> |
363 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/> | 367 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/> |
364 </inputvalues> | 368 </inputvalues> |
365 \end{lstlisting} | 369 \end{lstlisting} |
366 | 370 |
367 | |
368 \begin{lstlisting} | 371 \begin{lstlisting} |
369 SELECT DISTINCT | 372 SELECT DISTINCT |
370 ... | 373 ... |
371 TSP.FEATUREID = ? AND | 374 TSP.FEATUREID = ? AND |
372 TSP.FEATUREID = ? | 375 TSP.FEATUREID = ? |
394 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/> | 397 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/> |
395 </inputvalues> | 398 </inputvalues> |
396 \end{lstlisting} | 399 \end{lstlisting} |
397 | 400 |
398 | 401 |
402 %% FIXME HP: For the fisname, we get NOCOLUMNINDB? Why? Better to take an existing/real example ... | |
399 \begin{lstlisting} | 403 \begin{lstlisting} |
400 SELECT DISTINCT | 404 SELECT DISTINCT |
401 ... | 405 ... |
402 TSP.FEATUREID = ? AND | 406 TSP.FEATUREID = ? AND |
403 TSP.FEATUREID = ? AND | 407 TSP.FEATUREID = ? AND |
442 \begin{itemize} | 446 \begin{itemize} |
443 \item from: The ID of the State which you have to come from | 447 \item from: The ID of the State which you have to come from |
444 \item to: The ID of the State which can be reached. | 448 \item to: The ID of the State which can be reached. |
445 \item condition: The Condition which have to be fulfilled. | 449 \item condition: The Condition which have to be fulfilled. |
446 \end{itemize} | 450 \end{itemize} |
451 %% FIXME: What type of conditions do exist? | |
447 | 452 |
448 \paragraph{Outputstate} | 453 \paragraph{Outputstate} |
449 | 454 |
450 The OutputState is an special State which was created to define | 455 The OutputState is an special State which was created to define |
451 the different possibilities of Outputs for each Product. | 456 the different possibilities of Outputs for each Product. |
458 | 463 |
459 \begin{itemize} | 464 \begin{itemize} |
460 \item TimeSeries: TimeSeriesOutputState | 465 \item TimeSeries: TimeSeriesOutputState |
461 \item Horizontalprofile: HorizontalProfileOutputState | 466 \item Horizontalprofile: HorizontalProfileOutputState |
462 \item Horizontalprofile on Meshes: HorizontalProfileMeshOutputState | 467 \item Horizontalprofile on Meshes: HorizontalProfileMeshOutputState |
468 %% FIXME HP: Whats the reason for this split up? Horizontale Schnittprofile? Explain orally. | |
463 \item Verticalcrosssection:VerticalCrossSectionOutputState | 469 \item Verticalcrosssection:VerticalCrossSectionOutputState |
464 \item Verticalprofiles: VerticalProfileOutputState | 470 \item Verticalprofiles: VerticalProfileOutputState |
465 \item Horizontalcrosssections: HorizontalCrossSectionMeshOutputState | 471 \item Horizontalcrosssections: HorizontalCrossSectionMeshOutputState |
466 \item Layer: LayerOutputState | 472 \item Layer: LayerOutputState |
467 \end{itemize} | 473 \end{itemize} |