Flow Survey Data - CSV File Format

The following Flow Survey time varying data events can be imported from CSV file format:

Depth
Flow
Velocity

This topic describes the appropriate format for these files.

Below is an example of a Flow Survey Depth event that has been exported from InfoWorks ICM to CSV format by right clicking on the event and choosing Export | to CSV from the popup menu.

Click on the image below to reveal the flow survey depth event CSV example.

The use of field headers allows for flexibility in the ordering of fields and permits fields to be easily omitted if desired.
Units specification is optional. If the units are not specified then they are assumed to be the current user display units.
Subevent Properties and Profile Properties are specified in the "Global" and "Local" rows of the file.
An optional date/time column alongside the time varying value columns may be included. InfoWorks ICM derives the timestep from the relative values in the date/time column and inserts subevents at any point where the timestep changes.
If the date/time column is not used, a fixed timestep and a start date must be specified. Multiple events can be imported from one CSV file; for each subevent include "Global" and "Local" rows before the sub-event values.

CSV File Headers

File Header Row

Description

UserSettings

UserSettingsValues

Units and date-time format are specified in these fields. Units supported by InfoWorks ICM may be specified.

Where units are not specified, InfoWorks ICM assumes values in the csv file are in the current display units.

Field Header	Field value
U_LEVEL	Depth Data only: Determines the units for both Invert Level and Ground Level fields
U_CONDHEIGHT	Depth Data only: Determines the units for Height of Conduit field
U_VALUES	Observed values units
U_DATETIME	The value of U_DATETIME may be one of three options: dd-mm-yyyy mm-dd-yyyy yyyy-mm-dd Dates in the csv file will be interpreted using this date/time format

Sub-Event Properties

The fields describing sub-event (global) properties are as below.

G_NPROFILES, G_TS and G_START

The G_NPROFILES field is mandatory. If this field is incorrect, data will not be imported as expected. At least one of G_TS (the timestep value) and P_DATETIME (the date-time column) must be provided. If both are present the G_TS value is used in conjunction with the G_STARTvalue to determine hydrograph timesteps and start time.

Field Header

Sub-Event Property

G_START

Start date

G_TS

Hydrograph Time Step in the format <n>[<u>], where <n> is an integer greater than zero and <u> is an optional unit specifier (representing seconds, minutes, hours and days respectively), e.g. 10m = 10 minutes.

If <u> is not specified, a unit of seconds is assumed.

G_NPROFILES

Mandatory field.

Number of profiles in the sub-event

Profile Properties

The lines describing profile (local) properties are optional. If the csv files contains local properties field headers, a line for each profile must be included in the file (even if this is an empty line).

Depth Data

Field Header	Profile Property
L_LINKID	Label of the link where the data originated. This link may be from another model, or a real link where the data was measured.
L_INVERTLEVEL	Invert level of the link where the data originated
L_CONDHEIGHT	Height of the conduit where the data originated
L_GROUNDLEVEL	Ground level for the link where the data originated
L_PTITLE	Descriptive title

Discharge Data

Field Header	Profile Property
L_LINKID	Label of the link where the data originated. This link may be from another model, or a real link where the data was measured.
L_CONDCAPACITY	Pipe full capacity of the link where the data originated
L_PTITLE	Descriptive Title

Velocity Data

Field Header	Profile Property
L_LINKID	Label of the link where the data originated. This link may be from another model, or a real link where the data was measured.
L_PTITLE	Descriptive title

P_DATETIME

Profile index

The P_DATETIME (date-time) column is optional, but if present must be on the left hand side of the event values.

At least one of G_TS(the timestep value) and P_DATETIME must be provided. If G_TS value is not provided the P_DATETIME column will be used to deduce values for the subevent start time and timesteps.

Subevents will be automatically created where changes in timestep intervals occur in the P_DATETIME column.

The numbers following P_DATETIME in the header row number the profiles starting from 0.

Events - CSV File Formats

Importing Flow Surveys