Here’s a quick ‘tip & trick’ that was brought to my attention and I think it’s top, a top tip & trick, as it were.
The navigate button doesn’t display the entire list of associated objects if these are too numerous, see below.
Navigate Menu Doesn’t Display All Associated Object if too Numerous.
If you need to display these then you can create a grid of all the objects that are associated with your current object, use the menu option ‘Show All In Grid’, again accessed through the navigate button, see image below.
Allow multiple survey databases import
InfoMaster now has the ability to batch import multiple PACP databases into one set of survey import. A new dialog box was introduced to allow users to select as many PACP databases as they wish.
InfoMaster assumes all the selected PACP databases have the same schema and all databases will be imported use the same mapping settings.
The inline bank is a flexible link which can serve a number of purposes. It can be used as 1D irregular weir connecting between two 1D nodes or it can be used to allow a 1D-2D Linear connection in an inline sense (as opposed to a lateral sense). For example, the 1D-2D linear connection can be used to represent flow onto a 2D representation of a bridge deck, or allow flows from a channel represented in 1D to connect to a 2D representation (or vice versa) or represent the spill of flow into a 2D storage area. The inline bank could also potentially be used to represent a linear gully connection into the drainage network.
The inline bank is a linear feature, similar to the banklines, but allows the inline connection of between 2D and 1D based on the weir equation (shown in the help under the ‘River Reach-Bank Flows’ topic. It is a very flexible piece of functionality both in a pipe network context and a river context as it will allow the transfer of flow between 1D and 2D, and vice versa, along a number of mesh elements.
The first step is to set up a bankline. This can be digitised using the New Objects tool. The bank line essentially governs the connectivity between the 1D and 2D. The bankline needs elevations, discharge coefficients and modular limits associated with it. If required the elevations can be gathered from any open ground model by selecting the bankline and going to Model->Sample line elevations from ground model.
I have been working on the various versions of SWMM since 1980 when I was a co-author and co-developer of SWMM3, a co-author and co-developer of SWMM4 in 1988 and a co-developer of SWMM 5 from 2002/2006. I have worked at Innovyze as a Product Sector Leader since 2008 and have grown to love the power and ability of InfoSWMM and all Innovyze software such as InfoWater, InfoWorks ICM, H2OMap SWMM and InfoSewer. This blog post explains based on my experience why InfoSWMM makes you a better modeler or modeller for the SWMM 5 engine rather than just directly using the SWMM 5 engine and GUI available from the USEPA. I am still an almost daily user of SWMM 5 so I have a constant comparison between the ability of the InfoSWMM Modeling Platform over the SWMM 5 GUI.
The basic layout and features of InfoSWMM as an Arc Map in Arc GIS
My Top Ten Reasons for preferring InfoSWMM over SWMM 5 based on my experience: These are the top ten reasons I have found over the last seven years for using InfoSWMM over the SWMM 5 GUI:
- Scenario, Database and Facility Managers, InfoSWMM allows you to have present and future scenarios and a facility manager so that it is easy to have active and inactive sections of your network, make smaller networks and simulate only portions of your network for calibration or design. Domain and Selection Sets for editing and output graphics. Two hundred plus tools for Elevation Extraction, Pond Extraction, Data Inference, Data Connectivity etc. based on the proven technology and creativity from the past 18 years of InfoWater development.
- The Tools of InfoSWMM and construction of InfoSWMM are based on almost 18 years of InfoWater Arc Map development; you are buying tools that have been proven across platform and modeling engines for many years.
- Database editing of Network Elements and Output Files in either the Attribute Browser, DB Tables or the Output Report Manager Tables and Graphs. Continue reading
The problem: Imagine you are interested in selecting and displaying in a table the node with the lowest ground level in your network. You might initially think that the following would work:
Erroneous SQL Syntax
SELECT node_id, MIN(ground_level)
However what is displayed is an arbitrary node ID in the network and the lowest ground level value. This is simply how SQL works in any database. The syntax in the SELECT query simply asks for a list of node IDs and the minimum ground level. But since there is only one minimum ground level, the list of node IDs is condensed to just the one, and NOT the one corresponding to the minimum ground level.
InfoSWMM has real time control or control rules for the three types of pump in addition to the pump on and pump off depth rules. Each of the rules have a priority in case two or more rules apply at any one time step. This blog shows how to see the pump setting in the Speed Ratio graphs.
Step 1. Set the Pump Startup and Shutoff Depths, not elevations or levels.
Figure 1. Pump Startup and Shutoff Depth
Depths to turn the Pump On and turn the Pump Off. In this example, the pump will be off when the Wet Well Depth is less than 2 feet, the Pump will be off between a Wet Well Depth between 2 and 5.75 feet if the Pump is currently Off and the Pump will be On between a Wet Well Depth between 5.75 and 2 feet.
Step 2. RTC Rule for the Pump Setting when the Wet Well Depth is less than 6.25 feet. We need to add the AND statement so that the setting is only reset when the Pump is On. You do not want the pump setting to be reset when the pump should be off (Figure 2). Continue reading
Initialisation is a process where InfoWorks attempts to achieve a steady state in the system before simulation. During initialisation the dry weather flow input starts at zero and gradually increases to the full value. The full value is the sum of the first value in all dry weather inputs including population flows, trade flows, inflows and infiltration. InfoWorks will continue to iterate until a steady state has been reached, i.e. InfoWorks continues to redefine values and re-calculates to an acceptable level of accuracy. The steady state is defined by convergence criteria parameters listed under network / simulation parameters. If for some reason the convergence criteria cannot be reached then initialisation continues ad infinitum, the model will not complete initialisation.
The most common reason for a model not initialising is due to flooding occurring in the model, oscillating volume or a never ending rise in level in some nodes.
Intoduction: InfoSewer is used worldwide by municipal engineers and planners to create detailed, accurate models of their sewer infrastructure systems. These models enable users to evaluate the effect of new developments, zoning changes, and other additional loads on system flows; pinpoint current and future problem areas; predict overflows and backups; and determine how to best restore needed capacity lost to infiltration and inflow with the least rehabilitation. In addition, users rely on these models to compute hydrogen sulfide generation and corrosion potential; analyze the rate of Biochemical Oxygen Demand (BOD) exertion; track sediment movement and deposition; calculate the amount of pollutant transported to the wastewater treatment plant; and assess pollutants’ impacts on receiving waters. Extensive scenario management along with domain and facility management functionality makes the program capable of analyzing existing or proposed sewage collection systems. It has a Steady State, Design and EPS run modes and includes many of the same Arc Map tools that exist in InfoWater and InfoSWMM.
This blog discusses how to use Peaking factors from a Steady State simulation in an EPS simulation. One of the advantages of the three Run options in InfoSewer (Bullet 1 in the image) which are Steady Sate, Design and Extended Period or EPS Modeling is that you can use Peaking Flow Factors for the Steady State Loading Manholes (Bullet 2 in the image). Unfortunately, you cannot use Peaking Factors for EPS simulations which is often a modeling issue. However, you can copy the Total Flow for each node in the Steady State Output Report and use this Total Flow as an EPS “other” loading (Bullet 3 in the image). In an EPS Simulation you can use the Advanced Force Main Modeling option and automatically have flow splits for Force Mains and model more complicated Force Main configurations. If you just simulate the EPS for one hour then you have a quasi steady state simulation with Total Flow (Unpeakable + Peakable) and the Advanced Force Main Solution.
A list of steps you need to take to use the Peak Flow from a Steady State Run in an EPS Simulation include
1. Use Peaking Factor in InfoSewer for Steady State
2. Copy Total Loads at Manholes
3. Use the Total Loads in an EPS simulation
4. Run the EPS Simulation for a short period of time
5. If might help to have two scenarios for this copy and pasting
6. Use the Advanced FM solution for only the EPS Simulation
Peaking flow in InfoSewer Steady State applied as Total Flow in an EPS Simulation
Once a field has been added to a form it is subsequently possible to change the type of field to better suit your data capture requirements. For example you may want to change a field from a text box to combo box. This would allow you create a selection list for user to populate the field with rather than simple free typing, helping to reduce errors and increase data quality.
In the example below you will see how the location code field can be modified from its default text box to be a combo box.
The location code field has been added to a manhole survey form in its default configuration.
About a year ago I wrote about customising InfoNet’s built-in Word reports. Read “Customising InfoNet’s Built-in Word Reports”.
In this post I’m going to expand on that blog entry to explain how to add a field to the report that doesn’t appear in the Word Bookmark List. As of the latest version of InfoNet, version 15.0, all fields in an object are exposed to the reports. These can be added by using the database field name, see image below. In this example I am adding the ‘Chamber Floor Depth From Cover’ to a manhole survey report, and as such use ‘chamberfloordepth’.
Adding a field to a report, using database field name.
I then highlight the database field name, see image below…