GisWater Documentation

Documentation http://www.old.giswater.
org/en/print/book/export/html/17
Published on Giswater (http://www.old.giswater.org)

Home > Documentation
Documentation
(English version only)
Disclaimer:
Mention of trade names or commercial products does not constitute endorsement or recommendation for use. Although It has been subjected to technical review
before being released and although it has made a considerable effort to assure that the results obtained are correct, the computer programs are experimental.
Therefore the author are not responsible and assume no liability whatsoever for any results or any use made of the results obtained from these programs, nor for
any damages or litigation that result from the use of these programs for any purpose.
CHAPTER 1. INTRODUCTION [1]

1.1 What is Giswater? [2]
1.2 Project web sites [3]
1.3 Quick references [4]
1.4 Giswater capabilities [5]
1.5 License [6]
CHAPTER 2. GETTING STARTED [7]

2.1 Software requeriments [8]
2.2 Installing Giswater [9]
2.3 Software configuration [10]
2.4 Database connection [11]
2.5 Creating and managing samples [12]
2.6 Giswater menu [13]
2.7 Administration [14]
CHAPTER 3. WATER SUPPLY USER'S GUIDE [15]

3.1 Notes on network topology [16]
3.2 Database data storage [17]
3.3 DBF data storage [18]
3.4 EPANET Giswater menu [19]
CHAPTER 4. URBAN DRAINAGE USER'S GUIDE [20]

4.1 Notes on network topology [21]
4.2 Database data storage [22]
4.3 DBF data storage [23]
4.4 EPA SWMM Giswater menu [24]
CHAPTER 5. RIVER ANALYSIS USER'S GUIDE [25]

5.1 Introduction [26]
5.2 [27]Quick start tutorial [27]
5.3 [28]Software overview [28]
5.4 References [29]
APPENDIX A - DATABASE GIS PROJECTS [30]
APPENDIX B - DBF DATA MODEL SPECIFICATIONS [31]
APPENDIX C - USEFUL TABLES [32]
APPENDIX D - ERROR AND WARNING MESSAGES [33]
APPENDIX E - BUGS [34]
[35]
Giswater documentation is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License [35].
Last updated: Feb 10, 2015. Version code: 1.1.beta
Стр. 1 из 16 03.03.2018, 12:27

Documentation http://www.old.giswater.org/en/print/book/export/html/17
CHAPTER 1. INTRODUCTION
1.1 What is Giswater?
Giswater is an open software project with the goal of moving from acquired knowledge to shared knowledge in the areas of water supply management, sewerage management,
urban drainage management and river hydraulics. Thanks to Giswater today it's possible to manage spatial data in order to communicate with EPANET or EPA SWMM. In addition
it's also possible to create a SDF file (a standard DEM file) which it's possible to use in order to import terrain data from GIS to other GIS tools or analysis tools such as HEC-RAS.
In some cases the communication could be bi-directional and by this way, the result data modeled from this programs could be stored, indexed and consulted into the spatial
database.
A case scenario enables these 'hydro-programs' with a powerful GIS interface, and lays the foundation for achieving management, full operability of water supply systems,
sewerage systems, drainage networks and rivers using Web Map Services (WMS), System Control and data Acquisition (SCADA) or Customer Relationship Management Systems
(CRMS).
The versions of the code are released under GNU GENERAL PUBLIC LICENSE. (GPL v3), but it is subordinate to the License Agreements of the constituent software packages.
These may be more or less restrictive than the GNU GPL v3. Please ensure that you agree with the terms of all the licenses before using this software- these can be found in the
folders for the constituent programs.
1.2 Project web sites

Giswater project:
Web site: www.giswater.org [36]
Source code: https://github.com/giswater/giswater [37]
Youtube: http://www.youtube.com/channel/UCuuFlmjnu3HWVrXcyO3I-ow/videos [38]
Remember: Giswater runs with a Java Runtime Environment (JRE) installed and updated on your computer.
1.3 Quick references

POSTGRESQL. http://www.postgresql.org/ [39] with geospatial extension POSTGIS 2.0 http://postgis.net/ [40]. Open source object-relational database management system
(ORDBMS) with an emphasis on extensibility and standards compliance. Giswater is connecting POSTGRESQL with EPA and HEC programs and by this way these programs are
also connected with any Geographic Information System (GIS) drived to POSTGRESQL.
JAVA. Is a general-purpose high programming language and a powerful software platform. It allows the same program to be executed on multiple operating systems,it uses object
oriented programming methodology and it contains built in support for computer networks and is easy to use. Actually billion devices use JAVA, and Giswater needs to run a Java
Runtime Environment (JRE).
1.4 Giswater capabilities

Giswater allows the following communication framework:
Urban Drainage - Compatible with EPA SWMM version 5.0.022
DBF to INP and RPT to DBF, full capabilities
DB to INP and RPT to DB, full capabilities
Water Supply - Compatible with EPANET version 2.0012
DBF to INP and RPT to DBF, full capabilities
DB to INP and RPT to DB, full capabilities
River analysis - SDF compatible with HEC-RAS
DBF to INP: Not alloved
DB to SDF: 'Pre-Ras' capabilities
Data storage
DBF: Shape file and DBF file
DATABASE: PostgreSQL with PostGIS 2.0 or higher
1.5 License
This product as a whole is distributed under the GNU General Public License version 3, but it is subordinate to the License Agreements of the constituent software packages. These
may be more or less restrictive than the GNU GPL v3, but it is subordinate to the License Agreements of the constituent software packages. These may be more or less restrictive
than the GNU GPL v3.
Please ensure that you agree with the terms of all the licenses before using this software- these can be found in the folders for the constituent programs.
You can see <http://www.gnu.org/licenses/> [41].
Стр. 2 из 16 03.03.2018, 12:27

CHAPTER 2. GETTING STARTED

2.1 Software requeriments
To enjoy full capabilities of Giswater, you need this software installed on your computer running under the W indows 7, Windows Vista, Windows 8 and W indows 10.
Windows XP is not supported.
- EPANET (version 2.0.12) [42]
Source code: EPA United States Environmental Protection Agency
- EPA SWMM (version 5.0.022 or higher) [43]
Source code: EPA United States Environmental Protection Agency
- HEC-RAS (version 4.1 or higher) [44]
Source code: US Army Corps of Engineers
- Java Runtime Environment (JRE) installed and updated [45]
Source code: Oracle corporation
- Text editor installed and configured
If you use Giswater on database data storage, you also need QGIS. On the other hand, if you only run Giswater on DBF data storage, you can use any GIS you like. We
recommend open source GIS software as gvSIG or QGIS.
2.2 Installing Giswater

Giswater is designed to run under the Windows 7, Windows Vista, Windows 8 and W indows 10. (*)
(*) Giswater is not supported running under Windows XP
To install you must download the installer package and execute it. Remember you can choose the Giswater stand-alone install package or the all-in-one install package [46]. The
all-in-one installer package is designed with a portable version of PostgreSQL+PostGIS 2.1.
If you already have installed PostgreSQL+PostGIS 2.0 or higher, you can download the stand-alone install package [47]. Otherwise, if you don't have PostgreSQL+PostGIS 2.0 or
higher, and you don't like it, you can download Giswater stand-alone install package and use it on DBF mode. Not all capabilities of Giswater are allowed in DBF mode.
Remember you need to have installed an updated Java Runtime Environment (JRE) on your computer.
If you have the correct JRE, automatically, Giswater will run under it. If not, you must install the correct JRE (you must download it from the java project website) or if you have
more than one JRE, you must associate it to the correct one.
ERROR: 'Could not find the main class: org.Giswater.gui.MainClass program will exit' is showing us JRE need to be updated.
You can download the latest release of Java JRE from the website of the project, and to associate it, you must go to the Windows Control Panel\Programs\Default Programs\Set
Associations (associated a file type or protocol with a specific program) and you must associate jar extension file with the correct JRE.
2.3 Software configuration

In this chapter you will find information on how to configurate giswater and all the software needed. Giswater → Configuration → Software configuration. Remember we
recommend EPANET and EPA SWMM programs installed on your computer.
Here you can configurate different parameters of the software, and also you can define where is your DB administrator in order to integrate with Giswater
In addition, you need a text editor installed and configured to open by default (.rpt) and (.inp) files. We recommend notepad++(www.notepad-plus-plus.org [48])
2.4 Project preferences

On Giswater → Configuration → Project preferences you will found all you need to configurate your project. Parameters as Water Software, Data Storage, Project Data
Management could be defined here..
Remember that if you are using the Giswater all-in-one installer package, this Database connection will be automatically configured with the correct parameters.
2.5 Creating and managing samples

With Giswater it is easy to create samples in order to practice before starting a real case. This option is only available on database data storage mode. You must follow the next
steps:
1- Create a new Project Preferences
2- Create a Water Supply, Urban Drainage or River Analisys example (Giswater → Project example) and Giswater will create a Project Data Schema into database and will
introduce the data of a sample case.
2- Create GIS project: Giswater will generate a GIS project with sample data.
3- Start GIS software and enjoy it!
2.6 Giswater menu

The Giswater menu options are:
File
In this menu you will found options to manage, the Giwater files (Project preferences file and Project data file).
Giswater project preferences file is a file with *.gsw extension. By creating this file you will store information about your project: water software, data storage, connection and
project propierties.
Giswater project data file is a file with *.sql extension and contains all the data of your project in a Standard Query Language.
Project preferences
Water software
You must configure your Giswater project in combination with EPANET, EPA SWMM or HEC-RAS. You must select one in order to preceed with your project.
Database Storage
You must select your storage mode (DBF or DB). We prefer DB mode!!!!
Connection parameters
If you have selected DB mode, you must to configurate the connection parameters Specifies parameters of database connection the default PostgreSQL driver. The parameters
are: IP address, Port, Database, User and Password.
Project Data (scheme) Management
If you are working in a project on Database storage format, here you can manage your data. You can Create, Delete, Rename or Copy project data schemas on your database.
This option will only serve us for Database data storage mode. You can find different options are explained below:
Create Schema: Create a schema with which, among other things, serve to create a GIS project without some data.
Rename Schema: You can rename a schema created before.
Delete Schema: You can delete a schema created before.
Copy Schema: You can copy from one scheme to other
Create Gis Project
This option menu creates a GIS project. You can choose from the following parameters: Project folder and project name, water software, data storage and schema name (if
database data storage is selected).
DBF data storage is not allowed on GIS HEC-RAS projects. If DBF data storage is selected, only shape file and DBF tables of EPANET or EPA SWMM will be created. You can
choose GIS software if you like and proceed to add these layers and tables on the table of contents (gvSIG, QGIS or ArcGIS). If database data storage is selected, a QGIS project
will be created.
Project data
Restore project data
This option allows you to restore data into schema from sql data file
Backup project data As
This option allows you to create a backup file of your data in order to share, keep or edit this information
Project example
There is a possibility of creating a new GIS project or having the support of an illustration created for consulting.
Water supply
This option menu creates an EPANET scheme with sample data. In this way users can train and get started with a simple case.
Urban drainage
This option menu creates an EPA SWMM 1D model schema with sample data. In this way users can train and get started with a simple case.
Urban drainage 2D
This option menu creates an EPA SWMM 1D/2D model schema with sample data. In this way users can train and get started with a simple case.
River analysis
This option menu creates a HEC-RAS scheme with sample data. In this way users can train and getting started with a simple case.
Data
Database administrator
If you have configurated the database administrator option, by clik on this menu your database administrator will be opened
SQL file launcher

This option allows you the possibility to execute a SQL sentence aplied to your project (with the connections parameters).
Only you can do is open your browser and select what is the file you need.
Configuration
The getting started steps are specified here.
Software configuration
In this configuration we can predefine several program options.
Automatic start Postgis portable: When the option is ENABLED, Giswater automatically starts working with portable Postgis that it's integrated into the program.
Database automatic connection: When the option is ENABLED, Giswater automatically connect the database with specified connection parameters.
DB Admin: By default, the program management databases is pgAdmin, but it can be changed if another is preferred.
About
On this Giswater menu section you will find information about Giswater version you are using, software license, user's manual, technical references, project website, agreements
and others....
2.7 Administration
2.7.1 Database administration
To administrate the Database you can use Giswater menu-Project- Database Administrator. [49]
To configure which DBadministrator you would like to use, you can configurate this option in Giswater menu-Configuration-Software configuration [50].
2.7.2 Log and SQL files

When you install Giswater both stand-alone or all-in-one, the installer creates one folder on user's path with name Giswater. Into this folder you will find the log folder. Giswater uses
this log folder in order to store log information and SQL information (if you have enabled this option). We recommend you keep this. In order to manage this, you can configure
Giswater to notice you when the data folder size exceed size you have set.
Стр. 3 из 16 03.03.2018, 12:27

CHAPTER 3. EPANET USER'S GUIDE

This provides a tutorial on how to use Giswater with EPANET.
If you are not familiar with the components that comprise a water distribution network and how these are shown in a pipe network model, you might want ot consider taking a look at
the first two sections of Chapter 3 - EPANET's user's manual.
However, if you are familiar with the components that comprise a water distribution network and how these are shown in a pipe network model, you must review the APPENDIX C
of EPANET's user's manual.
3.1 Notes on network topology

GIS network will be created according to an arc-node topology. Arc-node topology has four basic rules. The following rules apply:
1. Nodes are the main elements of the network. They are POINT geometry type
2. Arcs join the Nodes and the start point and endpoints are called Node1 and Node2. They are LINESTRINGS geometry type.
3. Points (optional) along an arc that define its shape are called Vertices. They are POINT geometry type.
4. Every Arc has a direction (same or not as the hydraulic direction)
3.2 Database data storage

This provides a tutorial on how to use Giswater with EPANET with Database data storage. In order to activate this data storage mode go to: Giswater → Project preferences →
Data storage: Database
3.2.1 Quick start tutorial

A simple case can be performed following the steps below:
1) Start the project by creating the new project preferences file: File → New project preferences
2) Select the Water software: EPANET
3) Select the Data storage: Database
4) Configurate the connection parameters
5) Create a new project data scheme: Fill the project name,the project title and select the SRID.
6) Create the GIS project: Fill in the information for project folder and project name.Also choose the water software and the data storage (in this case EPANET and data storage),
and finally select the scheme name necessary.
7) Click on Accept on the Project Preferences menu
8) Select US or metric units: Options → flow units. Choosing US flow unit; this means that all other quantities of the project will be expressed in US units, while choosing a metric
flow unit will force all quantities to be expressed in metric units.
8) Complete the material catalogue at least with one record: Material catalog. The default formula used for computing head loss for flow through a pipe is Hazen-Williams (H-W). It
can be seen that in the EPANET's user manual,it explains how to determine the roughness value. In addition, this can be changed to the Head loss formula from: Options → Head
loss.
9) Open GIS project and build the network which should contain the next layers:
GIS PROJECT – Sector. You must create at least one sector.

EPANET DATA – Hydraulics - Node - Reservoirs. You must create and edit at least one reservoir. See APPENDIX C – EPANET users manual (JUNCTIONS and RESERVOIRS
target) for more information.
EPANET DATA – Hydraulics – Node - Junctions. You must create and edit the junction records of your network. See APPENDIX C – EPANET users manual (JUNCTIONS target)
for more information.
EPANET DATA – Hydraulics - Arc - Pipes. You must create and edit the pipe records of your network (joining the different nodes). See APPENDIX C – EPANET users manual
(PIPES target) for more information.
10) Configure INP file additional parameters. You can define how many sectors will be simulated: Sector selection, and configure the simulation options, times and report data:
Options / Times / Report.
11a) Generate INP file: export INP checkbox. In this way, Giswater driver will create a text file (inp extension) stored on the selected folder.
11b) Execute the command line EPANET: Execute EPA software checkbox. Giswater will execute the command line EPANET file with the inp file, and EPANET will generate two
result files (*.rpt file and *.out file.) stored on the selected folder.
11c) Import Results (optional): Import results check box. Giswater will read the result data stored on rpt file and will write the values on the schema result tables with the project
name selected.
12) Returns to the GIS project and enjoy the simulation's results on the different shapes and tables of SIMULATION ANALYSIS.
3.2.2 Database key relations

Key relations between features and tables should be mentioned at this point.
First of all, the key relations from ARC and NODE to other tables are defined as 'on delete cascade on update cascade.' This means that if you delete one feature from these
tables, all related features from other tables will be deleted. On the other hand if you update values from these tables, values in all related features will be updated in cascade too.
Further, key relations from SECTOR and MATERIAL are defined 'on delete restrict on update cascade'. This is quite different from the previous one, because it means that you can
not delete used features from these tables. On the other hand, if you update values from these tables, values in all related features will be updated in cascade too.
The rest of features do not have relations. Elements as EMITTERS, ENERGY, STATUS, CONTROLS, RULES, DEMANDS, CURVES, PATTERNS, QUALITY, REACTIONS,
SOURCES, MIXING do not have key relations from theirs to other tables. In this way you must know that If you update features, the values will not be updated on related tables (if
they exist) and if you delete features, mentioned on related tables will not be deleted (if they exist too).
3.2.3 Database sequences

Sequences are an interesting option of databases as PostreSQL. They are autonumeric and they can be used in order to facilitate the work on several tables. Enjoy it!!
3.2.4 Additional information

For more information about the GIS Table Of Contents (TOC) of EPANET project, please visit the EPANET section of APPENDIX A - DATABASE GIS PROJECTS [51]
3.3 DBF data storage

This provides a tutorial on how to use Giswater with EPANET on DBF data storage. In order to activate this data storage mode: Project preferences → Data storage: DBF
WARNING: Full capabilities are not allowed on DBF storage mode !!!

A simple case can be performed following the steps below:
1) Create the new project preferences file
2) Select the water software: EPANET
3) Select the Data storage: DBF and define the data folder
4) Create a GIS project: Fill in the file folder and file name, check DBF data storage and a group of Shape file and DBF will be created. Finally choose the GIS program you prefer
and buid your own project.
5) On the GIS project, build your network according the topology rules.
You must create and edit at least one node as reservoir. See APPENDIX C – EPANET users manual (JUNCTIONS and RESERVOIRS target) for more information. The rest of
nodes will be juction or tanks. See APPENDIX C – EPANET users manual for more information.
You must create and edit the arcs as pipe of your network (joining the different nodes). See APPENDIX C – EPANET users manual (PIPES target) for more information. Valve and
pumps are optional.
6) Generate and edit DBF files from node and arc according EPANET DATA MODELS. You will create DBF from node shape file such as JUNCTION, RESERVOIR and TANKS
and DBF from arc shape file such as PUMP, PIPE or different types of VALVE.
7) Edit the control DBF files (OPTIONS, TIMES and REPORT).
8) Additional DBF file must be created (if you need it) according EPANET DATA MODELS. This DBF files could be among others, CONTROLS, RULES, CURVES, PATTERNS,
EMITTERS, DEMANDS, QUALITY, SOURCES, ENERGY or much more.
9a) Generate INP file: Giswater → Software → EPANET → export INP checkbox. In this way, Giswater driver will create a text file (inp extension) stored on the selected folder.
9b) Execute the command line EPANET: Giswater → Software → EPANET → Execute EPA software checkbox. Giswater will execute the command line EPANET file with the inp
file, and EPANET will generate two result files (*.rpt file and *.out file.) stored on the selected folder.
10) Returns to the GIS project insert and join the different shapes and tables and enjoy of the simulation's results.

DBF mode is a deprecated mode.
We encourage you to upgrade this work mode to database storage mode!!!
3.4 EPANET giswater menu

Depending on the operating data storage mode, the Giswater EPANET menu has different options enabled or disabled. In order to simplify the maintenance of released version,
only the latest version of EPANET (built 2.0.012) is allowed.
If you are working on DBF data storage Giswater menu, it only allows Data folder, Export INP, Execute EPA software and Import Results.
On the other hand, if you are working on DB data storage, Giswater menu allows Schema management, Data and Pre-process options, post-process data Analysis and of course,
Export INP, Execute EPA software and Import Results.
3.4.1 Data manager

The Data manager contains the different parameters such as Material catalog, curves, patterns, emitters, demands, rules, controls and project data which are essential to configure
our EPANET project.
Material Catalog
The material catalog defines the pipes used in the network including a description of each pipe.
Curves
Curves are graphical representations containing data pairs showing a relationship between two quantities. In EPANET there are four different types of curves:
Pump curves
Efficiency curves
Volume curves
Head Loss Curves
Patterns
Patterns refer to time patterns and are used in order to set a collection of multipliers in order to be applied on a quantity to allow it to vary oever time. The components which allow
time patterns include reservoirs, nodes, pumps, water quality source inputs.
Emitters
They are devices associated with junctions that model the flow through a nozzle or orifice that discharges to the atmosphere. The flow rate through an emitter varies as a function of
pressure at the node.
Demands
They are used to supplement the junctions and define different demands at different junction nodes. There are different parameters which need to be defined to complete the
demand on a junction node.
Rules
The Ruled-Based Controls allow link status and settings to be based on a combination of conditions that may arise in the network after an initial hydraulic state of the system is
computed.
Controls
Controls are statements that determine how the network is operated over time. They specify the status of selected links as a function of time,tank water levels, and pressures at
select points.
The Simple Controls are used to change the status of or setting of a link based on different parameters on the tanks, junctions, simulation and time of the day.
Project Data
The project data includes the title of the project, the author and the data which can be changed in this section.
3.4.2 Preprocess options

Sector selection
Sector selection allows you to select all the elements of a sector. However, with the 'Insert' button, you can add more than one sector, which you can study with the set of elements
of differents sectors.
Options
Defines various simulation options.
Units: Sets the units in which flow rates are expressed where:
CFS = cubic feet per second

GPM = gallons per minute
MGD = million gallons per day
IMGD = Imperial MGD
AFD = acre-feet per day
LPS = liters per second
LPM = liters per minute
MLD = million liters per day
CMH = cubic meters per hour
CMD = cubic meters per day
For CFS, GPM, MGD, IMGD, and AFD other input quantities are expressed in US Customary Units. If flow units are in liters or cubic meters then Metric Units must be used for all
other input quantities aswell. (See Appendix A os SWMM's Manual. Units of Measurement). The default flow units are LPS.
Headloss: Selects a formula to use for computing head loss for flow through a pipe. The choices are the Hazen-Williams (H-W), Darcy-Weisbach (D-W), or Chezy-Manning (C-M)
formulas. The default is H-W.
Hydraulics: Option allows you to either SAVE the current hydraulics solution to a file or USE a previously saved hydraulics solution. This is useful when studying factors that only
affect water quality behaviour.
Quality: Selects the type of water quality analysis to perform. The choices are NONE, CHEMICAL, AGE, and TRACE. In place of CHEMICAL the actual name of the chemical can
be used followed by its concentration units (e.g., CHLORINE mg/L). If TRACE is selected it must be followed by the ID label of the node being traced. The default selection is
NONE (no water quality analysis).
Unbalanced: Determines what happens if a hydraulic solution cannot be reached within the prescribed number of TRIALS at some hydraulic time step into the simulation. "STOP"
will halt the entire analysis at that point. "CONTINUE" will continue the analysis with a warning message issued. "CONTINUE n" will continue the search for a solution for another "n"
trials with the status of all links held fixed at their current settings. The simulation will be continued at this point with a message issued about whether convergence was achieved or
not. The default choice is "CONTINUE".
Viscosity: Is the kinematic viscosity of the fluid being modelled relative to that of water at 20 deg. C (1.0 centistoke). The default value is 1.0.
Trials: Are the maximum number of trials used to solve network hydraulics at each hydraulic time step of a simulation. The default is 40.
Accuracy: Prescribes the convergence criterion that determines when a hydraulic solution has been reached. The trials end when the sum of all flow changes from the previous
solution divided by the total flow in all links is less than this number. The default is 0.001.
Emitter exponent: Specifies the power to which the pressure at a junction is raised when computing the flow issuing from an emitter. The default is 0.5.
Check freq:
Max check:
Damp limit:
Hydraulics fname:
Node id:
Unbalanced_n:
Specific Gravity: Is the ratio of the density of the fluid being modelled to that of water at 4 deg. C (unit less).
Diffusivity: Is the molecular diffusivity of the chemical being analysed relative to that of chlorine in water. The default value is 1.0. Diffusivity is only used when mass transfer
limitations areconsidered in pipe wall reactions. A value of 0 will cause EPANET to ignore mass transfer limitations.
Tolerance: Is the difference in water quality level below which one can say that one parcel of water is essentially the same as another. The default is 0.01 for all types of quality
analyses (chemical, age (measured in hours), or source tracing (measured in percent)).
Pattern: Provides the ID label of a default demand pattern to be applied to all junctions where no demand pattern was specified. If no such pattern exists in the [PATTERNS] table
then by default the pattern consists of a single multiplier equal to 1.0. If this option is not used, then the global default demand pattern has a label of "1".
Demand multiplier: Is used to adjust the values of baseline demands for all junctions and all demand categories. For example, a value of 2 doubles all baseline demands, while a
value of 0.5 would halve them. The default value is 1.0.
Times values
Defines various time step parameters used in the simulation.
Duration: Is the duration of the simulation. Use 0 to run a single period snapshot analysis. The default is 24.
Quality timestep: Is the time step used to track changes in water quality throughout the network. The default is 1/10 of the hydraulic time step.
Pattern timestep: Is the interval between time periods in all time patterns. The default is 1 hour.
Report timestep: Sets the time interval between which output results are reported. The default is 1 hour.
Start clocktime: Is the time of day (e.g., 3:00 PM) at which the simulation begins. The default is 12:00 AM midnight.
Hydraulic timestep: determines how often a new hydraulic state of the network is computed. If greater than either the PATTERN or REPORT time step it will be automatically
reduced. The default is 1 hour.
Rule timestep: Is the time step used to check for changes in system status due to activation of rule-based controls between hydraulic time steps. The default is 1/10 of the hydraulic
time step.
Pattern start: Is the time offset at which all patterns will start. For example, a value of 6 hours would start the simulation with each pattern in the time period that corresponds to hour
6. The default is 0.
Report start: Is the length of time into the simulation at which output results begin to be reported. The default is 0.
Statistic: Determines what kind of statistical post-processing should be done on the time series of simulation results generated. AVERAGED reports a set of time-averaged results,
MINIMUM reports only the minimum values, MAXIMUM the maximum values, and RANGE reports the difference between the minimum and maximum values. NONE reports the full
time series for all quantities for all nodes and links and is the default.
Report options
Describes the contents of the output report produced from a simulation.
Pagesize: Sets the number of lines written per page of the output report. The default is 0, meaning that no line limit per page is in effect.
File: Supplies the name of a file to which the output report will be written (ignored by the Windows version of EPANET).
Status: Determines whether a hydraulic status report should be generated. If YES is selected the report will identify all network components that change status during each time
step of the simulation. If FULL is selected, then the status report will also include information from each trial of each hydraulic analysis. This level of detail is only useful for de-
bugging networks that become hydraulically unbalanced. The default is YES.
Summary: Determines whether a summary table of number of network components and key analysis options is generated. The default is YES.
Energy: Determines if a table reporting average energy usage and cost for each pump is provided. The default is YES.
Nodes: Identifies which nodes will be reported on. You can either list individual node ID labels or use the keywords NONE or ALL. Additional NODES lines can be used to continue
the list. The default is ALL.
Links: Identifies which links will be reported on. You can either list individual link ID labels or use the keywords NONE or ALL. Additional LINKS lines can be used to continue the
list. The default is ALL.
Elevation: The distance above some common reference of the junction. It is an essential information to calculate pressure.
Demand: There are different types of demands such as base demand and demand patterns.
Head: the pressure head
Pressure: pressure of the system
Quality: quality of water at a location specified
Length:
Diameter:
Flow:
Velocity:
Headloss: Selects a formula to use for computing head loss for flow through a pipe. The choices are the Hazen-Williams (H-W), Darcy-Weisbach (D-W), or Chezy-Manning (C-M)
formulas. The default is C-M.
Setting: Roughness for pipes, speed for pumps, pressure/flow setting for valves. The default is YES.
Reaction: Reaction rate. The default is YES.
F factor: Friction factor. The default is YES.
3.4.3 File manager

The file manager controls the format at which files would be exported, imported and how we will analyze our system. The latest refert to the option of executing EPA software and
where the results would be saved. The file manager exports INP files and executing an RPT file.
3.4.4 Postprocess options

Result selector
This selects the results we want to view on our GIS software. Only the result selected will be visible on our project.
Results catalog
This catalog includes all the results obtained in a network analysis showing the parameters which were computed.
Стр. 4 из 16 03.03.2018, 12:27

CHAPTER 4. EPA SWMM USER'S GUIDE

This provides a tutorial on how to use Giswater with EPA SWMM.
If you are not familiar with the components that comprise an urban drainage and sewerage system and how these are represented in conduit network models you might want to
review the first two sections of Chapter 3 of the EPA SWMM's user's manual.
However, if you are familiar with the components that comprise an urban drainage and sewerage system and how these are represented in a conduit network model, you must
review APPENDIX D of EPA SWMM's user's manual.
4.1 Notes on network topology

GIS network will be created acording an arc-node topology. Arc-node topology has four basic rules. These essential rules are listed below:
1. Nodes are the main elements of the network. They are POINT geometry types
2. Arcs join only Nodes and the startpoint and endpoints are called Node1 and Node2. They are LINESTRING geometry types.
3. Points (optionals) along an arc that define its shape are called Vertices. They are POINT geometry types.
4. Every Arc has a direction (same or not as hydraulic direction)
4.2 Database data storage

This provides a tutorial on how to use Giswater with EPA SWMM on Database data storage. To activate this data storage mode: Project preferences → Data storage: Database

In order to perform a simple case you must follow the next steps:
1) Start your project by creating your new project preferences file: File → New project preferences
2) Select the Water software: You have four options with different versions of EPA SWMM. You can select:
EPASWMM_50022: Original version 5.0.022 from EPA (Deprecated)
EPASWMM_51006: Original version 5.1.006 from EPA
EPASWMM_51006_2D: Adapted version of 5.1.006 from EPA. This version allows the possibility of working with a coupled model 2D/1D. (Testing)
EPASWMM_51006_C: Adapted version of 5.1.006 customizing the results file
3) Select Data storage: Database
4) Configure your connection parameteres
5) Create a new project data scheme: Fill project name, project title and select your SRID.
6) Create your GIS project: Fill project folder and project name, choose software water and data storage (in this case EPA SWMM and data storage), and finally select the scheme
name you need.
7) Click on Accept button on the Project Preferences menu
8) Select US or metric units: Options → flow units. Choosing US flow unit, means that all other quantities of your project will be expressed in US units, while choosing a metric flow
unit will force all quantities to be expressed in metric units.
9) Complete the material catalog at least with one record: Material catalog. The formula used to computing head loss for flow is Manning's equation. You can found into the EPA
SWMM user's manual different roughness values.
10) Complete the conduit catalog at least with one record: Arc catalog. You must introduce the catalog values. You can found into the EPA SWMM user's manual different conduit
sections and his geometry values. Special attention with CUSTOM and IRREGULAR conduit sections.
CUSTOM conduit sections must to be defined with a shape curve value: Curves. You can found how to do it into the CURVES target of the APPENDIX D of EPA SWMM user's
manual.
IRREGULAR conduit sections must to be defined with a transects dat into the GIS project (EPASWMM - Hydraulics - Arc - Transects). You can found how to do it into the
TRANSECTS target of the APPENDIX D of EPA SWMM user's manual.
11) Complete the timeseries catalog at least with one record: Timeseries. You can found how to do it into the TIMESERIES target of APPENDIX D of EPA SWMM user's manual.
12) Complete the hydrologic catalog at least with one record. Default scenario (hc_default) is able for you. It use the curve number infiltration method. You must change it or create
another one.
13) Open GIS project and build your network, working at least with the next layers:
GIS FEATURES - Sector. You must to create at least one sector.
EPA SWMM - Hydraulics - Node - Outfall. You must to create and edit at least one outfall. You can found how to do it into the OUTFALLS target of the APPENDIX D of EPA
SWMM user's manual.
EPA SWMM - Hydraulics - Node - Junctions. You must to create and edit the junction records of your network. You can found how to do it into the JUNCTIONS target of the
APPENDIX D of EPA SWMM user's manual.
EPA SWMM - Hydraulics - Arc - Conduits. You must to create and edit the pipe records of your network (joining the different nodes). You can found how to do it into the
CONDUITS target of the APPENDIX D of EPA SWMM user's manual.
EPA SWMM - Hydrology - Raingage. You must to create at least one feature. You can found how to do it into the RAINGAGE target of the APPENDIX D of EPA SWMM user's
manual.
EPA SWMM - Hydrology - Subcatchment. You must to create at least one feature. You can found how to do it into the SUBCATCH, SUBAREAS & INFILTRATION targets of the
14) Configure INP file additional parameters. You can define how many sectors will be simulated: Sector selection and also you can cofigure the simulation and raingage options:
Options /Raingage and the simulation report data: Report.
15a) Generate the INP file: export INP checkbox and Giswater driver will create a text file (inp extension) stored in the selected folder.
15b) Execute the command line EPA SWMM: Execute EPA software checkbox. Giswater will execute the command line EPA SWMM file with the inp file, and EPA SWMM will
generate two result files (*.rpt file and *.out file.) stored on the selected folder.
15c) Import Results (if you like): Import results. Giswater will read the result data stored on *.rpt file and will write the values on the schema result tables.
16) Return to GIS project and enjoy the simulation's results on SIMULATION ANALYSIS
4.2.2 Database key relations

