Page History

...

To encrypt the password, use F12 menu (clipboard - > encrypt password, available since 2016.01)

time dependent z

location relations

...

Relations between location relations can be used in attribute functions, transformations and time series sets. Currently the one to many relations can only be used for time series sets in the filters.xmlIt .

<locationSet id="LocationSetWithTimeDependentAttributesStations">
	<csvFile><esriShapeFile>
		<file>TimeDependentLocationSet.csv<<file>Stations</file>
		<geoDatum>WGS 1984</geoDatum>
		<id>%id%<<id>%ID%</id>
		<name>%ID%</name>
		<x>0<<x>%X%</x>
		<y>0<<y>%Y%</y>
		<z>0</z>
		<attributeFile>
			<csvFile>TimeDependentLocationSetAttributes.csv<<csvFile>upstream</csvFile>
			<id>%id%<<id>%ID%</id>
			<startDateTime>%START%</startDateTime>
<oneToManyRelation id="UPSTREAM">
				<endDateTime>%END%<<relatedLocationId>%RELATION%</endDateTime>relatedLocationId>
			<z>%z%<</z>oneToManyRelation>
			<attribute<relation id="timeDependentAttributeCATCHMENT">
				<text>%timeDependentAttribute%<<relatedLocationId>%CATCHMENT%</text>relatedLocationId>
			</attribute>relation>   
		</attributeFile>
	</csvFile>
</locationSet>

In this example the above database table PEILBUIZEN is read from the database and completely converted to a zipped DBase file, named PEILBUIZEN.dbz. This file is used by FEWS to read all the required data.
To use a Firebird/Derby database file you should use the element <databaseFile> instead of <dbServerName>. Other connection strings:

• jdbc:postgresql://dummy_hostname:port/dummy_databasename
• jdbc:oracle:thin:@dummy_hostname:port/dummy_servicename
• jdbc:oracle:thin:@dummy_hostname:port:SID
• jdbc:oracle:thin:@TNSName
• jdbc:sqlserver://dummy_hostname:port/dummy_databasename

...

esriShapeFile>  

time dependent z (since 2022.01)

...

When using a separate attribute file the z can be time dependent. The z is used for converting a local datum to a global datum (water level).

<locationSet id="LocationSetWithTimeDependentAttributes">
	<csvFile>
		<file>TimeDependentLocationSet.csv</file>
		<id>%id%</id>
		<x>0</x>
		<y>0</y>
		<attributeFile>
			<csvFile>TimeDependentLocationSetAttributes.csv</csvFile>
			<id>%id%</id>
			<startDateTime>%START%</startDateTime>
			<endDateTime>%END%</endDateTime>
			<z>%z%</z>
			<attribute id="timeDependentAttribute">
				<text>%timeDependentAttribute%</text>
			</attribute>
		</attributeFile>
	</csvFile>
</locationSet>

ID;START;END;timeDependentAttribute;z
TD_Loc1;19000101;21000101;A;1
TD_Loc2;19000101;19850103;A;2
TD_Loc2;19850103;21000101;B;3
TD_Loc3;19000101;19850103;B;4
TD_Loc3;19850103;21000101;A;5
TD_Loc4;19000101;19850103;A;6
TD_Loc4;19850103;21000101;B;7
TD_Loc5;19000101;19850103;A;8
TD_Loc5;19850103;21000101;B;9 

using attributes, constraints, relations etc.

...