Product(s): | WaterCAD, WaterGEMS, HAMMER |
Version(s): | 08.11.XX.XX and higher |
Area: | Import Export |
With WaterCAD or WaterGEMS, Is it possible to import from or export to a water modeling competitor product such as the list below?
It would not be practical for the OpenFlows product to attempt to directly support all possible competitor products and versions, which may often change. So, the OpenFlows products offer a rich set of data import functionality to support standard data formats. For the Water products, the best option is often the standard EPANET INP file format. In the other product, look for the ability to export to EPANET / INP format. Once you have the EPANet INP file created, you will be able to import it into WaterCAD, WaterGEMS or HAMMER by going to File > Import > EPANET.
Note:
a) Number of facilities (pipes, junctions, tanks, pumps, valves, reservoir...)
b) Total length of pipes, total *** of C-values
c) Junction elevations: Min, Max, Zeros if any
d) Pump elevations, pump curve --> 1 point, 3 points, multiple...
e) Valve type and settings (Double check the settings type, HGL or Pressure and adjust the value as needed)
f) Controls: If original model (like H2OMap/H2ONet/InfoWater) had PLC's (Programmable logical control) or Simple control, controls may have to be created manually.
g) Patterns: If pattern name is "1", double check the pattern data. Count the total number of patterns and double-check the data.
h) Initial Status: check for pump, pipe and valves at the minimum.
If the product does not support exporting to EPANET (for whatever reason) and if you have access to that software then I assume, you can export your features (elements, it's data) to shapefiles. Export or copy/paste the tabular data like pump curve, demand pattern to spreadsheet software like MS Excel. Once you have data in shapefile, dxf, Excel etc, you can use ModelBuilder (Tools > ModelBuilder) to Import your data to a Blank model (or an existing model). This link help you understand how ModelBuilder works.
If you no longer have access to InfoWater and cannot export the model to EPANET INP format (to then import into WaterGEMS/WaterCAD), please contact Technical Support for assistance as we may be able to provide another solution.
Important note: If the coordinate unit in the Infowater model does not match the units of other values like demand/flow, the EPANET export will not work properly. EPANET relies on the "Flow Unit" (such as GPM or LPS) to determine if all values in the model are assumed to be metric or US. So, your demands, flow, diameter, etc may convert correctly, while the coordinates may have the correct value but the wrong unit (such as feet vs. meters).
This can happen notably if the Coordinate System in Infowater is Web Mercator, which converts the projected (lat/long) WGS 1984 coordinates to linear values in meters.
This also means that if the coordinate system of the model in Infowater is different than what you would like to use in WaterGEMS, you may also need to reproject the model (to convert the coordinates from one unit system to another). So, a mix of Shapefile export (via Flextables, for all element types), reprojection (via ArcGIS, QGIS or MicroStation for example) and ModelBuilder import may be necessary.
EPANET is free software. To Import an EPANET model, it will need to be in INP format (from EPANET itself, the .INP file can be exported). In WaterCAD or WaterGEMS, go to File > Import > EPANET.
To export a WaterCAD/WaterGEMS model to EPANET, go to File > Export > EPANET. If you have a WaterCAD/GEMS model but no longer have access to a license, either user it in trial mode to perform the export, or send the files (.WTG and .WTG.SQLITE, zipped) to Bentley Support.
The Scenario Name is provided to EPANET through the [TITLE] part of the exported INP file.
This is an optional part of the INP, but WaterCAD and WaterGEMS will populate the text here during EPANET export. This can be useful to confirm the scenario corresponding to the INP file.
Or in EPANET itself:
Keep in mind the following limitations: What are the limitations of importing/exporting EPANET files?
See Also
Troubleshooting problems with importing EPANET or EPASWMM files