Page History

...

Currently the GeneralCsv and Database import require a table layout description configured by the user. Non-standard imports (plug-ins) can also required require a table layout. See the third party documentation of the specific import.

There are different types of table structures supported.

• Every parameter has it’s its own column
• Every location has it’s its own column.
• Every qualifier has it’s its own column.
• Every parameter/location/qualifier combination has it’s its own column
• Single value column and a parameter, location, qualifier and unit column to describe the value in the value column.
• All values for a single month a listed in a single row, for every day of month there is separate column.
• All values for a single day listed in a single row, for every time of day there is separate column.
• Variants and combinations of the above are sometimes allowed

...

data time pattern
The date time patterns are handled by the JDK class SimpleDateFormat

Any characters within the date-time stamp can be accommodated by including that character in the pattern, surrounded by single quotes, e.g. <dateTimeColumn name="date_obs" pattern="yyyy-MM-dd'T'HH:mm:ss'Z'"/> allows for reading a date-time column that is formatted as: 2022-03-29T09:30:00Z.

Schema
Image AddedSchema
Image Removed

examples

<table>
   <dateTimeColumn name="Time" pattern="dd-MM-yyyy HH:mm"/>
   <valueColumn unit="m" locationId="Bosscheveld" parameterId="H.meting" name="Waterstand"/>
   <valueColumn unit="min" locationId="Bosscheveld" parameterId="DT.meting" name="Pomp-1 Born"/>
</table>

...

<table name="StageList">
  <dateTimeColumn name="InDate"/>
  <valueColumn name="Shemen" locationId="HS03" unit="m" parameterId="H.obs"/>
  <valueColumn name="Clouds" locationId="HS02" unit="m" parameterId="H.obs"/>
  <valueColumn name="High" locationId="1140H043" unit="m" parameterId="H.obs"/>
  <valueColumn name="Angle" locationId="1140H002" unit="m" parameterId="H.obs"/>
  <valueColumn name="Jade" locationId="HS01" unit="m" parameterId="H.obs"/>
  <valueColumn name="Show" locationId="1140H041" unit="m" parameterId="H.obs"/>
  <valueColumn name="Kide" locationId="HS04" unit="m" parameterId="H.obs"/>
</table>

<table>
	<dateTimeColumn pattern="dd-MM-yy HH:mm"/>
	<locationColumn name="Location"/>
	<parameterColumn name="Parameter"/>
	<flagSourceColumn name="A" id="A"/>
	<flagSourceColumn name="B" id="B"/>
	<flagSourceColumn name="C" id="C"/>
	<flagSourceColumn name="D" id="D"/>
	<flagSourceColumn name="E" id="E"/>
	<valueColumn name="Value"/>
</table>

Sample, properties and qualifiers example

Since 2014.02 it is possible to use sampleIdColumn (normal ComplexColumnType with just name attribute), propertyColumn (with mandatory key attribute) and attribute column (with mandatory id attribute) which can only be used for export since attributes can not be imported but only configured. qualifierColumn is extended with the optional prefix attribute which will be added in front of the external qualifier id, this can be useful for id mapping. 

Below configuration is shown which can import sample data, with properties and multiple qualifiers. In case sample data is imported the properties will be automatically used for the sample instead of the time step.

...

The qualifier columns use the prefix again, to recognise from the external id which qualifier should be put in the column. When the qualifier is found, the prefix will be stripped from the external id.

...