Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Definition of the time series set to be displayed in the selected grid plot. This can refer to one location with valuetype grid or longitudinal profile, or it can refer to a locationSet of scalars. Contourlines can only be displayed in combination with a regular grid. 

When 2D or 3D data is imported using multiple domain partitions, this data can be displayed using LocationSets. All partitions have a LocationId and a LocationSet can be created for reference to all partitions. This LocationSet can be used consistently throughout the gridDisplay configuration, like when displaying:

  • 2D data, e.g. water level
  • 3D data, e.g. a combination of uTimeSeriesSet, VTimeSeriesSet and sigmaScaleReferenceTimeSeriesSet
  • 3D data, e.g. a combination of timeSeriesSet (e.g. temperature) and sigmaScaleReferenceTimeSeriesSet
legendStyle

The legend can be shown as table legend or as bar legend.
Default legend style is table. Bar legend shows fluent scale bar on the right.

...

The background maps to be displayed are defined in the geoMap element. More information on the configuration of the geoMap element can be found here

Configuration (

...

Examples)

The following example shows how to configure a Meteosat image as grayScaleImage in the Grid display.

Code Block
xml
xml
titleExtract of SpatialDisplay.xml
<gridPlotGroup id="Meteosat Images">
	<gridPlot id="MeteoSat">
		<timeSeriesSet>
			<moduleInstanceId>ImportMeteosat</moduleInstanceId>
			<valueType>grid</valueType>
			<parameterId>image</parameterId>
			<locationId>meteosat</locationId>
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="minute" multiplier="15"/>
			<relativeViewPeriod unit="hour" start="-12" end="36"/>
			<readWriteMode>read only</readWriteMode>
		</timeSeriesSet>
		<classBreaks>
			<lowerColor>black</lowerColor>
			<upperColor>white</upperColor>
			<lowerValue>0</lowerValue>
			<lowerValue>8</lowerValue>
			<lowerValue>16</lowerValue>
			<lowerValue>24</lowerValue>
			<lowerValue>32</lowerValue>
			<lowerValue>40</lowerValue>
			<lowerValue>48</lowerValue>
			<lowerValue>56</lowerValue>
			<lowerValue>64</lowerValue>
			<lowerValue>72</lowerValue>
			<lowerValue>80</lowerValue>
			<lowerValue>88</lowerValue>
			<lowerValue>96</lowerValue>
			<lowerValue>104</lowerValue>
			<lowerValue>112</lowerValue>
			<lowerValue>120</lowerValue>
			<lowerValue>128</lowerValue>
			<lowerValue>136</lowerValue>
			<lowerValue>144</lowerValue>
			<lowerValue>152</lowerValue>
			<lowerValue>160</lowerValue>
			<lowerValue>168</lowerValue>
			<lowerValue>176</lowerValue>
			<lowerValue>184</lowerValue>
			<lowerValue>192</lowerValue>
			<lowerValue>200</lowerValue>
			<lowerValue>208</lowerValue>
			<lowerValue>216</lowerValue>
			<lowerValue>224</lowerValue>
			<lowerValue>232</lowerValue>
			<lowerColor>orange</lowerColor>
			<upperColor>red</upperColor>
			<lowerValue>240</lowerValue>
			<lowerValue>248</lowerValue>
			<lowerValue>255</lowerValue>
		</classBreaks>
	</gridPlot>
</gridPlotGroup>

The following example shows how to configure 3D data originating from several computational domains in the Grid display.

Code Block
title3D data example for SpatialDisplay.xml
<gridPlot id="Arabian Gulf" name="###################">
	<dataLayer>
		<arrowColor>white</arrowColor>
		<arrowSymbol>flow</arrowSymbol>
		<multipleArrowsPerValue>false</multipleArrowsPerValue>
		<uTimeSeriesSet>
			<moduleInstanceId>AGM_DFlowFM_FC</moduleInstanceId>
			<valueType>grid</valueType>
			<parameterId>C.simulated.u</parameterId>
			<locationSetId>AG.DFlowFM_0_####</locationSetId>
			<timeSeriesType>simulated forecasting</timeSeriesType>
			<timeStep unit="nonequidistant"/>
			<readWriteMode>read complete forecast</readWriteMode>
		</uTimeSeriesSet>
		<vTimeSeriesSet>
			<moduleInstanceId>AGM_DFlowFM_FC</moduleInstanceId>
			<valueType>grid</valueType>
			<parameterId>C.simulated.v</parameterId>
			<locationSetId>AG.DFlowFM_0_####</locationSetId>
			<timeSeriesType>simulated forecasting</timeSeriesType>
			<timeStep unit="nonequidistant"/>
			<readWriteMode>read complete forecast</readWriteMode>
		</vTimeSeriesSet>
		<uvAmplitudeParameterId>C.simulated.speed</uvAmplitudeParameterId>
		<uvDirectionParameterId>C.simulated.dir</uvDirectionParameterId>
		<sigmaScaleReferenceTimeSeriesSet>
			<moduleInstanceId>AGM_DFlowFM_FC</moduleInstanceId>
			<valueType>grid</valueType>
			<parameterId>WD.simulated</parameterId>
			<locationSetId>AG.DFlowFM.merged</locationSetId>
			<timeSeriesType>simulated forecasting</timeSeriesType>
			<timeStep unit="nonequidistant"/>
			<readWriteMode>read complete forecast</readWriteMode>
		</sigmaScaleReferenceTimeSeriesSet>
	</dataLayer>

	<barLegend>
		<position>right</position>
		<width>50</width>
		<length>400</length>
		<labelsInside>true</labelsInside>
	</barLegend>
	<classBreaksId>Class.Currents</classBreaksId>
	<contourLinesColor>antique white</contourLinesColor>
</gridPlot>

 

Logo at map

Some satelite products require to be shown with a logo, where the imageFile with the logo should be located in the MaplayerFiles directory.

...