...
A common model set-up in D-Flow FM will make use of several models for an project area. For example, you could have a large scale coarse regional model, with 1 (or more) finer model(s) zooming in on the area of interest which is (are) located within the regional model area, i.e. the model areas overlap. When you display all models in 1 gridPlot, you don't want to see the coarse grid peaking out from underneath the finer local model(s). The example in the figure has 3 different model areas, going from coarse (blue grid), through intermediate (red grid) to a fine resolution (green grid).
In order to hide the coarser grids where a finer grid is available, you'll need to define a shapefile which masks the area of each model domain that you would like visualised in the gridDisplay. These shapefiles should (barely) overlap, see example in the figure on the right. All data is still available in the gridPlot, but only the data within the shapefile contour is displayed in the gridDisplay. When the user double-clicks in the gridDisplay, a timeSeriesDisplay with scalar data for all models with data for that location (in this example up to 3) is displayed, eventhough even though the data might be masked in the gridDisplay. Config example below.
Display of 3D data (sigma layers)
...
| Code Block | ||
|---|---|---|
| ||
<gridDisplay 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/gridDisplay.xsd"> <title>title</title> <gridPlotGroup id="gridPlotGroupId" name="gridPlotGroupName"> <gridPlot id="gridPlotId" name="gridPlotName"> <dataLayer> <uTimeSeriesSet> <moduleInstanceId>DFlowFM_HC</moduleInstanceId> <valueType>grid</valueType> <parameterId>parameter</parameterId> <locationSetId>SigmaLayer_0_####</locationSetId> <!-- Configure only the top layer (index = 0). The sibling locations (i.e. other sigma layers) are resolved through the parent of the top layer. --> <timeSeriesType>simulated historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </uTimeSeriesSet> <vTimeSeriesSet> <moduleInstanceId>DFlowFM_HC</moduleInstanceId> <valueType>grid</valueType> <parameterId>parameter</parameterId> <locationSetId>SigmaLayer_0_####</locationSetId> <!-- Configure only the top layer (index = 0). The sibling locations (i.e. other sigma layers) are resolved through the parent of the top layer. --> <timeSeriesType>simulated historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </vTimeSeriesSet> <sigmaScaleReferenceTimeSeriesSet> <!-- when this is configured, a vertical slider becomes automatically visible in GridDisplay to slide through the water column --> <moduleInstanceId>DFlowFM_HC</moduleInstanceId> <valueType>grid</valueType> <parameterId>parameter</parameterId> <locationSetId>sigma.merged</locationSetId> <!-- parentLocations for all domains, linking to all sigma layers --> <timeSeriesType>simulated historical</timeSeriesType> <timeStep unit="nonequidistant"/> <readWriteMode>read complete forecast</readWriteMode> </sigmaScaleReferenceTimeSeriesSet> </dataLayer> <verticalSliderRange start="0" end="100"/> <!-- limit the min and max water depth used in the vertical slider in the GridDisplay --> <!-- if not configured the range of slider is automatically set to cover all available water depths in the grid for the entire period displayed --> </gridPlot> </gridPlotGroup> |
Masking - display D-Flow FM 3D results in GridDisplay (multiple overlapping models)
When you have multiple overlapping models and you want to control which data is displayed in the gridDisplay, you can make use of a masking shapefile. Link this file to a locationSet. The <id> specified in the <esriShapeFile> config can be used in the GridDisplay, which will mask the data shown. For more information visit the wiki on the D-Flow FM model adapter: Display of 2D data for overlapping domains
| Code Block | ||
|---|---|---|
| ||
<locationSet id="wave_clipper.shp">
<esriShapeFile>
<file>wave_clipper.shp</file>
<id>Wave</id>
<x>0</x>
<y>0</y>
</esriShapeFile>
</locationSet> |
| Code Block | ||
|---|---|---|
| ||
<valueTimeSeriesSet>
<moduleInstanceId>Wave_HC</moduleInstanceId>
<valueType>grid</valueType>
<parameterId>Wave.height.simulated</parameterId>
<locationId>Wave</locationId>
<timeSeriesType>simulated historical</timeSeriesType>
<timeStep multiplier="1" unit="hour"/>
<readWriteMode>read complete forecast</readWriteMode>
</valueTimeSeriesSet> |