This is a choice among available type of source files:
Shape file
The source can be a Shape file containing any feature type: point (containing data on e.g. network nodes), polyline (containing data on e.g. network links) or polygon (containing data on e.g. catchments).
As shape files contain one data table only, an import job with a Shape file as a source cannot include import of multiple tables.
Excel file
An EXCEL file may contain several data tables to be included in the job definition. Each column in a table must contain a text header in Row1 and the data in consecutive rows. All data in one column must be of the same type.
CAD file
AutoCAD proprietary format "DWG" is supported, as well as “DXF” format. Because it is not an open standard format, MIKE+ import supports it with some limitations. E.g. geometry and some simple attributes are supported, while labels are not supported.
Geodatabase
Import can access tables in the ESRI geodatabase
ODBC
Open Database Connectivity (ODBC) interface is a C programming language interface that makes it possible for applications to access data from a variety of database management systems (DBMSs). ODBC implementation in MIKE+ import supports the following sources:
· MS Access
· SQLite
Relevant drivers for reading these file formats are not installed with MIKE+. To import a Microsoft Access database, the user must therefore install the Microsoft Access Database Engine driver beforehand. To import a SQLite database, the user must install the SQLite ODBC driver.
The geometry for the features shown on the map must be defined in Well Known Text (WKT) format.
ISYBAU file
The ISYBAU exchange formats are used for the standardized exchange of data for the planning, construction and operation of wastewater facilities, originating from Germany. ISYBAU is a column-oriented exchange format in text form.
MIKE+ DB
MIKE+ database (SQLite or PostGIS) can be used as a source for data import, typically when the current project needs to be populated with data from another MIKE+ project.
Result Layer
This option is used for export of mapped 1D network results to external formats, e.g. to shape. 2D result layers cannot be exported from this tool (use instead the option to export to shape file, from the 'Layers and symbols' tree view).
SQL Server
This option is used to connect to a database hosted on a SQL Server.
The geometry for the features shown on the map must be defined in one of the following formats: SQL Geometry, Well Known Binary (WKB) format or Well Known Text (WKT) format.
Oracle spatial
This option is used to connect to an Oracle spatial database.
ICM (csv format)
This option is used to read and import individual .csv files previously exported from a ICM model setup (one file per ICM database table). The recommended workflow to import these data is as follows:
· Export the ICM model setup to individual .csv files, all saved in a common folder
· Create an import job in MIKE+, and select this folder as import source
· Click the 'Automap sections' buttons: this will load a predefined configuration, to import the collection system data (rivers and 2D model data not yet configured)
· Review the import configuration and adjust if necessary
· Run the import.
Note that this import option allows importing network data to MIKE+, but differences of numerical methods between the two different products imply that some data may not be imported or may need further manual adjustments after the import, especially for example for Rainfall-Runoff modelling. Also note that no automatic conversion of units nor coordinate system is performed during this import.