...
If a timeseries with direction data is available, this is where the TimeSeriesSet should be placed. Note: a TimeSeriesSet with velocity values is required in the ValueTimeSeriesSet!.
Use classbreaks to scale the arrows, when values are too small the arrows can bcome invisible.
For example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<dataLayer>
<visibleInTimeSeriesDisplay>true</visibleInTimeSeriesDisplay>
<visibleInSpatialDisplay>true</visibleInSpatialDisplay>
<arrowColor>black</arrowColor>
<arrowSymbol>flow</arrowSymbol>
<arrowDirection>from</arrowDirection>
<multipleArrowsPerValue>false</multipleArrowsPerValue>
<arrowMinimumPixelDistanceBetweenTwoCellCenters>2</arrowMinimumPixelDistanceBetweenTwoCellCenters>
<valueTimeSeriesSet>
<moduleInstanceId>Import_Wavenet</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Wave.obs.total.height</parameterId>
<locationSetId>UK_Coastal_Gauged_Wave</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<relativeViewPeriod unit="hour" start="-48" startOverrulable="true" end="0" endOverrulable="false"/>
<readWriteMode>read only</readWriteMode>
</valueTimeSeriesSet>
<directionTimeSeriesSet>
<moduleInstanceId>Import_Wavenet</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>Wave.obs.peak.dir</parameterId>
<locationSetId>UK_Coastal_Gauged_Wave</locationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="nonequidistant"/>
<relativeViewPeriod unit="hour" start="-48" startOverrulable="true" end="0" endOverrulable="false"/>
<readWriteMode>read only</readWriteMode>
</directionTimeSeriesSet>
</dataLayer>
<classBreaks>
<lowerColor>blue</lowerColor>
<upperColor>red</upperColor>
<lowerSymbolSize>20</lowerSymbolSize>
<upperSymbolSize>100</upperSymbolSize>
<lowerValue>0</lowerValue>
<lowerValue>5</lowerValue>
</classBreaks> |
uTimeSeriesSet / vTimeSeriesSet
...