You can import network data from various external sources. When importing a network, you can also import a control file containing control data for the network.
If the control file contains a record that refers to a network object that is not in the network, that record will be ignored.
If you use the lock method of version control, imported version controlled items are always checked in. You will need to check out the network before you can make changes.
You can import data from an InfoWater XINP file. See Import InfoWater Data.
You can import data from the Synergi Water modelling package from GL Water. See Import Synergi Data.
You can import data from EPANET v2 networks into InfoWorks WS Pro. You must first export your EPANET model as text files. InfoWorks WS Pro does not import the binary format (.NET) files. See Import EPANET Data.
The EPANET software package simulates hydraulic and water quality behaviour in pressurised pipe networks. EPANET is produced by the United States Environmental Protection Agency. For further information, see the EPANET 2 User Manual.
You can import data from AQUIS .dat files into InfoWorks WS Pro. See Import AQUIS Data.
You can import data from WATSYS/WaterMax v96 networkrs into InfoWorks. See Import WATSYS/WaterMax Data.
You can import network data from an AutoCAD DWG file. See Import from AutoCAD DWG.
You can import data from CSV files. The files must be in an appropriate format and may need specific filenames. You can find further details on format requirements in CSV File Formats. See Import from CSV Files.
You can import network data from an InfoAsset snapshot file. See Import from InfoAsset Snapshot File.
You can set up your own mapping between fields in the import data and fields in the database. Advanced users can also use scripts to control the import process.