Predefined Import and Export Routines

MIKE+ comes with some standard (automated) routines for import and export from and to commonly used formats. These include the following:

• Import of projects from MIKE URBAN formats (*.mdb and *.gdb)
• Import of MIKE 21 model setup
• Import of MIKE HYDRO River model setup.
• Import of MIKE 11 model setup. Some functionalities and options from MIKE 11 are not supported in MIKE+ and cannot be imported.
• Import of MIKE FLOOD model setup. Two options are available:
  • Import full MIKE FLOOD model setup: imports all data from a MIKE FLOOD setup file. All data files used in the selected MIKE FLOOD setup will be imported to the MIKE+ database: MIKE URBAN classic, MIKE 21, MIKE HYDRO River, MIKE 11, couplings. Some functionalities and options from MIKE 11 are not supported in MIKE+ and cannot be imported.
  • Import MIKE FLOOD couplings: imports only the couplings from a MIKE FLOOD file. Related river, urban and/or 2D data files are not imported. A related MIKE HYDRO River file can be reused in MIKE+ using the coupling to MIKE HYDRO River, instead of importing its data into the MIKE+ database.
• Import of SWMM model setup
• Import of EPANET model files
• Export of CS and River model setup to MIKE1D engine input file (M1DX)
• Export of 2D overland setup (MIKE 21 model)
• Export of MIKE FLOOD couplings
• Export of SWMM collection system model setup to SWMM model file
• Export of WD model setup to EPANET model file

The predefined Import/Export jobs are accessed directly through the main "File" menu option, rather than going to the Import/Export tool.

 

Figure: Example of pre-defined Import jobs for MIKE+ CS and Rivers, accessed from "File" menu

Any pre-defined import works in "Overwrite" mode, i.e. any content in the current MIKE+ Database will be deleted and replaced by the new contents, except the import from MIKE HYDRO River and from MIKE 11 which will append the imported data to the existing data in the database.

 

Figure: Before executing any the pre-defined import, user gets prompted to accept overwrite of any contents which might exist in the current target database

Any warning or error occurring during a predefined import task will be reported in the log view in MIKE+. In some cases, this log view can report actions to undertake after the import, and should therefore be reviewed carefully. These reported messages are also saved to a log file saved in the database's folder, so that they can be reviewed at a later stage.

Import from a MIKE URBAN Model

Importing a MIKE URBAN model to MIKE+ requires that MIKE URBAN (Release 2020 Update 1) is installed on the computer. This is because the import routine uses some software components associated with MIKE URBAN Classic.

Before using the predefined import for a MIKE URBAN model, it is necessary to update any old models to MIKE URBAN Release 2020 Update 1 so that the *.MDB or .*.GDB source database is in the correct format. Ensure that all related files (including any selection files, customized dhiapp.ini files, time series files, etc.) are all correctly selected in the MIKE URBAN project so that the paths to these files can be properly imported. Finally, for Collection System models, ensure that your simulation(s) run with the MIKE 1D engine, and correct input data as necessary if any error is reported.

Once the MIKE URBAN model is prepared, the following steps will import the model into MIKE+:

• Open a new MIKE+ window
• Click on File|Import

 

Figure: Accessing and activating the pre-defined import of a MIKE URBAN Classic project

• Choose the source database type (“*.MDB” or “*.GDB”)
• Browse the source database
• Specify the target MIKE+ database’s type and location

 

Figure: The 'Import from MIKE URBAN' window

• Press the 'Run' button, which will initiate the import process
• The progress and success (or failure) of the import can be followed in the Log tab

 

Figure: Log View reports on import progress, and issues warnings and error messages. Upon completed import, the log should be carefully reviewed and in case of any anomaly reported, an appropriate action should be taken

If a MIKE+ database is opened before opening the 'Import from MIKE URBAN' window, the MIKE URBAN project will automatically be imported into the opened MIKE+ database. This MIKE+ database will be overwritten during the import, i.e. all data previously defined in the database will be lost and replaced by data and settings imported from MIKE URBAN.

Import limitations of MIKE URBAN models

The data below are not imported when importing a Collection System project from MIKE URBAN Classic:

• WQ Process model data (N/A in MIKE+)
• SRQ data (New concepts are implemented in MIKE+, see documentation)
• SWQ Surface Runoff pollutants (New concepts are implemented in MIKE+, see documentation)
• SWQ local treatments (N/A in MIKE+)
• ST data
• LTS statistics specifications (included as part of MIKE+ output definition)
• Emptying storage nodes (N/A in MIKE+)

Import from a MIKE HYDRO River model

Before importing a MIKE HYDRO River model to MIKE+, it is necessary to save the MIKE HYDRO River file in its latest software version, i.e. with MIKE Zero 2023, so that the file is in the correct format. Ensure that the MIKE HYDRO River simulation runs successfully before importing, in order to avoid errors during the import.

Once the MIKE HYDRO River model is prepared, the following steps will import the model into MIKE+:

• Select the model type 'Rivers, collection system and overland flows' in the 'Model type' editor
• Click on File|Import
• Choose 'Import MIKE HYDRO River model (mhydro)

 

Figure: Accessing and activating the pre-defined import of a MIKE HYDRO River model

• Browse the source file
• Press the 'OPEN' button, which will initiate the import process
• The progress and success (or failure) of the import can be followed in the Log View

During the import, if the map projections defined respectively in the MIKE HYDRO River and the MIKE+ models differ, the MIKE HYDRO River data will be reprojected in the map projection used in MIKE+.

Import from a MIKE 11 model

Before importing a MIKE 11 model to MIKE+, it is necessary to save the MIKE 11 files with their latest software version, i.e. with MIKE Zero 2023, so that the files are in the correct format. Ensure that the MIKE 11 simulation runs successfully with the MIKE 1D engine before importing, in order to avoid errors during the import.

