dive4elements/gnv-client: doc/config-manual/model_of

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

-:a0c54d4edbdf
+:4615bc4dc822
 \end{itemize}
 Within each of these files, the steps for gathering the values for the
 parameterisation are configured by defining states, transitions and outputs
 (c.f. \ref{ref:config-a-product}).  The definition of states, transitions and
-outputs reference the actual SQL-statements via identifier. The SQL-statements
+outputs reference the actual SQL-statements via an identifier. The SQL-statements
-are gathered in the file \verb+conf/queries.txt+.
+are gathered in the file \verb+conf/queries.properties+.
-\subsection{General principle of model of transitions}
+\subsection{Explaining the background of the XML configuration}
 It is possible to configure the GNV in many ways.
 It is possible to add or remove FIS, add or remove Products from a FIS or
 to manipulate the steps which must be gone until a product can be create
 a diagram or generate an CSV-Export.
 It is possible to configure several Artifactfactories.
 The Artifactfactories will be configured in the Section
 /artifact-database/artifact-factories of the Configurationfile.
 \begin{lstlisting}
-<artifact-factory name='fis\_marnet'
+<artifact-factory name='fis_NEWFISNAME'
 description='Factory to create an artifact to be used with the FIS NEWFISNAME'
 ttl='3600000'
 artifact='de.intevation.artifactdatabase.ProxyArtifact'>
 de.intevation.gnv.artifacts.GNVProductArtifactFactory
 </artifact-factory>
 The Artifacts are configured in the Section /artifact-database/artifacts of
 the Configurationfile.
 \begin{lstlisting}
-<artifact name='fis\_marnet'>
+<artifact name='fis_NEWFISNAME'>
 <products>
 ...
 </products>
 </artifact>
 \end{lstlisting}
 \item queryID: The ID of the Query which should be used to fetch the Data
 displayed in this state. All Queries are defined in the File
 conf/queries.properties
 \item dataname: The ID of the Data which will be displayed in this State.
 The ID will be use to localize the description of the Data.
+%% FIXME HP: Where are this localization files; a hint is enough
 \item data-multiselect: true it is possible to select 1 or more Items.
 false it is possible to select only one Item.
 \item inputvalues: The Values which can be "feed" to this State and which
 will be used as Values in SQL-statements.
 \end{itemize}
 State which was visited before.
 \item type: The type of the Value. This is required for the Validation
 of the Value.
 This might be String, Integer, Double, Date, Point, LineString,
 Polygon, Coordinate, Geometry and AttributeName.
+%% FIXME HP: Explain Coordinate, AttributeName
 \item multiselect: true if more than on Value can be feed or put into the SQL-statement.
 false if one on Value will be accepted.
 \item usedinquery: Number how often the value should be put into the SQL-Statement:
 0: Value will not out into the Statement.
 1: Value will put once into the Statement,
 The next part will explain the usage of inputvalues.
 This SQL-statement is configured to use in the State above.
+%% FIXME HP: What do we expect with this statement? Whats the result?
 \begin{lstlisting}
 SELECT DISTINCT
 p.PARAMETERID KEY,
 p.GERMANNAME || '  ['|| p.UNIT ||']' VALUE,
 p.GERMANNAME
 If there are put the Inputvalues in it it will look like this
 if we assume that the inputvalues has got the following values:
 \begin{itemize}
 \item featureid: 4 (Marnet)
 \item fisname: fis\_marnet
+%% FIXME HP: Where does these values come from? Do not get the context, sense here.
 \item parameterid: not set because it's the value that should be
 chosen in this state.
 \end{itemize}
 \begin{lstlisting}
 <inputvalue name="fisname" type="String" multiselect="false" usedinquery="0"/>
 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/>
 </inputvalues>
 \end{lstlisting}
 \begin{lstlisting}
 SELECT DISTINCT
 ...
 TSP.FEATUREID = ? AND
 TSP.FEATUREID = ?
 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/>
 </inputvalues>
 \end{lstlisting}
+%% FIXME HP: For the fisname, we get NOCOLUMNINDB? Why? Better to take an existing/real example ...
 \begin{lstlisting}
 SELECT DISTINCT
 ...
 TSP.FEATUREID = ? AND
 TSP.FEATUREID = ? AND
 \begin{itemize}
 \item from: The ID of the State which you have to come from
 \item to:   The ID of the State which can be reached.
 \item condition: The Condition which have to be fulfilled.
 \end{itemize}
+%% FIXME: What type of conditions do exist?
 \paragraph{Outputstate}
 The OutputState is an special State which was created to define
 the different possibilities of Outputs for each Product.
 \begin{itemize}
 \item TimeSeries: TimeSeriesOutputState
 \item Horizontalprofile: HorizontalProfileOutputState
 \item Horizontalprofile on Meshes: HorizontalProfileMeshOutputState
+%% FIXME HP: Whats the reason for this split up? Horizontale Schnittprofile? Explain orally.
 \item Verticalcrosssection:VerticalCrossSectionOutputState
 \item Verticalprofiles: VerticalProfileOutputState
 \item Horizontalcrosssections: HorizontalCrossSectionMeshOutputState
 \item Layer: LayerOutputState
 \end{itemize}

Mercurial > dive4elements > gnv-client

comparison doc/config-manual/model_of_transitions.tex @ 931:4615bc4dc822