Key relations between features and tables should be mentioned at this point.
First of all, the key relations from ARC and NODE to other tables are defined as 'on delete cascade on update cascade'. This means that if you delete one feature from these
tables, all related features from other tables will be deleted .On the other hand if you update values from these tables, values in all related features will be updated in cascade too.
Otherwise, key relations from SECTOR, CONDUIT CATALOG and MATERIAL are defined as 'on delete restrict on update cascade'. This is quite different because it means that
you can not delete used features from these tables. On the other hand if you update values from these tables, values in all related features will be updated in cascade too.
The rest of features do not have key relations. Elements as RAINGAGE, SUBCATCHMENT, CONTROLS, TIMESERIES, CURVES, PATTERNS, POLLUTANTS, LANDUSES,
TREATMENT do not have key relations from theirs to other tables. In this way, you must knowthat If you update features the values will not be updated on related tables (if they
exist) and if you delete features mentioned on related tables will nor be deleted (if they exist too).
4.2.3 Database sequences

Sequences are an interesting option of databases as PostreSQL. They are autonumeric and we use them in order to facilitate our work on several tables. Enjoy it!!

For more information about the GIS Table Of Contents (TOC) of EPA SWMM project, please visit the EPA SWMM section of APPENDIX A - DATABASE GIS PROJECTS [52]
4.3 DBF data storage

This provides a tutorial on how to use Giswater with EPA SWMM on DBF data storage. To activate this data storage mode: Giswater → EPA SWMM → Data storage: DBF.
WARNING: Full capabilities not are allowed on DBF storage mode !!!

To proceed with a simple case you follow the next steps:
1) Create a GIS project: Giswater → GIS project. Fill file folder and file name, check DBF data storage and a group of Shape file and DBF will be created. Finally choose GIS
program you like and buid your own project.
2) Open the GIS program and build your network according the topology rules.
To proceed with a simple case you must follow the next steps:
You must to create and edit at least one outfall. You can found how to do it into the OUTFALLS target of the APPENDIX D of EPA SWMM user's manual. Additionally you must to
create and edit all the junction records of your network. You can found how to do it into the JUNCTIONS target of the APPENDIX D of EPA SWMM user's manual. Afther that you
can create and edit the pipe records of your network (joining the different nodes). You can found how to do it into the CONDUITS target of the APPENDIX D of EPA SWMM user's
manual.
3) Generate the DBF files from arc and node according to the EPA SWMM DATA MODELS. This DBF files from node shape file such are JUNCTION, OUTFALL, DIVIDER or
STORAGE and from arc shape file are CONDUIT, PUMPS, WEIR, ORIFICE or OUTLET.
4) You must to create at least one raingage and one subcathcment. You can found how to do it into the RAINGAGE, SUBCATH, SUBAREAS & INFILTRATION targets of the
5) Generate the DBF files from Raingage and Sucatchment (SUBCATCHMENT, RGAGE_TS or RGAGE_FL, TIMSER_ABS or TIMSER_REL or TIMSER_FL. You can found how to
do it into the TIMESERIES, RAINGAGE target of APPENDIX D of EPA SWMM user's manual.
6) Edit the control DBF files (OPTIONS and REPORT).
7) Additional DBF files must be created (if you need it) according EPA SWMM DATA MODELS. This DBF files could be among others, CONTROLS, CURVES, PATTERNS,
TEMPERATURE, LOADINGS, HYDROGRAPHS, LANDUSES, POLLUTANT or much more.
8a) Generate the INP file: Giswater → Software → EPA SWMM → export INP checkbox and Giswater driver will create a text file (inp extension) stored in the selected folder.
8b) Execute the command line EPA SWMM: Giswater → Software → EPA SWMM → Execute EPA software checkbox. Giswater will execute the command line EPA SWMM file
with the inp file, and EPA SWMM will generate two result files (*.rpt file and *.out file.) stored on the selected folder.
8c) Import Results (if you like): Giswater – Software → EPA SWMM → Import results. Giswater will read the result data stored on *.rpt file and will write the values on the
9) Returns to the GIS project insert and join the different shapes and tables and enjoy of the simulation's results.

4.4 EPA SWMM Giswater menu
Depending on the operating data storage mode, the Giswater EPA SWMM menu has different options enabled or disabled. In order to simplify the maintenance of released version.
If you are working on DBF data storage Giswater menu only allows Data folder, Export INP, Execute EPA software and Import Results.
On the other hand, If you are working on DB data storage, Giswater menu allows Schema management, Data and Pre-process options, post-process data Analysis and of
course, Export INP, Execute EPA software and Import Results.
4.4.1 Data Manager

The data manager contains the different parameters such as material catalog, curves, patterns, timeseries, arc catalog, hydrologic catalog, controls and project data.
Material catalog
The material catalog defines the pipes used in the network including a description of each pipe.
Curves
They are objects which are used to describe a functional relationship between two quantities. In EPA SWMM th eavalable curves include storage, shape, diversion, tidal, pump,
rating, and control.
Patterns
Patterns refer to time patterns which allow Dry Weather Flow (DWF) to vary in a periodic fashion. There are different types of patterns including monthly, daily, hourly and
weekend.
Timeseries
Time series objects are used to define how certain object properties vary with time. They can be used to describe temperature data, evaporation data, rainfall data, water stage at
outfall nodes, external inflow hydrographs at drainage system nodes, external inflow pollutographs at drainage system nodes and control settings for pumps and flow regulators.
Arc catalog
The arc catalog defines the arcs on the network including the geometry and a description.
Hydrologic catalog
You can define differents hydrologic scenarios using this catalog.
id: Name of your scenario
Infiltration: Selects a model for computing infiltration of rainfall into the upper soil zone of subcatchments. The default model is CURVE NUMBER. Other infiltration models are:
HORTON / GREEN_AMPT.
Descritpion: Optional text to descript the propierties of this scenario.
By default the scenario hc_default is created
Controls
These elements determine hw pumps and regulators will be adjusted based on simulation time or conditions at specific nodes and links.
Project data
Project data includes the title, the author and date of creation of the project. This information can be edited here.
4.4.2 Preprocess options

Sector selection
Sector selection allows you to select all the elements of a sector. However, with the 'Insert' button, you can add more than one sector, which you can study with the set of elements
of differents sectors.
Options
Simulation options parameters. All values are recorded on inp_options table.
General
Flow units: Makes a choice of flow units. The default is CMS (Cubic Meter Second). Other flow units are:CFS / GPM / MGD / LPS / MLD.
WARNING: Selecting a US flow unit means that all other quantities will be expressed in US units, while choosing a metric flow unit will force all quantities to be expressed in metric
units.
Hydrology: Selects a scenario from hydrologic catalog. By selecting this option, the model for computing infiltration of rainfall into the upper soil zone of subcatchments will be
defined on each subcatchment.
Flow routing: Determines which method is used to route flows through the drainage system. STEADY refers to sequential steady state routing (i.e. hydrograph translation),
KINWAVE to kinematic wave routing, DYNWAVE to dynamic wave routing. The default routing method is DINWAVE.
Link offets: Determines the convention used to specify the position of a link offset above the invert of its connecting node. DEPTH indicates that offsets are expressed as the
distance between the node invert and the link while ELEVATION indicates that the absolute elevation of the offset is used. The default is DEPTH.
Allow ponding: Determines whether excess water is allowed to collect atop nodes and be re-introduced into the system as conditions permit. The default is NO ponding. In order for
ponding to actually occur at a particular node, a non-zero value for its Ponded Area attribute must be used.
Min slope: Is the minimum value allowed for a conduit’s slope (%). If zero (the default) then no minimum is imposed (although SWMM uses a lower limit on elevation drop of 0.001 ft
(0.00035 m) when computing a conduit slope).
Ignore rainfall: Is set to YES if all rainfall data and runoff calculations should be ignored. In this case SWMM only performs flow and pollutant routing based on user-supplied direct
and dry weather inflows. The default is NO.
Ignore snowmelt: Is set to YES if snowmelt calculations should be ignored when a project file contains snow pack objects. The default is NO.
Ignore groundwater: Is set to YES if groundwater calculations should be ignored when a project file contains aquifer objects. The default is NO.
Ignore routing: Is set to YES if only runoff should be computed even if the project contains drainage system links and nodes. The default is NO.
Ignore quality: Is set to YES if pollutant washoff, routing, and treatment should be ignored in a project that has pollutants defined. The default is NO.
Skip steady state: Should be set to YES if flow routing computations should be skipped during steady state periods of a simulation during which the last set of computed flows will
be used. A time step is considered to be in steady state if there has been no significant change in external inflows, storage volumes, and either node water depths (for dynamic
wave routing) or conduit flows (for other forms of routing). The default for this option is NO.
Date & Time steps

Start date: Is the date when the simulation begins. The default date is 01/01/2001.
Start time: Is the time of day on the starting date when the simulation begins. The default is 12 midnight (00:00:00).
End date: Is the date when the simulation is to end. The default is the start date.
End time: Is the time of day on the ending date when the simulation will end. The default is 24:00:00.
Report start date: Is the date when reporting of results is to begin. The default is the simulation start date.
Report start time: Is the time of day on the report starting date when reporting is to begin. The default is the simulation start time of day.
Report step: Is the time interval for reporting of computed results. The default is 0:15:00.
Runoff dry step: Is the time step length used for runoff computations (consisting essentially of pollutant buildup) during periods when there is no rainfall and no ponded water.
The default is 1:00:00.
Runoff wet step: Is the time step length used to compute runoff from subcatchments during periods of rainfall or when ponded water still remains on the surface. The default
is 0:05:00.
Routing step: Is the time step length in seconds used for routing flows and water quality constituents through the conveyance system. The default is 10 sec wich could be
augmented if using kinenamic wave routing. Fractional values (e.g., 2.5) are permissible as are values entered in hours:minutes:seconds format.
Sweep start: Is the day of the year (month/day) when street sweeping operations begin. The default is 01/01.
Sweep end: Is the day of the year (month/day) when street sweeping operations end. The default is 12/31.
Dry days: Is the number of days with no rainfall prior to the start of the simulation. The default is 10.
Dynamic wave
Force main: Establishes whether the Hazen-Williams (H-W) or the Darcy-Weisbach (D-W) equation will be used to compute friction losses for pressurized flow in conduits that
have been assigned a Circular Force Main cross- section shape. The default is H-W.
Normal flow limited: Specifies which condition is checked to determine if flow in a conduit is supercritical and should thus be limited to the normal flow. Use SLOPE to check if
the water surface slope is greater than the conduit slope, FROUDE to check if the Froude number is greater than 1.0, or BOTH to check both conditions. The default is BOTH
Lengthening step: Is a time step, in seconds, used to lengthen conduits under dynamic wave routing, so that they meet the Courant stability criterion under full- flow conditions (i.e.,
the travel time of a wave will not be smaller than the specified conduit lengthening time step). As this value is decreased, fewer conduits will require lengthening. A value of 0 (the
default) means that no conduits will be lengthened.
Variable step: Is a safety factor applied to a variable time step computed for each time period under dynamic wave flow routing. The variable time step is computed so as to satisfy
the Courant stability criterion for each conduit and yet not exceed the routing step value. If the safety factor is 0 (the default), then no variable time step is used.
Inertial damping: Indicates how the inertial terms in the Saint Venant momentum equation will be handled under dynamic wave flow routing. Choosing NONE maintains
these terms at their full value under all conditions. Selecting PARTIAL will reduce the terms as flow comes closer to being critical (and ignores them when flow is
supercritical). Choosing FULL will drop the terms altogether. The default is NONE
Min sufarea: Is a minimum surface area used at nodes when computing changes in water depth under dynamic wave routing. If 0 is entered, then the default value of 1.14 m2 is
used.
Max trials: Allowed from 5.1 version or later. Maximum trials computed. If 0 is entered, then the default value of 8 is used.
Head tolerance: Allowed from 5.1 version or later. Tolerance of head pressure during the computational time. If 0 is entered, then the default value of 0.0015 m is used.
System flow tolerance: Allowed from 5.1 version or later. Tolerance of system flow. Default value is 5%
Lateral flow tolerance: Allowed from 5.1 version or later. Tolerance of lateral flow. Defalut value is 5%
Raingage
Options for setting up a rain gage.
General
Id: This code refers to each of the spatial objects and must have a consecutive order (1, 2, 3,...) in relation to how they have been creating these objects.
Raingage type: Type of rain gage (FILE or TIMESERIES).
Intvl: Time interval between gage readings (in decimal hours or hours:minutes format).
Form type: Form to recorded rainfall, either INTENSITY, VOLUME or CUMULATIVE.
Scf: Snow catch deficiency correction factor (use 1.0 for no adjustament).
Timeseries
Timeseries id: Name of time series.
File
Fname: Name of external file with rainfall data. Rainfall files are discussed in Chapter 11.3 of SWMM's Manual.
Units: Rain depth units used in the rain file, either IN (inches) or MM (millimeters).
Sta: Name of recording station used in the rain file.
Report options
Describes the contents of the report file that is produced.
Input: Specifies whether or not a summary of the input data should be provided in the output report. It can be YES or NO.
Continuity: Specifies whether continuity checks should be reported or not. It can be YES or NO.
Flowstats: Specifies whether summary flow statistics should be reported or not. It can be YES or NO.
Controls: Specifies whether all control actions taken during a simulation should be listed or not. It can be YES or NO.
Subcatchments: Gives a list of subcatchments whose results are to be reported. The default is ALL.
Nodes: Gives a list of nodes whose results are to be reported. The default is ALL.
Links: Gives a list of links whose results are to be reported. The default is ALL.
4.4.3 File manager

The file manager controls the format at which files would be exported, imported and how we will analyze our system. The latest refert to the option of executing EPA software and
where the results would be saved. The file manager exports INP files and executing an RPT file.
4.4.4 Postprocess options

Result catalog
This catalog includes all the results obtained in a network analysis showing the parameters which were computed.
Result selector
This selects the results we want to view on our GIS software. Only the result selected will be visible on our project.
Стр. 5 из 16 03.03.2018, 12:27

CHAPTER 5. HEC-RAS USER'S GUIDE

This chapter provides a general view of the tool including a description of the technological approach and a quick start guide (tutorial).
5.1 Introduction
In the recent years HEC-RAS (USACE-HEC 1995) model has become a crucial tool in the hydraulic and fluvial engineering modeling. The development of remote sensing
technologies has provoked an impressive increase in the topographical information availability. This evolution has forced to create a powerful link between hydraulic models, like
HEC-RAS, and GIS (Geographic Information System) tools.
GIS constitutes the optimum framework to manage and combine the wide range of available information, it also provides a common interface to interact with such amount of
heterogeneous data, including aerial pictures, satellite images, geological maps, topographical grids, land use info, etc. Most of the data sources mentioned above are relevant to
hydraulic modeling, therefore, in order to construct a hydraulic model of a natural landscape, GIS become mandatory.
In this framework a couple of tools exist that link GIS and HEC-RAS. The most famous one is the free tool HEC-geoRAS developed by the HEC-RAS producers (USACE HEC).
Hence the performance of the tool and its interaction with GIS and HEC-RAS would make it the best choice.
The main dawback of this tool is that it works as an ESRI ArcGIS extension; therefore a complete set of ESRI licenses should be owned to use HEC-geoRAS. GISWATER is the
open source alternative to HEC-geoRAS which is presented here. The aim on the background of this project is to create a serious alternative to the proprietary software required
by HEC-geoRAS. Therefore all the software is released as open source and supported by GITHUB (https://github.com/Giswater/giswater [53]).
GISWATER Association is in charge of the bug control and updates of the tool.
5.2 Software overview

At the first stages of this new tool of design and implementation, a couple of questions emerge, however the most relevant one was related to the selection of the open source GIS
software used as the target platform. The concern was that once the GIS software is selected, the tool must be developed constrained to GIS platform requirements. This GIS
software acts as a container and the GISWATER tool behaves as a kind of extension or plugin.
The analysis of the existing GIS open source projects reveals that it is a dynamical area where different projects coexist and most of them just for a short period of time. So there
is an important uncertainty in the GIS tool life cycle and expectancy. After realizing these facts a brainstorming of the tool designers (GITS-UPC, TecnicsAssociats) concludes in a
new proposal for the development platform. In this case the PostgreSQL (Stonebraker & Rowe 1986)/PostGIS (Regina O. Obe 2011) combination was considered.
The key features that exist in PostgreSQL database that are of great importance for hydraulic tools, inventories and collections are naturally included in an object oriented
database. These inventories can include multiple elements of a hydraulic model such as bridges, pipes, gage stations etc… all these elements are essential parts of the hydraulic
model.
From the system architecture point of view the database environment provides a rational way to share the information and store it. Concurrent access to information makes it
interesting for team work.
Another crucial element of the PostgreSQL which important for its selection is the PostGIS extension.
PostGIS is an open source extension intended to include geometrical/geographical information in a database. It also includes more than 200 spatial functions to interact with the
geographical data. From topology to metrics everything is included in the extension. Also since version 2.0 PostGIS launch, there is the ability to manage raster datasets and allows
interaction between vectorial/raster information. This was a major requirement in GISWATER development for HEC-RAS, where the terrain role is crucial. Therefore as described
here the tool landscape is represented by a DTM (Digital Terrain Model) which is stored within the database as a standard table.
Almost all the existing open source GIS have a driver to interact with a PostgreSQL database, therefore all of them become a useful interface to the tool. As has been described
previously all the information is collected in the database, and this database includes all the necessary spatial algorithms, therefore the GIS becomes just a graphical interface to
view/edit the information but processing is performed in the database. This means that light GIS viewers are capable of running the tool, neither a simple intersection command is
necessary in the GIS platform.
As a consequence of these facts, using a simple SQL console pointing to the database is all you need to create the HEC-RAS geometry file, but the support of any GIS tool
improves the user experience and the tool becomes user-friendly. In the following three different examples of GISWATER interfacing will be presented, GRASS, gvSIG and QGIS,
but this are three examples in a long list.
Figure 1. GISWATER database loaded into

GRASS GIS.
In the Figure 1 the GRASS GIS interfacing to the tool is presented. This is one of the first open source GIS developed. It has some constraints in working with PostgreSQL. In the
version 6 the layers coming from the database could not be edited, just shown, the table views are not accepted as a layer.
Figure 2. GISWATER Database into gvSIG GIS.
In Figure 2 the gvSIG interface to the database is also presented, this software has a great strength in the community. It was able to interact to the whole tool but the stability of the
platform accessing a Postgres database was poor.
Figure 3. GISWATER Database into a QGIS platform.
In the Figure 3 the QGIS interface is presented. It was selected as the best tool to run the model. The stability and the power of the software was its main advantage. The driver is
complete and works in both direction read/write.
Therefore, most of the commands and processes of the HEC-RAS tool are included into the database. Standard HEC-RAS users are far from being database experts, hence a
JAVA interface is provided in order to trigger the main tool commands. Most of the tool practitioners will use the tool without any direct contact to database working in the
background. For advanced users, accessing the database is a way to tune and customize the tool.
As it is known the PostgreSQL database is based in the schema paradigm. This means that the database is decomposed in parts, each one named “schema”. This is a kind of
organization system.
Following this idea and, to take advantage of its strength, these schemes are used in the developed tool. Each schema in the database is considered as a “case”. A case is a group
of tables that contains all the geographic information necessary to construct a “HEC-RAS” GIS file (“sdf”).
Therefore, every time a case is stored in the database it creates a new schema using the name provided by the user. This philosophy is coherent with the fact of a database being
used. One single database is able to contain all the cases developed by a user or a group of users.
5.3 Quick start tutorial

The complete process to generate a HEC-RAS model could be divided in two different phases. The first phase involves creating the project case database, loading the
topographical raster and finally exporting the HEC-RAS GIS import file (sdf). The second phase is carried out inside the GIS and it involves the delineation of the involved lines,
checking the topology, etc. It is mainly supported by the editing tools provided by the GIS software. In this case the QGIS will be the selected platform.
Most of the processes are developed inside the database, GISWATER acts just as an interface to trigger processes in the database, but any other database-interfaces are valid. A
Postgresql console could be used to launch the commands or a SQL console as well. The list of the database commands is described in the "Functions description" document
section.
5.3.1 JAVA GISWATER Interface

As has been commented in the previous section, GISWATER JAVA user interface provides a simple way to manipulate the Postgres database and including the following essential
steps:
0) Start GISWATER
1) Create project
2) Add DTM to the project
3) Generate GIS project
4) Export projecto to HEC-RAS
GISWATER works linked to a database. There two general approaches to work with database are firstly the user could have an installed postgres database, in a corporative server
or in a local computer. GISWATER could connect to this existing database. The second approach is to use the GISWATER distributed database, named "portable postgres".
Depending on the selected installation file the porstable database is installed or no.
In case of having a portable database it is started by GISWATER on launch. If the portable database is used is mandatory to have it active during project development, otharways
the databse is not available for adding/editing process. During the development of the tool there has been several issues concerning database and Windows OS. Depending on the
OS version new issues emerge. Bug report is provided in GISWATER, the address is bugreport@giswater.org [54]
Due to this issues the portable database is stored in the user's folder in the Windows file system,a folder named "giswater" could be found in this directory.
A project in the database is a list of information tables. The tables contain data field and spatial information as well. When a project is created the user should select the type of
project. The last GISWATER release includes the EPANET, SWMM and HEC-RAS interface.
5.3.2 Why using GISWATER for river analysis?

