Mercurial > dive4elements > gnv-client

comparison doc/config-manual/model_of_transitions.tex @ 934:c2ce233cd9cf

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Answerd Questions and increase some Sections of the Documentation doc/trunk@1075 c6561f87-3c4e-4783-a992-168aeb5c3f6f
author Tim Englich <tim.englich@intevation.de>
date Fri, 07 May 2010 08:23:18 +0000
parents 4615bc4dc822
children 14df4bcabc3c
comparison
equal deleted inserted replaced
933:d7ec35e1b0a1 934:c2ce233cd9cf
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 The Localization is located in Module gnv-artifacts in Folder
252 src/main/resources.
252 \item data-multiselect: true it is possible to select 1 or more Items. 253 \item data-multiselect: true it is possible to select 1 or more Items.
253 false it is possible to select only one Item. 254 false it is possible to select only one Item.
254 \item inputvalues: The Values which can be "feed" to this State and which 255 \item inputvalues: The Values which can be "feed" to this State and which
255 will be used as Values in SQL-statements. 256 will be used as Values in SQL-statements.
256 \end{itemize} 257 \end{itemize}
286 State which was visited before. 287 State which was visited before.
287 \item type: The type of the Value. This is required for the Validation 288 \item type: The type of the Value. This is required for the Validation
288 of the Value. 289 of the Value.
289 This might be String, Integer, Double, Date, Point, LineString, 290 This might be String, Integer, Double, Date, Point, LineString,
290 Polygon, Coordinate, Geometry and AttributeName. 291 Polygon, Coordinate, Geometry and AttributeName.
291 %% FIXME HP: Explain Coordinate, AttributeName 292 Coordinate is a Format which accepts Geographical Coodinates in
293 the following Syntax: 56n30 6e20
294 AttributeName marks a StringValue which will be used in
295 SQL-Statement without surrounding with "'" in the Statement.
296 Usage is e.g. for determining the Axis (i or j) in the Workflow
297 of HorizontalProfiles.
292 \item multiselect: true if more than on Value can be feed or put into the SQL-statement. 298 \item multiselect: true if more than on Value can be feed or put into the SQL-statement.
293 false if one on Value will be accepted. 299 false if one on Value will be accepted.
294 \item usedinquery: Number how often the value should be put into the SQL-Statement: 300 \item usedinquery: Number how often the value should be put into the SQL-Statement:
295 0: Value will not out into the Statement. 301 0: Value will not out into the Statement.
296 1: Value will put once into the Statement, 302 1: Value will put once into the Statement,
299 Inner-Selects are used) 305 Inner-Selects are used)
300 \end{itemize} 306 \end{itemize}
301 307
302 The next part will explain the usage of inputvalues. 308 The next part will explain the usage of inputvalues.
303 309
304 This SQL-statement is configured to use in the State above. 310 This SQL-statement is configured to use in the State above, which will fetch
305 311 all ParameterIDs with the according german name which are reffered to the given
306 %% FIXME HP: What do we expect with this statement? Whats the result? 312 TimeSeriesPoint (e.g.Arkona Basin Buoy FeatureID = 100011 )
313
314
307 \begin{lstlisting} 315 \begin{lstlisting}
308 SELECT DISTINCT 316 SELECT DISTINCT
309 p.PARAMETERID KEY, 317 p.PARAMETERID KEY,
310 p.GERMANNAME || ' ['|| p.UNIT ||']' VALUE, 318 p.GERMANNAME || ' ['|| p.UNIT ||']' VALUE,
311 p.GERMANNAME 319 p.GERMANNAME
321 TSP.FEATUREID = ? 329 TSP.FEATUREID = ?
322 ORDER BY P.GERMANNAME 330 ORDER BY P.GERMANNAME
323 \end{lstlisting} 331 \end{lstlisting}
324 332
325 If there are put the Inputvalues in it it will look like this 333 If there are put the Inputvalues in it it will look like this
326 if we assume that the inputvalues has got the following values: 334 if we assume that the inputvalues has got the following values
327 \begin{itemize} 335 which where feed by choosing this FIS (fisname) and the Station
328 \item featureid: 4 (Marnet) 336 (featureid: Arkona Basin Buoy ):
337 \begin{itemize}
338 \item featureid: 100011 (Marnet ==> Arkona Basin Buoy)
329 \item fisname: fis\_marnet 339 \item fisname: fis\_marnet
330 %% FIXME HP: Where does these values come from? Do not get the context, sense here.
331 \item parameterid: not set because it's the value that should be 340 \item parameterid: not set because it's the value that should be
332 chosen in this state. 341 chosen in this state.
333 \end{itemize} 342 \end{itemize}
334 343
335 \begin{lstlisting} 344 \begin{lstlisting}
344 MEDIAN.TIMESERIESPOINT TSP 353 MEDIAN.TIMESERIESPOINT TSP
345 WHERE M.FEATUREID = TSP.FEATUREID AND 354 WHERE M.FEATUREID = TSP.FEATUREID AND
346 M.MEASUREMENTID = TSV.MEASUREMENTID AND 355 M.MEASUREMENTID = TSV.MEASUREMENTID AND
347 TS.TIMESERIESID = TSV.TIMESERIESID AND 356 TS.TIMESERIESID = TSV.TIMESERIESID AND
348 P.PARAMETERID = TS.PARAMETERID AND 357 P.PARAMETERID = TS.PARAMETERID AND
349 TSP.FEATUREID = 4 358 TSP.FEATUREID = 100011
350 ORDER BY P.GERMANNAME 359 ORDER BY P.GERMANNAME
351 \end{lstlisting} 360 \end{lstlisting}
352 361
353 The value of featureid will be inserted into the Query because 362 The value of featureid will be inserted into the Query because
354 the Attribute usedinquery is set to "1". 363 the Attribute usedinquery is set to "1".
379 This SQL-statement will be modified to 388 This SQL-statement will be modified to
380 389
381 \begin{lstlisting} 390 \begin{lstlisting}
382 SELECT DISTINCT 391 SELECT DISTINCT
383 ... 392 ...
384 TSP.FEATUREID = 4 AND 393 TSP.FEATUREID = 100011 AND
385 TSP.FEATUREID = 4 394 TSP.FEATUREID = 100011
386 ORDER BY P.GERMANNAME 395 ORDER BY P.GERMANNAME
387 \end{lstlisting} 396 \end{lstlisting}
388 397
389 398
390 If the Attribute usedinquery of the inputvalue fisname additionally is set to "1" 399 At the next Step of the Workflow it is nessesary to determine all depths where
391 this might happen. 400 the choosen parameters are meaured.
401 To do this we might have the following InputValues:
392 402
393 \begin{lstlisting} 403 \begin{lstlisting}
394 <inputvalues> 404 <inputvalues>
395 <inputvalue name="featureid" type="Integer" multiselect="false" usedinquery="2"/> 405 <inputvalue name="featureid" type="Integer" multiselect="false" usedinquery="2"/>
396 <inputvalue name="fisname" type="String" multiselect="false" usedinquery="1"/> 406 <inputvalue name="fisname" type="String" multiselect="false" usedinquery="0"/>
397 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="0"/> 407 <inputvalue name="parameterid" type="Integer" multiselect="true" usedinquery="1"/>
408 <inputvalue name="measurementid" type="Integer" multiselect="true" usedinquery="0"/>
398 </inputvalues> 409 </inputvalues>
399 \end{lstlisting} 410 \end{lstlisting}
400 411
401 412 \begin{itemize}
402 %% FIXME HP: For the fisname, we get NOCOLUMNINDB? Why? Better to take an existing/real example ... 413 \item featureid: 100011 (Marnet ==> Arkona Basin Buoy)
403 \begin{lstlisting} 414 \item fisname: fis\_marnet
404 SELECT DISTINCT 415 \item parameterid: 2 (Salzgehalt [pSal])
405 ... 416 \item measurementid: not set because it's the value that should be
406 TSP.FEATUREID = ? AND 417 chosen in this state.
407 TSP.FEATUREID = ? AND 418 \end{itemize}
408 NOCOLUMNINDB = ? 419
409 ORDER BY P.GERMANNAME 420 \begin{lstlisting}
421 SELECT DISTINCT
422 M.MEASUREMENTID KEY,
423 M.ZLOCATION VALUE,
424 P.PARAMETERID PARAMETERID
425 FROM MEDIAN.MEASUREMENT M,
426 MEDIAN.TIMESERIESVALUE TSV,
427 MEDIAN.TIMESERIES T,
428 MEDIAN.PARAMETER P
429 WHERE M.MEASUREMENTID = TSV.MEASUREMENTID AND
430 TSV.TIMESERIESID = T.TIMESERIESID AND
431 T.PARAMETERID = P.PARAMETERID AND
432 M.FEATUREID = ? AND
433 M.FEATUREID = ? AND
434 P.PARAMETERID IN (?)
435 ORDER BY m.ZLOCATION DESC
410 \end{lstlisting} 436 \end{lstlisting}
411 437
412 This SQL-statement will be modified to 438 This SQL-statement will be modified to
413 439
414 \begin{lstlisting} 440 \begin{lstlisting}
415 SELECT DISTINCT 441 SELECT DISTINCT
416 ... 442 M.MEASUREMENTID KEY,
417 TSP.FEATUREID = 4 AND 443 M.ZLOCATION VALUE,
418 TSP.FEATUREID = 4 AND 444 P.PARAMETERID PARAMETERID
419 NOCOLUMNINDB = 'fis\_marnet' 445 FROM MEDIAN.MEASUREMENT M,
420 ORDER BY P.GERMANNAME 446 MEDIAN.TIMESERIESVALUE TSV,
447 MEDIAN.TIMESERIES T,
448 MEDIAN.PARAMETER P
449 WHERE M.MEASUREMENTID = TSV.MEASUREMENTID AND
450 TSV.TIMESERIESID = T.TIMESERIESID AND
451 T.PARAMETERID = P.PARAMETERID AND
452 M.FEATUREID = 100011 AND
453 M.FEATUREID = 100011 AND
454 P.PARAMETERID IN (2)
455 ORDER BY m.ZLOCATION DESC
421 \end{lstlisting} 456 \end{lstlisting}
422 457
423 458
424 \paragraph{Transitions} 459 \paragraph{Transitions}
425 460
446 \begin{itemize} 481 \begin{itemize}
447 \item from: The ID of the State which you have to come from 482 \item from: The ID of the State which you have to come from
448 \item to: The ID of the State which can be reached. 483 \item to: The ID of the State which can be reached.
449 \item condition: The Condition which have to be fulfilled. 484 \item condition: The Condition which have to be fulfilled.
450 \end{itemize} 485 \end{itemize}
451 %% FIXME: What type of conditions do exist? 486
487 At this Moment only EQUAL and NOTEQUAL are supported as condition for an
488 ValueCompareTransition.
452 489
453 \paragraph{Outputstate} 490 \paragraph{Outputstate}
454 491
455 The OutputState is an special State which was created to define 492 The OutputState is an special State which was created to define
456 the different possibilities of Outputs for each Product. 493 the different possibilities of Outputs for each Product.
463 500
464 \begin{itemize} 501 \begin{itemize}
465 \item TimeSeries: TimeSeriesOutputState 502 \item TimeSeries: TimeSeriesOutputState
466 \item Horizontalprofile: HorizontalProfileOutputState 503 \item Horizontalprofile: HorizontalProfileOutputState
467 \item Horizontalprofile on Meshes: HorizontalProfileMeshOutputState 504 \item Horizontalprofile on Meshes: HorizontalProfileMeshOutputState
468 %% FIXME HP: Whats the reason for this split up? Horizontale Schnittprofile? Explain orally.
469 \item Verticalcrosssection:VerticalCrossSectionOutputState 505 \item Verticalcrosssection:VerticalCrossSectionOutputState
470 \item Verticalprofiles: VerticalProfileOutputState 506 \item Verticalprofiles: VerticalProfileOutputState
471 \item Horizontalcrosssections: HorizontalCrossSectionMeshOutputState 507 \item Horizontalcrosssections: HorizontalCrossSectionMeshOutputState
472 \item Layer: LayerOutputState 508 \item Layer: LayerOutputState
473 \end{itemize} 509 \end{itemize}
http://dive4elements.wald.intevation.org