Here you have all the specifications for the pump’s properties and how to modify them both in GIS files and EPANET. Check this table to see all accepted aliases for each property.
Qatium will process your data by running some validation checks and we’ll try to fill any gaps. Learn more about how Qatium works in this article.
Status
Data you add to your files
GIS editor | |
---|---|
Field | Status |
Attribute |
Open Closed |
EPANET | |
---|---|
Property | Initial Status |
Value |
Open Closed |
How Qatium processes that data
If not specified, Qatium will apply a default value: Open.
The pump’s status in Qatium reads On (for open) and Off (for closed).
Relative speed
Data you add to your files
GIS editor | |
---|---|
Field | Speed |
Attribute | <number> |
EPANET | |
---|---|
Property | Speed |
Value | <number> |
How Qatium processes that data
If not specified, Qatium will ignore it.
Power
Data you add to your files
GIS editor | |
---|---|
Field | Power |
Attribute | <number> |
EPANET | |
---|---|
Property | Power |
Attribute | <number> |
How Qatium processes that data
If neither the Power nor the Operating curve is specified, Qatium will apply a default value for Power: 0.01 kW.
Operating curve (head curve)
Data you add to your files
GIS editor | |
---|---|
Field | pump_curve |
Attribute | x1 y1;x2 y2;x3 y3, etc. |
EPANET | |
---|---|
Property | Pump Curve |
Value | x1 y1;x2 y2;x3 y3, etc. |
The format of the curve must be: x1 y1;x2 y2;x3 y3... Where x is related to flows and y is related to heads. The ; (semi-colon) separates different point curves and a space separates the x and y values.
x | flow |
Example: x1 y1;x2 y2;x3 y3 |
---|---|---|
y | head | |
; | separates different point curves | |
[space] | separates x and y values |
As it is something mandatory in Epanet, we define an ID for the pump curve. In this case, we use the asset ID + _HC.
For example: if the pump ID is P_Mandalorian we create a curve with the ID P_Mandalorian_HC.
How Qatium processes that data
If the curve is not specified and the Power property is not defined by the user, Qatium assigns a default value for the Power (0.01 kW). Curves don’t have default values.
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 you have defined both height and elevation for your pumps in the corresponding file, the result will be the sum of both. Otherwise, Qatium will define the elevation using the 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:
Pipe 1 properties: Pipe 1 OPEN AT TIME 3, Pump 2 CLOSED AT TIME 2, Pump 2 OPEN AT TIME 3
Will apply both to Pipe 1 and Pump2, regardless of the pump’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
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.