InfoSewer Control.DBF File in the IEDB Folder

 InfoSewer Control.DBF File in the IEDB Folder

Parameter	Value	Description
ID		Identifier for the object/element
METHOD		Control method or rule applied
ON		Condition for activating the control
OFF		Condition for deactivating the control
STA_FLOW		Starting flow rate for the control
BASE_FLOW		Base flow rate without control
PATTERN		Flow pattern or profile
MIN_SPEED		Minimum allowed speed for flow control
MAX_SPEED		Maximum allowed speed for flow control

InfoSWMM to InfoSewer - Caveats with Emojis

🚧 The primary challenge in transitioning from 🌧️ InfoSWMM to 🚰 InfoSewer lies in the differences between the two software's requirements and restrictions. InfoSewer, unlike InfoSWMM, has a more ⛓️ rigid set of rules and constraints, which can make the conversion process 🔄 complex and ⏳ time-consuming. Some of these rules and constraints are as follows:

🌲 Dendritic network: InfoSewer requires a dendritic network structure, meaning that the network must be a tree-like structure without loops or closed circuits. This constraint ensures a simpler flow path and a more stable 🌊 hydraulic simulation.

💪 Strict force main and pump rules: InfoSewer enforces specific rules for force mains and pumps, such as the requirement to connect force mains directly to pump stations and the need for wet wells. These rules help maintain the accuracy and consistency of simulations in pressurized systems.

⛰️ Adverse slope issues: InfoSewer is sensitive to pipe slopes and may flag adverse slopes that could lead to hydraulic issues or incorrect flow directions. Careful attention must be paid to the elevation data to avoid these problems.

🔄 Loop issues: As mentioned earlier, InfoSewer requires a dendritic network without loops. Loops in the network must be removed or modified to adhere to this constraint, which can be a challenging and manual process.

🔗 Disconnected node issues: InfoSewer does not allow orphan or disconnected nodes, which means all nodes must be connected to the main network. These disconnected elements must be identified and either connected or removed from the model.

🌊 Flow splits: InfoSewer requires proper flow splits to ensure accurate flow distribution among downstream pipes. This may necessitate the manual adjustment of flow splits, making the conversion process more time-consuming.

While automating the entire conversion process from 🌧️ InfoSWMM to 🚰 InfoSewer is difficult due to these rules and constraints, the use of 📑 CSV and 🌍 shapefile import and export tools can streamline certain aspects of the process. These tools help in transferring data between different formats and can make the conversion process more manageable. However, a thorough review and adjustment of the model's elements are still required to ensure that the resulting InfoSewer model adheres to its specific rules and produces accurate simulations. 🎯

The primary challenge in transitioning from InfoSWMM to InfoSewer lies in the differences between the two software's requirements and restrictions. InfoSewer, unlike InfoSWMM, has a more rigid set of rules and constraints, which can make the conversion process complex and time-consuming. Some of these rules and constraints are as follows:

1. Dendritic network: InfoSewer requires a dendritic network structure, meaning that the network must be a tree-like structure without loops or closed circuits. This constraint ensures a simpler flow path and a more stable hydraulic simulation.

2. Strict force main and pump rules: InfoSewer enforces specific rules for force mains and pumps, such as the requirement to connect force mains directly to pump stations and the need for wet wells. These rules help maintain the accuracy and consistency of simulations in pressurized systems.

3. Adverse slope issues: InfoSewer is sensitive to pipe slopes and may flag adverse slopes that could lead to hydraulic issues or incorrect flow directions. Careful attention must be paid to the elevation data to avoid these problems.

4. Loop issues: As mentioned earlier, InfoSewer requires a dendritic network without loops. Loops in the network must be removed or modified to adhere to this constraint, which can be a challenging and manual process.

5. Disconnected node issues: InfoSewer does not allow orphan or disconnected nodes, which means all nodes must be connected to the main network. These disconnected elements must be identified and either connected or removed from the model.

6. Flow splits: InfoSewer requires proper flow splits to ensure accurate flow distribution among downstream pipes. This may necessitate the manual adjustment of flow splits, making the conversion process more time-consuming.

While automating the entire conversion process from InfoSWMM to InfoSewer is difficult due to these rules and constraints, the use of CSV and shapefile import and export tools can streamline certain aspects of the process. These tools help in transferring data between different formats and can make the conversion process more manageable. However, a thorough review and adjustment of the model's elements are still required to ensure that the resulting InfoSewer model adheres to its specific rules and produces accurate simulations.

ALINK.csv CBNode.csv ANODE.csv CBLINK.csv InfoSewer Files in the IEDB folder

 ALINK.csv CBNode.csv ANODE.csv CBLINK.csv InfoSewer Files in the IEDB folder have only 2 Columns, ID and Type.

