Page History

...

• 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

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.

Image Added
Example of a flagCountsTable

Declarations section

In the declaration section the layout of the table needs to be defined in a flagCountsTableFormat.

The following options are available:

• id: identifier of this table format.
• tableStyle: The tableStyle to use for this table. The available tableStyles are defined in the report tables .css file.
• hyperlinkUrl: Optional URL. If specified, then the location name for each time series will be a hyperlink that refers to this URL. It is possible to insert the following tags: !LOCATION_ID!, !LOCATION_NAME!, !PARAMETER_ID! and !PARAMETER_NAME!. The !LOCATION_ID! tag will be replaced with the location id for the time series. The !LOCATION_NAME! tag will be replaced with the location name for the time series. The !PARAMETER_ID! tag will be replaced with the parameter id for the time series. The !PARAMETER_NAME! tag will be replaced with the parameter name for the time series. This can e.g. be used to link each row in this FlagCountsTable to a page (or an anchor within a page) that contains a FlagSourceCountsTable with more detailed information about the time series for that row.
• scrollableTable: Use this to split the table into two parts, one for the header row(s) and one for the data rows. The data row part refers to the tableStyle for this table with "_scrollable" appended. This can be used to make the data rows scrollable while the header row(s) remain fixed. For this to work the referred style needs to be defined in the report tables .css file.

Configuration example:
TODO

Report section

In the reports section define a flagCountsTable.

The following options are available:

• id: Identifier for this FlagCountsTable that is used in the report template html file in the table tag (e.g: $TABLE(table1)$).
• formatId: The id of the FlagCountsTableFormat to use for this FlagCountsTable.
• inputVariableId: One or more ids of inputVariables that are defined at the start of this report. For each time series in the inputVariable(s), there will be one row in the table with the location, parameter and flag counts for that time series. For a given time series this uses only the data within the relativeViewPeriod that is defined for that time series in the timeSeriesSet. If a timeSeriesSet contains multiple time series (e.g. a locationSet), then for each time series in the timeSeriesSet a separate row is created.

Configuration example:
TODO

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".

Image Added
Example of a flagSourceCountsTable

Declarations section

In the declaration section the layout of the table needs to be defined in a flagSourceCountsTableFormat.

The following options are available:

• id: identifier of this table format.
• tableStyle: The tableStyle to use for this table. The available tableStyles are defined in the report tables .css file.
• scrollableTable: Use this to split the table into two parts, one for the header row(s) and one for the data rows. The data row part refers to the tableStyle for this table with "_scrollable" appended. This can be used to make the data rows scrollable while the header row(s) remain fixed. For this to work the referred style needs to be defined in the report tables .css file.

Configuration example:
TODO

Report section

In the reports section define a flagSourceCountsTable.

The following options are available:

• id: Identifier for this FlagSourceCountsTable that is used in the report template html file in the table tag (e.g: $TABLE(table1)$).
• formatId: The id of the FlagSourceCountsTableFormat to use for this FlagSourceCountsTable.
• inputVariableId: The id of an inputVariable that is defined at the start of this report. The time series of this inputVariable is used for this table. This table shows for each validation rule (hard max, hard min, rate of change, etc.) the number of values that were rejected because of that validation rule. This uses only the data within the relativeViewPeriod that is defined for the time series in the timeSeriesSet. If the timeSeriesSet contains multiple time series (e.g. a locationSet), then an error message is given.

Configuration example:
TODO

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.

Figure 102 Example of a maximumStatusTable (NE Region)

Declarations section

In the declaration sections the layout of the table needs to be defined.

...

• id: unique identifier (as reference to this table);
• tableStyle: a choice of tableStyle which can be influenced by using the corresponding classes in a cascading style sheet. Choices are tableStyle1 to tableStyle10;
• headerRow1Text: text to be displayed in table header (first line);
• headerRow2Text: text to be displayed in table header (second line);
• dataColumns: definition of individual column with a time interval for aggregating precipitation. Each column should contain:
  • columnHeader: text to be displayed in column header (first line);
  • unitHeader text to be displayed in column header (second line);
  • relativeViewPeriod: period to aggregate the data;
    • unit: unit to aggregate. Choices: day/hour/minute/second/week
    • start: start of interval (in time unit) compared to T0;
    • end: end of interval (in time unit) compared to T0;
• nameColumnWidth: integer value of width of the name column (most left column (if present);
• dataColumnWidth: integer value of width of the data columns;
• suppressNameColumn boolean value for setting the name column visible or not. This column, when visible, is filled with the (full) location name of the timeseries which is visualised in this table.

Report section

In the report section the content (timeseries) are 'attached' to this table.

...