Page History

chainageLocationAttributeId

...

<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>

Since 2020.02 it is possible to use time dependent chainage location attributes see Time Dependent Chainage Location Sets.

For configuring location attributes see all detailed information at the  next page

...

This element can be used to generate multiple locationsets from location attributes; these are normally invluded for locations in dbf or CSV files. In the example below a locationSet is created Warrington_Fluvial_Catchments_PDM from locationSet UK_Fluvial_Catchments_PDM where the location attribute Centre contains Warrington. By using the subLocationSetIdFunction, multiple locationSets are generated as well for all river_segments that can be found in the locationattribute @River_Segment@.

	<locationSet id="Warrington_Fluvial_Catchments_PDM">
		<subLocationSetIdFunction>@River_Segment@_Warrington_Model_PDM</subLocationSetIdFunction>
		<locationSetId>UK_Fluvial_Catchments_PDM</locationSetId>
		<constraints>
			<attributeTextContains id="Centre" contains="Warrington"/>
		</constraints>
	</locationSet>

...

Note that sublocationsets can not be added to other locationsets. So it is adviced to create an overarching locationset (like UK_Fluvial_Catchments_PDM) from which sublocationsets are created by the function.

Label

It is possible to define a label that is presented in the map. For more information, see Explorer.