Giswater is an open source software connecting spatial data with water analysis software such as EPANET, EPA SWMM and HEC-RAS. Also it is possible to create an SDF file in
order to import terrain data from GIS to other GIS tools such as HEC-RAS.
In the latest case of the using it as a tool to facilitate the river study in HEC-RAS, it could be used for
a) Flooding analysis
b) Risk assessment
c) Options appraisal
d) Risk management
Firstly the area under investigation needs to be identified with the areas having more flood risks problems as well. Then the river system needs to be specified including the source,
the pathway and the receptors and the different risks associated with this system. In the past such studies were only based on traditional hydrological modeling, but nowadays
more information is necessary in order to produce a more accurate model of the system which is closest to reality and hence produce more relevant and accurate results. Hence
river systems are now being modeled using different sources of information such as cadastral, topographical, hydrological and meteorological data with the use of Geographic
Information Systems (GIS) in order to create flood risk assessment maps. This kind of data is easier to interpret and include much more information for the interested parties.
The problem arises in connecting GIS software to river analysis software. The methodology to toggle the problem is by using Giswater which is able of connect to a GIS, a river
analysis software using a geospatial database.
5.3.3 Methodology
The case scenario is the river Onyar in Girona, in Catalonia Spain begins at the Guilleries massif and it joins river Ter at the city of Girona. The river has flooded in the past
creating devastating damages to the city. Analyses on the vulnerable areas of the city have been carried out in the past. However, the case developed below would show the areas
affected with different flow regime of the river and the vulnerability to flooding without any specifications on land use.
The GISWATER platform involves four main elements, the GISWATER interface, the database, the GIS and the HEC-RAS software. First of all the GISWATER interface should be
started using the desktop icon. GISWATER would try to connect to an existing database in your system or an external one, stored in the default preferences. If a database is not
found in your system or configured in the default settings, it would try to launch the portable version included in the ‘all-in-one’ distribution. In case that a database connection is
not obtained, the first task of the user is to manually configure it. Once the connection is successful, the settings are stored in the default project or they could also be saved as a
new project.
The methodology of how to connect to GIS using a database and then importing it to HEC-RAS (river analysis software) would be described below. In order to facilitate the
procedure the case scenario of river Onyar above would be used. The following steps are to be followed after opening Giswater in order to successfully create the case scenario∶
1. Edit project preferences
2. HEC-RAS preferences- configuration of the project
3. Setting up the river scenario using GIS
4. Export SDF file
5. Set up the river analysis study
5.3.3.1 Edit project preferences

The first step is to set up new/edit project preferences. The user interface of ‘Edit project preferences’ is shown below.
Figure 1. Edit preferences user interface
1. Water software∶ is to be chosen between EPANET, EPA SWMM and HEC-RAS. In this case we should choose HEC-RAS for a river study.
2. Data storage∶ choose between Database and DBF (filename extension). In this case choose Database.
3. Database storage∶ ensure that the connection to the database storage is open.
4. Project Data Management∶ here the GIS project is created. Click on create. A screen shown on figure 2 below would appear.
5. Finally, at the end of the page click on accept to finalize the edition of the project preferences. This would lead you to the user interface of HEC-RAS preferences.
Figure 2. Create project interface
Set the Project name and project title taking into account that it should be a name that it is easy to remember, it does not have any weird characters like accents, question marks or
any other characters which is not widely used. Also ensure that the SRID (Spatial Reference System Identifier) is the correct one for the study of interest. Click on accept and
close to create the project.For this project the project name chosen was hec_demo and the project title was Onyar from the name of the river.
5.3.3.2 HEC-RAS preferences - configuration of the project

In the HEC-RAS preferences, the Digital Terrain Model (DTM) of the area under study is to be loaded. The HEC-RAS user interface is shown below in figure 3.
Figure 3. HEC-RAS preferences
Giswater accepts any file type of DTM including GDAL (geoTIF,img, asc, txt..). After finding the file, click on accept in order to connect to the database. This step takes a while to
execute. This step is vital in order to successfully create the GIS project. Then return to the previous screen by clicking on ‘Edit Project Preferences’ at the bottom of the page.
At the bottom left corner of the interface there is a button ‘Create Gis Project’, click on the button in order to create a new QGIS project. A screen would pop-up shown in figure 4
below.
Figure 4. Create GIS project interface
Choose the location which the file would be located, name the Gis Project and click on accept to create the new project. The following screen shown on figure 5 would pop-up.
Click on ‘Yes’.
Figure 5. Pop-up message to create a new GIS project
This process might take a few minutes. Then it asks if you want to open the new file created. The GIS software then opens with the new project which was created with the data
specified in the previous steps such as the SRID and the DTM.
5.3.3.3 Setting up the river scenario using QGIS

Once the file created by Giswater opens, it should be noted that it contains the layers which are vital in order to set the project. They are grouped in two blocks: input and output.
Both blocks are strongly connected because some of them correspond to the same database table (i.e. ‘view_banks and banks). They are collected into groups because in the
group ‘input’ includes just the layers and fields which are compulsory to the user. In the input group, the layers are named ‘views’ as the layers are only partially presented, hence
in a database view, not a table. The output group includes all the project layers and every layer contains all the fields, with some of them being internal fields to the tool. The layers
which were created include ‘view_banks’, ‘view_flowpaths’, ‘view_xscutlines’ and ‘view_river’. The Gis project generated is shown in figure 6 below.
Figure 6. New QGIS prohect- hec_demo
These layers need to be drawn. In order to draw these layers it is essential to load the raster layers of the area including the orthophotos, the DTM (Digital Terrain Model) and the
cartography to facilitate the task. Even though by default the terrain layer is included in the ‘output’ group with the name ‘mdt’, the performance is reduced if the user uses this
layer. This is due to the fact that if the database is in the cloud every pan movement or zoom involves a new terrain download for the database, adding a delay. In order to reduce
the delay it is recommended to load the QGIS table of content (ToC) a new terrain layer, linked to a local version of the terrain raster, avoiding the active visualization of the ‘mdt’
layer of the data base. Also it is recommended to generate a layer demonstrating the terrain relief and hence depict the most possible path of the river. When loading all the layers
necessary for the study the map canvas should look as the figure below.
Figure 7. Area under study
The next step is to start drawing the layers which were generated in the Gis project. Using the orthophoto and in conjunction with the elevation and shadow layers all the layers
should be drawn starting with the view_river, ensuring that the line follows the river flow in the middle of the channel. Note that after drawing the river, the data in the attribute table
should be entered as shown below. Failing to include this data, the model would be incomplete.
Figure 8. Attribute table for river_view layer
Following the view_river, the view_flowpaths should be drawn. In this layer there are three different lines which should be drawn for the three different flows which could exist such
as normal flow regime, over flooding the banks of the river both on left and right sides of the river. Note that the normal flow regime should be the same as the view_river and also
the other two lines on the left and side of the river should be drawn in such a way that the flow is the easiest path that the water could follow taking into consideration the relief of the
terrain as well as possible obstacles which could be found such as buildings, trees. The flow paths should look relatively the same as in the figure below.
Figure 9. Flow path of the river for 3 case scenario flows
Then each line should be specified on the attribute table. There are three different line types, channel, left and right. In order to correctly specify each line consideration should be
given in the direction of the flow of the river as shown below. For this, it is essential to know the direction of the river and that the left bank is the one on the left-hand side if
watching at the same direction as the flow of the river and the same implies for the right side.
Figure 10. Classification of river flow paths
Then the next layer to be drawn is the view_banks. The river banks are the borders of the river during normal flow regime (depth of the river has not reached maximum river flow
and hence no risk of flooding). The river banks are shown in the figure below. Note that all the layers which were drawn up to this point should not cross each other at any moment
except from the channel in the flow paths and the river which should be the same.
Figure 11. River banks of area under study
The last layer to be drawn is the view_xscutlines. This layer includes various lines which are cut all the above layers. These are the sections of the river at different locations and
depending on the length of the river under study they should be placed equidistance from each one, in this case the distance between each section is approximately 30m. The final
results of all the layers being drawn are shown below.
Figure 12. GIS project of the study area
5.3.3.4 Export SDF file

After finishing the Gis project on the GIS software, the project should be exported in a format which is acceptable by HEC-RAS. In order to do this, Giswater should be used. In the
HEC-RAS user interface inside Giswater (see figure below), specify the location and the name of the file which would be created. In this case the folder is Results and the name of
the file ‘hec_demo’ (the same as the Gis project). Finally click on Accept in order to create the SDF file. This might take some minutes. When the file is created, the river study
could be performed using HEC-RAS.
Figure 13. Exportation of SDF file
5.3.3.5 Set up the river analysis study

The river analysis study would be performed using HEC-RAS hence the tool should be opened. The main window of HEC-RAS is shown below.
Figure 14. HEC-RAS main window- Edit menu
The first step in HEC-RAS is to enter the geometry data of the area under investigation. In order to do that click on ‘Edit/Enter geometric data’, a new window would pop-up. Then
you should go to file, import Geometry Data and GIS Format (as shown in the figure below).
Figure 15. Geometry data import - SDF file
The Geometry Data to be imported as a GIS Format is the SDF file which was created in Giswater. The following window would open, locate the location of the file, choose the file
and click on ‘OK’.
Figure 16. Import Geometry Data-SDF file
Note that HEC-RAS would ask with what units the analysis should be performed (as shown in figure below). For this case choose SI(metric) units, then ‘Next’ and ‘Finish- Import
Data’.
Figure 17. Unit specification
The geometry would be imported in the window. This saves a lot of time in performing a river analysis as the geometry is inserted directly without having to insert it manually. Then
from the main menu, go to file and ‘Save Geometry Data As’. The next steps are to configure the Manning’s coefficient, the boundary layers. For this, go to ‘Tables’, ‘Manning’s n
or k values (Horizontally varied)’ (see figure 18 below).
Figure 18. Configuring Manning's coefficient
In the columns n#1 and n#3 set the value of Manning’s coefficient at 0.06 which it is the value for the left and right bank respectively. In column n#2 set the value at 0.04 which is
the value at the channel of the river. In order to set the values first select the column to be filled (the column would be colored on lilac), click on ‘Set values’, fill in the black with the
corresponding values; all the values would be set therefore you should not fill in the blanks one by one. Then click on ‘OK’.
Figure 19. Manning's coefficient for banks and channel
The next step is to enter the steady flow data. In order to bring up the steady Flow data editor, select the ‘Steady Flow Data’ icon from the ‘Edit’ menu on the HEC-RAS main
window. The steady flow data editor should appear as shown in the figure below. Fill in the blank box named ‘PF1’ with 400.
Figure 20. Steady Flow Data Editor
Then the Boundary conditions should also be set; click on ‘Reach Boundary Conditions’ and a new window will appear as shown in the figure below.
Figure 21. Steady Flow boundary conditions
The Boundary conditions should be set for both Upstream and Downstream locations; in this case choose for both of them ‘Critical Depth’. Choosing the Critical Depth’ does not
require entering any further information. The program will compute critical depth for all the profiles and this would be used as the boundary condition.
Finally click on ‘Perform a steady flow simulation’, choose the flow regime ‘Mixed’. The window which would appear is shown in the figure below. Click on ‘Perform’ to compute
results.
Figure 22. Steady Flow analysis
In order to view the results, click on ‘Close’ on the new window that appears, go to the main menus of HEC-RAS and click on ‘View 3D multiple cross section plot’. The following
screen would appear showing the results of the analysis.
Figure 23. Results in a 3D multiple cross section plot
5.4 References
Regina O. Obe, L. S. H. (2011), PostGIS in action, Greenwich, Conn.
Stonebraker, M. & Rowe, L. (1986), The design of postgres, in ‘Proc. ACM-SIGMOD Conference on Management of Data’.
USACE-HEC (1995), HEC-RAS, River Analysis System, Hydraulics Reference Manual. CPD-69, Hydrological Engineering Center, Davis, CA.
Стр. 6 из 16 03.03.2018, 12:27

APPENDIX A - DATABASE GIS PROJECTS

Here you will found information about GIS projects on Database storage mode [55] .
Remember, on DBF storage mode when you create the GIS project, the only files created are DBF and Shape files. The GIS projects (we recommend gvSIG or QGIS) are not
automatically created.
1- EPANET
The next TOC (Table of contents of GIS interface) will be avaliable when you create EPANET GIS project: Giswater → GISProject
GIS FEATURES
Arc
Arc geometries (pipes, valves and pumps)
arc_id: ID label.
node_1: ID of start node.
node_2: ID of end node.
diameter: Pipe diameter in inches (mm).
matcat_id: Material as stated in the catalog of materials.
enet_type: Arc type as EPANET.
sector_id: The code sector where is the space object.
Node
Node geometries (junction, reservoir or tank)
node_id: ID label.
elevation: The spot elevation node. Ft (m)
enet_type: Node type as EPANET.
sector_id: Sector where there is the node.
Sector
Defines the network sectors. You must need minimun at once.
sector_id: Code sector.
descript: Description of the sector.
EPANET DATA
Backdrop
Identifies a backdrop image and dimensions for the network EPANET map.
id: Defines the order of the line text. You must to use this code in order to sort as you need the lines of text. As you sort the text lines Giswater reads by this order the information.
See definition and remark's section for more information.
text: Text options Backdrop.
Definitions:
DIMENSIONS provides the X and Y coordinates of the lower-left and upper-right corners of the map’s bounding rectangle. Defaults are the extents of the nodal coordinates
supplied in your Gis project selection.
UNITS specifies the units that the map’s dimensions are given in (FEET/METERS/DEGREES/NONE). Default is NONE.
FILE is the name of the file that contains the backdrop image.
OFFSET lists the X and Y distance that the upper-left corner of the backdrop image is offset from the upper-left corner of the map’s bounding rectangle. Default is zero offset.
Remarks:
a. The [BACKDROP] table is optional and is not used at all when EPANET is run as a console application.
b. Only Windows Enhanced Metafiles and bitmap files can be used as backdrops.
Hydraulics
Node
Junction
Defines junction nodes contained in the network.
node_id: ID label.
elevation: The spot elevation junction. (ft or m).
demand: Base demand (flow units). This field is optional.
pattern_id: Demand pattern ID. This field is optional.
sector_id: Sector where there is the junction.
Remarks
a. At least one juction is required
b. If no demand pattern is supplied then the junction demand follows the Default Demand Pattern specified in the [OPTIONS] [56] parameteres or Pattern 1. If the default pattern (or
Pattern 1) does not exist, then the demand remains constant.
c. Demands can also be entered in the [DEMANDS] [57] table and include multiple demand categories per junction.
Reservoir
Defines all reservoir nodes contained in the network.
node_id: ID label.
elevation: The spot elevation reservoir. Ft (m).
head: Head, ft (m).
pattern_id: Head pattern ID. This field is optional
sector_id: The sector where there is the reservoir.
Remarks:
a. Head is the hydraulic head (elevation + pressure head) of water in the reservoir.
b. A head pattern can be used to make the reservoir head vary with time.
c. At least one reservoir or tank must be contained in the network.
Source
Defines locations of water quality sources.
node_id: ID label.
sourc_type: Source type (CONCEN, MASS, FLOWPACED, or SETPOINT).
quality: Baseline source strength.
pattern_id: Time pattern ID.
Remarks:
a. For MASS type sources, strength is measured in mass flow per minute. All other types measure source strength in concentration units.
b. Source strength can be made to vary over time by specifying a time pattern.
c. A CONCEN source:
represents the concentration of any external source inflow to the node
applies only when the node has a net negative demand (water enters the network at the node)
if the node is a junction, reported concentration is the result of mixing the source flow and inflow from the rest of the network
if the node is a reservoir, the reported concentration is the source concentration
if the node is a tank, the reported concentration is the internal concentration of the tank
is best used for nodes that represent source water supplies or treatment works (e.g., reservoirs or nodes assigned a negative demand)
should not be used at storage tanks with simultaneous inflow/outflow.
d. A MASS, FLOWPACED, or SETPOINT source:
represents a booster source, where the substance is injected directly into the network irregardless of what the demand at the node is
affects water leaving the node to the rest of the network in the following way:
- a MASS booster adds a fixed mass flow to that resulting from inflow to the node
- a FLOW PACED booster adds a fixed concentration to the resultant inflow concentration at the node
- a SETPOINT booster fixes the concentration of any flow leaving the node (as long as the concentration resulting from the inflows is below the setpoint)
the reported concentration at a junction or reservoir booster source is the concentration that results after the boosting is applied; the reported concentration for a tank with a
booster source is the internal concentration of the tank
is best used to model direct injection of a tracer or disinfectant into the network or to model a contaminant intrusion.
e. A [SOURCES] table is not needed for simulating water age or source tracing.
Tank
Defines all tank nodes contained in the network.
node_id: Node ID label.
elevation: Bottom elevation. (ft or m).
initlevel: Initial water level. (ft or m).
minlevel: Minimum water level. (ft or m).
maxlevel: Maximum water level. (ft or m).
diameter: Nominal diameter. (ft or m).
minvol: Minimum volume. (cubic ft or cubic meters).
curve_id: Volume curve ID.
sector_id: Sector where there is the tank.
Remarks:
a. Water surface elevation equals bottom elevation plus water level.
b. Non-cylindrical tanks can be modeled by specifying a curve of volume versus water depth in the [CURVES] [58] table.
c. If a volume curve is supplied the diameter value can be any non-zero number
d. Minimum volume (tank volume at minimum water level) can be zero for a cylindrical tank or if a volume curve is supplied.
e. A network must contain at least one tank or reservoir.
Mixing
Identifies the model that governs mixing within storage tanks.
node_id: ID label.
mix_type: Mixing model (MIXED, 2COMP, FIFO or LIFO).
value: Options value parameters of EPANET project.
Remarks:
a. Mixing models include:
Completely Mixed (MIXED)
Two-Compartment Mixing (2COMP)
Plug Flow (FIFO)
Stacked Plug Flow (LIFO)
b. The compartment volume parameter only applies to the two-compartment model and represents the fraction of the total tank volume devoted to the inlet/outlet compartment.
c. The [MIXING] table is optional. Tanks not described in this table are assumed to be completely mixed.
Emitter
Defines junctions modeled as emitters (sprinklers or orifices).
node_id: ID label.
coef: Flow coefficient, flow units at 1 psi (1 meter) pressure drop.
Remarks:
a. Emitters are used to model flow through sprinkler heads or pipe leaks.
b. Flow out of the emitter equals the product of the flow coefficient and the junction pressure raised to a power.
c. The power can be specified using the EMITTER EXPONENT option in the option parameters. The default power is 0.5, which normally applies to sprinklers and nozzles.
d. Actual demand reported in the program's results includes both the normal demand at the junction plus flow through the emitter.
e. An [EMITTERS] table is optional.
Demand
Replace to [JUNCTION] [59] feature for defining multiple water demands at junction nodes. WARNING: If this junction values are used the value of [JUNCTION] is ignored.
id: Row id. Unique value needed.
node_id: Junction ID label.
demand: Base demand (flow units).
pattern_id: Demand pattern ID.
deman_type: Name of demand category preceded by a semicolon.
Remarks:
a. Only use for junctions whose demands need to be changed or supplemented from entries in [JUNCTION] feature.
b. Data in this section replaces any demand entered in [JUNCTION] feature for the same junction.
c. Unlimited number of demand categories can be entered per junction.
d. If no demand pattern is supplied then the junction demand follows the Default Demand Pattern specified in the [OPTIONS] [56] option parameters or Pattern 1 if no default pattern
is specified. If the default pattern (or Pattern 1) does not exist, then the demand remains constant.
Arc
Pipe
Defines all pipe links contained in the network.
arc_id: ID label.
diameter: Diameter. (inches or mm).
minorloss: Minor loss coefficient.
status: Status (OPEN, CLOSED or CV)
sector_id: Sector where there is the pipe.
Remarks:
a. Roughness coefficient is unitless for the Hazen-Williams and Chezy-Manning head loss formulas and has units of millifeet (mm) for the Darcy-Weisbach formula. Choice of
head loss formula is supplied in the [OPTIONS] [60]option parameters.
b. Setting status to CV means that the pipe contains a check valve restricting flow to one direction.
c. If minor loss coefficient is 0 and pipe is OPEN then these two items can be dropped form the input line.
Pump
Defines all pump links contained in the network.
arc_id: ID label of pump.
diameter: Diameter in inches or mm.
power: Write it POWER, leave a space and write the value of power. (Power value for constant energy pump, hp (kW))
curve_id: ID label.
speed: Write it SPEED, leave a space and write the value of speed. (Relative speed setting (normal speed is 1.0, 0 means pump is off))
pattern: Write it PATTERN, leave a space and write the value of pattern. (ID of time pattern that describes how speed setting varies with me)
sector_id: Sector where there is the pump.
Remarks:
a. Keywords consists of:
POW ER – power value for constant energy pump, hp (kW)
HEAD - ID of curve that describes head versus flow for the pump
SPEED - relative speed setting (normal speed is 1.0, 0 means pump is off)
PATTERN - ID of time pattern that describes how speed setting varies with time
b. Either POWER or HEAD must be supplied for each pump. The other keywords are optional.
Valve
Defines all control valve links contained in the network.
arc_id: ID label of valve.
diameter: Diameter in inches or mm.
valv_type: Valve type (see remarks)
pressure: Pressure in psi or m.
flow: Flow (flow units)
coef_loss: Loss coefficient.
curve_id: ID of head loss curve
minor_loss: Minor loss coefficient [61]
status: Valve status (see remarks).
sector_id: Sector where there is the valve.
Remarks:
a. Valve types and settings include:
Valve type Setting
PRV (pressure reducing valve) Pressure, psi (m)
PSV (pressure sustaining valve) Pressure, psi (m)
PBV (pressure breaker valve) Pressure, psi (m)
FCV (flow control valve) Flow (flow units)
TCV (throttle control valve) Loss Coefficient
GPV (general purpose valve) ID of head loss curve
b. Shutoff valves and check valves are considered to be part of a pipe, not a separate control valve component (see [PIPE] [62])
c. The status value can be OPEN or CLOSED. For control valves (e.g., PRVs, FCVs, etc.) this means that the valve is either fully opened or closed, not active at its control setting.
d. The setting value can be a speed setting for pumps or valve setting for valves.
e. Check valves cannot have their status be preset.
f. If a CLOSED or OPEN control valve is to become ACTIVE again, then its pressure or flow setting must be specified in the control or rule that re-activates it.
Material catalog
Materials catalog.
descript: Material description.
roughness: Roughness coefficient [63].
Controls
Controls
Defines simple controls that modify links based on a single condition.
text: Controls text (See the example below).
Example:
;Close Link 12 if the level in Tank 23 exceeds 20 ft.
LINK 12 CLOSED IF NODE 23 ABOVE 20
;Open Link 12 if pressure at Node 130 is under 30 psi
LINK 12 OPEN IF NODE 130 BELOW 30
Remarks:
a. Simple controls are used to change link status or settings based on tank water level, junction pressure, time into the simulation or time of day.
b. See the notes for the [STATUS] parameter in value domain for conventions used in specifying link status and setting, particularly for control valves.
Rules
Defines rule-based controls that modify links based on a combination of conditions.
text: Defines rule-based controls that modify links based on a combination of conditions.
Example:
RULE 1
IF TANK 1 LEVEL ABOVE 19.1
THEN PUMP 335 STATUS IS CLOSED AND PIPE 330 STATUS IS OPEN
Remarks:
a. Only the RULE, IF and THEN portions of a rule are required; the other portions are optional.
b. When mixing AND and OR clauses, the OR operator has higher precedence than AND, i.e.,
IF A or B and C
is equivalent to
IF (A or B) and C.
If the interpretation was meant to be
IF A or (B and C)
then this can be expressed using two rules as in
IF A THEN ...
IF B and C THEN ...
c. The PRIORITY value is used to determine which rule applies when two or more rules require that conflicting actions be taken on a link. A rule without a priority value always has
a lower priority than one with a value. For two rules with the same priority value, the rule that appears first is given the higher priority.
Curve & patterns

Curve
Defines data curves and their X,Y points.
curve_id: Name assigned to table.
x_value: An x (independent variable) value.
y_value: An y (independent variable) value.
Remarks:
a. Curves can be used to represent the following relations:
Head v. Flow for pumps
Efficiency v. Flow for pumps
Volume v. Depth for tanks
Headloss v. Flow for General Purpose Valves
b. The points of a curve must be entered in order of increasing X-values (lower to higher).
c. If the input file will be used with the Windows version of EPANET, then adding a comment which contains the curve type and description, separated by a colon, directly above
the first entry for a curve will ensure that these items appear correctly in EPANET’s Curve Editor. Curve types include PUMP, EFFICIENCY, VOLUME, and HEADLOSS.
Pattern
Defines time patterns.
pattern_id: Pattern ID label.
factor_1: Pattern value (one or more multipliers).
factor_2: Pattern value (one or more multipliers)
...
Remarks:
a. Multipliers define how some base quantity (e.g., demand) is adjusted for each time period.
b. All patterns share the same time period interval as defined in the [TIMES] table.
c. Each pattern can have a different number of time periods.
d. When the simulation time exceeds the pattern length the pattern wraps around to its first period.
e. Use as many lines as it takes to include all multipliers for each pattern.
Curve catalog
Curve catalog.
See definition and remark's section for more information.
curve_type: Curve types include PUMP, EFFICIENCY, VOLUME, and HEADLOSS.
Options
Quality
Describes the contents of the output report produced from a simulation.
node_id: ID label.
initqual: Initial quality.
Remarks:
Selects the type of water quality analysis to perform. The choices are NONE, CHEMICAL, AGE, and TRACE. In place of CHEMICAL the actual name of the chemical can be used
followed by its concentration units (e.g., CHLORINE mg/L). If TRACE is selected it must be followed by the ID label of the node being traced. The default selection is NONE (no
water quality analysis).
Global energy
Defines global parameters -for all pumps- used to compute pumping energy and cost.
energ_type: Energy type. Must be GLOBAL or DEMAND CHARGE
parameter: Options parameters. See below
value: Values for the selected parameter.
Remarks:
Parameters are defined as follows:
If you select GLOBAL, Parameters are defined as follows:
PRICE: average cost per kW-hour

PATTERN: ID label of time pattern describing how energy price varies with time.
EFFIC: either a single percent efficiency for global setting or the ID label of an efficiency curve for a specific pump.
If you select DEMAND CHARGE, parameter remain on blank and directly you can fill data on value field.
The default global pump efficiency is 75% and the default global energy price is 0.
Single energy
Defines parameters used to compute pumping energy and cost (by specified pump)
pump_id: ID label.
parameter: Options parameters. Must be PRICE, PATTERN or EFFIC
value: Value of the parameter selected
Remarks
Parameters are defined as follows:
PRICE: average cost per kW-hour

