Follow these specs to specify your valves’ type, their status, and/or edit their properties.
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.
Type
Shut-off valves
Data you add to your files
| GIS editor | |
|---|---|
| Field | Type |
| Attribute | TCV |
| EPANET | |
|---|---|
| Property | Type |
| Value | TCV |
How Qatium processes that data
If not specified, Qatium will apply a default value: TCV.
Regulating valves
Data you add to your files
| GIS editor | |
|---|---|
| Field | Type |
| Attribute |
PBV FCV PSV PRV GPV |
| EPANET | |
|---|---|
| Property | Type |
| Value |
PBV FCV PSV PRV GPV |
How Qatium processes that data
If not specified, Qatium will apply a default value: TCV.
Setting
Data you add to your files
| GIS editor | |
|---|---|
| Field | Setting |
| Attribute | <number> |
| EPANET | |
|---|---|
| Property | Setting |
| Value | <number> |
How Qatium processes that data
If not specified, it will be ignored and the Status will be Active.
Status
Shut-off valves
Data you add to your files
| GIS Editor | |
|---|---|
| Field | Status |
| Attribute |
Active Open Closed |
| EPANET | |
|---|---|
| Property | Fixed Status |
| Value |
None Open Closed |
How Qatium processes that data
If not specified, Qatium will apply a default value: Active/Open.
Regulating valves
Data you add to your files
| GIS Editor | |
|---|---|
| Field | Status |
| Attribute |
Active Open Closed |
| EPANET | |
|---|---|
| Property | Fixed Status |
| Value |
None Open Closed |
How Qatium processes that data
If not specified, Qatium will apply a default value: Open (or active–regulating, in case there’s a setting property).
You can also modify the valve’s status directly in Qatium while performing scenarios. But bear in mind that this change won’t persist in your actual network.
Diameter
Data you add to your files
| GIS editor | |
|---|---|
| Field | Diameter |
| Attribute | <number> |
| EPANET | |
|---|---|
| Property | Diameter |
| Value | <number> |
How Qatium processes that data
If not specified, Qatium will apply a default value:
| SI units | US units |
|---|---|
| 200 mm | 8 in |
Terrain elevation
For GIS datasets, Qatium processes elevation data when it's included as an attribute in point assets, like junctions, tanks, supply sources, valves, and pumps.
Data you add to your files
| GIS editor | |
|---|---|
| Field | Elevation |
| Attribute | <number> |
In EPANET, to update elevation data for line assets — such as valves and pumps —, you need to edit the elevation of the upstream and downstream junctions connected to them.
Data you add to your files
| EPANET | |
|---|---|
| Property | Elevation (of the upstream and downstream connected junctions) |
| Value | <number> |
How Qatium processes that data
If not specified: Qatium will add it from Mapbox elevation data.
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:
Pipe1 properties: Pipe1 OPEN AT TIME 3, Valve2 CLOSED AT TIME 2, Valve2 OPEN AT TIME 3
Will apply both to Pipe1 and Valve2, 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.
Orientation
To define the orientation, we recommend defining the upstream pipe in your pump and valve layers as it limits inferences.
Data you add to your files
| GIS editor | |
|---|---|
| Field | Upstream |
| Attribute | Upstream pipe ID |
| EPANET | |
|---|---|
| Property | Start node / End node |
| Value | Upstream and downstream nodes ID |
How Qatium processes that data
If not specified, Qatium will calculate orientation. Learn more in this article.