...
By configuring <chainageLocationAttributeId> all locations that have a value for this attribute will be contained in this location set. This attribute will automatically be used as sortingLocationAttributeId so the locations are in the order of ascending chainage value. The attribute must be of type numeric.
Referring to the chainage location set can only be done in combination with <readWriteMode>read only</readWriteMode> by configuring <chainageLocationSetId> in <timeSeriesSet>:
Code Block | ||||
---|---|---|---|---|
| ||||
<timeSeriesSet>
<moduleInstanceId>ExportRunMultipleTimeSeries</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.m</parameterId>
<chainageLocationSetId>CHAINAGE_D</chainageLocationSetId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="day"/>
<relativeViewPeriod unit="day" start="-7" end="0"/>
<readWriteMode>read only</readWriteMode>
</timeSeriesSet>
| ||||
<locationSet id="CHAINAGE_C">
<chainageLocationAttributeId>CHAINAGE_C</chainageLocationAttributeId>
</locationSet> |
For For configuring location attributes see all detailed information at the next page
Referring to the chainage location set can only be done in combination with <readWriteMode>read only</readWriteMode> by configuring <chainageLocationSetId> in <timeSeriesSet>, which is shown at the display groups page:
description
Optional description of the location set. Used for reference purposes only.
...