Versions Compared

Key

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

Overview

Imports time series data from the Microsoft Access database file.

...

There is no flag column when data type is digital?

Status

Both analog and digital data format can be used.

...

Jira Issues
urlhttp://issues.wldelft.nl/jira/secure/IssueNavigator.jspa?view=rss&&query=tmx&summary=true&description=true&body=true&sorter/field=status&sorter/order=ASC&tempMax=25&reset=true&decorator=none

Configuration (Example)

The configuration files below define import of 4 time series from the tmx .mdb file:

...

Info
titleNote

Tmx database (mdb) may contain data for both digital and analog types of data.
When data are in analog format they usually stored in tables which names are defined using location and parameter name, e.g.: Loc063Ao1, Loc063Ai1. In case of digital format everything is stored in one table, e.g.: ReportAo

ModuleConfigFiles/

Time series which are listed in this file can be imported into fews.

...

Code Block
xml
xml
titleImportTmx.xml
<?xml version="1.0" encoding="UTF-8"?>
<timeSeriesImportRun xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews/schemas/version1.0/timeSeriesImportRun.xsd">
	<import>
		<general>
			<importType>Tmx</importType>
			<folder>../junit_test_output/nl/wldelft/fews/system/plugin/dataImport/TimeSeriesImportTestData/import/tmx</folder>
			<idMapId>tmxMapId</idMapId>
			<importTimeZone>
				<timeZoneOffset>+01:00</timeZoneOffset>
			</importTimeZone>
		</general>


		<!-- Analog, table = Loc063Ai1 -->
		<timeSeriesSet>
			<moduleInstanceId>ImportTmx</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>P1.m</parameterId> <!-- parameter = Ai1 -->
			<locationId>tmx_location1</locationId> <!-- location = Loc063 -->
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="minute" multiplier="15"/>
			<relativeViewPeriod unit="day" start="0" end="11"/>
			<readWriteMode>add originals</readWriteMode>
		</timeSeriesSet>
    
		<!-- Analog, table = Loc063Ao1 -->
		<timeSeriesSet>
			<moduleInstanceId>ImportTmx</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>P2.m</parameterId> <!-- parameter = Ao1 -->
			<locationId>tmx_location1</locationId> <!-- location = Loc063 -->
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="day" multiplier="1"/>
			<relativeViewPeriod unit="day" start="0" end="11"/>
			<readWriteMode>add originals</readWriteMode>
		</timeSeriesSet>

		<!-- Digital, table = ReportAo, defined in the mapping -->
		<timeSeriesSet>
			<moduleInstanceId>ImportTmx2</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>P3.m</parameterId> <!-- Channel = 1 -->
			<locationId>tmx_location2</locationId> <!-- LocCode = 46 -->
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="day" multiplier="1"/>
			<relativeViewPeriod unit="day" start="400" end="470"/>
			<readWriteMode>add originals</readWriteMode>
		</timeSeriesSet>

		<!-- Digital, table = ReportAo, defined in the mapping -->
		<timeSeriesSet>
			<moduleInstanceId>ImportTmx</moduleInstanceId>
			<valueType>scalar</valueType>
			<parameterId>P3.m</parameterId> <!-- Channel = 1 -->
			<locationId>tmx_location3</locationId> <!-- LocCode = 51 -->
			<timeSeriesType>external historical</timeSeriesType>
			<timeStep unit="day" multiplier="1"/>
			<relativeViewPeriod unit="day" start="400" end="470"/>
			<readWriteMode>add originals</readWriteMode>
		</timeSeriesSet>
	</import>
</timeSeriesImportRun>

IdMapFiles/

Info

Defines mappings between TMX and FEWS parameters and locations.

...