What | DisplayGroups.xml |
|---|---|
Config group | SystemConfigFiles |
Required | no |
Description | Defines pre-configured displays |
schema location | https://fewsdocs.deltares.nl/schemas/version1.0/displayGroups.xsd |
Still to document: TimeSpanComplexType |
A list of pre-configured displays can be configured in the Display groups. When available on the file system, the name of the XML file is for example: DisplayGroups.xml
The pre-configured displays are organised in a tree view in the time series display (see example in Figure 1). Each pre-configured display is identified by its name, and may include one or more subplots, each with one or more time series lines.
Figure 1 Example of time series display, showing two sub-plots and tree-view of pre-configured displays
Another option is to plot a longitudinal profile in the time series display (see figure 2). The main difference with the normal time series plot is, that on the X-axis the river chainage is plotted. With the control toolbar a specific time step can be selected.
Figure 2 Example of time series display, showing longitudinal profile.
The display groups are configured by first listing the names of the filters to be shown in the display (for example "Rain gauges", "Gauges" and "Fractions" in figure 3 below) under the displayGroup descriptor. The names of the subplots can then be added (e.g. "MacRitchie" and "Woodleigh" below). Each of the subplots is assigned a plotId which links to the definitions of the plots and the time series set to be used. For example in the Fractions displayGroup a stackPlot is defined with a max and min (this file is attached as an example). Please note that the colours, linestyle, precision etc are defined in the TimeSeriesDisplayConfig.
figure 3 - example of a configured displayGroup file (click to enlarge)
Figure 4 Root element of the display groups definition
Root element for each displayGroup. A display group forms one of the main nodes in the tree view and may contain multiple displays. Multiple display groups may be defined.
Attributes:
Defines the plots relating to the displayGroup
Elements:
Defines the groups of plots to be viewed (i.e. the branches of the shortcuts in the display)
Attributes:
By defining a location loop within a displayGroup, the display group will be created for each location of location set configured in the loop.
<displayGroup name="Validations Location Loop">
<displayGroup name=" ">
<locationLoop>
<locationSetId>FloodingAreas</locationSetId>
<includeChildren>true</includeChildren>
<locationRelationId>L_AREA</locationRelationId>
<locationRelationId>L_VISIBILIY</locationRelationId>
<locationRelationId>MEASUREMENT_PARENT</locationRelationId>
</locationLoop>
<displayGroup name="Waterbalance">
<display name="Waterbalance">
<plotId>Waterbalance</plotId>
</display>
<display name="Waterbalance incl. error">
<plotId>Waterbalance_error</plotId>
</display>
</displayGroup>
...
</displayGroup>
</displayGroup> |
Root element for each subplot. Multiple sub-plots may be defined per display.
Subplot configuration elements :
By default the <subPlotType> is set to 'standard', which means the default plot type for the configured timeSeriesType will be used. Optionally, you can configure the following other subplot types.
Time series of this subplot are plotted as stacked areas (if lineStyle is solid) or stacked bars (if lineStyle is bar).
Time series of this subplot are plotted as stacked bars. Color of the bar matches the paint scale color associated with the bar value. Height of all bars is the same, and equals Y-axis range / number of series in the plot.
A horizontal bar is plotted for each time series. The color of the bars signify the value for that time series at the given time on the x-axis.
|  |
|---|
2022.02 and later |
Use elements leftAxis and rightAxis to confiure the axes separately.If the rightAxis is configured, the leftAxis must be configured too.
An example :
<subplot>
<leftAxis min="-10" max="100"/>
<axisLabel>Label left axis</axisLabel>
<lowerMarginPercentage>10</lowerMarginPercentage>
<upperMarginPercentage>20</upperMarginPercentage>
</leftAxis>
<rightAxis min="20" max="50"/>
<axisLabel>Label right axis</axisLabel>
<lowerMarginPercentage>5</lowerMarginPercentage>
<upperMarginPercentage>5</upperMarginPercentage>
</rightAxis>
..... |
If the optional attributes min and max are not configured, then subplot attributes min and max are used.
Use the <area> element in combination with a <lineStyle> to obtain vertical lines.
<subplot>
<area>
<lineStyle>solid</lineStyle>
<lineWidth>10</lineWidth>
<color>blue</color>
<opaquenessPercentage>50</opaquenessPercentage>
<timeSeriesSet>
<moduleInstanceId>ImportMSW</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Q.m</parameterId>
<locationId>H-MS-LUIK</locationId>
<locationId>H-MS-SINT</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour"/>
<relativeViewPeriod unit="day" start="-2" end="0"/>
<readWriteMode>read only</readWriteMode>
</timeSeriesSet>
</area>
</subplot>
|
This tag can be used to invert the y-axis of a plot. Below a screenshot of an inverted graph. In the example the timeseries with parameter RAIM is inverted.
Available since 2020.02. If it is set to true, the subplot y-axis (or domain axis) will be logarithmic. A parameter can also be configured to always/never be displayed on a logarithmic scale, but the subplot setting has precedence. If a parameter is set logarithmic true, but the subplot it appears in is configured logarithmic-false, the axis will not be logarithmic. It is also possible to configure a mixture of logarithmic and non-logarithmic subplots in the same plot:
Logarithmic axis can also be turned on and off manually, using the menu bar. If you do so, the setting will effect all subplots the same way. Should you wish to reset the subplots to the configured version, use the reset domain axis to configured button.
Available since 2020.02. Default is scaleOutsideMinAndMax. If it is set to scaleOutsideMinAndMax, the y axis will scale to the data available. If it is set to fixedBetweenMinAndMax, the min and max of the y axis will always be the configured values, regardless of the data. This could make the entire data set fall of the visible chart. If all the data is in the middle of min and max withing a small range, the axis will scale to the data, it will appear as a small line in the middle. If it is set to scaleBetweenMinAndMax, the min will never be smaller than what is configured, and the max will never be greater than configured, but if the available data falls between these values, the axis will scale so that the data fills the whole area. If the data falls entirely outside of min and max, it will not be visible.
This option makes it possible to cluster bars per timestep. A code example can be found here. This example shows how clustered bars are displayed:
This option can be used to invert drawing order of the lines. By default the lines are drawn in the same order as shown in the legend : the first line first, the last line last. The last line is then on top. If drawing order is inverted the last line in the legend is drawn first and the first line last. The first line is then on top.
Thresholds can be displayed on the left axis, or on the right axis, or on both. By default the thresholds are displayed on the left axis.
To change it, an option ‘ thresholdAxis’ can be used . Configure <thresholdAxis>right</thresholdAxis> if only the right axis should have thresholds, or <thresholdAxis>both</thresholdAxis> if both left and right axes should have thresholds
The tag line can be used to configure both single or dual y-axis. Enables the configuration of a custom colour. visibleInLegend, visibleInPlot and visibleInTable are optional, default setting is true. If visibleInLegend is set to false, the series will show up in the plot area, but not in the legend. If visibleInTable is set to false, the time series can still be sen on the plot, but the data will not show in the table. If visibleInPlot is set to false, the time series can be still shown in the table, but will not be visible in the plot. VisibleInLegend, visibleInPlot and visibleInTable are supported by clustered bars too.
Important notice: It is possible to configure <visibleInTable>,<visibleInPlot> outside of the wrapper elements <line>, <clusteredBars> or <area>, but it should not be done. There is a bug in one of the external libraries, that causes a mixup, and the wrong <visibleInTable>,<visibleInPlot> will be paired with the wrong timeSerieSet. Always use <visibleInTable> <visibleInPlot> together with <line>, <clusteredBars> or <area>.
Example:
<plot id="Test">
<subplot>
<line>
<color>dark orange</color>
<visibleInLegend>false</visibleInLegend>
<visibleInTable>false</visibleInTable>
<visibleInPlot>true</visibleInPlot>
<timeSeriesSet>
<moduleInstanceId>Import</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.m</parameterId>
<locationId>LocA</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour"/>
<relativeViewPeriod unit="hour" start="-12" end="12"/>
<readWriteMode>editing visible to all future task runs</readWriteMode>
</timeSeriesSet>
</line>
</subplot>
</plot> |
<displayGroup name="bars">
<display name="clusteredBars">
<subplot>
<clusteredBars axis="left">
<bar>
<color>blue</color>
<visibleInLegend>false</visibleInLegend>
<visibleInPlot>false</visibleInPlot>
<timeSeriesSet>
<moduleInstanceId>Import</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.m</parameterId>
<locationId>LocA</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour"/>
<relativeViewPeriod unit="hour" start="-12" end="12"/>
<readWriteMode>editing visible to all future task runs</readWriteMode>
</timeSeriesSet>
</bar>
<bar>
<color>red</color>
<visibleInTable>false</visibleInTable>
<label>Rated Discharge</label>
<timeSeriesSet>
<moduleInstanceId>Import</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Q.m</parameterId>
<locationId>LocA</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour"/>
<relativeViewPeriod unit="hour" start="-12" end="12"/>
<readWriteMode>editing visible to all future task runs</readWriteMode>
</timeSeriesSet>
</bar>
</clusteredBars>
</subplot>
</display> |
It is possible to have two y-axis visible in the same plot. This can be done by having multiple timeseries where some are assigned to the left y axis and some to the right y axis, or by having a timeseries on the left y axis with an associated rating curve on the right y axis. So every timeseries plot (also in reports) will have a mandatory left y axis to which a timeseries is associated and an optional right y axis to which a timeseries or rating curve is associated.
The display of threshold lines are supported for one y axis. But there can be threshold lines for either the left or the right y axis, but not both.
To associate a timeseries to the left or right y axis use the <axis> element. This element is optional and leaving it out will associate it (default) to the left axis. Please note that at least one timeseries should be on the left axis (by either settings <axis>left</axis> or leaving the element out and using the default).
Below are two examples of a config and the resulting plot.
|
| |
|
|
When a discharge is displayed, it is possible to show the stage on the right axis. It is not possible to configure this rating on the left axis (and the timeseries on the right axis), since a plot has to have at least one timeseries on the left axis.
The right axis is then not a linear axis but the ticks on the right axis are calculated from the discharge ticks on the left axis.
It is also possible to display the stage and show the discharge on the right axis. The example below shows a display which plots several discharge time series.
The left axis is a linear axis with ticks for the discharge. The right axis is a non-linear axis.
The ticks on the right axis are calculated from the value of the discharge on the left axis by using a rating curve.
Below an configuration and resulting plot
|
|
Adding DescriptiveFunctions will result in an extra panel in the display, showing relevant descriptive information about the timeseries in view. More information on the descriptive functions available can be found at TimeSeriesDisplayConfiguration
Options available when creating an variable line width type display
Attributes:
Example
Below a screenshot of a variable line width plot for different ensemble members that have different line width's. In this case line width is an indication of the probability of the ensemble member. The sum of probability of all ensemble members at a time is one. Selecting separate ensemble members will mark them with the color black.
Single location displays can be used to easily create plots for individual locations. This can either be done for individual locations, or alternatively for a locationSet which will then produce a list of location with their corresponding plot.
(Since 2016.02) By using a chainage location set in a time series set of a plot in the display groups, a longitudinal profile can be plot based on scalar time series for different locations
<plot id="Langsprofiel_Caspargouwse_Wetering"> <subplot> <timeSeriesSet> <moduleInstanceId>WerkFilter</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.G.15</parameterId> <chainageLocationSetId>Langsprofiel_Caspargouwse_Wetering</chainageLocationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="day" start="-32" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </subplot> </plot> <displayGroup name="LangsProfiel"> <display name="Langsprofiel_Caspargouwse_Wetering"> <locationSetId>Langsprofiel_Caspargouwse_Wetering</locationSetId> <plotId>Langsprofiel_Caspargouwse_Wetering</plotId> </display> </displayGroup> |
Notice that it is not possible to combine a longitudinal plot in with a standard plot (having time on the X-axis). Furthermore, it is not possible to use it for relatedLocations, and also thresholds will not be shown.
Time series with one domain axis are displayed as one xy chart per time step, like longitudinal profiles. A slider is used to navigate through time.
<timeSeriesSet> <moduleInstanceId>LMW_Import_spectrum</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Wave.variancedensity.meting</parameterId> <domainParameterId>f</domainParameterId> <locationSetId>LMW_Czz10</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="60"/> <relativeViewPeriod unit="day" start="-2" end="2"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> |
When a second domain axis is available this will always be used as direction for a polor plot by the time series dialog. When second domain axis is not a directional parameter or the time series has more than two domain axes the time series can not be diplayed the time series dialog with the current functionality
<subplot> <classBreaks> <break symbolSize="10" color="000080" lowerValue="0"/> <break symbolSize="10" color="0000A8" lowerValue="0.0005"/> <break symbolSize="10" color="0000E6" lowerValue="0.001"/> <break symbolSize="10" color="004DFF" lowerValue="0.0025"/> <break symbolSize="10" color="00B3FF" lowerValue="0.005"/> <break symbolSize="10" color="1AFFE5" lowerValue="0.01"/> <break symbolSize="10" color="80FF80" lowerValue="0.015"/> <break symbolSize="10" color="E6FF19" lowerValue="0.02"/> <break symbolSize="10" color="FFB200" lowerValue="0.025"/> <break symbolSize="10" color="FF4C00" lowerValue="0.035"/> <break symbolSize="10" color="E50000" lowerValue="0.04"/> <break symbolSize="10" color="A80000" lowerValue="0.045"/> <break symbolSize="10" color="800000" lowerValue="0.05"/> </classBreaks> <direction>from</direction> <timeSeriesSet> <moduleInstanceId>Swan_dcsmv6_hirlam_forecast_import</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Wave.variancedensity2D.voorspeld</parameterId> <domainParameterId>f</domainParameterId> <domainParameterId>dir</domainParameterId> <locationSetId>SWAN_POINTS2</locationSetId> <timeSeriesType>simulated forecasting</timeSeriesType> <timeStep unit="minute" multiplier="60"/> <relativeViewPeriod unit="day" start="-2" end="2"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </subplot> |
Additional time series can be configured in display group plots. These series are found via attribute functions in the <locationFunctionEquals selected=@ATTRIBUTE_ID_A@ additional="@ATTRIBUTE_ID_B@"> of the selected time series and the additional time series. When the attribute functions evaluate to the same value the additional time series are added as invisible by default. When additional time series are available the icon of the visibility dialog will change which shows that invisible time series are available and can be made visible.
Since 2020.02, it is possible to match the time series based on any view period (not just the current system time) by setting the showLocationsOutsideVisibilityPeriod option to true.
When it is desired that the additional time series are added only for the same locations then all locations should have an attribute that is equal to their id for example LOC_ID and the locationFunctionEqualselement can be used as follows:
<locationFunctionEquals selected=@LOC_ID@ additional="@LOC_ID@">
In the example below locationFunctionEquals selected="@LOC_ID@" additional="@AFGB_NAAR@"/> is used which will show all a timeseries from the additional time series set where the location has an attribute value AFGB_NAAR which equals the LOC_ID attribute of the shown location of the normal time series set, which can be multiple or even 0.
There is an extra option to show the additional time series in a separate sub plot to make sure there are no plots with incompatible parameter combinations.
Each additional time series element can be given a name, this name will be used as prefix in the legend of the time series and as GroupNode label in the visibility dialog.
<plot id="WATERBALANS_DAG_CAW"> <subplot stackPlot="true"> <lineStyle>bar</lineStyle> <timeSeriesSet> <moduleInstanceId>BalansAfvoergebieden</moduleInstanceId> <valueType>scalar</valueType> <parameterId>H.G.i.d</parameterId> <locationSetId>AFVOERGEBIEDEN</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="day" timeZone="GMT+1"/> <relativeViewPeriod unit="day" start="-32" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> <additionalTimeSeries name="*AFGB_NAAR*" separateSubPlot="true"> <locationFunctionEquals selected="@LOC_ID@" additional="@AFGB_NAAR@"/> <timeSeriesSet> <moduleInstanceId>ImportOpvlWater</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Q.G.15</parameterId> <locationSetId>OPVLWATER_SUBLOC_DEBIETEN</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="-70" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </additionalTimeSeries> <additionalTimeSeries name="*AFGB_VAN*" separateSubPlot="true"> <locationFunctionEquals selected="@LOC_ID@" additional="@AFGB_VAN@"/> <timeSeriesSet> <moduleInstanceId>ImportOpvlWater</moduleInstanceId> <valueType>scalar</valueType> <parameterId>Q.G.15</parameterId> <locationSetId>OPVLWATER_SUBLOC_DEBIETEN</locationSetId> <timeSeriesType>external historical</timeSeriesType> <timeStep unit="minute" multiplier="15"/> <relativeViewPeriod unit="hour" start="-70" end="0"/> <readWriteMode>read only</readWriteMode> </timeSeriesSet> </additionalTimeSeries> </subplot> </plot> |
In a display group the element <showAsScatterPlot> can be used to use a plot where different time series are plotted against each other with the values of the different time series on the X and Y axis.
In between the element <referencePoints> there can be <point> elements defined that will be shown as an interaction line.
With the elements <xAxisRange> and <yAxisRange> the range of the x and y axis can be defined.
By default all time series with the same location are paired up.
Since 2017.02 time series with the same parameter can be paired up by using the element <createPairsByMatchingParameter>true</createPairsByMatchingParameter>
Since 2019.02 it is enabled that when there are only 2 time series they will be paired up irregardless of their location or parameter.
Since 2019.02 The element <markerVisibility> is introduced which enables the possibility the choose whether all data points "all", no data points "none" or only the last data point "onlyLast" should be visualised using a marker
Since 2020.02 it is possible to automatically pair up the time series based on their configured order: <matchTimeSeriesPair>timeSeriesOrder</matchTimeSeriesPair>
Since 2020.02 It is possible to draw colored areas based on configured points. Also, in the plot, the grid lines in the background and the interaction line are visible, and legends are added next to the plot.
Since 2022.02 the scatter series are shown in standard time series table and all configuration elements are optional , so it is enough to configure <showAsScatterPlot/>.
A simple scatter plot , without any additional option, is shown below :
This feature is available since 2021.02
Using statisticalFunctionId it is possible to create a preconfigured display with any statistical function.
The statistical function should have an id configured in TimeSeriesDisplay.xml, for example :
<statisticalFunction function="centralMovingAverage" id="CMA" ignoreMissings="true"> <movingAccumulationTimeSpan unit="hour" multiplier="6"/> </statisticalFunction> |
This id can be used in displays to create a predefined display with the required statistical function :
<display name="Central Moving Average"> <locationId>LocD</locationId> <plotId>PlotId</plotId> <statisticalFunctionId>CMD</statisticalFunctionId> </display> |
Definition of a pre-configured display. Each display may contain multiple sub-plots. Multiple displays may be defined per display group.
[
Figure 4 Elements in the Display section of the DisplayGroups configuration
Attributes;
Normally, displays are defined with a relative view period, so that the view window progresses with current system time.
This paradigm does not fit systems that are more oriented towards seasonal or water year analysis. Therefore an option has been added since 2011.02 to define a season, such that the time axis is fixed, while the vertical red line (current system time) moves over time from left to right through the display.
To utilize this functionality, a season should be defined instead of a relative view period. This season specification if composed of a start and end date, as well an entry called 'startForwardLookingPeriod'.
The software compares the currentSystemTime against the date specified in the 'startForwardLookingPeriod' entry, to decide if the time axis needs to shift to the next year/season. This decision is relevant within a water supply forecasting context since a few weeks before the end of the water year you may like to look forward to the next wateryear instead of the current wateryear. Use readWriteMode=read only in your time seriessets, as other modes such as 'read complete forecast' stretches the time horizon, disrupting the time horizon displayed outside the season.
E.g. in the code example below, a wateryear is defined from 1st of October to 30th of September. The startForwardLookingPeriod is defined as 1st of September.
currentSystemTime | view period x-axis (start-end) |
|---|---|
12 Aug.2012 | 1 Oct.2011 - 30 Sept.2012 |
12 Sept.2012 | 1 Oct.2012 - 30 Sept.2013 |
12 Oct.2012 | 1 Oct.2012 - 30 Sept.2013 |
<display name="SELI1 - Selway R nr Lowell - SWE"> <startForwardLookingPeriod>--09-01</startForwardLookingPeriod> <season> <startMonthDay>--10-01</startMonthDay> <endMonthDay>--09-30</endMonthDay> </season> <locationId>SELI1L</locationId> <locationId>SELI1U</locationId> <plotId>SWE</plotId> </display> |
The associated display looks like:
To tie the date/time ticks to the valid times of the (cardinal) time step, configure ‘tickTimeStep’ in DisplayGroups.xml. For example, if the ‘tickTimeStep’ is 6 hours then the ticks are always aligned with the synoptic times 00Z, 06Z, 12Z, 18Z. When we are zooming out and there is no space to display all date/times along the x-axis, then one or more synoptic times ticks are omitted. For example we see ticks at 00Z and 18Z.
Options available when creating an area type display
Attributes:
Making stacked graphs Since 2007/02 release the functionality of the SubPlotArea complex type has been extended to include stack plots. The only thing needed to implement this is to add a stackPlot="true" attribute to a subplot element. Attached to this page is a example of this funtionality. If stackPlot is True, the timeseries of this subplot are plotted as stacked areas, except for the timeseries that are specified inside the (optional) element <area>. Area-series are always plotted as so called 'difference area'. Attribute stackPlot is intended as overruling of the default series paint (i.e. line or bar) It is not possible to combine 'stacked areas' and lines/bars in one plot. A configuration example of an application of stacked graphs can be find in the how to page How to import and visualize rain and dropsize distribution data from WaterML 2.0 format. |
Display groups may be defined while DELFT-FEWS is running and reloaded by re-opening the time series dialogue. If a mistake is made, then the shortcuts item to open the tree view will not appear and an appropriate message will be generated. After resolving the mistake the item will again become available on re-loading the display. |
