Here you have all the specifications for pipe’s properties and how to modify them both in GIS editor and EPANET. Check this table to see all accepted aliases for each property.
Qatium will process that information by running some validation checks and we’ll try to fill any gaps.
Learn more about how Qatium works in this article.
More details about EPANET specifications here.
Status
Data you add to your files
GIS editor | |
---|---|
Field | Status |
Attribute |
Open Closed CV |
EPANET | |
---|---|
Property | Initial Status |
Value |
Open Closed CV |
How Qatium processes that data
If there's no data or it doesn't pass the validation stage, Qatium will apply a default value: Open.
You can also modify the pipe’s status directly in Qatium using the Shutdown panel. But bear in mind that this state won’t persist in your network as it’s just an imaginary scenario.
Laterals
Data you add to your files
GIS editor | |
---|---|
Field | Group |
Attribute | lateral |
EPANET | |
---|---|
Property | Description |
Value | lateral |
Download the GIS file example in the additional resources for a demo of the data to include.
How Qatium processes that data
If there's no data or it doesn't pass the validation stage, Qatium will apply a default value: Main.
If you include laterals in your network, you can also add customer points, even if they are not directly connected to them.
Notes:
You can also specify laterals directly in the .inp file using a text editor. Edit the file including the group in the description or in the extra properties column that appears on fifth position. Example: DI_20220706_1.2_12.5_lateral;aDescription
Material
Data you add to your files
GIS editor | |
---|---|
Field | Material |
Attribute | Material name* |
EPANET | |
---|---|
Property | Description |
Value |
[Material]_[other information] Example: DI_20220706 |
How Qatium processes that data
If not specified, Qatium will ignore it.
Installation date
Data you add to your files
GIS editor | |
---|---|
Field | Installation date |
Attribute | YYYYMMDD |
EPANET | |
---|---|
Property | Description |
Value |
YYYYMMDD Example: DI_20220706 |
How Qatium processes that data
If not specified, Qatium will ignore it.
Length
Data you add to your files
GIS editor | |
---|---|
Field | Length |
Attribute | <number> |
EPANET | |
---|---|
Property | Length |
Value | <number> |
How Qatium processes that data
If there's no data or doesn't pass the validation stage, Qatium will apply default values. Here, the default value for length will be calculated from the pipe geometry.
Qatium uses the turf.js library to do so, without taking into account the elevation of each vertex. The length is rounded to 2 decimal places for both systems of units.
Diameter
Data you add to your files
GIS editor | |
---|---|
Field | Diameter |
Attribute | <number> |
EPANET | |
---|---|
Property | Diameter |
Value | <number> |
How Qatium processes that data
If there's no data or doesn't pass the validation stage, Qatium will apply a default value:
SI units | US units |
---|---|
50 mm | 2 in |
Roughness & headloss equation
Data you add to your files
GIS editor | |
---|---|
Field | Roughness |
Attribute | <number> |
EPANET | |
---|---|
Property | Roughness |
Value | <number> |
How Qatium processes that data
The equation (H-W, D-W or C-M) is inferred from roughness values (if available). If not, we’ll apply the default value: Hazen-Williams (H-W), roughness = 148.
Qatium can also infer roughness from Material and Installation date, if available.
Learn more about how Qatium infers roughness based on material and installation date in this article.
Minor loss
Data you add to your files
GIS editor | |
---|---|
Field | Loss coefficient |
Attribute | <number> |
EPANET | |
---|---|
Property | Loss coefficient |
Value | <number> |
How Qatium processes that data
If there's no data or it doesn't pass the validation stage, Qatium will apply a default value: 0.
Flow & velocities
If you want to add historical data or readings to provide actual flow and velocity, read this article.
Simple controls
In both .inp and GIS files, Qatium supports 3 kinds of simple controls as defined in EPANET for pipes, valves, and pumps. You can also include your controls in a field named [“control ”, “controls ”].
In GIS files only, Qatium also accepts a short version of controls, consisting of the element type and ID followed by a list of its different settings:
Element properties: OPEN AT TIME 3
Will be interpreted as ELEMENT OPEN AT TIME 3
If you specify these controls for all assets in just one asset’s properties, they will apply to every specified asset regardless of the location of the control.
For example:
Pipe 1 properties: Pipe 1 OPEN AT TIME 3, Valve 2 CLOSED AT TIME 2, Valve 2 OPEN AT TIME 3
Will apply both to Pipe 1 and Valve 2, regardless of the valve’s control being in the pipe’s properties.
Qatium accepts multiple control separators: tab, comma, semicolon, break line. If a control is not valid, it will not be applied to the model. Instead, it will be shown as a comment in the .inp file.
Connecting pipes at T-junctions
If one end of the pipe (not connected to another) spatially coincides with another pipe, the latter is split and a junction is added at the intersection.
The two resulting pipes inherit the properties of the original split pipe; only the length of each section is recalculated (proportionally to the original one).
In this case, a tolerance of 0.1 m is used and the ends of the new pipes are extended to the end of the pipe that generates the split. Normally, these extensions are not noticeable on the map.
Thresholds
Configure warnings by setting minimum and maximum thresholds for your assets. We'll let you know you if data falls below or above these limits.
To set thresholds, upload a .CSV file including the following columns:
Column label | Asset | Property | Min | Max | Unit |
Type of data | <string> | <string> | <number> | <number> | <string> |
- Asset: the asset ID.
- Property: could be flow, pressure, or level, for example.
- Min: the threshold minimum value.
- Max: the threshold maximum value.
- Unit: of the property.
For example:
asset,property,min,max,unit
J_00028,pressure,10,60,kPa
J_00029,pressure,10,60,kPa
Make sure the units for the threshold values match the units of the variable we're setting the warnings to:
- Pipe flow = flow unit
- Tank level = level unit
- Junction pressure = pressure unit
How Qatium processes that data
If not specified, Qatium will ignore it and you won’t receive any warnings.