Viewing model data tables

<< Click to Display Table of Contents >>

Navigation:  HydroSWMM Tutorial > HydroSWMM Tutorial: step-by-step > Capturing, editing and saving the model data >

Viewing model data tables

All the data required for the hydraulic analysis of the existing system has now been captured. The data resides in a SQLite geodatabase (resident only in program memory because not saved yet), for which the location was previously specified.

 

The data is kept in a number of different “categories”. A grid table for each of these categories can be opened for viewing the data (and results), and for further editing if required.  This is done by double-clicking on tables in the GIS pane, prefixed with 'St_'. There is also an option to load a Curves grid table, which is for advanced use of the program where special pump curves and tank volume versus level curves apply. This is not addressed in this tutorial.

 

Open the St_Conduit_Tables table. This table gives a list of all the Conduits in the system.   In this table all the data associated with the Conduits are shown, e.g. their geometries, diameters, lengths and roughness coefficients and analysis results if available.

 

Browsing through the table will show that the various columns/fields are grouped together in categories (displayed in distinctive colours), similar to the various groups and fields found in the Database box of an individual pipe. The grouping of fields and the formatting of the display (numeric format, background colour) can be set as a table “Layout” that can be saved and later retrieved.  But a variety of such layouts are predefined and loaded at program installation, e.g. an “Data” layout focusing on the input data, a “Analysis” layout focusing on the flows and pressures, etc.  Regular HydroSWMM users can pick an appropriate layout and do not have to bother with creating and specifying their own customised layout.

 

In the “All Fields” layout the first four columns display the Topology info, i.e. Link Type, Link Code, From Code and To Code. The next 6 Hydraulic columns are the system data fields, required for hydraulic calculations. Then there are Physical, Descriptive, Results, Planning and Assets groups.  These are followed by Results group use for storing and presenting the various maximums recorded during analysis. The final four groups are: Integrity; GUID and Geometry; Selection.

 

Any changes made in the table and others will only be updated permanently to the geodatabase when the table is closed and the model is saved. The table can be closed by clicking on the TableCloseIcon Close icon in the top right-hand corner of the table window, or by selecting File > Close. Therefore, use the File > Close option to exit the table and then Manage Models > Save Model followed by Yes to confirm to save the  changes made up to this point to the geodatabase (if not already saved).

 

Open the St_Conduit_Tables table. This table gives a list of all the ordinary nodes (junctions) in the system. In this table the data associated with the ordinary nodes are shown, e.g. their outputs. Browsing through the table will show that the various columns/fields are grouped together in categories (displayed in distinctive colours), similar to the various groups and fields found in the Database box of an individual node. As for the pipe table (and in fact any table in the model or in the GIS environment), the grouping of fields and the formatting of the display (numeric format, background colour) can be set as a table “Layout” that can be saved and later retrieved.

 

In the “All Fields” layout, the first three columns display Topology info, i.e. Node Type, Node Code and Elevation (m). The next two Hydraulic columns are the system data, required for hydraulic calculations such as the Output field. This table contains similar field group types to the Junction table.

 

All of the data tables can be used to edit system info, and can be customized to the users preferences with regards to which columns should be visible, number formats, font sizes, colors, etc. Any edits/changes made in the tables, when updated to program memory, will  also be reflected in the Albion environment, and in the individual node and link Database boxes.