To create an IDMA display, a DoubleMassDisplay.xml should be configured. As the example below Example 1 shows, the content of this display include includes three time series sets, namely: baseGroupTimeSeriesSet, observedTimeSeriesSet, and estimatedTimeSeriesSet. These time series sets refer to a locationSetId, as shown on lines 10, 21, and 32, in the example.DoubleMassDisplay configuration examplefrom which, a number of locations are filtered to be shown on the IDMA display. These specific locations are referred to in the configured nodes in Topology.xml. Example 2 shows a configured node with four location IDs.
In addition, in the DoubleMassDisplay.xml, a modifier ID should be configured, which refers to the id of a time series modifier, defined in ModifierTypes.xml. This time series modifier also refers to the same location set referred to in DoubleMassDisplay.xml. Example 3 shows a configured time series modifier.
Example 1: a DoubleMassDisplay.xml configuration:
Code Block |
---|
language | xml |
---|
firstline | 1 |
---|
linenumbers | true |
---|
|
<doubleMassDisplay xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews
http://fews.wldelft.nl/schemas/version1.0/doubleMassDisplay.xsd">
<modifierId>IDMATest</modifierId>
<baseGroupTimeSeriesSet>
<moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>PP_Month</parameterId>
<qualifierId>merged</qualifierId>
<qualifierId>pxpp_pp24</qualifierId>
<locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId>
<timeSeriesType>simulated historical</timeSeriesType>
<timeStep unit="month"/>
<readWriteMode>read complete forecast</readWriteMode>
</baseGroupTimeSeriesSet>
<observedTimeSeriesSet>
<moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>PP_Month</parameterId>
<qualifierId>merged</qualifierId>
<qualifierId>pxpp_pp24</qualifierId>
<locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId>
<timeSeriesType>simulated historical</timeSeriesType>
<timeStep unit="month"/>
<readWriteMode>read complete forecast</readWriteMode>
</observedTimeSeriesSet>
<estimatedTimeSeriesSet>
<moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>PP_Month</parameterId>
<qualifierId>merged</qualifierId>
<qualifierId>pxpp_pp24</qualifierId>
<locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId>
<timeSeriesType>simulated historical</timeSeriesType>
<timeStep unit="month"/>
<readWriteMode>read complete forecast</readWriteMode>
</estimatedTimeSeriesSet>
</doubleMassDisplay> |
Example 2: a configured node with four location ids in Topology.xml:
Code Block |
---|
linenumbers | true |
---|
collapse | true |
---|
|
<node id="PRISM" name="PRISM">
<locationId>NY0254</locationId>
<locationId>NY0641</locationId>
<locationId>NY0542</locationId>
<locationId>NY0658</locationId>
<workflowId>ImportPRISM</workflowId>
<mapExtentId>CONUS</mapExtentId>
<filterId>ImportPRISM</filterId>
<showRunApprovedForecastButton>true</showRunApprovedForecastButton>
</node>
|
Example 3: a configured time series modifier in ModifierTypes.xml:
Code Block |
---|
|
<timeSeriesModifier id="IDMATest" name="IDMATest">
<timeSeries>
<moduleInstanceId>Calb_PreProcessing_PXPP</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>PP_Month</parameterId>
<qualifierId>merged</qualifierId>
<qualifierId>pxpp_pp24</qualifierId>
<locationSetId>NERFC_Calb_Preproc_Gages_pcpn_pp24</locationSetId>
<timeSeriesType>simulated historical</timeSeriesType>
<timeStep unit="month"/>
</timeSeries>
<defaultStartTime>start run</defaultStartTime>
<defaultEndTime>end run</defaultEndTime>
<defaultValidTime/>
<resolveInWorkflow>true</resolveInWorkflow>
<resolveInPlots>false</resolveInPlots>
</timeSeriesModifier> |