Column Label	Description
ID	A unique identifier for a specific record or row in the file. This could be a sequential number, a randomly generated code, or any other system for identifying individual entries in the file. InfoSewer Element ID.
Type	A categorical variable that assigns a type or category to each record in the file. This could be used to group similar items together, classify data based on a certain criterion, or any other use case where data needs to be organized by type. Domain or Active

The DBF Files in the IEDB Folder of InfoSewer - All Files

 

FILENAME	DESCRIPTION
ALINK.csv	File containing information about a specific type of link element
ANNO.csv	File containing annotation data
ANNODATA.csv	File containing additional annotation data
ANODE.csv	File containing information about a specific type of node element
CBLINK.csv	File containing information about a specific type of link element
CBNODE.csv	File containing information about a specific type of node element
CHAMBOUT.csv	File containing data related to chamber output
CONTOUR.csv	File containing contour data
CONTROL.csv	File containing control data
COSTING.csv	File containing costing information
CTRDATA.csv	File containing control data
CTRLSET.csv	File containing control settings
CURVE.csv	File containing curve data
CUVDATA.csv	File containing data related to culverts
DISCGHGL.csv	File containing information about discharge GHGLs
DMLINK.csv	File containing information about a specific type of link element
DMNODE.csv	File containing information about a specific type of node element
FDMDATA.csv	File containing FDM data
FDSDATA.csv	File containing FDS data
FLDMAP.csv	File containing FLD map data
FLDSET.csv	File containing FLD settings
FORCEOUT.csv	File containing force output data
FOXUSER.csv	File containing user data
GISFDATA.csv	File containing GISF data
GISGATE.csv	File containing GIS gate data
HLLINK.csv	File containing information about a specific type of link element
HLNODE.csv	File containing information about a specific type of node element
HYDROGRH.csv	File containing hydrographic data
LINK.csv	File containing information about a specific type of link element
LINK.DBF.csv	File containing information about a specific type of link element
LKHLINKS.csv	File containing LKH links data
LUCOEFF.csv	File containing LUC coefficients
MANCOVER.csv	File containing manhole cover data
MANHOLE.csv	File containing manhole data
MAPSSLK.csv	File containing MAPSS link data
MAPSSND.csv	File containing MAPSS node data
MHHYD.csv	File containing MH hydraulic data
MHOFFSET.csv	File containing MH offset data
MHOUT.csv	File containing MH output data
MHSET.csv	File containing MH settings
MHSHP.csv	File containing MH shape data
MOLINK.csv	File containing information about a specific type of link element
MONODE.csv	File containing information about a specific type of node element
NAMEVIEW.csv	File containing name view data
NCPIDGN.csv	File containing NCP IDGN data
NCPIXSEC.csv	File containing NCP IXSEC data
NDHLINKS.csv	File containing NDH links data
NDSOURCE.csv	File containing ND source data
NODE.csv	File containing information about a specific type of node element
NODE.DBF.csv	File containing information about a specific type of node element
OPERSET.csv	File containing operator settings
OUTLEOUT.csv	File containing outlet output data
PATNDATA.csv	File containing pattern data
PATTERN.csv	File containing pattern information
PIDGNSET.csv	File containing PIDGN settings
PIIISET.csv	File containing PIII settings
PIPE.csv	File containing information about a specific type of pipe element

FILENAME	DESCRIPTION
PIPECNST.csv	File containing pipe construction data
PIPEDGN.csv	File containing pipe design data
PIPEHYD.csv	File containing pipe hydraulic data
PIPEII.csv	File containing pipe II data
PIPEOUT.csv	File containing pipe output data
PIPESET.csv	File containing pipe settings
PIPESHP.csv	File containing pipe shape data
PIPESPLT.csv	File containing pipe split data
PIPEWQ.csv	File containing pipe water quality data
PISPTSET.csv	File containing PI/SP/TSET data
POLYREG.csv	File containing polygon regression data
PUMP.csv	File containing pump data
PUMPHYD.csv	File containing pump hydraulic data
PUMPOUT.csv	File containing pump output data
PUMPSET.csv	File containing pump settings
QRYSET.csv	File containing query settings
QSETDATA.csv	File containing query set data
QSSSLK.csv	File containing QSSS link data
QSSSND.csv	File containing QSSS node data
QUERY.csv	File containing query data
RELATE.csv	File containing data about element relationships
REPORT.csv	File containing report data
RPTDATA.csv	File containing report data
RUNOPT.csv	File containing run options
SCENARIO.csv	File containing scenario data
SELSET.csv	File containing selection set data
STATUS.csv	File containing status data
TIME.csv	File containing time settings
VERTEX.csv	File containing vertex data
WWELL.csv	File containing well data
WWELLHYD.csv	File containing well hydraulic data
WWELLOUT.csv	File containing well output data
WWELLSET.csv	File containing well settings
XLOAD.csv	File containing external load data
XLOADSET.csv	File containing external load settings
XNGLINK.csv	File containing cross-nodal links data
XNGNODE.csv	File containing cross-nodal node data