Once the MIKE 11 model is prepared, the following steps will import the model into MIKE+:

• Select the model type 'Rivers, collection system and overland flows' in the 'Model type' editor
• Click on File|Import
• Choose 'Import MIKE 11 model (sim11)
• Browse the source *.sim11 file
• Press the 'OPEN' button, which will initiate the import process
• The progress and success (or failure) of the import can be followed in the Log View

During the import, if the map projections defined respectively in the MIKE 11 and the MIKE+ models differ, the MIKE 11 data will be reprojected in the map projection used in MIKE+.

Note

Some functionalities and options from MIKE 11 are not supported in MIKE+ and cannot be imported. This especially applies to the Sediment Transport module, which has been fully revisited compared to its MIKE11 version. The functionalities and the scientific theory used in MIKE+ are therefore different: some MIKE 11 functionalities may not be supported anymore in MIKE+, whereas new functionalities are added. When converting a MIKE11 model including Sediment Transport to MIKE+, it is therefore expected that significant differences of sediment transport results are encountered, which may require that you adjust the model definition if needed.

Import of 2D Overland Setup Files

• Select the model type 'Rivers, collection system and overland flows' in the 'Model type' editor
• Click on File|Import
• Choose one among three available options for overland model sources (complete MIKE FLOOD setup, MIKE 21 model or MIKE FLOOD couplings)

 

Figure: Accessing and activating the pre-defined import of a MIKE 21 model setup

• Browse the source file

 

Figure: File-browser points to the wanted source file (.m21, .m21fst or .m21fm). Alternatively, only coupling data or complete MIKE FLOOD setup can be imported by pointing to a MIKE FLOOD file (.couple).

• Press the 'OPEN' button, which will initiate the import process
• The progress and success (or failure) of the import can be followed in the Log View as well as a progress bar

 

Figure: Log View reports on import progress, and issues warnings and error messages. Upon completed import, the log should be carefully reviewed and in case of any anomaly reported, an appropriate action should be taken.

Import of SWMM File

• Select the model type 'SWMM5 collection system and overland flows' in the 'Model type' editor
• Click on File\Import\Import SWMM model

 

Figure: Accessing and activating the pre-defined import of SWMM model file (.inp)

• Browse the source file (*.INP)

 

Figure: File-browser points to the wanted SWMM file (.inp)

• Press the 'OPEN' button, which will initiate the import process
• The progress and success (or failure) of the import can be followed in the Log View as well as a progress bar

Import of EPANET File

• Select the model type 'Water distribution' in the 'Model type' editor
• Click on File\Import\Import EPANET model

 

Figure: Accessing and activating the pre-defined import of EPANET model file (.inp)

• Browse the source file (.inp)

 

Figure: File-browser points to the wanted EPANET file (.inp)

• Press the 'OPEN' button, which will initiate the import process
• The progress and success (or failure) of the import can be followed in the Log View as well as a progress bar

 

Figure: Log View reports on import progress, and issues warnings and error messages. Upon completed import, the log should be carefully reviewed and in case of any anomaly reported, an appropriate action should be taken

Export to .m1dx File

To export the model to a .m1dx file:

• Select the model type 'Rivers, collection system and overland flows' in the 'Model type' editor
• Choose File|Export
• Click on 'Export to M1DX file'

 

Figure: Accessing and activating the pre-defined export of MIKE+ CS project to MIKE1D input file (.m1dx)

• Browse the location to export the new MIKE 1D file
• Optionally change the name of the new export file which has by default the name of the current project

 

Figure: The file is saved at a location specified by the user. Per default, the filename is given as the name of the MIKE+ source database but can be modified by the user.

• Press the 'Save' button

After the export has completed, the dialog will be closed automatically. Two files are created (CS network): a cross sections file (*.xns11) and a m1dx File (*.m1dx).

Export to MIKE 21 FM Setup File

To export the model to an *.m21fm file:

• Select the model type 'Rivers, collection system and overland flows' in the 'Model type' editor
• Choose File|Export
• Click on 'Export to MIKE 21 FM setup file'

 

Figure: Accessing and activating the pre-defined export of MIKE+ 2D overland data MIKE 21 FM model file (.m21fm)

• Browse the location to export the new MIKE 21 FM file
• Optionally change the name of the new export file which has by default the name of the current project

 

Figure: The file is saved at a location specified by the user. Per default, the file name is given as the name of the MIKE+ source database but can be modified by the user.

• Press the 'Save' button

Export to EPANET Model File

To export the model to an EPANET *.inp file:

• Select the model type 'Water distribution' in the 'Model type' editor
• Choose File\Export\Export EPANET model

 

Figure: Accessing and activating the pre-defined export of MIKE+ WD project to EPANET model file (.inp)

• Browse the location to export the new EPANET model file
• Optionally change the name of the new export file which has by default the name of the current project

 

Figure: The EPANET file is saved at a location specified by the user. Per default, the file name is given as the name of the MIKE+ source database but can be modified by the user.

• Press the 'Save' button

Export to SWMM Model File

To export the model to a SWMM *.inp file:

• Select the model type 'SWMM5 collection system and overland flows' in the 'Model type' editor
• Choose File\Export\Export SWMM model

 

Figure: Accessing and activating the pre-defined export of MIKE+ SWMM data to SWMM model file (.inp)

• Browse the location to export the new SWMM model file
• Optionally change the name of the new export file which has by default the name of the current project

 

Figure: The SWMM file is saved at a location specified by the user. Per default, the file name is given as the name of the MIKE+ source database but can be modified by the user.

• Press the 'Save' button