PATTERN: ID label of time pattern describing how energy price varies with time.
EFFIC: either a single percent efficiency for global setting or the ID label of an efficiency curve for a specific pump.
The default global pump efficiency is 75% and the default global energy price is 0.
Global reactions
Defines global parameters -for all elements- related to chemical reactions occurring in the network.
react_type: Reaction type. Must be ORDER or GLOBAL (see below)
parameter: Options parameters. Must be BULB, WALL, TANK, LIMITING POTENCIAL or ROUGHNESS CORRELATION
value: Value of the specified parameter
Remarks:
ORDER is used to set the order of reactions occurring in the bulk fluid, at the pipe wall, or in tanks, respectively. Values for wall reactions must be either 0 or 1. If not supplied the
default reaction order is 1.0.
GLOBAL is used to set a global value for all bulk reaction coefficients (pipes and tanks) or for all pipe wall coefficients. The default value is zero.
BULK, WALL and TANK are used to override the global reaction coefficients for specific pipes and tanks.
For LIMITING POTENCIAL or ROUGHNESS CORRELATION fill blank the field react_type
LIMITING POTENCIAL specifies that reaction rates are proportional to the difference between the current concentration and some limiting potential value.
ROUGHNESS CORRELATION will make all default pipe wall reaction coefficients be related to pipe roughness in the following manner:
Head Loss Equation Roughness Correlation
Hazen-Williams F/C
Darcy-Weisbach F / log(e/D)
Chezy-Manning F*n
a. Remember to use positive numbers for growth reaction coefficients and negative numbers for decay coefficients.
b. The time units for all reaction coefficients are 1/days.
c. All entries in this section are optional. Items offset by slashes (/) indicate allowable choices.
Single reactions
Defines individual parameters -specific for each element- related to chemical reactions occurring in the network.
parameter: BULK, WALL or TANK. Used to override the global reaction coefficients for specific pipes and tanks
arc_id: Element ID with specific chemical reaction.
value: Reaction coefficient vaules
Remarks:
a. Remember to use positive numbers for growth reaction coefficients and negative numbers for decay coefficients.
b. The time units for all reaction coefficients are 1/days.
c. All entries in this section are optional. Items offset by slashes (/) indicate allowable choices.
Value domain
Folder with tables used on other tables as value domain data. Gis projects uses this tables but data is not updatable. You do not have to do anything, but you can not delete it.
Tags
Associates category labels (tags) with specific nodes and links on EPANET user inferface.
object: The keyword NODE or LINK.
node_id: The node or link ID label.
tag: The text of the tag label (with no spaces).
Remarks:
a. Tags can be useful for assigning nodes to different pressure zones or for classifying pipes by material or age.
b. If a node or link’s tag is not identified in this section then it is assumed to be blank.
c. The [TAGS] table is optional and has no effect on the hydraulic or water quality calculations.
Labels
Assigns coordinates to map labels on EPANET user inferface.
xcoord: Horizontal coordinate of vertex relative to origin in lower left of map.
ycoord: Vertical coordinate of vertex relative to origin in lower left of map.
label: Text of label in double quotes.
node_id: ID label.
Remarks:
a. Include one line for each label on the map.
b. The coordinates refer to the upper left corner of the label and are with respect to an arbitrary origin at the lower left of the map.
c. The optional anchor node anchors the label to the node when the map is re-scaled during zoom-in operations.
d. The [LABELS] table is optional and is not used at all when EPANET is run as a console application.
SIMULATION ANALYSIS
Node minimum values
Node minimum values simulation analisys data.
node_id: ID label of node.
result_id: ID simulation result.
elevation: Elevation (ft or m).
max_demand: Maximum bse demand (flow units)
min_demand: Minimum base demand (flow units).
max_head: Maximum head (ft or m).
min_head: Minimum head (ft or m)
max_pressure: Maximum pressure (psi or m).
min_pressure: Minimum pressure (psi or m).
Node maximum values

Node simulation maximum values simulation analisys data.
node_id: ID label of node.
elevation: Elevation (ft or m).
max_demand: Maximum bse demand (flow units).
min_demand: Minimum base demand (flow units).
max_head: Maximum head (ft or m).
min_head: Minimum head (ft or m).
max_pressure: Maximum pressure (psi or m).
min_pressure: Minimum pressure (psi or m).
Arc minimum values

Arc minimum values simulation analisys data.
arc_id: ID label of arc.
max_flow: Maximum flow (flow units).
min_flow: Minimum flow (flow units).
max_vel: Maximum velocity (fps).
min_vel: Minimum velocity (fps).
max_headloss: Maximum headloss (/1000ft).
min_headloss: Minimum headloss (/1000ft).
max_setting: Maximum setting. (Roughness for pipes, speed for pumps, pressure/flow setting for valves).
min_setting: Minimum setting. (Roughness for pipes, speed for pumps, pressure/flow setting for valves).
max_reaction: Maximum reaction.
min_reaction: Minimum reaction.
max_ffactor: Maximum friction factor.
min_ffactor: Minimum friction factor.
Arc maximum values

Arc maximum values simulation analisys data.
max_flow: Maximum flow (flow units).
min_flow: Minimum flow (flow units).
max_vel: Maximum velocity (fps).
min_vel: Minimum velocity (fps).
max_headloss: Maximum headloss (/1000ft).
min_headloss: Minimum headloss (/1000ft).
max_setting: Maximum setting. (Roughness for pipes, speed for pumps, pressure/flow setting for valves).
min_setting: Minimum setting. (Roughness for pipes, speed for pumps, pressure/flow setting for valves).
max_reaction: Maximum reaction.
min_reaction: Minimum reaction.
max_ffactor: Maximum friction factor.
min_ffactor: Minimum friction factor.
Energy usage values

Energy usage values simulation analisys data.
pump_id: ID label of pump.
usage_fact: Usage factor.
avg_effic: Average efficiency.
kwhr_mgal: Kw – hr (/Mgal).
avg_kw: Average (Kw).
peak_kw: Peak (Kw)
cost_day: Cost (/day)
Hydraulic status
Hydraulic status values simulation analisys data.
time: 'Time'.
text: 'Text'.
2- EPA SWMM
The next TOC (Table of contents of GIS interface) will be avaliable when you create EPA SWMM GIS project: Giswater → GISProject
GIS FEATURES
Arc
Arc geometries (conduits, orifices, weirs, pumps or outlets)
arc_id: ID label.
z1: Offset of upstream end of conduit invert above the invert elevation of its upstream node (ft or m).
z2: Offset of downstream end of conduit invert above the invert elevation of its downstream node (ft or m).
arccat_id: Arc type as stated in the catalog of arches.
swmm_type: Arc type as EPA SWMM.
sector_id: Sector where there is the arc.
Node
Node geometries (juctions, outfalls, dividers or storages)
node_id: ID label.
top_elev: Elevation of junction top (ft or m).
ymax: Depth from ground to invert elevation (ft or m) (default is 0).
swmm_type: Node type as EPA SWMM.
Sector
Defines the network sectors. You must need minimum at once.
sector_id: Code sector.
descript: Description of the sector.
EPA SWMM DATA

Files
Identifies optional interface files used or saved by a run.
actio_type: USE / SAVE.
fil_type: The file type can be: RAINFALL, RUNOFF, HOTSTART, RDII or ROUTING
fname: Name of file.
Remarks:
Rainfall, Runoff, and RDII files can either be used or saved in a run, but not both. A run can both use and save a Hot Start file (with different names).
Climatology
Windspeed
Windspeed data.
wind_type: Wind speed type (MONTHLY or FILE).
value_1: Wind speed value parameters of SWMM project (mph or km/hr).
...
fname: Name of external file with wind speed data.
Snowmelt
Snowmelt parameters are climatic variables that apply across the entire study area when simulating snowfall and snowmelt.
stemp: Air temperature at which precipitation falls as snow (deg F or C).
atiwt: Antecedent temperature index weight (default is 0.5).
rnm: Negative melt ratio (default is 0.6).
elev: Average elevation of study area above mean sea level (ft or m) (default is 0).
lat: Latitude of the study area in degrees North (default is 50).
dtlong: Correction, in minutes of time, between true solar time and the standard clock time (default is 0).
i_f0: In imprevious area, fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.
i_f1: In imprevious area, fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.1.
...
i_f9: In imprevious area, fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.9
p_f0: In previous area, fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.
p_f1: In previous area, fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.1.
...
p_f9: In previous area, fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.9.
Temperature
Specifies daily air temperatures, monthly wind speed, and various snowmelt parameters for the study area. Required only when snowmelt is being modeled or when evaporation
rates are computed from daily temperatures or are read from an external climate file.
temp_type: Temperature type (TIMESERIES or FILE).
timser_id: Name of time series in [TIMESERIES] [64] table with temperature data.
fname: Name of external Climate file with temperature data.
start: date to begin reading from the file in month/day/year format (default is the beginning of the file).
Remarks:
Use the TIMESERIES line to read air temperature from a time series or the FILE line to read it from an external Climate file. Climate files are discussed in chapter 11.4 of SWMM's
Manual. If neither format is used, then air temperature remains constant at 70 degrees F.
Wind speed can be specified either by monthly average values or by the same Climate file used for air temperature. If neither option appears, then wind speed is
assumed to be 0.
Separate Areal Depletion Curves (ADC) can be defined for impervious and pervious sub-areas. The ADC parameters will default to 1.0 (meaning no depletion) if no data are
supplied for a particular type of sub-area.
Evaporation
Specifies how daily evaporation rates vary with time for the study area.
evap_type: Evaporation type (CONSTANT, MONTHLY, TIMESERIES, TEMPERATURE or FILE)
evap: Constant evaporation rate (in/day or mm/day).
timser_id: Name of time series in [TIMESERIES] [64] table with evaporation data.
value_1: Evaporation value parameters of SWMM project. Evaporation rate in January (in/day or mm/day).
value_2: Evaporation value parameters of SWMM project. Evaporation rate in February (in/day or mm/day).
...
value_12: Evaporation value parameters of SWMM project. Evaporation rate in December (in/day or mm/day).
pan_1: Pan coefficient for January.
pan_2: Pan coefficient for February.
...
pan_12: Pan coefficient for December.
recovery: Identifies an optional monthly time pattern of multipliers used to modify infiltration recovery rates during dry periods. For example, if the normal infiltration recovery rate
was 1% during a specific time period and a pattern factor of 0,8 applied to this period, then the actual recovery rate would be 0,8%
dry_only: Determines if evaporation only occurs during periods with no precipitation. The default is NO.
Remarks:
Use only one of the above formats (CONSTANT, MONTHLY, TIMESERIES, TEMPERATURE, or FILE). If no [EVAPORATION] table appears, then evaporation is assumed to be 0.
TEMPERATURE indicates that evaporation rates will be computed from the daily air temperatures contained in an external climate file whose name is provided in the
[TEMPERATURE] [65] table. This method also uses the site’s latitude, which can also be specified in the [TEMPERATURE] table.
FILE indicates that evaporation data will be read directly from the same external climate file used for air temperatures as specified in the [TEMPERATURE] table.
RECOVERY identifies an optional monthly time pattern of multipliers used to modify infiltration recovery rates during dry periods. For example, if the normal infiltration recovery
rate was 1% during a specific time period and a pattern factor of 0.8 applied to this period, then the actual recovery rate would be 0.8%.
DRY_ONLY determines if evaporation only occurs during periods with no precipitation. The default is NO.
Adjustments
Adjustments are +- changes to temperature and evaporation or multipliers for rainfall that can vary month of the year
adj_type: Values are TEMPERATURE, EVAPORATION, RAINFALL
value_1: Evaporation value parameters of SWMM project.
value_2: Evaporation value parameters of SWMM project
-----
value_12: Evaporation value parameters of SWMM project
Hydrology
Raingage
Identifies each rain gage that provides rainfall data for the study area.
rg_id: ID label (name assigned to raingage).
form_type: Form of recorded rainfall, either INTENSITY, VOLUME or CUMULATIVE.
intvl: Time interval between gage readings in decimal hours or hours:minutes format (e.g., 0:15 for 15-minute readings).
scf: Snow catch deficiency correction factor (use 1.0 for no adjustment).
rgage_type: Raingage type (TIMESERIES or FILE)
timser_id: Name of time series in [TIMESERIES] table with rainfall data.
fname: Name of external file with rainfall data. Rainfall files are discussed in chapter 11.3 of SWMM's Manual.
sta: Name of recording station used in the rain file.
units: Rain depth units used in the rain file, either IN (inches) or MM (millimeters).
link: Additional information.
Subcatchment
Identifies each subcatchment within the study area. Subcatchments are land area units which generate runoff from rainfall.
subc_id: ID label (name assigned to subcatchment).
node_id: ID label (name of a node that receives runoff from subcatchment).
rg_id: ID label (name of rain gage in RAINGAGES section assigned to subcatchment).
area: Area of subcatchment (acres or hectares).
imperv: Percent imperviousness of subcatchment.
width: Characteristic width of subcatchment (ft or meters).
slope: Subcatchment slope (percent).
clength: Total curb length (any length units).
snow_id: Name of snow pack object that characterizes snow accumulation and melting over the subcatchment.
nimp: Manning's N for overland flow over the impervious sub-area.
nperv: Manning's N for overland flow over the pervious sub-area.
simp: Depression storage for impervious sub-area (inches or mm).
sperv: Depression storage for pervious sub-area (inches or mm).
zero: Percent of impervious area with no depression storage (default = 0.00).
routeto: Use IMPERVIOUS if pervious area runoff runs onto impervious area, PERVIOUS if impervious runoff runs onto impervious area, or OUTLET if both areas drain to the
subcatchment's outlet. (default is IMPERVIOUS).
rted: Percent of runoff routed from one type of area to another (default = 100).
maxrate: Maximum infiltration rate on Horton curve (in/hr or mm/hr).
minrate: Minimum infiltration rate on Horton curve (in/hr or mm/hr).
decay: Decay rate constant of Horton curve (l/hr).
drytime: Time it takes for fully saturated soil to dry (days).
maxinfil: Maximum infiltration volume possible (0 if not applicable) (in or mm).
suction: Soil capillary suction (in or mm).
conduct: Soil saturated hydraulic conductivity (in/hr or mm/hr).
initdef: Initial soil moisture deficit (volume of voids / total volume).
curveno: SCS Curve Number.
conduct_2: Soil saturated hydraulic conductivity (in/hr or mm/hr) (This property has been deprecated and is no longer used).
drytime_2: Time it takes for fully saturated soil to dry (days).
sector_id: Sector where there is the subcatchment.
hydrology_ïd: Hydrologic scenario used. You must to fill this field and the value should be compatible with the infiltration parameters used.
Aquifer
Supplies parameters for each unconfined groundwater aquifer in the study area. Aquifers consist of two zones – a lower saturated zone and an upper unsaturated zone.
aquif_id: ID label (Aquifer name).
por: Soil porosity (fraction).
wp: Soil wilting point (fraction).
fc: Soil field capacity (fraction).
k: Saturated hydraulic conductivity (in/hr or mm/hr).
ks: Slope of hydraulic conductivity versus moisture content curve.
ps: Slope of soil tension versus moisture content curve.
uef: Fraction of total evaporation available for evapotranspiration in the upper unsaturated zone.
led: Maximum depth into the lower saturated zone over which evapotranspiration can occur (ft or m).
gwr: Rate of percolation from saturated zone to deep groundwater when water table is at ground surface (in/hr or mm/hr).
be: Elevation of the bottom of the aquifer (ft or m).
wte: Water table elevation at start of simulation (ft or m).
umc: Unsaturated zone moisture content at start of simulation (fraction).
pattern_id: Monthly pattern of adjustments to upper evaporation fraction
Groundwater
Supplies parameters that determine the rate of groundwater flow between the aquifer underneath a subcatchment and a node of the conveyance system.
subc_id: ID label (subcatchment name).
aquif_id: ID label (name of groundwater aquifer underneath the subcatchment).
node_id: ID label (name of node in conveyance system exchanging groundwater with aquifer).
surfel: Surface elevation of subcatchment (ft or m).
a1: Groundwater flow coefficient (see remarks).
b1: Groundwater flow exponent (see remarks).
a2: Surface water flow coefficient (see remarks).
b2: Surface water flow exponent (see remarks).
a3: Surface water – groundwater interaction coefficient (see remarks).
tw: Fixed depth of surface water at receiving node (ft or m) (set to zero if surface water depth will vary as computed by flow routing).
h: Groundwater table height which must be reached before any flows occurs (ft or m). Leave blank to use the height of the receiving node's invert above the aquifer bottom.
fl_eq_lat: To supply a custom equation for lateral groundwater flow. Enter an expression to use in addtion to the standard equation for lateral groundwater flow
fl_eq_deep: To supply a custom equation for deep groundwater flow. Enter an expression to use in addtion to the standard equation for deep groundwater flow
Remarks:
These coefficients (A1, A2, B1, B2 and A3) appear in the following equation that computes groundwater flow as a function of groundwater and surface water levels:
Qgw = A1 (Hgw - H*) B1 - A2 (Hsw - H*)B2 + A3 Hgw Hsw
Where:
Qgw = groundwater flow (cfs per acre or cms per hectare),
Hgw = height of saturated zone above bottom of aquifer (ft or m),
Hsw = height of surface water at receiving node above aquifer bottom (ft or m),
H* = threshold groundwater table height (ft or m).
Unit Hydrograph
Specifies the shapes of the triangular unit hydrographs that determine the amount of rainfall-dependent infiltration/inflow (RDII) entering the drainage system.
text: Should follow the format described below:
Name Raingage
Name Month SHORT/MEDIUM/LONG R T K (Dmax Drec D0)
Remarks:
Name: Name assigned to a unit hydrograph group.
Raingage: Name of the rain gage used by the unit hydrograph group.
Month: Month of the year (e.g., JAN, FEB, etc. or ALL for all months)
R: Response ratio for the unit hydrograph.
T: Time to peak (hours) for the unit hydrograph.
K: Recession limb ratio for the unit hydrograph.
Dmax: Maximum initial abstraction depth available (in rain depth units).
Drec: Initial abstraction recovery rate (in rain depth units per day).
D0: initial abstraction depth already filled at the start of the simulation (in rain depth units).
For each group of unit hydrographs, use one line to specify its rain gage followed by as many lines as are needed to define each unit hydrograph used by the group throughout
the year. Three separate unit hydrographs, that represent the short-term, medium-term, and long-term RDII responses, can be defined for each month (or all months taken
together). Months not listed are assumed to have no RDII.
The response ratio (R) is the fraction of a unit of rainfall depth that becomes RDII. The sum of the ratios for a set of three hydrographs does not have to equal 1.0.
The recession limb ratio (K) is the ratio of the duration of the hydrograph’s recession limb to the time to peak (T) making the hydrograph time base equal to T*(1+K) hours. The
area under each unit hydrograph is 1 inch (or mm).
The optional initial abstraction parameters determine how much rainfall is lost at the start of a storm to interception and depression storage. If not supplied then the default is no
initial abstraction.
Snowpack
Specifies parameters that govern how snowfall accumulates and melts on the plowable, impervious and pervious surfaces of subcatchments.
snow_id: ID label (name assigned to snowpack parameter set ).
cmin_1: Minimum melt coefficient (in/hr-deg F or mm/hr-deg C).
cmax_1: Maximum melt coefficient (in/hr-deg F or mm/hr-deg C).
tbase_1: Snow melt base temperature (deg F or deg C).
fwf_1: Ratio of free water holding capacity to snow depth (fraction).
sd0_1: Initial snow depth (in or mm water equivalent).
fw0_1: Initial free water in pack (in or mm).
snn0_1: Fraction of impervious area that can be plowed.
sd100_1: Snow depth above which there is 100% cover (in or mm water equivalent).
sd100_2: Snow depth above which there is 100% cover (in or mm water equivalent).
sdplow: Depth of snow on plowable areas at which snow removal begins (in or mm).
fout: Fraction of snow on plowable area transferred out of watershed.
fimp: Fraction of snow on plowable area transferred to impervious area by plowing.
fperv: Fraction of snow on plowable area transferred to pervious area by plowing.
fimelt: Fraction of snow on plowable area converted into immediate melt.
fsub: Fraction of snow on plowable area transferred to pervious area in another subcatchment.
subc_id: ID label (name of subcatchment receiving the Fsubcatch fraction of transferred snow).
Remarks:
Use one set of PLOWABLE, IMPERVIOUS, and PERVIOUS lines for each snow pack parameter set created. Snow pack parameter sets are associated with specific
subcatchments in the [SUBCATCHMENTS] [66] feature. Multiple subcatchments can share the same set of snow pack parameters.
The PLOWABLE line contains parameters for the impervious area of a subcatchment that is subject to snow removal by plowing but not to areal depletion. This area is the fraction
SNN0 of the total impervious area. The IMPERVIOUS line contains parameter values for the remaining impervious area and the PERVIOUS line does the same for the entire
pervious area. Both of the latter two areas are subject to areal depletion.
The REMOVAL line describes how snow removed from the plowable area is transferred onto other areas. The various transfer fractions should sum to no more than 1.0. If the line
is omitted then no snow removal takes place.
Lid catalog
Defines scale-independent LID controls that can be deployed within subcatchments.
lidco_id: ID label (name assigned to LID process).
lidco_type: The Lid Controls can be: SURFACE, SOIL, PAVEMENT, STORAGE, DRAIN.
value_2: Value dependent on Lidco type (see Remarks).
Remarks:
The first row must be as showed below:
lidco_id: ID label (name assigned to LID process).
lidco_type: BC for bio-retention cell; PP for porous pavement; IT for infiltration trench; RB for rain barrel; VS for vegetative swale
Values for SURFACE:
Value 2: StorHt: When confining walls or berms are present this is the maximum depth to which water can pond above the surface of the unit before overflow occurs (in inches or
mm). For LIDs that experience overland flow it is the height of any surface depression storage. For swales, it is the height of its trapezoidal cross section.
Value_3: VegFrac: Fraction of the area above the surface that is filled with vegetation.
Value_4: Rough: Manning's n for overland flow over the surface of porous pavement or a vegetative swale. Use 0 for other types of LIDs.
Value_5: Slope: Slope of porous pavement surface or vegetative swale (percent). Use 0
for other types of LIDs.
Value_6: Xslope: Slope (run over rise) of the side walls of a vegetative swale's cross section. Use 0 for other types of LIDs.
Values for SOIL:
Value_2: Thick: Thickness of the soil layer (inches or mm).

Value_3: Por: Soil porosity (volume of pore space relative to total volume).
Value_4: FC: Soil field capacity (volume of pore water relative to total volume after the soil has been allowed to drain fully).
Value_5: WP: Soil wilting point (volume of pore water relative to total volume for a well dried soil where only bound water remains).
Value_6: Ksat: Soil’s saturated hydraulic conductivity (in/hr or mm/hr).
Value_7: Kcoeff: Slope of the curve of log(conductivity) versus soil moisture content (dimensionless).
Value_8: Suct: Soil capillary suction (in or mm).
Values for PAVEMENT:
Value_2: Thick: Thickness of the pavement layer (inches or mm).
Стр. 7 из 16 03.03.2018, 12:27

Value_3: Vratio: Void ratio (volume of void space relative to the volume of solids in the pavement for continuous systems or for the fill material used in modular systems). Note that
porosity = void ratio / (1 + void ratio).
Value_4: FracImp: Ratio of impervious paver material to total area for modular systems; 0 for continuous porous pavement systems.
Value_5: Perm: Permeability of the concrete or asphalt used in continuous systems or hydraulic conductivity of the fill material (gravel or sand) used in modular systems (in/hr or
mm/hr).
Value_6: Vclog: Number of pavement layer void volumes of runoff treated it takes to completely clog the pavement. Use a value of 0 to ignore clogging.
Values for STORAGE:
Value_2: Height: Thickness of the storage layer or height of a rain barrel (inches or mm).
Value_3: Vratio: Void ratio (volume of void space relative to the volume of solids in the layer). Note that porosity = void ratio / (1 + void ratio).
Value_4: Filt: The filtration rate of the layer when first constructed (in/hr or mm/hr). If there is an impermeable floor or liner below the layer then use a value of 0.
Value_5: Vclog: Number of storage layer void volumes of runoff treated it takes to completely clog the layer. Use a value of 0 to ignore clogging.
Values for DRAIN:
Value_2: Coeff: Coefficient C that determines the rate of flow through the underdrain as a function of height of stored water above the drain bottom.
Value_3: Expon: Exponent n that determines the rate of flow through the underdrain as a function of height of stored water above the drain outlet.
Value_4: Offset: Height of underdrain piping or outlet above the bottom of the storage layer or rain barrel (inches or mm).
Value_5: Delay: The number of dry weather hours that must elapse before the drain line in a rain barrel is opened (the line is assumed to be closed once rainfall begins). This
parameter is ignored for other types of LIDs.
Values for DRAINAGE MAT:
Value_2: Thickness (in or mm)

Value_3: Void fraction
Value_4: Roughness (Mannings n)
The following table shows which layers are required (x) or are optional (o) for each type of LID process:
LID type SURFACE PAVEMENT SOIL STORAGE DRAIN DRAINAGE MAT
Bio Retention Cell x x x o
Porous Pavement x x x o
Infiltration Trench x x o
Rain Barrel x x
Vegetative Swale x
Green Roof x x x
Rain Garden x x
The equation used to compute flow rate out of the underdrain per unit area of the LID (in in/hr or mm/hr) is q = C (h - Hd) n where q is outflow, h is height of stored water (inches
or mm) and Hd is the drain offset height.
The actual dimensions of an LID control are provided in the [LID_USAGE] [67] table when it is placed in a particular subcatchment.
Lid usage (subc. x lid)

