Page History

...

Related TAG: $TABLE(tableId)$

1. table: original table;
2. rowPerLocationHtmlTable: table with a row per location
3. htmlTable: new style table with same functionality as 'table';
4. countTables:
   1. thresholdsCrossingsTable: table containing numbers (count) of threshold crossings.
   2. thresholdsCrossingsCountTable: new thresholdsCrossingTable
   3. flagCountTable
   4. flagSourceCountTable
5. maximumStatusTable: table containing (coloured) indicating threshold crossings over time.
6. mergedPrecipitationTable: table containing (merged) precipitation figures in specific time intervals
7. systemStatusTable: tables containing system (management) information;
   1. liveSystemStatus: information about live system: MC and FSS('s);
   2. exportStatus: information about exported files/reports;
   3. importStatus: information about files imported;
   4. scheduledWorkflowStatus: information about (next) scheduled workflows;
   5. completedWorkflowStatus: information about number of workflows completed in last 24 hrs.
   6. currentForecastStatus: information about which workflows are set to CURRENT;
   7. logMessageListing list of logmessages (based on a query)

   8. forecastHistory: historic overview of forecasts.

Tables 3 to 7 have references to cascading style sheets.

table

See Table above

rowPerLocationHtmlTable

Anchor
rowPerLocationHtmlTable rowPerLocationHtmlTable

The rowPerLocationHtmlTable can be configured directly in <report> section, or in the <declarations> section and reffered from the <report> section. This table is a generic table type and contains for each configured location one row with several columns. The data displayed in a particular column are result of the function that is configured for that column.

...

<declarations>
	  <rowPerLocationHtmlTableFormat id="rowPerLocationFormat1" tableStyle="tableStyle3" >
  	   
  	   <column>
	  	<header>Naam</header>
	  	<format>_data_yellow</format>
		<function>LOCATIONATTRIBUTE(shortname)</function>
	    </column>
	   
	       <column>
	    	<header>Tijd maximale overschrijding</header>
	    	<function>THRESHOLDCROSSING(MAX_DATETIME;Qobserved;dateFormat1)</function>
	     </column>			            
	   
	      
	       <column>
	    	<header>Waarde maximale overschrijding (m3/s)</header>
	    	<function>THRESHOLDCROSSING(MAX_VALUE;Qobserved;numberFormat1)</function>
	     </column>			            

	     <column>
	     	 <header>Tijd maximale waterstand</header>
	         <function>MAXTIME(Hobserved;dateFormat1)</function>
	     </column>
	     
	     <column>
	     	 <header>Maximale waterstand (m)</header>
	         <function>MAXVALUE(Hobserved;numberFormat1)</function>
	     </column>
	     
	  </rowPerLocationHtmlTableFormat>
</declarations>

htmlTable

Anchor
htmlTable htmlTable

The htmlTable is the successor of the table described earlier. The configuration of this htmlTable is easier and more readable.

...

countTables

thresholdsCrossingsTable

Anchor
thresholdsCrossingsTable thresholdsCrossingsTable

...

Since this type of table is a table in which you can aggregate data (which means combine timeseries) the following option is available: mergeLocations.

thresholdCrossingCountsTable

Anchor
thresholdCrossingCountsTable thresholdCrossingCountsTable

A thresholdCrossingsCountsTable displays threshold crossing counts depending on which thresholds have been crossed within a given time period. The thresholdCrossingCountsTable is a new version of the thresholdsCrossingsTable. A thresholdCrossingCountsTable has the same layout as a thresholdCrossingCountsTab in the thresholdOverviewDisplay for consistency.

...

• id: identifier for the template tag (in this case: $TABLE(table1)$);
• formatId: reference to the format of this table (to one of the thresholdCrossingCountsTableFormats in the declarations section);
• mergeLocations: boolean indicator. True means: treat all locations of mentioned timeseries together for combined assessment. False means: extract individual timeseries so that every row indicates one location (timeseries);
• Choice between
  o timeSeries;
  o table; --> this can be used to display a table within another one.
  o tableRow

flagCountsTable

Anchor
flagCountsTable flagCountsTable

FlagCountsTable is available since Delft-FEWS release 2011.01. A FlagCountsTable displays flag counts depending on the flags of the values in a time series within a given time period.

...

<flagCountsTable id="flagCountsTable" formatId="flagCountsTableFormat">
	<inputVariableId>Cowbeech</inputVariableId>
	<inputVariableId>Romsey</inputVariableId>
	<inputVariableId>CrosslandsDrive</inputVariableId>
</flagCountsTable>

flagSourceCountsTable

Anchor
flagSourceCountsTable flagSourceCountsTable

FlagSourceCountsTable is available since Delft-FEWS release 2011.01. A FlagSourceCountsTable displays counts of flag sources depending on the flag sources of the values in a time series within a given time period. The flag source for a value contains the reason why that value got a certain flag. For example if a value was rejected by a "hard max" validation rule, then it gets flag unreliable and flag source "hard max".

...

<flagSourceCountsTable id="flagSourceCountsTable1" formatId="flagSourceCountsTableFormat">
	<inputVariableId>Cowbeech</inputVariableId>
</flagSourceCountsTable>

maximumStatusTable

Anchor
maximumStatusTable maximumStatusTable

A maximumStatusTable indicates, by colouring, when certain threshold levels are crossed. In this type of table, the rows should be defined individually and can contain more than one series. The boolean value 'mergLocation' plays an important role in combining the locations or treat them individually.

...

For the two tables for which this is valid, the last example does not give much additional value for a thresholdsCrossingsTable. Then each row (which is equal to one locatation) will have a '1' in one of the cells. A maximumStatusTable supplies more value because it will indicate when this (maximum) threshold will be reached.
See below mentioned (simplified) figures.

mergedPrecipitationTable

Anchor
mergedPrecipitationTable mergedPrecipitationTable

A mergedPrecipitationTable contains both observed rainfall as well as forecast rainfall, preferably in P.merged timeseries. Data can be visualised in configurable time intervals compared to T0 and will appear in separate columns. Additionally, a single column can be added to visualise any parameter (e.g. CWI). An example can be found below (without extra column). In the example below, actually two tables are plotted next to each other. The left table (with names) contains the historical date. The one on the right hand side contains the forecast timeseries and has no name column. A table like this has two header rows to be defined by the user.

...

• id: identifier (reference to the template tag)
• formatId: reference to the format of this table (to one of the mergedPrecipitationTables in the declarations section);
• table:
  • id: identifier (used for comments only)
  • formatId: reference to the format of this table (to one of the mergedPrecipitationTables in the declarations section)
  • timeSeries: reference to an inputVariable.

SystemStatusTables

Anchor
SystemStatusTables SystemStatusTables

SystemStatusTables display information about the status and behaviour of the FEWS system itself (like in the System monitor).

...