Deploys LID controls within specific subcatchment areas.
subc_id: ID label (name of the subcatchment using the LID process).
lidco_id: ID label (name of an LID process defined in the [LID_CONTROLS] table).
number: The number of replicate LID units deployed.
area: The area of each replicate unit (ft2 or m2).
width: The width of the outflow face of each identical LID unit (in ft or m). This parameter only applies to LID processes such as porous pavement and vegetative swales that use
overland flow to convey surface runoff off of the unit. (The other LID processes, such as bio-retention cells and infiltration trenches simply spill any excess captured runoff over
their berms.)
initsat: The percent to which the unit's soil layer or storage layer is initially filled with water.
fromimp: The percent of the impervious portion of the subcatchment's non-LID area whose runoff is treated by the LID units. If the LID unit treats only direct rainfall, such as with a
green roof, then this value should be 0. If the LID takes up the entire subcatchment then this field is ignored.
toperv: 1 if the outflow from the LID is returned onto the subcatchment's pervious area rather than going to the subcatchment's outlet; 0 otherwise. An example of where this might
apply is a rain barrel whose contents are used to irrigate a lawn area. This field is ignored if the LID takes up the entire subcatchment.
rptfile: Optional name of a file to which detailed time series results for the LID will be written. Enclose the name in double quotes if it contains spaces and include the full path if it is
different than the SWMM input file path.
Remarks:
More than one type of LID process can be deployed within a subcatchment as long as their total area does not exceed that of the subcatchment and the total percent impervious
area treated does not exceed 100.
Hydraulics
Node
Junction
Identifies each junction node of the drainage system. Junctions are points in space where channels and pipes connect together. For sewer systems they can be either connection
fittings or manholes.
node_id: ID label (name assigned to junction node).
y0: Water depth at start of simulation (ft or m) (default is 0).
ysur: Maximum additional head above ground elevation that manhole junction can sustain under surcharge conditions (ft or m) (default is 0).
apond: area subjected to surface ponding once water depth exceeds Ymax (ft2 or m2) (default is 0).
sector_id: Sector where there is the junction.
Outfall
Identifies each outfall node (i.e., final downstream boundary) of the drainage system and the corresponding water stage elevation. Only one link can be incident on an outfall node.
node_id: ID label (name assigned to outfall node).
top_elev: Top elevation (ft or m).
outfall_type: An outfall can be: FREE, NORMAL, FIXED, TIDAL or TIMESERIES.
stage: Elevation of fixed stage outfall (ft or m).
curve_id: ID label (name of curve in [CURVES] table containing tidal height (i.e., outfall stage) v. hour of day over a complete tidal cycle).
timser_id: ID label (name of time series in [TIMESERIES] [68] table that describes how outfall stage varies with time).
gate: YES or NO depending on whether a flap gate is present that prevents reverse flow.
sector_id: Sector where there is the outfall.
Divider
Identifies each flow divider node of the drainage system. Flow dividers are junctions with exactly two outflow conduits where the total outflow is divided between the two in a
prescribed manner.
node_id: ID label (name assigned to divider node).
divider_type: A divider can be: OVERFLOW, CUTOFF, TABULAR or WEIR.
arc_id: ID label (name assigned to arc)
curve_id: ID label (name of curve for TABULAR divider that relates diverted flow to total flow).
qmin: Flow at which diversion begins for either a CUTOFF or WEIR divider (flow units).
ht: Height of WEIR divider (ft orm).
cd: Discharge coefficient for WEIR divider.
ysur: Maximum additional head above ground elevation that node can sustain under surcharge conditions (ft or m) (default is 0).
apond: Area subjected to surface ponding once water depth exceeds Ymax (ft2 or m2) (default is 0).
sector_id: Sector where there is the divider.
Storage
Identifies each storage node of the drainage system. Storage nodes can have any shape as specified by a surface area versus water depth relation.
node_id: ID label (name assigned to storage node).
top_elev: Top elevation (ft or m).
ymax: Maximum water depth possible (ft or m).
storage_type: A sotrage can be: TABULAR or FUNCTIONAL.
curve_id: ID label (name of curve in [CURVES] [64] table with surface area (ft2 or m2) as a function of depth (ft or m) for TABULAR geometry).
a1: Coefficient of FUNCTIONAL relation between surface area and depth.
a2: Exponent of FUNCTIONAL relation between surface area and depth.
a0: Constant of FUNCTIONAL relation between surface area and depth.
fevap: Fraction of potential evaporation from surface realized (default is 0).
sh: Soil capillary suction head (in or mm).
hc: Soil saturated hydraulic conductivity (in/hr or mm/hr).
imd: Initial soil moisture deficit (volume of voids / total volume).
ysur: Maximum additional head above ground elevation that node can sustain under surcharge conditions (ft or m) (default is 0).
apond: Area subjected to surface ponding once water depth exceeds Ymax (ft2 or m2) (default is 0).
sector_id: Sector where there is the storage.
Remarks:
A1, A2, and A0 are used in the following expression that relates surface area (ft2 or m2) to water depth (ft or m) for a storage unit with FUNCTIONAL geometry:
Area = A0 + A1 x DepthA2
Dwf
Specifies dry weather flow and its quality entering the drainage system at specific nodes.
node_id: ID label (name of node where dry weather flow enters).
value: Average baseline value for corresponding Item (flow or concentration units).
pat1
...
pat4: Name of up to four time patterns appearing in the [PATTERNS] [69] table.
Remarks:
The actual dry weather input will equal the product of the baseline value and any adjustment factors supplied by the specified patterns. (If not supplied, an adjustment factor defaults
to 1.0.)
Inflow
Specifies external hydrographs and pollutographs that enter the drainage system at specific nodes.
node_id: ID label (name of node where external inflow enters).
timser_id: ID label (name of time series in [TIMESERIES] [64] table describing how external inflows vary with time).
sfactor: Scaling factor that multiplies the recorded time series values (default is 1.0).
base: Constant baseline value added to the time series value (default is 0.0).
pattern_id: Name of optional time pattern in [PATTERNS] [69] table used to adjust the baseline value on a periodic basis.
Remarks:External inflows are represented by both a constant and time varying component as follows:
Inflow = (Baseline value)*(Pattern factor) + (Scaling factor)*(Time series value)
If an external inflow of a pollutant concentration is specified for a node, then there must also be an external inflow of FLOW provided for the same node, unless the node is an
Outfall. In that case a pollutant can enter the system during periods when the outfall is submerged and reverse flow occurs.
RDII (node)
Specifies the parameters that describe rainfall-dependent infiltration/inflow (RDII) entering the drainage system at specific nodes.
node_id: ID label (name of a node).
hydro_id: ID label (name of an RDII unit hydrograph group specified in the [HYDROGRAPHS] [70] table).
sewerarea: Area of the sewershed which contributes RDII to the node (acres or hectares).
Arc
Conduit
Identifies each conduit link of the drainage system. Conduits are pipes or channels that convey water from one node to another.
arc_id: ID label (name assigned to conduit link).
z1: Value of upstream node (see figure below)
z2: Value of downstream node (see figure below)
arccat_id: Arc type as stated in the catalog of arches.
barrels: Number of barrels (i.e., number of parallel pipes of equal size, slope, and roughness) associated with a conduit (default is 1).
culvert: Code number from Table A.10 (from Appendix A of SWMM's Manual) [71] for the conduit's inlet geometry if it is a culvert subject to possible inlet flow control (leave blank
otherwise)
kentry: Entrance minor head loss coefficient.
kexit: Exit minor head loss coefficient.
kavg: Average minor head loss coefficient across length of conduit.
flap: YES if conduit has a flap gate that prevents back flow, NO otherwise (default is NO).
q0: Flow in conduit at start of simulation (flow units) (default is 0).
qmax: Maximum flow (flow units)
seepage: Rate of seepage loss into surrounding soil
sector_id: Sector where there is the conduit.
Remarks:
The figure below illustrates the meaning of the Z1 and Z2 parameters.
These offsets are expressed as a relative distance above the node invert if the LINK_OFFSETS option is set to DEPTH (the default) or as an absolute elevation if it is set to
ELEVATION.
Orifice
Identifies each orifice link of the drainage system. An orifice link serves to limit the flow exiting a node and is often used to model flow diversions.
arc_id: ID label (name assigned to orifice link).
ori_type: Orientation of orifice: either SIDE or BOTTOM.
_offset: Amount that a Side Orifice’s bottom or the position of a Bottom Orifice is offset above the invert of inlet node (ft or m, expressed as either a depth or as an elevation,
depending on the LINK_OFFSETS option setting).
cd: Discharge coefficient (unitless).
orate: Time in decimal hours to open a fully closed orifice (or close a fully open one). Use 0 if the orifice can open/close instantaneously.
flap: YES if flap gate present to prevent reverse flow, NO if not (default is NO).
shape: The only allowable shapes are CIRCULAR and RECT_CLOSED (closed rectangular).
geom1: Maximum depth (ft or m).
geom2: Width parameter (ft or m)
geom3: Auxiliary parameters (width,side,slopes, etc.) as listed in Table D-1 from Appendix D of SWMM's Manual.
sector_id: Sector where there is the orifice.
Remarks:
The only allowable shapes are CIRCULAR and RECT_CLOSED (closed rectangular).
Weir
Identifies each weir link of the drainage system. Weirs are used to model flow diversions.
arc_id: ID label (name assigned to weir link.)
weir_type: A weir can be: TRANSVERSE, SIDEFLOW, V-NOTCH, or TRAPEZOIDAL.
_offset: Amount that the weir’s crest is offset above the invert of inlet node (ft or m, expressed as either a depth or as an elevation, depending on the LINK_OFFSETS option
setting).
cd: Weir discharge coefficient (for CFS if using US flow units or CMS if using metric flow units).
ec: Number of end contractions for TRANSVERSE or TRAPEZOIDAL weir (default is 0).
cd2: Discharge coefficient for triangular ends of a TRAPEZOIDAL weir (for CFS if using US flow units or CMS if using metric flow units) (default is value of Cd).
geom1: Full height of the cross-section (ft or m)
surcharge: Identifies if weir can surcharge or not
sector_id: Sector where there is the weir.
Remarks:
The following shapes must be used with each type of weir:
Weir type Cross-Section shape
Transverse RECT_OPEN
Sideflow RECT_OPEN
V-Notch TRIANGULAR
Trapezoidal TRAPEZOIDAL
Pump
Identifies each pump link of the drainage system.
arc_id: ID label (name assigned to pump link).
curve_id: ID label (name of pump curve listed in the [CURVES] table of the input).
status: Status at start of simulation (either ON or OFF; default is ON).
start_up: Depth at inlet node when pump turns on (ft or m) (default is 0).
shutoff: Depth at inlet node when pump shuts off (ft or m) (default is 0).
Remarks:
See chapter 3.2.8 os SWMM's Manual [72], for a description of the different types of pumps available.
Outlet
Identifies each outlet flow control device of the drainage system. These devices are used to model outflows from storage units or flow diversions that have a user-defined relation
between flow rate and water depth.
arc_id: ID label (name assigned to outlet link).
outlet_type: A outlet can be: TABULAR / DEPTH, TABULAR / HEAD, FUNCTIONAL / DEPTH or FUNCTIONAL / HEAD.
_offset: Amount that the outlet is offset above the invert of inlet node (ft or m, expressed as either a depth or as an elevation, depending on the LINK_OFFSETS option setting).
curve_id: ID label (name of the rating curve listed in the [CURVES] [64] table that describes outflow rate (flow units) as a function of:
water depth above the offset elevation at the inlet node (ft or m) for a TABULAR/DEPTH outlet
head difference (ft or m) between the inlet and outflow nodes for a TABULAR/HEAD outlet.
cd1
cd2: coefficient and exponent, respectively, of a power function that relates outflow (Q) to:
water depth (ft or m) above the offset elevation at the inlet node for a FUNCTIONAL/DEPTH outlet
head difference (ft or m) between the inlet and outflow nodes for a FUNCTIONAL/HEAD outlet. (i.e., Q = C1(H)C2 where H is either depth or head).
sector_id: Sector where there is the outlet.
Transects
Describes the cross-section geometry of natural channels or conduits with irregular shapes following the HEC-2 data format.
text: Should follow the format described below:
NC Nleft Nright Nchanl

X1 Name Nsta Xleft Xright 0 0 0 Lfactor Wfactor Eoffset
GR Elev Station ... Elev Station
Remarks:
Nleft: Manning’s n of right overbank portion of channel (use 0 if no change from previous NC line).
Nright: Manning’s n of right overbank portion of channel (use 0 if no change from previous NC line).
Nchanl: Manning’s n of main channel portion of channel (use 0 if no change from previous NC line).
Name: Name assigned to transect.
Nsta: Number of stations across cross-section at which elevation data is supplied.
Xleft: Station position which ends the left overbank portion of the channel (ft or m).
Xright: Station position which begins the right overbank portion of the channel (ft or m).
Lfactor: Meander modifier that represents the ratio of the length of a meandering main channel to the length of the overbank area that surrounds it (use 0 if not applicable).
Wfactor: Factor by which distances between stations should be multiplied to increase (or decrease) the width of the channel (enter 0 if not applicable).
Eoffset: Amount added (or subtracted) from the elevation of each station (ft or m).
Elev: Elevation of the channel bottom at a cross-section station relative to some fixed reference (ft or m).
Station: Distance of a cross-section station from some fixed reference (ft or m).
Transect geometry is described as shown below, assuming that one is looking in a downstream direction:
The first line in this section must always be a NC line. After that, the NC line is only needed when a transect has different Manning’s n values than the previous one.
The Manning’s n values on the NC line will supersede any roughness value entered for the conduit which uses the irregular cross-section.
There should be one X1 line for each transect. Any number of GR lines may follow, and each GR line can have any number of Elevation-Station data pairs. (In HEC-2 the GR line
is limited to 5 stations.)
The station that defines the left overbank boundary on the X1 line must correspond to one of the station entries on the GR lines that follow. The same holds true for the right
overbank boundary. If there is no match, a warning will be issued and the program will assume that no overbank area exists.
The meander modifier is applied to all conduits that use this particular transect for their cross section. It assumes that the length supplied for these conduits is that of the longer
main channel. SWMM will use the shorter overbank length in its calculations while increasing the main channel roughness to account for its longer length.
Quality
Pollutant
Identifies the pollutants being analyzed.
poll_id: ID label (name assigned to pollutant).
units_type: Concentration units (MG/L for milligrams per liter, UG/L for micrograms per liter, or #/L for direct count per liter).
crain: Concentration of pollutant in rainfall (concentration units).
cgw: Concentration of pollutant in groundwater (concentration units).
cii: Concentration of pollutant in inflow/infiltration (concentration units).
kd: First-order decay coefficient (1/days).
sflag: YES if pollutant buildup occurs only when there is snow cover, NO otherwise (default is NO).
copoll_id: ID label (name of co-pollutant (default is no co-pollutant)).
cofract: Fraction of co-pollutant concentration (default is 0).
cdwf: Concentration of pollutant in dry weather flow (concentration units).
Remarks:
FLOW is a reserved word and cannot be used to name a pollutant.
If pollutant buildup is not restricted to times of snowfall and there is no co-pollutant, then the last three parameters can be omitted.
When pollutant X has a co-pollutant Y, it means that fraction CoFract of pollutant Y’s runoff concentration is added to pollutant X’s runoff concentration when wash off from a
subcatchment is computed.
The dry weather flow concentration can be overriden for any specific node of the conveyance system by editing the node’s Inflows property.
Landuse
Identifies the various categories of land uses within the drainage area. Each subcatchment area can be assigned a different mix of land uses. Each land use can be subjected to a
different street sweeping schedule.
landus_id: ID (label land use name).
sweepint: Days between street sweeping.
availab: Fraction of pollutant buildup available for removal by street sweeping.
lastsweep: Days since last sweeping at start of the simulation.
Coverage (landuses x subc.)

Specifies the percentage of a subcatchment’s area that is covered by each category of land use.
subc_id: ID label (subcatchment name).
landus_id: ID label (land use name).
percent: Percent of subcatchment area.
Remarks:
More than one pair of land use - percentage values can be entered per line. If more than one line is needed, then the subcatchment name must still be entered first on the
succeeding lines.
If a land use does not pertain to a subcatchment, then it does not have to be entered.
If no land uses are associated with a subcatchment then no contaminants will appear in the runoff from the subcatchment.
Buildup (poll. x landuses)

Specifies the rate at which pollutants build up over different land uses between rain events.
poll_id: ID label (pollutant name).
funcb_type: Buildup function type: ( POW / EXP / SAT / EXT ).
c1
c2
c3: Buildup function parameters (see Table D-2 from Appendix D of SWMM's Manual).
perunit: AREA if buildup is per unit area, CURBLENGTH if per length of curb.
Remarks:
Buildup is measured in pounds (kilograms) per unit of area (or curb length) for pollutants whose concentration units are either mg/L or ug/L. If the concentration units are counts/L,
then the buildup is expressed as counts per unit of area (or curb length).
Loading (poll. x subc.)

Specifies the pollutant buildup that exists on each subcatchment at the start of a simulation.
poll_id: ID label (name of a pollutant).
subc_id: ID label (name of a subcatchment).
ibuildup: Initial buildup of pollutant (lbs/acre or kg/hectare).
Remarks:
More than one pair of pollutant - buildup values can be entered per line. If more than one line is needed, then the subcatchment name must still be entered first on the succeeding
lines.
If an initial buildup is not specified for a pollutant, then its initial buildup is computed by applying the DRY_DAYS option (specified in the [OPTIONS] option parameters) to the
pollutant’s buildup function for each land use in the subcatchment.
Inflow (poll. x node)

Specifies external hydrographs and pollutographs that enter the drainage system at specific nodes.
poll_id: ID label (name of pollutant).
node_id: ID label (name of node where external inflow enters).
timser_id: ID label (name of time series in [TIMESERIES] table describing how external inflows vary with time.
form_type: CONCEN if pollutant inflow is described as a concentration, MASS if it is described as a mass flow rate (default is CONCEN).
mfactor: The factor that converts the inflow’s mass flow rate units into the project’s mass units per second, where the project’s mass units are those specified for the pollutant in the
[POLLUTANTS] table (default is 1.0).
sfactor: Caling factor that multiplies the recorded time series values (default is 1.0).
pattern_id: Name of optional time pattern in [PATTERNS] table used to adjust the baseline value on a periodic basis.
Remarks:
External inflows are represented by both a constant and time varying component as follows:
Inflow = (Baseline value)*(Pattern factor) + (Scaling factor)*(Time series value)
If an external inflow of a pollutant concentration is specified for a node, then there must also be an external inflow of FLOW provided for the same node, unless the node is an
Outfall. In that case a pollutant can enter the system during periods when the outfall is submerged and reverse flow occurs.
Washoff (poll. x landuses)

Specifies the rate at which pollutants are washed off from different land uses during rain events.
poll_id: ID label (pollutant name).
funcw_type: Washoff function type: EXP / RC / EMC.
c1
c2: Washoff function coefficients(see Table D-3 from Appendix D of SWMM's Manual).
sweepeffic: Street sweeping removal efficiency (percent).
bmpeffic: BMP removal efficiency (percent).
Remarks:
See Table D-3 in Appendix A of SWMM's Manual.
Each washoff function expresses its results in different units.
For the Exponential function the runoff variable is expressed in catchment depth per unit of time (inches per hour or millimeters per hour), while for the Rating Curve function it is in
whatever flow units were specified in the [OPTIONS] table of the input file (e.g., CFS, CMS, etc.). The buildup parameter in the Exponential function is the current total buildup over
the subcatchment’s land use area in mass units. The -units of C1 in the Exponential function are (in/hr) C2 per hour (or (mm/hr) -C2 per hour). For the Rating Curve function, the
units of C1 depend on the flow units employed. For the EMC (event mean concentration) function, C1 is always in concentration units.
Dwf (poll. x node)

Specifies pollutant inflow to drainage system at specific nodes.
poll_id: ID label (pollutant name)
node_id: ID label (name of node where dry weather flow enters).
value: Average baseline value for corresponding Item (flow or concentration units).
pat1
...
pat4: Names of up to four time patterns appearing in the [PATTERNS] table.
Remarks:
The actual dry weather input will equal the product of the baseline value and any adjustment factors supplied by the specified patterns. (If not supplied, an adjustment factor defaults
to 1.0.)
Treatment (poll. x node)

Specifies the degree of treatment received by pollutants at specific nodes of the drainage system.
node_id: ID label (name of node where treatment occurs).
poll_id: ID label (name of pollutant receiving treatment).
function: Mathematical function expressing treatment result in terms of pollutant concentrations, pollutant removals, and other standard variables (see Remarks). In treatment
function we can choose between:
C – function computes effluent concentration

R – function computes fractional removal.
Examples:
;1-st order decay of BOD
Node23 BOD C = BOD * exp(-0.05*HRT)
; lead removal is 20% of TSS removal

Node23 Lead R = 0.2 * R_TSS
Remarks:
Treatment functions can be any well-formed mathematical expression involving:
inlet pollutant concentrations (use the pollutant name to represent a concentration)

removal of other pollutants (use R_ prepended to the pollutant name to represent removal)
process variables which include:
FLOW for flow rate into node (user’s flow units) DEPTH for water depth above node invert (ft or m) AREA for node surface area (ft2 or m2)
DT for routing time step (seconds)
HRT for hydraulic residence time (hours)
Curves & Timeseries

Curve catalog
Curve catalog. This table could be edited through giswater control panel: Giswater → Data → Curves
curve_type: STORAGE / DIVERSION / TIDAL / PUMP1 / PUMP2 / PUMP3 / PUMP4 / RATING.
Curve values
Table relative to curve values. This table could be edited through giswater control panel: Giswater → Data → Curves
curve_id: Name assigned to table.
x_value: An x (independent variable) value.
y_value: The y (dependent variable) value corresponding to x.
Timeseries catalog
Timeseries catalog. This table could be edited trough giswater control panel: Giswater → Data → Timeseries
timser_type: Time series type.
times_type: Times type.
Timeseries values
Table relative to timeseries values. This table could be edited trough giswater control panel: Giswater → Data → Timeseries
timser_id: ID label (name assigned to time series).
date: Date in Month/Day/Year format (e.g., June 15, 2001 would be 6/15/2001).
hour: 24-hour military time (e.g., 8:40 pm would be 20:40) relative to the last date specified (or to midnight of the starting date of the simulation if no previous date was specified).
time: Hours since the start of the simulation, expressed as a decimal number or as hours:minutes.
value: Value corresponding to given date and time.
fname: Name of a file in which the time series data are stored.
Remarks:
There are two options for supplying the data for a time series:
i. directly within this input file section as described by the first two formats
ii. through an external data file named with the third format.
When direct data entry is used, multiple date-time-value or time-value entries can appear on a line. If more than one line is needed, the table's name must be repeated as the first
entry on subsequent lines.
When an external file is used, each line in the file must use the same formats listed above, except that only one date-time-value (or time-value) entry is allowed per line. Any line
that begins with a semicolon is considered a comment line and is ignored. Blank lines are not allowed.
Note that there are two methods for describing the occurrence time of time series data:
as calendar date/time of day (which requires that at least one date, at the start of the series, be entered)
as elapsed hours since the start of the simulation.
For the first method, dates need only be entered at points in time when a new day occurs.
Value domain
Folder with tables used on other tables as value domain data. Gis projects uses this tables but data is not updatable. You do not have to do anything, but you can not delete it.
Material Catalog
Material catalog with hydraulic data. Your project need minimun at once. This table could be edited trough giswater control panel: Giswater → Data → Material catalog
descript: Material description.
n: Manning coefficient [73].
Arc catalog
Table with arc catalog data. Your project need minimun at once. This table could be edited trough giswater control panel: Giswater → Data → Arc catalog
shape: Cross-section shape (see Table 3-1 for available shapes of SWMM's Manual [74])
tsect_id: ID label (name of an entry in the transects table than describes the cross-section geometry of an irregular channel)
curve_id: ID label (name of a Shape Curve in the [CURVES] [64] table that defines how width varies with depth)
geom1: Auxiliary parameters (e.g., side slopes) (See Table D-1 for details of SWMM's Manual)
geom_r: Real geometry we use when we can not describe the geometry with the above fields.
short_des: Short description.
descript: Arc description.
Patterns
Specifies time pattern of dry weather flow or quality in the form of adjustment factors applied as multipliers to baseline values. This table could be edited trough giswater control
panel: Giswater → Data → Patterns
pattern_id: ID label (name used to identify the pattern)
pattern_type: A pattern can be: MONTHLY, DAILY, HOURLY or WEEKEND (see Remarks)
factor_1: Multiplier values.
...
Remarks:
The MONTHLY format is used to set monthly pattern factors for dry weather flow constituents.
The DAILY format is used to set dry weather pattern factors for each day of the week, where Sunday is day 1.
The HOURLY format is used to set dry weather factors for each hour of the of the day starting from midnight. If these factors are different for weekend days than for weekday days
then the WEEKEND format can be used to specify hourly adjustment factors just for weekends.
More than one line can be used to enter a pattern’s factors by repeating the pattern’s name (but not the pattern type) at the beginning of each additional line.
The pattern factors are applied as multipliers to any baseline dry weather flows or quality concentrations supplied in the [DWF] [75] table.
Controls
Determines how pumps and regulators will be adjusted based on simulation time or conditions at specific nodes and links.
text: Should follow the format described below. Each control rule is a series of statements of the form:
Example:
RULE R1
IF SIMULATION TIME > 8
THEN PUMP 12 STATUS = ON ELSE PUMP 12 STATUS = OFF
Remarks:
RuleID an ID label assigned to the rule.
condition_n a condition clause.
action_n an action clause.
value a priority value (e.g., a number from 1 to 5).
A condition clause of a Control Rule has the following format: Object Name Attribute Relation Value where Object is a category of object, Name is the object’s assigned ID
name, Attribute is the name of an attribute or property of the object, Relation is a relational operator (=, <>, <, <=, >, >=), and Value is an attribute value.
SIMULATION ANALYSIS
Arc flow
Arc flow simulations analysis data.
arc_type: Arc type.
max_flow: Maximum total inflow (CMS).
time_days: Time of max occurrence (days).
time_hour: Time of max occurrence (hr:min)
max_veloc: Maximum velocity (m/sec)
mfull_flow: Maximum full flow.
mfull_dept: Maximum full depth.
max_shear: Maximum shear
max_hr: Maximun hidraulic radius
max_slope: Maximum slope
day_max: Time of max occurrence (days)
time_max: Time of max occurrence (hr:min)
min_shear: Minimum shear
day_min: Time of min occurrence (days)
time_min:Time of min occurrence (hr:min)
Conduit surcharge
Conduit surcharge simulations analysis data.
both_ends: Both ends.
upstream: Upstream.
dnstream: Downstream.
hour_nflow: Hours above full normal flow.
hour_limit: Hours capacity limited.
sector_id: Sector where there is the conduit.
Pumping summary
Pumping summary simulations analysis data.
percent: Percent utilized.
max_flow: Maximum flow (cms).
avg_flow: Average flow (cms).
vol_ltr: Total volume (10^6 ltr).
powus_kwh: Power usage (Kw-hr).
timoff_cur: % Time off curve.
Flow class
Flow classification simulations analysis data.
length: Adjusted / Actual length.
dry: Dry.
up_dry: Up dry.
down_dry: Down dry.
sub_crit: Sub crit.
sub_crit_1: Sub crit.
up_crit: Up crit.
sector_id: Sector where there is the flow.
Node flooding
Node flooding simulations analysis data.
node_id: ID name assigned to node.
hour_flood: Hours flooded.
max_rate: Maximum rate (cms).
time_hour: Time of max occurrence (hr:min).
tot_flood: Total flood volume (10^6 ltr).
max_ponded: Maximum ponded depth (meters).
Node surcharge
Node surcharge simulations analysis data.
swnod_type:
hour_surch: Hous surcharged.
max_height: Maximum height above crown (meters).
min_depth: Minimum depth below rim (meters).
sector_id: Sector where is the node.
Node inflow
Node inflowsimulations analysis data.
swnod_type: Node type, on SWMM model. Remember JUNCTION, OUTFALL, DIVIDER or STORAGE.
max_latinf: Maximum lateral inflow (cms).
max_totinf: Maximum total inflow (cms).
latinf_vol: Lateral inflow volume (10^6 ltr).
totinf_vol: Total inflow volume (10^6 ltr).
flow_balance_error: Error of flow balance
Node depth
Node depth simulations analysis data.
swnod_type:
aver_depth: Average depth (meters).
max_depth: Maximum depth (meters).
max_hgl: Maximum HGL (meters).
Outfall flow
Outfall flow simulations analysis data.
flow_freq: Flow frequency. (Percentage).
avg_flow: Average flow (cms).
max_flow: Maximum flow (cms).
total_vol: Total volume (10^6 ltr).
sector_id: Sector where is the outfall.
Outfall load
Outfall load simulations analysis data
poll_id: ID name assigned to pollutant.
value: Value.
sector_id: Sector where is the outfall.
Storage volume
Storage volume simulations analysis data.
aver_vol: Average volume 1000m3.
avg_full: Average percentage full.
ei_loss: E&I Percentage loss.
max_vol: Maximum volume 1000m3.
max_full: Maximum percentage full.
max_out: Maximum outflow (cms).
sector_id: Sector where is the storage.
Subcatchment runoff
Subcatchment runoff simulations analysis data.
subc_id: Name assigned to subcatchment.
tot_precip: Total precipitation (mm).
tot_runon: Total runon (mm).
tot_evap: Total evaporation (mm).
tot_infil: Total infiltration (mm).
tot_runoff: Total runoff (mm).
tot_runofl: Total runoff (10^6 ltr).
peak_runof: Peak runoff (cms).
runoff_coe: Runoff coefficient.
vxmax: Maximum velocity on x axis
vymax: Maximum velocity on y axis
depth: Maximum depth
vel: Maximum velocity
vhmax: Maximum (velocity x depth) value
sector_id: Sector where is the subcatchment.
Subcatchment washoff
Subcatchment washoff simulations analysis data.
value: Value.
sector_id: Sector where is the subcatchment.
Arc pollutant load

Arc pollutant load simulations analysis data.
poll_id: ID for the pollutant
LID performance
LID performance simulations analysis data.
lidco_id: ID LID control.
tot_inflow: Total inflow (mm).
evap_loss: Evaporation loss (mm).
infil_loss: Infiltration loss (mm).
surf_outf: Surface outflow (mm).
drain_outf: Drain outflow (mm).
init_stor: Initial Storage (mm).
final_stor: Final Storage (mm).
per_error: Percentage error.
sector_id: Sector where is the lid.
Rainfall dependent
Rainfall dependent simulations analysis data.
sewer_rain: Sewershed Rainfall.
rdiip_prod: RDII Produced.
rdiir_rat: RDII Ratio.
Runoff quality
Runoff quality simulations analysis data.
init_buil: Initial Buildup.
surf_buil: Surface Buildup.
wet_dep: Wet Deposition.
sweep_re: Sweeping Removal.
infil_loss: Infiltration Loss.
bmp_re: BMP Removal.
surf_runof: Surface Runoff.
rem_buil: Remaining Buildup.
cont_error: Continuity Error (%).
Runoff quantity
Runoff quantiity simulations analysis data.
Стр. 8 из 16 03.03.2018, 12:27

initsw_co: Initial Snow Cover.
total_prec: Total Precipitation.
evap_loss: Evaporation Loss.
infil_loss: Infiltration Loss.
surf_runof: Surface Runoff.
snow_re: Snow Removed.
finalsw_co: Final Snow Cover.
finals_sto: Final Surface Storage.
initlid_sto: Initial storage on LID.
Groundwater continuity
Groundwater continuity simulations analysis data.
init_stor: Initial Storage.
infilt: Infiltration.
upzone_et: Upper Zone ET.
lowzone_et: Lower Zone ET.
deep_perc: Deep Percolation.
groundw_fl: Groundwater Flow.
final_stor: Final Storage.
Flow routing continuity

Flow routing continuity simulations analysis data.
dryw_inf: Dry Weather Inflow.
wetw_inf: Wet Weather Inflow.
ground_inf: Groundwater Inflow.
rdii_inf: RDII Inflow.
ext_inf: External Inflow.
ext_out: External Outflow.
int_out: Internal Outflow.
stor_loss: Storage Losses.
initst_vol: Initial Stored Volume.
finst_vol: Final Stored Volume.
evap_losses: Losses of evaporation
seepage_losses: Losses of seepage.
Quality routing continuity

Quality routing continuity simulations analysis data.
dryw_inf: Dry Weather Inflow.
wetw_inf: Wet Weather Inflow.
ground_inf: Groundwater Inflow.
rdii_inf: RDII Inflow.
ext_inf: External Inflow.
int_inf: Internal Flooding.
ext_out: External Outflow.
mass_reac: Mass Reacted.
initst_mas: Initial Stored Mass.
finst_mas: Final Stored Mass.
Continuity errors
Continuity errors simulations analysis data.
text: 'Text'.
High continuity errors

High continuity errors simulations analysis data.
text: 'Text'.
Critical elements
Critical elements simulations analysis data.
text: 'Text'.
Timestep critical elements

Timestep critical elements simulations analysis data.
text: 'Text'.
Instability index
Instability index simulations analysis data.
text: 'Text'.
High flow instability index

High flow instability index simulations analysis data.
text: 'Text'.
Routing timestep
Routing timestep simulations analysis data.
text: 'Text'.
3- HEC-RAS
The next TOC (Table of contents of GIS interface) will be avaliable when you create HEC-RAS GIS project: Giswater → GISProject
Стр. 9 из 16 03.03.2018, 12:27

APPENDIX B - DBF DATA MODEL SPECIFICATIONS

In this appendix you will found information about GIS projects on DBF storage mode.
Remember, on DBF storage mode when you create the GIS project, the only files created are DBF and Shape files and a basic project file only with shape and someone DBF.
Here you can get all DBF datamodel you need:
EPANET DBF data model specifications [76]
EPA SWMM DBF data model specifications [77]
EPA SWMM 5.0.022

Shp
The shp files you need create are:
arc
The shp file contains the following fields:
arc_id: (string; 16) Name assigned to conduit link.
node_1: (string; 16) Name of upstream node.
node_2: (string; 16) Name of downstream node.
lenght: (double; 18, 6) Conduit lenght (ft or m).
n: (double; 18, 6) Value of N (i. e., roughness parameter) in Manning's equation.
z1: (double; 18, 6) Offset of upstream end of conduit invert above the invert elevation of its upstream node (ft or m).
z2: (double; 18, 6) Offset of downstream end of conduit invert above the invert elevation of its downstream node (ft or m).
q0: (double; 18, 6) Flow in conduit at start of simulation (flow units; default is 0).
shape: (string; 20) Cross-section shape (see Table 3-1 for available shapes of SWMM's Manual).
label: (string; 12) Text of label surrounded by double quotes.
geom1: (double; 18, 6) Full height of the cross-section (ft or m).
geom2: (double; 18, 6) Width parameter (ft or m).
geom3: (double; 18, 6) Auxiliary parameters (e. g., side slopes) (see Table D-1 for details of SWMM's Manual).
material: (string; 30) Type of material.
direction: (string; 2) Direction of flow of water.
swmm_type: (string; 20) Type of pipe as SWMM.
arc_type: (string; 20) Type of pipe.
sector_id: (string; 16) Name assigned to sector.
link: (string; 254) Link for searching files.
node
node_id: (string; 16) Name assigned to node.
elev: (double; 18, 6) Elevation of junction invert (ft or m).
ymax: (double; 18, 6) Depth from ground to invert elevation (ft or m; default is 0).
xcoord: (double; 18, 6) Horizontal coordinate of vertex relative to origin in lower left of map.
ycoord: (double; 18, 6) Vertical coordinate of vertex relative to origin in lower left of map.
y0: (double; 18, 6) Water depth at start of simulation (ft or m; default is 0).
ysur: (double; 18, 6) Maximum additional head above ground elevation that manhole junction can sustain under surcharge conditions (ft or m; default is 0).
apond: (double; 18, 6) Area subjected to surface ponding once water depth exceeds ymax (ft2 or m2).
swmm_type: (string; 20) Type of node as SWMM.
node_type: (string; 20) Type of node.
raingage
rg_id: (string; 16) Name assigned to rain gage.
form_type: (string; 12) Form to recorded rainfall, either INTENSITY, VOLUME or CUMULATIVE.
intvl: (string; 10) Time interval between gage readings (in decimal hours or hours:minutes format).
scf: (double; 12, 4) Snow catch deficiency correction factor (use 1 for no adjustament).
rgage_type: (string; 18) Type of rain gage.
type_rgfl: (string; 18) FILE.
type_rgts: (string; 18) TIMESERIES.
timser_id: (string; 16) Name of time series.
fname: (string; 254) Name of external file with rainfall data. Rainfall files are discussed in Section 11.3 of SWMM's Manual.
sta: (string; 12) Name of recording station used in the rain file.
units: (string; 3) Rain depth units used in the rain file, either IN (inches) or MM (millimeters).
subcatchment
subc_id: (string; 16) Name assigned to subcatchment.
node_id: (string; 16) Name of a node that receives runoff from subcatchment.
rg_id: (string; 16) Name of rain gage in RAINGAGES section assigned to subcatchment.
area: (double; 16, 6) Area of subcatchment (acres or hectares).
imperv: (double; 12, 4) Percent imperviousness of subcatchment.
width: (double; 12, 4) Characteristic width of subcatchment (ft or m).
slope: (double; 12, 4) Subcatchment slope (percent).
clenght: (double; 12, 4) Total curb length (any length units).
snow_id: (string; 16) Name of snow pack object (from SNOWPACKS section) that characterizes snow accumulation and melting over the subcatchment.
nimp: (double; 12, 4) Manning's N for overland flow over the impervious sub-area.
nperv: (double; 12, 4) Manning's N for overland flow over the pervious sub-area.
simp: (double; 12, 4) Depression storage for impervious sub-area (inches or mm).
sperv: (double; 12, 4) Depression storage for pervious sub-area (inches or mm).
zero: (double; 12, 4) Percent of impervious area with no depression storage.
routeto: (string; 20) Use IMPERV if pervious area runoff runs onto impervious area, PERV if impervious runoff runs onto impervious area or OUTLET if both areas drain to the
subcatchment's outlet (default is OUTLET).
rted: (double; 12, 4) Percent of runoff routed from one type of area to another (default is 100).
maxrate: (double; 12, 4) Maximum infiltration rate on Horton curve (in/hr or mm/hr).
minrate: (double; 12, 4) Minimum infiltration rate on Horton curve (in/hr or mm/hr).
decay: (double; 12, 4) Decay rate constant of Horton curve (l/hr).
drytime: (double; 12, 4) Time it takes for fully saturated soil to dry (days).
maxinfil: (double; 12, 4) Maximum infiltration volume possible (in or mm; 0 is not applicable).
suction: (double; 12, 4) Soil capillary suction (in or mm).
conduct: (double; 12, 4) Soil saturated hydraulic conductivity (in/hr or mm/hr).
initdef: (double; 12, 4) Initial soil moisture deficit (volume of voids / total volume).
curveno: (double; 12, 4) SCS Curve Number.
conduct_2: (double; 12, 4) Soil saturated hydraulic conductivity (in/hr or mm/hr; this property has been deprecated and is no longer used).
drytime2: (double; 12, 4) Time it takes for fully saturated soil to dry (days).
Dbf from shape

If you click on the shape file below, you will see what kind of dbf you need to work.
arc
The dbf files are shown below.
conduit_cu
The dbf contains the following fields:
length: (double; 12, 4) Conduit length (ft or m).
curve_id: (string; 16) Name of a Shape Curve in the [CURVES] section that defines how width varies with depth.
geom4: (double; 12, 4) Auxiliary parameters (e. g., side slopes) (see Table D-1 for details of SWMM'S Manual).
qmax: (double; 12, 4) Maximum flow.
barrels: (integer; 2) Number of barrels (i. e., number of parallel pipes of equal size, slope, and roughness) associated with a conduit (default is 1).
culvert: (string; 10) Code number from Table A.10 for the conduit's inlet geometry if it is a culvert subject to possible inlet flow control (leave blank otherwise).
conduit_no
length: (double; 12, 4) Conduit lenght (ft or m).
geom1: (double; 12, 4) Maximum depth (ft or m).
barrels: (integer; 2) Number of barrels (i. e., number of parallel pipes of equal size, slope, and roughness) associated with a conduit (default is 1).
culvert: (string; 10) Code number for the conduit's inlet geometry if it is a culvert subject to possible inlet flow control (leave blank otherwise).
conduit_xs
length: (double; 12, 4) Conduit length (ft or m).
tsect_id: (string; 16) Name of an entry in the transects section that describes the cross-section geometry of an irregular channel.
geom3: (double; 12, 4) Auxiliary parameters (e. g., side slopes; see table D-1 for details of SWMM's Manual).
geom4: (double; 12, 4) Auxiliary parameters (e. g., side slopes; see table D-1 for details of SWMM's Manual).
n: (double; 12, 4) Value of N (i. e., roughness parameter) in Manning's equation).
barrels: (integer; 2) Number of barrels (i. e., number of parallel pipes of equal size, slope and roughness) associated with a conduit (default is 1).
culvert: (string; 10) Code number for the conduit's inlet geometry if it is a culvert subject to possible inlet flow control (leave blank otherwise).
orifice
arc_id: (string; 16) Name assigned to conduit orifice.
node_1: (string; 16) Name of a node on inlet end of orifice.
node_2: (string; 16) Name of a node on outlet end of orifice.
ori_type: (string; 18) Orientation of orifice: either SIDE or BOTTOM.
offset: (double; 12, 4) Amount that a Side Orifice's bottom or the position of a Bottom Orifice is offset above the invert of inlet node (ft or m, expressed as either a depth or as an
elevation, depending on the LINK_OFFSETS option setting).
cd: (double; 12, 4) Discharge coefficient (unitless).
orate: (double; 12, 4) Time in decimal hours to open a fully closed orifice (or close a fully open one). Use 0 if the orifice can open/close instantaneously.
flap: (string; 3) YES if flap gate present to prevent reverse flow, NO if not (default is NO).
shape: (string; 18) The only allowable shape are CIRCULAR and RECT_CLOSED (closed rectangular).
geom3: (double; 12, 4) Write 0.
geom4: (double; 12, 4) Write 0.
outlet_fcd
arc_id: (string; 16) Name of the conduit.
node_1: (string; 16) Name of node on inlet end of link.
node_2: (string; 16) Name of node on outflow end of link.
type_oufcd: (string; 16) FUNCTIONAL/HEAD or FUNCTIONAL/DEPTH.
offset: (double; 12, 4) Amount that the outlet is offset above the invert of inlet node (ft or m, expressed as either a depth or as an elevation, depending on the LINK_OFFSETS
option setting).
cd1: (double; 12, 4) Coefficient and exponent, respectively, of a power function that relates outflow to:
- Water depth (ft or m) above the offset elevation at the inlet node for a FUNCTIONAL/DEPTH outlet.
- Head difference (ft or m) between the inlet and outflow nodes for a FUNCTIONAL/HEAD outlet.
outlet_fch
type_oufch: (string; 16) FUNCTIONAL/HEAD or FUNCTIONAL/DEPTH.
option setting).
outlet_tbd
type_outbd: (string; 16) TABULAR/HEAD or TABULAR/DEPTH.
option setting).
curve_id: (string; 16) Name of rating curve with outflow rate (flow units) as a function of head (ft or m) across the outlet for a TABULAR outlet.
outlet_tbh
type_outbh: (string; 16) TABULAR/HEAD or TABULAR/DEPTH.
option setting).
curve_id: (string; 16) Name of rating curve with outflow rate (flow units) as a function of head (ft or m) across the outlet for a TABULAR outlet.
pump
node_1: (string; 16) Name of node on inlet end of orifice.
node_2: (string; 16) Name of node on outlet end of orifice.
curve_id: (string; 16) Name of pump curve listed in the CURVES section of the input.
status: (string; 3) Status at start of simulation (either ON or OFF; default is ON).
startup: (double; 12, 4) Depth at inlet node when pump turns on (ft or m; default is 0).
shutoff: (double; 12, 4) Depth at inlet node when pump shuts off (ft or m; default is 0).
vertice
vertice_id: (string; 16) Name of vertice.
arc_id: (string; 16) Name of conduit.
weir
arc_id: (string; 16) Name of conduit.
node_1: (string; 16) Name of node on inlet side of weir.
node_2: (string; 16) Name of node on outlet side of weir.
weir_type: (string; 18) TRANSVERSE, SIDEFLOW, V-NOTCH or TRAPEZOIDAL (see the SWMM's Manual).
offset: (double; 12, 4) Amount that wier's crest is offset above the invert of inlet node (ft or m, expressed as either a depth or as an elevation, depending on the LINK_OFFSETS
option setting).
cd: (double; 12, 4) Weir discharge coefficient (for CFS if using US flow units or CMS if usin metric flow units).
ec: (double; 12, 4) Number of end contractions for TRANVSERVE or TRAPEZOIDAL weir (default is 0).
cd2: (double; 12, 4) Discharge coefficient for triangular ends of a TRAPEZOIDAL weir (for CFS if using US flow units or CMS if using metric flow units; default is value of Cd).
shape: (string; 18) Cross-section shape (see Table 3-1 in SWMM's Manual for available shapes).
geom2: (double; 12, 4) Auxiliary parameters (see Table D-1 in SWMM's Manual for details).
node
divider_cu
node_id: (string; 16) Name assigned to divider node.
elev: (double; 12, 4) Invert elevation (ft or m).
arc_id: (string; 16). Name assigned to conduit link.
type_dicu: (string; 18) Type of divider.
qmin: (double; 16, 6) Flow at which diversion begins for either a CUTOFF or WEIR divider (flow units).
ysur: (double; 12, 4) Maximum additional head above ground elevation that node can sustain under surcharge conditions (ft or m; default is 0).
apond: (double; 16, 6) Area subjected to surface ponding once water depth exceeds ymax (ft2 or m2; default is 0).
xcoord: (double; 16,6) Horizontal coordinate of vertex relative to origin in lower left of map.
divider_ov
type_diov: (string; 18) Type of divider.
divider_tb
type_ditb: (string; 18) Type of divider.
curve_id: (string; 16). Name of curve for divider.
divider_wr
type_diwr: (string; 18) Type of divider.
qmin: (double; 16, 6) Flow at which diversion begins for either a CUTOFF or WEIR divider (flow units).
ht: (double; 12, 4) Height of WEIR divider (ft or m).
cd: (double; 12, 4) Discharge coefficient for WEIR divider.
ymax: (double; 12, 4) Depth from ground to invert elevation (ft or m).
junction
node_id: (string; 16) Name assigned to junction node.
elev: (double; 12, 4) Elevation of junction invert (ft or m).
y0: (double; 12, 4) Water depth at star of simulation (ft or m; default is 0).
ysur: (double; 12, 4) Maximum additional head above ground elevation that manhole junction can sustain under surcharge conditions (ft or m; default is 0).
apond: (double; 16, 6) Area subjected to surface ponding once water depth exceeds ymax (ft2 or m2).
outfall_fi
node_id: (string; 16) Name assigned to outfall node.
type_otlfi: (string; 16) FIXED.
gate: (string; 3) YES or NO depending on whether a flap gate is present that prevents reverse flow.
outfall_fr
type_otlfr: (string; 16) FREE.
outfall_nm
type_otlnm: (string; 16) NORMAL.
outfall_ti
type_otlfi: (string; 16) TIDAL.
curve_id: (string; 16) Name of curve in CURVES section containing tidal height (i. e., outfall stage) v. hour of a day over a complete tidal cycle.
outfall_ts
type_otlts: (string; 16) TIMESERIES.
timser_id: (string; 16) Name of time series in TIMESERIES section that describes how outfall stage varies with time.
raingage
rgage_fl
id: (integer; 8) Defines the order of the line text. You must to use this code in order to sort as you need the lines of text. As you sort the text lines Giswater reads by this order the
information.
rgage_id: (string; 16) Name assigned to rain gage.
rgage_type: (string; 12) Raingage type (TIMESERIES or FILE).
fname: (string; 50) Name of external file with raifall data.
sta: (string; 16) Name of recording station used in the rain file.
format: (string; 16) Form of recorded rainfall, either INTENSITY, VOLUME or CUMULATIVE.
intvl: (string; 12) Time interval between gage readings in decimal hours or hours:minutes format (e. g., 0:15 for 15 minutes readings).
scf: (double; 12, 4) Snow catch deficiency correction factor (use 1.0 for no adjustment).
units_type: (string; 10) Rain depth units used in the rain file, either IN (inches) or MM (millimeters).
init_date: (string; 12) Date to begin reading from the file in Month-Day-Year format.
fin_date: (string; 12) Date to end reading from the file in Month-Day-Year format.
rgage_ts
information.
rgage_id: (string; 16) Name assigned to rain gage.
rgage_type: (string; 12) Raingage type (FILE or TIMESERIES).
timser_id: (string; 16) Name of time series in TIMESERIES section with rainfall data.
format: (string; 10) Form of recorded rainfall, either INTENSITY, VOLUME or CUMULATIVE.
intvl: (string; 12) Time interval between gage readings in decimal hours or hours:minutes format (e. g., 0:15 for 15 minute readings).
Dbf with general information

inp_options
parameter: (string; 20) Options parameters of SWMM project.
value: (string; 20) Options value parameters of SWMM project.
inp_project_id
title: (string; 254) Project title.
author: (string; 50) The author of the project.
date: (string; 12) Date.
inp_report
parameter: (string; 20) Options parameters of SWMM project.
value: (string; 20) Options value parameters of SWMM project.
Other dbf
aquifer
aquif: (string; 4) Aquifer name.
por: (double; 12, 4) Soil porosity (fraction).
wp: (double; 12, 4) Soil wilting point (fraction).
fc: (double; 12, 4) Soil field capacity (fraction).
k: (double; 12, 4) Saturated hydraulic conductivity (in/hr or mm/hr).
ks: (double; 12, 4) Slope of hydraulic conductivity versus moisture content curve.
ps: (double; 12, 4) Slope of soil tension versus moisture content curve.
uef: (double; 12, 4) Fraction of total evaporation available for evapotranspiration in the upper unsaturated zone.
led: (double; 12, 4) Maximum depth into the lower saturated zone over which evapotranspiration can occur (ft or m).
gwr: (double; 12, 4) Rate of percolation from saturated zone to deep groundwater when water table is at ground surface (in/hr or mm/hr).
be: (double; 12, 4) Elevation of the bottom of the aquifer (ft or m).
wte: (double; 12, 4) Water table elevation at start of simulation (ft or m).
umc: (double; 12, 4) Unsaturated zone moisture content at start of simulation (fraction).
backdrop
information.
text: (string; 254) Backdrop text (see SWMM user's manual for more details).
buildup
landus_id: (string; 16) Land use name.
poll_id: (string; 16) Pollutant name.
funcb_type: (string; 18) Buildup function type (POWER/ EXPONENTIAL/ SATURATION).
c1: (double; 12, 4) Buildup function parameters (see Table D-2 of SWMM's Manual).
perunit: (string; 10) AREA if buildup is per unit area, CURBLENGTH if per length of curb.
controls
information.
text: (string; 254) Map units text (see SWMM user's manual for more details).
coverages
subc_id: (string; 16) Subcatchment name.
percent: (double; 12, 4) Percent of subcatchment area.
curve
information.
curve_id: (string; 16) Name assigned to table.
curve_type: (string; 16) STORAGE/ DIVERSION/ TIDAL/ PUMP1/ PUMP2/ PUMP3/ PUMP4/ RATING.
x_value: (double; 18, 6) An x (independent variable) value.
y_value: (double; 18, 6) The y (dependent variable) value corresponding to x.
dwf
dwf_flow
node_id: (string; 16) Name of node where dry weather flow enters.
type_dwf: (string; 16) Type of dwf.
value: (double; 12, 4) Average baseline value for corresponding item (flow or concentration units).
pat1: (string; 16) Name of up to four time patterns appearing in the PATTERNS section.
dwf_load
poll_id: (string; 16) Name assigned to pollutant.
node_id: (string; 16) Name of node where dry weather flow enters.
value: (double; 12, 4) Average baseline value for corresponding item.
evap
evap_co
type_evco: (string; 16) Evaporation type (see the SWMM's Manual).
evap: (double; 12, 4) Constant evaporation rate (in/day or mm/day).
evap_do
type_evdo: (string; 16) Evaporation type (see the SWMM's Manual).
dry_only: (string; 3) Determines if evaporation only occurs during periods with no precipitation. The default is NO.
evap_fl
type_evfl: (string; 16) Evaporation type (see the SWMM's Manual).
pan_1: (double; 12, 4) Pan coefficient for January.
pan_2: (double; 12, 4) Pan coefficient for February.
pan_3: (double; 12, 4) Pan coefficient for March.
pan_4: (double; 12, 4) Pan coefficient for April.
pan_5: (double; 12, 4) Pan coefficient for May.
pan_6: (double; 12, 4) Pan coefficient for June.
pan_7: (double; 12, 4) Pan coefficient for July.
pan_8: (double; 12, 4) Pan coefficient for August.
pan_9: (double; 12, 4) Pan coefficient for September.
pan_10: (double; 12, 4) Pan coefficient for October.
pan_11: (double; 12, 4) Pan coefficient for November.
pan_12: (double; 12, 4) Pan coefficient for December.
evap_mo
type_evmo: (string; 16) Evaporation type (see the SWMM's Manual).
value_1: (double; 12, 4) Evaporation value parameters of SWMM project.
evap_pa
type_evpa: (string; 16) Evaporation type (see the SWMM's Manual).
recovery: (string; 16) Identifies an optional monthly time pattern of multipliers used to modify infiltration recovery rates during dry periods. For example, if the normal infiltration
recovery rate was 1% during a specific time period and a pattern factor of 0,8 applied to this period, then the actual recovery rate would be 0,8%.
evap_te
type_evte: (string; 16) Evaporation type (see the SWMM's Manual).
evap_ts
type_evts: (string; 16) Evaporation type (see the SWMM's Manual).
timeser_id: (string; 16) Name of TIMESERIES section with temperature data.
files
information.
actio_type: (string; 18) USE/ SAVE.
file_type: (string; 18) RAINFALL, RUNOFF, HOTSTART, RDII or ROUTING.
fname: (string; 254) Name of file.
groundwater
subc_id: (string; 16) Subcatchment name.
aquif_id: (string; 16) Name of groundwater aquifer underneath the subcatchment.
node_id: (string; 16) Name of node in conveyance system exchanging groundwater with aquifer.
surfel: (double; 10, 4) Surface elevation of subcatchment (ft or m).
a1: (double; 10, 4) Groundwater flow coefficient (see the SWMM's Manual).
b1: (double; 10, 4) Groundwater flow exponent (see the SWMM's Manual).
a2: (double; 10, 4) Surface water flow coefficient (see the SWMM's Manual).
b2: (double; 10, 4) Surface water flow exponent (see the SWMM's Manual).
a3: (double; 10, 4) Surface water-groundwater interaction coefficient (see the SWMM's Manual).
tw: (double; 10, 4) Fixed depth of surface water at receiving node (ft or m; set to zero if surface water depth will vary as computed by flow routing).
h: (double; 10, 4) Groundwater table height which must be reached before any flows occurs (ft or m). Leave blank to use the height of the receiving node's invert above the aquifer
bottom.
hydrographs
information.
text: (string; 254) Hydrographs text (see SWMM user's manual for more details).
inflows
inflows_flow
node_id: (string; 16) Name of node where external inflow enters.
type_inf_1: (string; 18) Infiltration type (see the SWMM's Manual).
timser_id: (string; 16) Name of time series describing how external inflows vary with time.
type_inf_2: (string; 18) Infiltration type (see the SWMM's Manual).
n1: (double; 12, 4) Write 1 (see the SWMM's Manual).
sfactor: (double; 12, 4) Scaling factor that multiplies the recorded time series values (default is 1).
base: (double; 12, 4) Constant baseline value added to the time series value (default is 0).
pattern_id: (string; 16) Name of optional time pattern in PATTERNS section used to adjust the baseline value on a periodic basis.
inflows_load
node_id: (string; 16) Name of node where external inflow enters.
timser_id: (string; 16) Name of time series describing how external inflows vary with time.
form_type: (string; 18) CONCEN if pollutant inflow is described as a concentration, MASS if it is described as a mass flow rate (default is CONCEN).
mfactor: (double; 12, 4) The factor that converts the inflow's mass flow rate units into the project's mass units per second, where the project's mass units are those specified for the
pollutant in the POLLUTANTS section (default is 1).
sfactor: (double; 12, 4) Scaling factor that multiplies the recorded time series values (default is 1).
base: (double; 12, 4) Constant baseline value added to the time series value (default is 0).
pattern_id: (string; 16) Name of optional time pattern in PATTERNS section used to adjust the baseline value on a periodic basis.
labels
xcoord: (double; 18, 6) Horizontal coordinate relative to origin in lower left of map.
ycoord: (double; 18, 6) Vertical coordinate relative to origin in lower left of map.
anchor: (string; 16) Name of node or subcatchment that anchors the label on zoom-ins (use an empty pair of double quotes if there is no anchor).
font: (string; 50) Name of label's font (surround by double quotes if the font name includes spaces).
size: (double; 12, 4) Font size in points.
bold: (string; 3) YES for bold font, NO otherwise.
italic: (string; 3) YES for italic font, NO otherwise.
landuses
sweepint: (double; 12, 4) Days between street sweeping.
availab: (double; 12, 4) Fraction of pollutant buildup available for renoval by street sweeping.
lastsweep: (double; 12, 4) Days since last sweeping at start of the simulation.
lid_control
information.
lidco_id: (string; 16) Name assigned to table.
lidco_type: (string; 10) BC for bio-retention cell; PP for porous pavement; IT for infiltration trench; RB for rain barrel; VS for vegetative swale.
value_2: (double; 12, 4) LID value parameters of SWMM project.
lidusage
subc_id: (string; 16) The name of the subcatchment using the LID process.
lidco_id: (string; 16) The name of an LID process defined in the LID_CONTROLS section.
number: (double; 12, 4) The number of replicate LID units deployed.
area: (double; 16, 6) The area of each replicate unit (ft2 or m2).
width: (double; 12, 4) The width of the outflow face of each identical LID unit (in ft or m). This parameter only applies to LID processes such as porous pavement and vegetative
swales that use overland flow to convey surface runoff of the unit (the other LID processes, such as bio-retention cells and infiltration trenches simply spill any excess captured
runoff over their berms).
initsat: (double; 12, 4) The percent to which the unit's soil layer or storage layer is initially filled with water.
fromimp: (double; 12, 4) The percent of the impervious portion of the subcatchment's non-LID area whose runoff is treated by the LID units. If the LID unit treats only direct
rainfall, such as with a green roof, then this value should be 0. If the LID takes up the entire subcatchment then this field is ignored.
toperv: (double; 12, 4) 1 if the outflow from the LID is returned onto the subcatchment's pervious area rather than going to the subcatchment's outlet; 0 otherwise. An example of
where this might apply is a rain barrel whose contents are used to irrigate a lawn area. This field is ignored if the LID takes up the entire subcatchment.
rptfile: (string; 10) Optional name of a file to which detailed time series results for the LID will be written. Enclose the name in double quotes if it contains spaces and include the full
path if it is different than the SWMM input file path.
loadings
poll_id: (string; 16) Name of a pollutant.
subc_id: (string; 16) Name of a subcatchment.
ib: (double; 12, 4) Initial buildup of pollutant (lbs/acre or kg/hectare).
losses
arc_id: (string; 16) Name of a conduit.
kentry: (double; 12, 4) Entrance minor head loss coefficient.
kexit: (double; 12, 4) Exit minor head loss coefficient.
kavg: (double; 12, 4) Average minor head loss coefficient across length of conduit.
flap: (string; 3) YES if conduit has a flap gate that prevents back flow, NO otherwise (default is NO).
map_dim
type_dim: (string; 18)
x1: (double; 18, 6) Lower-left X coordinate of full map extent.
y1: (double; 18, 6) Lower-left Y coordinate of full map extent.
x2: (double; 18, 6) Upper-left X coordinate of full map extent.
y2: (double; 18, 6) Upper-left Y coordinate of full map extent.
mapunits
type_unit: (string; 18) Map units text (see SW MM user's manual for more details).
map_type: (string; 18) Map units text (see SWMM user's manual for mor details).
pattern
pattern_dl
pattern_id: (string; 16) Name used to identify the pattern.
type_padl: (string; 16) DAILY.
factor_1: (double; 12, 4) Multiplier values.
pattern_ho
type_paho: (string; 16) HOURLY.
pattern_mo
type_pamo: (string; 16) MONTHLY.
Стр. 10 из 16 03.03.2018, 12:27

pattern_we
type_pawe: (string; 16) WEEKEND.
pollutant
units_type: (string; 18) Concentration units (MG/L for milligrams per liter, UG/L for micrograms per liter or #/L for direct count per liter).
crain: (double; 12, 4) Concentration of pollutant in rainfall (concentration units).
cgw: (double; 12, 4) Concentration of pollutant in groundwater (concentration units).
cii: (double; 12, 4) Concentration of pollutant in inflow/infiltration (concentration units).
kd: (double; 12, 4) First-order decay coefficient (1/days).
sflag: (string; 3) YES if pollutant buildcup occurs only when there is snow cover, NO otherwise (default is NO).
copoll_id: (string; 16) Name of co-pollutant (default is no co-pollutant).
cofract: (double; 12, 4) Fraction of co-pollutant concentration (default is 0).
cdwf: (double; 12, 4) Concentration of pollutant in dry weather flow (concentration units).
rdii
node_id: (string; 16) Name of a node.
hydro_id: (string; 16) Name of an RDII unit hydrograph group specified in the HYDROGRAPHS section.
sewerarea: (double; 16, 6) Area of the sewershed which contributes RDII to the node (acres or hectares).
snowpack
snow_id: (string; 16) Name assigned to snowpack parameter set.
type_snpk1: (string; 16) Type of snowpack (PLOWABLE, IMPERVIOUS, PERVIOUS, REMOVAL).
cmin_1: (double; 12, 4) Minimum melt coefficient (in/hr-deg F or mm/hr-deg C).
cmax_1: (double; 12, 4) Maximum melt coefficient (in/hr-deg F or mm/hr-deg C).
tbase_1: (double; 12, 4) Snow melt base temperature (deg F or deg C).
fwf_1: (double; 12, 4) Ratio of free water holding capacity to snow depth (fraction).
sd0_1: (double; 12, 4) Initial snow depth (in or mm water equivalent).
fw0_1: (double; 12, 4) Initial free water in pack (in or mm).
smn0_1: (double; 12, 4) Fraction of impervious area that can be plowed.
sd100_1: (double; 12, 4) Snow depth above which there is 100% cover (in or mm water equivalent).
sd100_2: (double; 12, 4) Snow depth above which there is 100% cover (in or mm water equivalent).
dplow: (double; 12, 4) Depth of snow on plowable areas at which snow removal begins (in or mm).
fout: (double; 12, 4) Fraction of snow on plowable area transferred out of watershed.
fimp: (double; 12, 4) Fraction of snow on plowable area transferred to impervious area by plowing.
fperv: (double; 12, 4) Fraction of snow on plowable area transferred to pervious area by plowing.
fimelt: (double; 12, 4) Fraction of snow on plowable area converted into immediate melt.
fsub: (double; 12, 4) Fraction of snow on plowable area transferred to pervious area in another subcatchment.
subc_id: (string; 16) Name of subcatchment receiving the subcatch fraction of transferred snow.
storage
storage_fc
node_id: (string; 16) Name assigned to storage node.
ymax: (double; 12, 4) Maximum water depth possible (ft or m).
y0: (double; 12, 4) Water depth at start of simulation (ft or m).
type_stfc: (string; 18) Type of storage.
a1: (double; 12, 4) Coefficient of FUNCTIONAL relation between surface area and depth.
a2: (double; 12, 4) Exponent of FUNCTIONAL relation between surface area and depth.
a0: (double; 12, 4) Constant of FUNCTIONAL relation between surface area and depth.
apond: (double; 16, 6) Surface area subjected to ponding once water depth exceeds ymax (ft2 or m2; default is 0).
fevap: (double; 12, 4) Fraction of potential evaporation from surface realized (default is 0).
sh: (double; 12, 4) Soil capillary suction head (in or mm).
hc: (double; 12, 4) Soil saturated hydraulic conductivity (in/hr or mm/hr).
imd: (double; 12, 4) Initial soil moisture deficit (volume of voids/total volume).
storage_tb
node_id: (string; 16) Name assigned to storage node.
ymax: (double; 12, 4) Maximum water depth possible (ft or m).
y0: (double; 12, 4) Water depth at start of simulation (ft or m).
type_sttb: (string; 18) Type of storage.
curve_id: (string; 16) Name of curve in CURVES section with surface area (ft2 or mm2) as a function of depth (ft or mm) for TABULAR geometry.
apond: (double; 16, 6) Surface area subjected to ponding once water depth exceeds ymax (ft2 or m2; default is 0).
fevap: (double; 12, 4) Fraction of potential evaporation from surface realized (default is 0).
sh: (double; 12, 4) Soil capillary suction head (in or mm).
hc: (double; 12, 4) Soil saturated hydraulic conductivity (in/hr or mm/hr).
imd: (double; 12, 4) Initial soil moisture deficit (volume of voids/ total volume).
temp
temp_fl
type_tefl: (string; 16) Temperature type (see the SWMM's Manual).
fname: (string; 254) Name of external Climate file with temperature data.
start: (string; 12) Date to begin reading from the file in Month-Day-Year format (default is the beginning of the file).
temp_sn
type_tesn: (string; 16) Temperature type (see the SWMM's Manual).
stemp: (double; 12, 4) Air temperature at which precipitation falls as snow (deg F or C).
atiwt: (double; 12, 4) Antecedent temperature index weight (default is 0.5).
rnm: (double; 12, 4) Negative melt ratio (default is 0.6).
elev: (double; 12, 4) Average elevation of study area above mean sea level (ft or mm; default is 0).
lat: (double; 12, 4) Latitude of the study area in degrees North (default is 50).
dtlong: (double; 12, 4) Correction, in minutes of time, between true solar time and the standard clock time (default is 0).
type_teai: (string; 16) Temperature type (see the SWMM's Manual).
i_f0: (double; 12, 4) Fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.0.
type_teap: (string; 16) Temperature type (see the SWMM's Manual).
p_f0: (double; 12, 4) Fraction of area covered by snow when ratio of snow depth to depth at 100% cover is 0.0.
temp_ts
type_tets: (string; 16) Temperature type (see the SWMM's Manual).
timser_id: (string; 16) Name of time series in TIMESERIES section with temperature data.
temp_wf
type_tews: (string; 16) Temperature type (see the SWMM's Manual).
type_tefl: (string; 16) Temperature type (see the SWMM's Manual).
fname: (string; 254) Name of external Climate file with temperature data.
temp_wm
type_tews: (string; 16) Temperature type (see the SWMM's Manual).
type_temo: (string; 16) Temperature type (see the SW MM's Manual).
value_1: (double; 12, 4) Temperature value parameters of SWMM project.
timser
timser_abs
information.
timser_id: (string; 16) Name assigned to time series.
date: (string; 12) Date in Month/Day/Year format (e. g., June 15, 2001 would be 6/15/2001).
hour: (string; 10) 24-hour military time (e. g., 8:40 pm would be 20:40) relative to the last date specified (or to midnight of the starting date of the simulation if no previous date was
specified).
value: (double; 12, 4) Value corresponding to given date and time.
timser_fl
type_times: (string; 16) Time series type (see the SWMM's Manual).
fname: (string; 254) Name of a file in which the time series data are stored.
timser_rel
information.
time: (string; 10) Hours since the start of the simulation, expressed as a decimal number or as hours:minutes.
value: (double; 12, 4) Value corresponding to given date and time.
transects
information.
text: (string; 254) Transects text (see SWMM user's manual for more details).
treatment
node_id: (string; 16) Name of a node where treatments occurs.
poll_id: (string; 16) Name of pollutant receiving.
function: (string; 100) Mathematical function expressing treatments result in terms of pollutant concentrations, pollutant removals, and other standard variables (see TREATMENT
section in SWMM's Manual).
washoff
poll_id: (string; 16) Pollutant name.
funcw_type: (string; 18) Washoff function type: EXP/ RC/ EMC.
c1: (double; 12, 4) Washoff function coefficients (see Table D-3).
c2: (double; 12, 4) Washoff function coefficients (see Table D-3).
sweepeffic: (double; 12, 4) Street sweeping removal efficiency (percent).
bmpeffic: (double; 12, 4) BMP removal efficiency (percent).
Rpt
rpt_arcflow_sum
information.
result_id: (string; 16) ID simulation result.
arc_id: (string; 16) ID label of arc.
max_flow: (double; 12, 4) Maximum total inflow (CMS).
time_days: (string; 10) Time of max occurrence (days).
time_hour: (string; 10) Time of max occurrence (hr:min).
max_veloc: (double; 12, 4) Maximum velocity (m/sec).
mfull_flow: (double; 12, 4) Ratio of maximum flow to full normal flow.
mfull_dept: (double; 12, 4) Ratio of maximum flow depth to full depth.
rpt_condsurcharge_sum
information.
both_ends: (double; 12, 4) Hours that conduit is full at both ends.
upstream: (double; 12, 4) Hours that conduit is full at upstream end.
dnstream: (double; 12, 4) Hours that conduit is full at downstream end.
hour_nflow: (double; 12, 4) Hours that conduit flows above full normal flow.
hour_limit: (double; 12, 4) Hours that conduits is capacity limited.
rpt_continuity_errors
information.
text: (string; 254) Text.
rpt_critical_elements
information.
rpt_flowclass_sum
information.
length: (double; 12, 4) Ratio of adjusted conduit length to actual length.
dry: (double; 12, 4) Fraction of time spent in dry on both ends.
up_dry: (double; 12, 4) Fraction of time spent in dry on the upstream end.
down_dry: (double; 12, 4) Fraction of time spent in dry on the downstream end.
sub_crit: (double; 12, 4) Fraction of time spent in subcritical flow.
sub_crit1: (double; 12, 4) Fraction of time spent in supercritical flow.
up_crit: (double; 12, 4) Fraction of time spent in critical flow at the upstream end.
down_crit: (double; 12, 4) Fraction of time spent in critical flow at the downstream end.
froud_numb: (double; 12, 4) Average froude number.
flow_chang: (double; 12, 4) Average change in flow between each time step (flow units).
rpt_flowrouting_cont
information.
dryw_inf: (double; 12, 4) Dry Weather Inflow.
wetw_inf: (double; 12, 4) Wet Weather Inflow.
ground_inf: (double; 12, 4) Groundwater Inflow.
rdii_inf: (double; 12, 4) RDII Inflow.
ext_inf: (double; 12, 4) External Inflow.
ext_out: (double; 12, 4) External outflow.
int_out: (double; 12, 4) Internal Outflow.
stor_loss: (double; 12, 4) Storage Losses.
initst_vol: (double; 12, 4) Initial Stored Volume.
finst_vol: (double; 12, 4) Final Stored Volume.
cont_error: (double; 12, 4) Continuity Error (%).
rpt_groundwater_cont
information.
init_stor: (double; 12, 4) Initial Storage.
infilt: (double; 12, 4) Infiltration.
upzone_et: (double; 12, 4) Upper Zone ET.
lowzone_et: (double; 12, 4) Lower Zone ET.
deep_ perc: (double; 12, 4) Deep Percolation.
final_stor: (double; 12, 4) Final Storage.
groundw_fl: (double; 12, 4) Groundwater Flow.
rpt_high_conterrors
information.
rpt_high_flowinest_ind
information.
rpt_instability_index
information.
rpt_lidperformance_sum
information.
lidco_id: (string; 16) ID LID control.
tot_inflow: (double; 12, 4) Total inflow (mm).
evap_loss: (double; 12, 4) Evaporation loss (mm).
infil_loss: (double; 12, 4) Infiltration loss (mm).
surf_outf: (double; 12, 4) Surface outflow (mm).
drain_outf: (double; 12, 4) Drain outflow (mm).
init_stor: (double; 12, 4) Initial Storage.
final_stor: (double; 12, 4) Final Storage.
per_error: (double; 12, 4) Percentage error.
rpt_nodedepth_sum
information.
node_id: (string; 16) ID name assigned to node.
swnod_type: (string; 18) Type of node.
aver_depth: (double; 12, 4) Average water depth (meters).
max_depth: (double; 12, 4) Maximum water depth (meters).
max_hgl: (double; 12, 4) Maximum hydraulic head (HGL) elevation (meters).
time_days: (string; 10) Time of maximum depth (days).
time_hour: (string; 10) Time of maximum depth (hr:min).
rpt_nodeflooding_sum
information.
result_id: (string; 16) ID simulation text.
hour_flood: (double; 12, 4) Hours flooded.
max_rate: (double; 12, 4) Maximum flooding rate (flow units).
time_days: (string; 10) Time of maximum flooding (days).
time_hour: (string; 10) Time of maximum flooding (hr:min).
tot_flood: (double; 12, 4) Total flood volume (106 ltr).
max_ponded: (double; 12, 4) Maximum ponded depth (meters).
rpt_nodeinflow_sum
information.
max_latinf: (double; 12, 4) Maximum lateral inflow (flow units).
max_totinf: (double; 12, 4) Maximum total inflow (flow units).
time_days: (string; 10) Time of maximum total inflow (days).
time_hour: (string; 10) Time of maximum total inflow (hr:min).
latinf_vol: (double; 12, 4) Total lateral inflow volume (106 ltr).
totinf_vol: (double; 12, 4) Total inflow volume (106 ltr).
rpt_nodesurcharge_sum
information.
hour_surch: (double; 12, 4) Hours surcharged.
max_height: (double; 12, 4) Maximum height of surcharge above node's crown (meters).
min_depth: (double; 12, 4) Minimum depth of surcharge below node's top rim.
rpt_outfallflow_sum
information.
flow_freq: (double; 12, 4) Percent of time that outfall discharges.
avg_flow: (double; 12, 4) Average discharge flow (flow units).
max_flow: (double; 12, 4) Maximum discharge flow (flow units).
total_vol: (double; 12, 4) Total volume of flow discharged (106ltr).
rpt_outfallload_sum
information.
poll_id: (string; 16) ID name assigned to pollutant.
value: (double; 12, 4) Value.
rpt_pumping_sum
information.
arc_id: (string; 16) ID label or arc.
percent: (double, 12, 4) Percent utilized.
max_flow: (double; 12, 4) Maximum flow (flow units).
avg_flow: (double; 12, 4) Average flow (flow units).
vol_ltr: (double; 12, 4) Total volume (106 ltr).
powus_kwh: (double; 12, 4) Power usage (Kw-hr).
timoff_cur: (double; 12, 4) % Time off curve.
rpt_qualrouting_cont
information.
dryw_inf: (double; 12, 4) Dry Weather Inflow.
wetw_inf: (double; 12, 4) Wet Weather Inflow.
ground_inf: (double; 12, 4) Groundwater Inflow.
rdii_inf: (double; 12, 4) RDII Inflow.
ext_inf: (double; 12, 4) External Inflow.
int_inf: (double; 12, 4) Internal Flooding.
ext_out: (double; 12, 4) External Outflow.
mass_reac: (double; 12, 4) Mass Reacted.
initst_mas: (double; 12, 4) Initial Stored Mass.
finst_mas: (double; 12, 4) Final Stored Mass.
rpt_rainfall_dep
information.
sewer_rain: (double; 12, 4) Sewershed Rainfall.
rdiip_prod: (double; 12, 4) RDII Produced.
rdiir_rat: (double; 12, 4) RDII Ratio.
rpt_result_cat
information.
flow_units: (string; 3) Flow units.
rain_runof: (string; 3) Rainfall/ Runoff.
snowmelt: (string; 3) Snowmelt.
groundw: (string; 3) Groundwater.
flow_rout: (string; 3) Flow Routing.
pond_all: (string; 3) Ponding Allowed.
water_q: (string; 3) Water Quality.
infil_m: (string; 18) Infiltration Method.
flowrout_m: (string; 18) Flow Routing Method.
start_date: (string; 25) Starting Date.
end_date: (string; 25) Ending Date.
dry_days: (double; 12, 4) Antecedent Dry Days.
rep_tstep: (string; 10) Report Time Step.
wet_tstep: (string; 10) Wet Time Step.
dry_tstep: (string; 10) Dry Time Step.
rout_tstep: (string; 10) Routing Time Step.
exec_date: (string; 50) Date when the simulation is executed.
rpt_routing_timestep
information.
rpt_runoff_qual
information.
init_buil: (double; 12, 4) Initial Buildup.
surf_buil: (double; 12, 4) Surface Buildup.
wet_dep: (double; 12, 4) Wet Deposition.
sweep_re: (double; 12, 4) Sweeping Removal.
infil_loss: (double; 12, 4) Infiltration Loss.
bmp_re: (double; 12, 4) BMP Removal.
surf_runof: (double; 12, 4) Surface Runoff.
rem_buil: (double; 12, 4) Remaining Buildup.
rpt_runoff_quant
information.
initsw_co: (double; 12, 4) Initial Snow Cover.
total_prec: (double; 12, 4) Total Precipitation.
evap_loss: (double; 12, 4) Evaporation Loss.
infil_loss: (double; 12, 4) Infiltration Loss.
surf_runof: (double; 12, 4) Surface Runoff.
snow_re: (double; 12, 4) Snow Removed.
finalsw_co: (double; 12, 4) Final Snow Cover.
finals_sto: (double; 12, 4) Final Surface Storage.
rpt_storagevol_sum
information.
aver_vol: (double; 12, 4) Average volume 1000 m3.
avg_full: (double; 12, 4) Average percentage full.
ei_loss: (double; 12, 4) E & I Percentage loss.
max_vol: (double; 12, 4) Maximum volume 1000 m3.
max_full: (double; 12, 4) Maximum percentage full.
time_days: (string; 10) Time of max occurrence (days).
time_hour: (string; 10) Time of max occurrence (hr:min).
max_out: (double; 12, 4) Maximum outflow (flow units).
rpt_subcatchwashoff_sum
information.
value: (double; 12, 4) Value.
rpt_subcathrunoff_sum
information.
tot_precip: (double; 12, 4) Total precipitation (mm).
tot_runon: (double; 12, 4) Total runon (mm).
tot_evap: (double; 12, 4) Total evaporation (mm).
tot_infil: (double; 12, 4) Total infiltration (mm).
tot_runoff: (double; 12, 4) Total runoff (mm).
tot_runofl: (double; 12, 4) Total runoff (106 ltr).
peak_runof: (double; 12, 4) Peak runoff (flow units).
runoff_coe: (double; 12, 4) Runoff coefficient.
rpt_timestep_critelem
information.
EPANET 2012
Shp
The shp files you need create are:
arc
arc_id: (string; 16) ID label of pipe.
node_1: (string; 16) ID of start node.
node_2: (string; 16) ID of end node.
length: (double; 18, 6) Length, ft (m).
diameter: (double; 18, 6) Diameter, inches (mm).
roughness: (double; 18, 6) Roughness coefficient.
minorloss: (double; 18, 6) Minor loss coefficient.
status: (string; 12) Status (OPEN, CLOSED or CV).
enet_type: (string; 18) Type of pipe as EPANET.
material: (string; 20) Type of material.
node
node_id: (string; 16) Junction ID label.
elevation: (double; 18, 6) Elevation, ft (m).
demand: (double; 18, 6) Base demand (flow units).
pattern: (string; 20) Demand pattern ID.
node_type: (string; 18) Type of node.
enet_type: (string; 18) Type of node as EPANET.
sector_id: (integer; 16) Name assigned to sector.
Dbf from shape

If you click on the shape file below, you will see what kind of dbf you need to work.
arc
pipe
arc_id: (string; 16) ID label of pipe.
roughness: (double; 18, 6) Roughness coefficient.
status: (string; 12) Status (OPEN, CLOSED or CV).
pump
arc_id: (string; 16) ID label of pump.
power: (string; 24) Write it POWER, leave a space and write the value of power (power value for constant energy pump, hp (kW)).
head: (string; 24) Write it HEAD, leave a space and write the value of head (ID of curve that describes head versus flow for the pump).
speed: (string; 24) Write it SPEED, leave a space and write the value of speed (relative speed setting (normal speed is 1.0; 0 means pump is off)).
pattern: (string; 24) Write it PATTERN, leave a space and write the value of pattern (ID of time pattern that describes how speed setting varies with me).
valve
valve_cu
arc_id: (string; 16) ID label of valve.
valv_type: (string; 18) Valve type (see EPANET manual).
curve_id: (string; 16) ID of head loss curve.
valve_fl
flow: (double; 18, 6) Flow (flow units).
valve_lc
coef_loss: (double; 18, 6) Loss coefficient.
valve_pr
pressure: (double; 18, 6) Pressure, psi (m).
vertice
arc_id: (string; 16) Link ID label.
node
demand
pattern_id: (string; 16) Demand pattern ID.
deman_type: (string; 18) Name of demand category preceded by a semicolon.
junction
node_id: (string; 16) ID label.
pattern_id: (string; 16) Demand pattern ID.
reservoir
head: (double; 18, 6) Head, ft (m).
pattern_id: (string; 16) Head pattern ID.
tank
elevation: (double; 18, 6) Bottom elevation, ft (m).
initlevel: (double; 18, 6) Initial water level, ft (m).
minlevel: (double; 18, 6) Minimum water level, ft (m).
maxlevel: (double; 18, 6) Maximum water level, ft (m).
diameter: (double; 18, 6) Nominal diameter, ft (m).
minvol: (double; 18, 6) Minimum volume, cubir ft (cubic meters).
curve_id: (string; 16) Volume curve ID.
Dbf with general information

inp_options
parameter: (string; 20) Options parameters of EPANET project.
value: (string; 20) Options value parameters of EPANET project.
inp_project_id
title: (string; 254) Project title.
author: (string; 20) The author of the project.
date: (string; 12) Date.
inp_report
Other dbf
backdrop
information.
text: (string; 254) Backdrop text (see EPANET user's manual for more details).
controls
information.
text: (string; 254) Controls text (see EPANET user's manual for more details).
curve
curve_id: (string; 16) Name assigned to table.
x_value: (double; 18, 6) An x (independent variable) value.
y_value: (double; 18, 6) An y (dependent variable) value.
emitter
coef: (double; 18, 6) Flow coefficient, flow units at 1 psi (1 meter) pressure drop.
Стр. 11 из 16 03.03.2018, 12:27

energy
energy_el
pump_id: (string; 16) ID label of pump.
energy_gl
energy_type: (string; 18) Type of energy.
label
information.
label: (string; 50) Text of label in double quotes.
mixing
mix_type: (string; 18) Mixing model (MIXED, 2COMP, FIFO or LIFO).
value: (double; 18, 6) Options value parameters of EPANET project.
pattern
pattern_id: (string; 16) Pattern ID label.
factor_1: (double; 12, 4) Pattern value (one or more multipliers).
quality
node_id: (string; 16) Node ID label.
initqual: (double; 18, 6) Initial quality.
reactions
reactions_el
arc_id: (string; 16) Name assigned to table.
reactions_gl
react_type: (string; 18) Type of reaction (see EPANET manual).
rules
text: (string; 254 Defines rule-based controls that modify links based on a combination of conditions (see EPANET manual).
source
node_id: (string; 16) Node ID label.
sourc_type: (string; 18) Source type (CONCEN, MASS, FLOWPACED or SETPOINT).
quality: (double; 18, 6) Baseline source strength.
pattern_id: (string; 16) Time pattern ID.
status
arc_id: (string; 16) Link ID label.
status: (string; 12) Status or setting.
tags
object: (string; 18) The keyword NODE or LINK.
node_id: (string; 16) The node or link ID label.
tag: (string; 50) The text of the tag label (with no spaces).
times
Rpt
rpt_arc
information.
flow: (double; 12, 4) Flow (flow units).
vel: (double; 12, 4) Velocity (fps).
headloss: (double; 12, 4) Headloss (1000 ft).
setting: (double; 12, 4)
reaction: (double; 12, 4)
ffactor: (double; 12, 4)
other: (string; 100)
time: (string; 100)
rpt_energy_usage
information.
pump_id: (string; 16) ID label of pump.
usage_fact: (double; 12, 4) Usage factor.
avg_effic: (double; 12, 4) Average efficiency.
kwjr_mgal: (double; 12, 4) Kw - hr (Mgal).
avg_kw: (double; 12, 4) Average (Kw).
peak_kw: (double; 12, 4) Peak (Kw).
cost_day: (double; 12, 4) Cost (day).
rpt_hydraulic_status
information.
time: (string; 10) Time.
rpt_node
information.
node_id: (string; 16) ID label of node.
head: (double; 12, 4) Head, ft (m).
press: (double; 12, 4) Pressure, psi (m).
other: (string; 100)
time: (string; 100) Time.
rpt_result_cat
information.
n_junction: (double; 12, 4) Number of junctions.
n_reservoir: (double; 12, 4) Number of reservoirs.
n_tank: (double; 12, 4) Number of tanks.
n_pipe: (double; 12, 4) Number of pipes.
n_pump: (double; 12, 4) Number of pumps.
n_valve: (double; 12, 4) Number of valves.
head_form: (string; 20) Headloss formula.
hydra_time: (string; 10) Hydraulic Timestep.
hydra_acc: (double; 12, 4) Hydraulic Accuracy.
st_ch_freq: (double; 12, 4) Status Check Frequency.
max_tr_ch: (double; 12, 4) Maximum Trials Checked.
dam_li_thr: (double; 12, 4) Damping Limit Threshold.
max_trials: (double; 12, 4) Maximum trials.
q_analysis: (string; 20) Quality Analysis.
spec_grav: (double; 12, 4) Specific Gravity.
r_kin_visc: (double; 12, 4) Relative Kinematic Viscosity.
r_che_diff: (double; 12, 4) Relative Chemical Diffusivity.
dem_multi: (double; 12, 4) Demand Multiplier.
total_dura: (string; 10) Total Duration.
exec_date: (string; 50)
Стр. 12 из 16 03.03.2018, 12:27

APPENDIX C - USEFUL TABLES

EPA SWMM
A.1 Units of Measurement
PARAMETER US CUSTOMARY SI METRIC
Area (Subcatchment) acres hectares
Area (Storage Unit) square feet square meters
Area (Ponding) square feet square meters
Capillary Suction inches millimeters
mg/L (milligrams/liter) mg/L

Concentration ug/L (micrograms/liter) ug/L
Count/L (counts/liter) Count/L
Decay Constant (Infiltration) 1/hours 1/hours
Decay Constant (Pollutants) 1/days 1/days
Depression Storage inches millimeters
Depth feet meters
Diameter feet meters
Discharge Coeffcient dimensionless dimensionless

Orifice
Weir CFS / footn CMS / meter n
Elevation feet meters
Evaporation inches / day millimeters / day
CFS (cubi feet / second) CMS (cubic meters / second)

Flow GPM (gallons / minute) LPS (liters / second)
MGD (million gallons / day) MLD (million liters / day)
Head feet meters
Hydraulic Conductivity inches / hour millimeters / hour
Infiltration Rate inches / hour millimeters / hour
Length feet meters
Manning's n seconds / meter 1/3 seconds / meter 1/3
mass / length mass / length

Pollutant Buildup
mass / acre mass / hectare
Rainfall Intensity inches / hour millimeters / hour
Rainfall Volume inches millimeters
Slope (Subcatchments) percent percent
Slope (Cross Section) rise / run rise / run
Street Cleaning Interval days days
Volume cubic feet cubic meters
Width feet meters
Source: Storm Water Management Model. User's Manual (version 5.0), page 159.
A.2 Soil Characteristics

A.2 Soil Characteristics
Soil Texture Class K ¥ Ø FC WP
Sand 4.74 1.93 0.437 0.062 0.024
Loamy sand 1.18 2.40 0.437 0.105 0.047
Sandy Loam 0.43 4.33 0.453 0.190 0.085
Loam 0.13 3.50 0.463 0.232 0.116
Silt Loam 0.26 6.69 0.501 0.284 0.135
Sandy Clay Loam 0.06 8.66 0.398 0.244 0.136
Clay Loam 0.04 8.27 0.464 0.310 0.187
Silty Clay Loam 0.04 10.63 0.471 0.342 0.210
Sandy Clay 0.02 9.45 0.430 0.321 0.221
Silty Clay 0.02 11.42 0.479 0.371 0.251
Clay 0.01 12.60 0.475 0.378 0.265
K = saturated hydraulic conductivity, in/hr

¥ = suction head, in.
Ø = porosity, fraction
FC = field capacity, fraction
WP = wilting point, fraction
Source: Rawls, W. J. et al., (1983). J. Hyd. Engr., 109:1316
A.3 NRCS Hydrologic Soil Group Definitions

Saturated
Hydraulic
Group Meaning
Conductivity
(in/hr)
Low runoff potential. Soils having high infiltration rates even when
A thoroughly wetted and consisting chiefly of deep, well to excessively drained = or > 0.45
sands or gravels.
Soils having moderate infiltration rates when thoroughly wetted and

consisting chiefly of moderately deep to deep, moderately well to well-
B 0.30 - 0.15
drained soils with moderately fine to moderately coarse textures. E.g.,
shallow loess, sandy loam.
Soils having slow infiltration rates when thoroughly wetted and consisting
chiefly of soils with a layer that impedes downward movement of water, or
C 0.15 - 0.05
soils with moderately fine to fine textures. E.g., clay loams, shallow sandy
loam.
High runoff potential. Soils having very slow infiltration rates when
thoroughly wetted and consisting chiefly of clay soils with a high swelling
D potential, soils with a permanent high water table, soils with a clay-pan or 0.05 - 0.00
clay layer at or near the surface, and shallow soils over nearly impervious
material.
A.4 SCS Curve Numbers

Hydrologic Soil Group
Land Use Description A B C D
Cultivated land
Without conservation treatment 72 81 88 91
With conservation treatment 62 71 78 81
Pasture or range land

Poor condition 68 79 86 89
Good condition 39 61 74 80
Meadow
30 58 71 78
Good condition
Wood or forest land

Thin stand, poor cover, no mulch 45 66 77 83
Good cover 2 25 55 70 77
Open spaces, lawns, parks, golf courses, cemeteries, etc

Good condition: grass cover on 75% or more of the area 39 61 74 80
Fair condition: grass cover on 50-75% of the area 49 69 79 84
Commercial and business areas (85% impervious) 89 92 94 95
Industrial districts (72% impervious) 81 88 91 93
Residential3
Average lot size (% Impervious4) 77 85 90 92
1/8 ac or less (65) 61 75 83 87
1/4 ac (38) 57 72 81 86
1/3 ac (30) 54 70 80 85
1/2 ac (25) 51 68 79 84
1 ac (20)
Paved parking lots, roofs, driveways, etc. 5 98 98 98 98
Streets and roads

Paved with curbs and storm sewers5 98 98 98 98
Gravel 76 85 89 91
Dirt 72 82 87 89
A.5 Depression Storage

Impervious surfaces 0.05 - 0.10 inches 1.27 - 2.54 millimeters
Lawns 0.10 - 0.20 inches 1.54 - 5.08 millimeters
Pasture 0.20 inches 5.08 millimeters
Forest litter 0.30 inches 7.62 millimeters
Source: ASCE, (1992). Design & Construction of Urban Stormwater Management Systems, New York, NY
A.6 Manning's n - Overland Flow

Surface n
Smooth asphalt 0.011
Smooth concrete 0.012
Ordinary concrete lining 0.013
Good wood 0.014
Brick with cement mortar 0.014
Vitrified clay 0.015
Cast iron 0.015
Corrugated metal pipes 0.024
Cement rubble surface 0.024
Fallow soils (no residue) 0.5
Cultivated soils
Residue cover <20% 0.06
Residue cover >20% 0.17
Range (natural) 0.13
Grass
Short, prarie 0.15
Dense 0.24
Bermuda grass 0.41
Woods
Light underbrush 0.40
Dense underbrush 0.80
Soruce: McCuen, R. et al. (1996), Hydrology, FHWA-SA-96-067, Federal Highway Administration, Washington, DC
A.7 Manning's n - Closed Conduits

Conduit Material Manning n
Asbestos-cement pipe 0.011 - 0.015
Brick 0.013 - 0.017
Cast iron pipe

- Cement-lined & seal coated 0.011 - 0.015
Concrete (monolithic)
- Smooth forms 0.012 - 0.014
- Rough forms 0.015 - 0.017
Concrete pipe 0.011 - 0.015
Corrugated-metal pipe
(1/2-in. x 2-2/3-in. corrugations) 0.022 - 0.026
- Plain 0.018 - 0.022
- Paved invert 0.011 - 0.015
- Spun asphalt lined
Plastic pipe (smooth) 0.011 - 0.015
Vitrified clay
- Pipes 0.011 - 0.015
- Liner plates 0.013 - 0.017
Source: ASCE (1982). Gravity Sanitary Sewer Design and Construction, ASCE Manual of Practice No. 60, New York, NY.
A.8 Manning's n - Open Channels

Channel Type Manning n
Lined Channels
- Asphalt 0.013 - 0.017
- Brick 0.012 - 0.018
- Concrete 0.011 - 0.020
- Rubble or riprap 0.020 - 0.035
- Vegetal 0.030 - 0.40
Excavated or dredged
- Earth, straight and uniform 0.020 - 0.030
- Earth, winding, fairly uniform 0.025 - 0.040
- Rock 0.030 - 0.045
- Unmaintained 0.050 - 0.140
Natural channels (minor streams, top width at flood stage < 100 ft)
- Fairly regular section 0.030 - 0.070
- Irregular section with pools 0.040 - 0.100
Source: ASCE (1982). Gravity Sanitary Sewer Design and Construction, ASCE Manual of Practice No. 60, ew York, NY.
A.9 Water Quality Characteristics of Urban Runoff

Even Mean
Constituent
Concentrations
TSS (mg/L) 180 - 548
BOD (mg/L) 12 - 19
COD (mg/L) 82 - 178
Total P (mg/L) 0.42 - 0.88
Soluble P (mg/L) 0.15 - 0.28
TKN (mg/L) 1.90 - 4.18
NO2/NO3-N (mg/L) 0.86 - 2.2
Total Cu (ug/L) 43 - 118
Total Pb (ug/L) 182 - 443
Total Zn (ug/L) 202 - 633
Source: U.S. Environmental Protection Agency. (1983). Results of the Nationwide Urban Runoff Program (NURP), Vol. 1, NTIS PB 84-185552), Water Planning Division,
Washington, DC
A.10 Culvert Code Numbers

Circular Concrete
1 Square edge with headwall
2 Groove end with headwall
3 Groove end projecting
Circular Corrugated Metal Pipe

4 Headwall
5 Mitered to slope
6 Projecting
Circular Pipe, Beveled Ring Entrance

7 45 deg. bevels
8 33.7 deg. bevels
Rectangular Box; Flared Wingwalls

9 30-75 deg. wingwall flares
10 90 or 15 deg. wingwall flares
11 0 deg. wingwall flares (straight sides)
Rectangular Box;Flared Wingwalls and Top Edge Bevel:

12 45 deg flare; 0.43D top edge bevel
13 18-33.7 deg. flare; 0.083D top edge bevel
Rectangular Box, 90-deg Headwall, Chamfered / Beveled Inlet Edges

14 chamfered 3/4-in.
15 beveled 1/2-in/ft at 45 deg (1:1)
16 beveled 1-in/ft at 33.7 deg (1:1.5)
Rectangular Box, Skewed Headwall, Chamfered / Beveled Inlet Edges

17 3/4" chamfered edge, 45 deg skewed headwall
20 45 deg beveled edge, 10-45 deg skewed headwall
Rectangular Box, Non-offset Flared Wingwalls, 3/4" Chamfer at Top of Inlet

21 45 deg (1:1) wingwall flare
22 8.4 deg (3:1) wingwall flare
23 18.4 deg (3:1) wingwall flare, 30 deg inlet skew
Rectangular Box, Offset Flared Wingwalls, Beveled Edge at Inlet Top

24 45 deg (1:1) flare, 0.042D top edge bevel
25 33.7 deg (1.5:1) flare, 0.083D top edge bevel
26 18.4 deg (3:1) flare, 0.083D top edge bevel
Corrugated Metal Box

27 90 deg headwall
28 Thick wall projecting
29 Thin wall projecting
Horizontal Ellipse Concrete

31 Grooved end with headwall
32 Grooved end projecting
Vertical Ellipse Concrete

34 Grooved end with headwall
35 Grooved end projecting
Pipe Arch, 18" Corner Radius, Corrugated Metal

36 90 deg headwall
37 Mitered to slope
38 Projecting
Pipe Arch, 18" Corner Radius, Corrugated Metal

39 Projecting
40 No bevels
41 33.7 deg bevels
Pipe Arch, 31" Corner Radius,Corrugated Metal

42 Projecting
43 No bevels
44 33.7 deg. bevels
Arch, Corrugated Metal

45 90 deg headwall
46 Mitered to slope
47 Thin wall projecting
Circular Culvert
48 Smooth tapered inlet throat
49 Rough tapered inlet throat
Elliptical Inlet Face

50 Tapered inlet, beveled edges
51 Tapered inlet, square edges
52 Tapered inlet, thin edge projecting
Rectangular
53 Tapered inlet throat
Rectangular Concrete
54 Side tapered, less favorable edges
55 Side tapered, more favorable edges
56 Slope tapered, less favorable edges
57 Slope tapered, more favorable edges
Source: Storm Water Management Model. User's Manual (version 5.0), pages 166-167.
A.11 Culvert Entrance Loss Coefficients

Type of Structure and Design of Entrance Coefficient
-Pipe, Concrete
Projecting from fill, socket end (groove-end) 0.2
Projecting from fill, sq. cut end 0.5
Headwall or headwall and wingwalls:

Socket end of pipe (groove-end) 0.2
Square-edge 0.5
Rounded (radius = D/12) 0.2
Mitered to conform to fill slope 0.7
*End-Section conforming to fill slope 0.5
Beveled edges, 33.7o or 45o bevels 0.2
Side -or slope- tapered inlet 0.2
- Pipe or Pipe-Arch. Corrugated Metal
Projecting from fill (no headwall) 0.9
Headwall or headwall and wingwalls square edge 0.5
Mitered to conform to fill slope, paved or unpaved slope 0.7
*End-Section conforming to fill slope 0.5
Beveled edges, 33.7o or 45o bevels 0.2
Side -or slope- tapered inlet 0.2
- Box, Reinforced Concrete
Headwall parallel to embankment (no wingwalls)

0.5
Square-edged on 3 edges
Rounded on 3 edges to radius of D/12 or B/12
0.2
or beveled edges on 3 sides
Wingwalls at 30o to 75o to barrel:

0.4
Square-edged at crown
Crown edge rounded to radius of D/12: 0.2
or beveled top edge
Wingwalls at 10o to 25o to barrel:

Square-edged at crown 0.5
Wingwalls parallel (extension of sides):

Square-edged at crown 0.7
Side-or slope- tapered inlet 0.2
*Note: "End Sections conforming to fill slope," made of either metal or concrete, are the sections commonly available from manufacturers. From limited hydraulic tests they are
equivalent in operation to a headwall in both inlet and outlet control. Some end sections, incorporating a closed taper in their design have a superior hydraulic performance. These
latter sections can be designed using the information given for the beveled inlet.
Source: Federal Highway Administration (2005). Hydraulic Design of Highway Culverts, Publication No. FHWA-NHI-01-020.
Table 3-1. Available cross section shapes for conduits
Example of a natural channel transect
Types of pumps
Type1
An off-line pump with a wet well where flow increases incrementally with available wet well volume.
Type2
An in-line pump where flow increases incrementally with inlet node depth.
Type3
An in-line pump where flow varies continuously with head difference between the inlet and outlet nodes.
Type4
A variable speed in-line pump where flow varies continuously with inlet node depth.
Ideal
An "ideal" transfer pump whose flow rate equals the inflow rate at its inlet node. No curve is required. The pump must be the only outflow link from its inlet node. Used mainly for
preliminary design. The on/off status of pumps can be controlled dynamically by specifying startup and shutoff water depths at the inlet node or through user-defined Control Rules.
Rules can also be used to simulate variable speed drives that modulate pump flow.
EPANET
Appendix A - Units of Measurement
PARAMETER US CUSTOMARY SI METRIC
Concentration mg/L or µg/L mg/L or µg/L
Demand (see Flow units) (see Flow units)
Diameter (Pipes) inches milimeters
Diameter (Tanks) feet meters
Efficiency percent percent
Elevation feet meters
Emitter Coefficient flow units / (psi) 1/2 flow units / (meters)1/2
Energy kilowatt-hours kilowatt-hours
CFS (cubic feet / sec) LPS (liters / sec)

GPM (gallons / min) LPM (liters / min)
Flow MGD (milion gal / day) MLD (megaliters / day)
IMGD (Imperial MGD) CMH (cubic meters / hr)
AFD (acre-feet / day) CMD (cubic meters / day)
Friction Factor unitless unitless
Hydraulic Head feet meters
Length feet meters
Minor Loss Coeffcient unitless unitless
Power horsepower kilowatts
Pressure pounds per square inch meters
Reaction Coefficient (Bulk) 1/day (1st-order) 1 / day (1st-order)
mass / L / day (0-order) mass / L / day (0-order)

Reaction Coefficient (Wall)
ft / day / (1st-order) meters / day (1st-order)
Roughness Coefficient 10-3 feet (Darcy-Weisbach, milimeters (Darcy-Weisbach,

unitless otherwise) unitless otherwise)
Source Mass Injection mass / minute mass / minute
Velocity feet / second meters / second
Volume cubic feet cubic meters
Water Age hours hours
Note: US Customary units apply when CFS, GPM, AFD, or MGD is chosen as flow units. SI Metric units apply when flow units are expressed using either liters or
cubic meters.
Source: EPANET 2. User's Manual, (Appendix A, page 135).
Table 3.2 Roughness Coeffcients for New Pipe
Hazen-Wiliams C Darcy-Weisbach E Manning's

Material
(Unitless) (feet x 10-3) (Unitless)
Cast Iron 130 - 140 0.85 0.012 - 0.015
Concrete or
120 - 140 1.0 -10 0.012 - 0.017
Concrete Lined
Galvanized Iron 120 0.5 0.015 - 0.017
Plastic 140 - 150 0.005 0.011 - 0.015
Steel 140 - 150 0.15 0.015 - 0.017
Vitrified Clay 110 0.013 - 0.015
Source: EPANET 2. User's Manual, page 31.
Table 3.3 Minor Loss Coefficients for Selecting Fittings

FITTING LOSS COEFFICIENT
Globe valve, fully open 10.0
Angle valve, fully open 5.0
Swing check valve, fully open 2.5
Gate valve, fully open 0.2
Short-radius elbow 0.9
Medium-radius elbow 0.8
Long-radius elbow 0.6
45 degree elbow 0.4
Closed return bend 2.2
Standard tee - flow through run 0.6
Standard tee - flow through branch 1.8
Square entrance 0.5
Exit 1.0
Source: EPANET 2. User's Manual, page 32.
HEC-RAS
The state-of-the-art of Giswater's HEC-RAS project doesn't needs useful tables. All data tables HEC-RAS project needs must be introduced from HEC-RAS editors.
Стр. 13 из 16 03.03.2018, 12:27

APPENDIX D - ERROR AND WARNING MESSAGES

INSTALLING GISWATER AND FIRST TIME USE
ERROR NUM.1: STARTING GISWATER AT FIRST TIME: 'Could not find the main class: org.Giswater.gui.MainClass program will exit' is showing us JRE need to be updated. You
must to update Java Runtime Environment.
ERROR NUM.2: STARTING GISWATER AT FIRST TIME: File not found: c:/users/user/giswater/config/giswater.propierties. It indicates there is no file in this directory. May be the
installation process was wrong. During the installation of Giswater the process installs the software on the selected folder, but also install some files into your user folder. If you use
Windows XP all you need is repair the installation process moving by your own the file and the directory data from 'Documents and Settings' to the right position.
USING GISWATER APPLIED TO URBAN DRAINAGE

USING GISWATER APPLIED TO WATER SUPPLY
USING GISWATER APPLIED TO RIVER ANALISYS
COMMON ERRORS
GISWATER IS NOT ALLOWED TO WORK WITH POLAR COORDINATES REFERENCE SYSTEM.
You must to work only with a SRID working with cartesian coordinates.
Стр. 14 из 16 03.03.2018, 12:27

APPENDIX E - BUGS
We have created this page in order to make easy for the user the traceability of Giswater bugs (available from 1.1.174 version and following of Giswater). On the other hand, we
ecourage you to collaborate with us to detect and fix bugs.
Thank you very much!
Error importing SWMM 5.1 rpt files on storage target (SOLVED)

Origin: 1.1.145
Solved: 1.1.222
Notes:
If you use SWMM 5.1 and try to import rpt files with storage target it doesn't run. To solve it you must use SWMM 5.0.022 or edit rpt file in order to modify the target data..
Error importing pump results on SWMM projects (SOLVED)

Origin: 1.0.121
Solved: 1.1.226
Notes:
If your project was created before 1.1.226, you must to modify the rpt_pumping_sum table adding three new numeric (14,4) fields, and modify the view v_rpt_pumping_sum addin
this three new columns. On the other hand if your project was created after 1.1.226, you don't have any problem with this bug.
Problem with backup project data as and restore data on 32bits O/S (SOLVED)
Origin: 1.1.145
Solved: 1.1.223
Notes:
If you have installed a all-in-one version of Giswater previous of 1.1.222 running on a 32bits O/S you must to replace pg_dump.exe and pg_restore.exe from user/giswater
/portable/bin with the wright ones incorporated into the new Giswater installer.
Problem with function triggers using renamed or copied schemes (SOLVED)

Origin: 1.0.121
Solved: 1.1.174
Notes:
The bug is solved for 1.1.174 version and below.. Unfortunatelly this problem is not solved if you have project data schema renamed or copied before the 1.1.174 version. In order
to repair it, you have two options:
1) Repeat the process of copy or rename schema with the version of Giswater 1.1.174 or below. It will run well.
2) Use your wrong project data schema 'as is' and repair it. In order to do this, you must to replace the trigger funtion's of the schema. You must to execute the
epanet_functrigger.sql file or epawswmm_functrigger.sql file (replacing SCHEMA_NAME by the name of your schema). To do this, you can use PGAdim or the sql file laucher of
Giswater. Thiese files are on the giswater instalation folder: giswater/sql/. This files will repair the function trigger in order to solve the problem of the copied or renamed schema.
Стр. 15 из 16 03.03.2018, 12:27

Source URL (modified on 11/13/2016 - 12:40): http://www.old.giswater.org/en/documentation
Links
[1] http://old.giswater.org/documentation/chapter1
[2] http://old.giswater.org/documentation/1.1
[9] http://www.old.giswater.org/documentation/2.2
[30] http://old.giswater.org/documentation/gisprojects
[31] http://old.giswater.org/documentation/dbf-datamodel
[32] http://old.giswater.org/documentation/useful-tables
[33] http://old.giswater.org/documentation/software-messages
[34] http://old.giswater.org/documentation/bugs
[35] http://creativecommons.org/licenses/by-sa/4.0/
[36] http://www.giswater.org
[37] https://github.com/giswater/giswater
[38] http://www.youtube.com/channel/UCuuFlmjnu3HWVrXcyO3I-ow/videos
[39] http://www.postgresql.org/
[40] http://postgis.net/
[41] http://www.gnu.org/licenses/>
[42] http://download.giswater.org/Epanet2w.exe
[43] http://download.giswater.org/Epaswmm5.exe
[44] http://www.hec.usace.army.mil/software/hec-ras/downloads.aspx
[45] https://www.java.com/es/download/
[46] http://download.giswater.org/giswater_all-in-one.exe
[47] http://download.giswater.org/giswater_stand-alone.exe
[48] http://www.notepad-plus-plus.org
[49] http://www.giswater.org/documentation/2.6/project/database-administrator
[50] http://www.giswater.org/documentation/2.6/configuration/software-configuration
[51] http://www.giswater.org/node/56
[52] http://giswater.org/documentationl/gisprojects/epaswmm
[53] https://github.com/Giswater/giswater
[54] mailto:bugreport@giswater.org
[55] http://www.giswater.org/documentation/4.2
[56] http://giswater.org/documentation/gisprojects/epanet/epanet-data/options
[57] http://giswater.org/documentation/gisprojects/epanet/epanet-data/hydraulics/node/demand
[58] http://giswater.org/documentation/gisprojects/epanet/epanet-data/curve-patterns/curve
[59] http://giswater.org/documentation/gisprojects/epanet/epanet-data/hydraulics/node/junction
[60] http://giswater.org/documentation/gisprojects/epanet/epanet-data/global-reactions
[61] http://giswater.org/documentation/useful-tables/epanet/minor-loss-coefficients
[62] http://giswater.org/documentation/gisprojects/epanet/epanet-data/hydraulics/arc/pipe
[63] http://giswater.org/documentation/useful-tables/epanet/roughness-coefficients
[64] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/curve-timeseries
[65] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/climatology/temperature
[66] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/hydrology/subcatchment
[67] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/hydrology/lid-usage
[68] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/curve-timeseries/timeseries-values
[69] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/patterns
[70] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/hydrology/unit-hydrograph
[71] http://giswater.org/documentation/useful-tables/epaswmm/culvert-code-numbers
[72] http://giswater.org/documentation/useful-tables/epaswmm/types_pumps
[73] http://giswater.org/documentation/useful-tables/epaswmm
[74] http://giswater.org/documentation/useful-tables/epaswmm/cross_section_shapes_conduits
[75] http://giswater.org/documentation/gisprojects/epaswmm/epaswmm-data/quality/dwf
[76] http://owncloud.giswater.org/public.php?service=files&t=37b4ae05b76bb0f6429bf6eaf16c78f5
[77] http://owncloud.giswater.org/public.php?service=files&t=d534a1c06351a9d96d250226526d43ad
Стр. 16 из 16 03.03.2018, 12:27

GisWater Documentation

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GisWater Documentation

Caricato da

Copyright:

Formati disponibili

Documentation http://www.old.giswater.

Published on Giswater (http://www.old.giswater.org)

(English version only)

CHAPTER 1. INTRODUCTION [1]

CHAPTER 2. GETTING STARTED [7]

CHAPTER 3. WATER SUPPLY USER'S GUIDE [15]

CHAPTER 4. URBAN DRAINAGE USER'S GUIDE [20]

CHAPTER 5. RIVER ANALYSIS USER'S GUIDE [25]

APPENDIX A - DATABASE GIS PROJECTS [30]

APPENDIX B - DBF DATA MODEL SPECIFICATIONS [31]

APPENDIX C - USEFUL TABLES [32]

APPENDIX D - ERROR AND WARNING MESSAGES [33]

APPENDIX E - BUGS [34]

Last updated: Feb 10, 2015. Version code: 1.1.beta

Стр. 1 из 16 03.03.2018, 12:27

1.2 Project web sites

Web site: www.giswater.org [36]

Source code: https://github.com/giswater/giswater [37]

Youtube: http://www.youtube.com/channel/UCuuFlmjnu3HWVrXcyO3I-ow/videos [38]

1.3 Quick references

1.4 Giswater capabilities

Urban Drainage - Compatible with EPA SWMM version 5.0.022

DBF to INP and RPT to DBF, full capabilities

DB to INP and RPT to DB, full capabilities

Water Supply - Compatible with EPANET version 2.0012

DBF to INP and RPT to DBF, full capabilities

DB to INP and RPT to DB, full capabilities

River analysis - SDF compatible with HEC-RAS

DBF to INP: Not alloved

DB to SDF: 'Pre-Ras' capabilities

DBF: Shape file and DBF file

DATABASE: PostgreSQL with PostGIS 2.0 or higher

You can see <http://www.gnu.org/licenses/> [41].

Стр. 2 из 16 03.03.2018, 12:27

CHAPTER 2. GETTING STARTED

Windows XP is not supported.

- EPANET (version 2.0.12) [42]

Source code: EPA United States Environmental Protection Agency

- EPA SWMM (version 5.0.022 or higher) [43]

Source code: EPA United States Environmental Protection Agency

- HEC-RAS (version 4.1 or higher) [44]

Source code: US Army Corps of Engineers

- Java Runtime Environment (JRE) installed and updated [45]

Source code: Oracle corporation

- Text editor installed and configured

2.2 Installing Giswater

(*) Giswater is not supported running under Windows XP

2.3 Software configuration

2.4 Project preferences

2.5 Creating and managing samples

1- Create a new Project Preferences

3- Start GIS software and enjoy it!

2.6 Giswater menu

Project Data (scheme) Management

Rename Schema: You can rename a schema created before.

Delete Schema: You can delete a schema created before.

Copy Schema: You can copy from one scheme to other

Create Gis Project

Backup project data As

SQL file launcher

2.7.2 Log and SQL files

Стр. 3 из 16 03.03.2018, 12:27

CHAPTER 3. EPANET USER'S GUIDE