This dialog is used to import data into an existing or new network.
To open the dialog when you want to create a network from scratch
using external data:
To open the dialog when you want to add objects to an existing network from external
data:
To open the dialog when you want to update an existing network from external
data:
| Item |
Description |
|
Table to Import Data Into
|
The database table into which you want to import data. You can
only import data one table at a time.
|
|
Flag Behaviour
|
The flags to be set on imported data:
|
Import flags from data source
|
If checked, displays an additional Flag Fields column
in the Assignment Grid.
This allows flag fields
in the external data to be mapped onto flag fields in the selected table.
|
|
Otherwise, set flag on imported fields to
|
For selecting the flag to be used for imported fields.
The flag will be applied to all
fields imported from the selected Data Source,
that can be flagged.
If the Import flags from data sourcebox has been checked, the flag will be applied only to imported fields
that do not have an imported flag.
|
|
Flag when Default Value is used
|
For selecting a flag from to apply to all fields
in which the value has been set from the Default
Values column of the Assignment Grid.
|
| Only flag genuine changes to data values |
With this option checked, the flag value will only be changed if the incoming value differs from the current value by more than the display precision. |
|
|
Data Source
|
This is for selecting the type of data you want to import. Once you have done
so, you will need to enter other information, such as a file name, or GeoPlan
layer name. You may also need to choose a data type or database table
containing the data you want to import.
|
Source Type
|
The types of data you can import. Only valid
data types are listed.
|
GeoPlan Layer
|
GIS data currently loaded as an additional
layer on the GeoPlan.
|
|
CSV Format Data
|
A text file with the fields separated
by commas.
|
|
Tab Separated Data
|
A text file with the fields separated by tab characters.
|
|
JET/Access Database
|
An Access (.mdb) database (also sometimes known as 'Jet database')
|
|
Oracle
|
For importing from Oracle databases.
The minimum version of Oracle supported for import without
spatial data is Oracle 8i. To import spatial data a minimum version of
Oracle 9.2 is required.
The following Oracle spatial geometries are supported or partially supported for import:
- Point
- Oriented Point - orientation vector is ignored
- Multi-Point - first point only imported
- Point Cluster - first point only imported
- Line String - supported where points are connected only by straight lines
- Polygon - supported where the boundary is connected only by straight lines or where it is a rectangle
- Multi-Polygon - first polygon (connected by straight lines or a rectangle) only imported
- Collection - first compatible element only imported (if present)
- Multi-Line String - first line string only imported
The following Oracle spatial geometries are not currently supported
for import:
- Line Strings where the points are connected by
arcs
- Compound Line Strings
- Polygons where the boundary is connected by arcs
or is a circle
- Compound Polygons
- Complex Collections
|
|
GeoDatabase
|
A format for storing GIS data developed by ESRI.
For importing data from Personal GeoDatabases and ArcSDE.
This option can also be used to import ESRI shapefiles.
Note: This option requires a licenced copy of ArcGIS™ installed
on the computer on which the import is being performed.
|
|
ArcView Shape File (.shp)
|
MapObjects or ArcGIS shape file format.
This option is available
only if using MapObjects as the current map control in the GeoPlan window.
|
|
MapInfo Tab File (.tab)
|
MapInfo Tab File format.
This option is available only if using MapX as the current map control
in the GeoPlan window.
|
|
Raw Shape File
|
Data in the ESRI shapefile format.
Imports shape files directly instead of using any map control.
|
|
XML Format Data
|
A text file formatted in the eXtensible Markup Language.
|
| SQL Server
|
For importing data from a Microsoft SQL Server database, via the OLE DB Driver for SQL Server. See Select SQL Server Data dialog for connection details.
|
|
|
File
|
For certain types of data you will need to specify a filename. You can use the
Browse button to find the file.
When importing from an Oracle database, this will display the Select Oracle Data dialog.
|
|
Feature
|
For certain types of data you will need to specify the feature. You can select
the feature from the dropdown list.
When importing from an Oracle database, only tables for which the user
has been granted the appropriate read permissions in Oracle will be available
for selection.
|
|
|
Script File (optional)
|
You can use a script to control the import process more precisely. You can use
this box to browse for the script file.
Note: Scripts are an advanced feature and not recommended
for anyone without experience of programming in a scripting language.
To help you with writing your own scripts, you can use the Reload button to load the latest version of your selected script after making
changes in an external editor such as Notepad. This allows you to adjust
the script and test the changes without closing and re-opening the dialog.
See Using a script to control import of network data for more details.
|
|
Units Behaviour
|
You can use the options in this dropdown list to specify how units are handled
during the import process. The options are:
| InfoWorks |
The external
data uses InfoWorks WS Pro native units |
| User |
The external data
uses the currently defined user units for the network. |
| Custom |
You can set the
units used for each field in the imported data yourself.
An extra Units column is added to the Assignment Grid. You can then select
the correct units from the options available in the dropdown list for
each field.
|
|
|
Load Config
|
Load in a previously saved configuration (CFG) file. The file contains
details only of the settings in the Assignment Grid.
You need to set the other options on the dialog, such as the Select
Table to Import into field, to match those used when the configuration
file was saved.
|
|
Save Config
|
You can save all the settings in the Assignment Grid to a file (suffix CFG). These settings can then be reused for future imports.
|
|
Clear Config
|
You can clear all previous field mappings using this button.
|
|
Auto-Map
|
You can click this button to attempt to automatically map fields in the external
data to fields in the master database. Make sure you have chosen the appropriate
table in the Select Table to Import into box before
using this button.
InfoWorks WS Pro uses the standard field names used when exporting from
InfoWorks WS Pro to try to link the fields up.
|
|
Assignment Grid
|
You can use this grid to define exactly how the external data should be imported
into fields in the master database.
|
Object Fields
|
This column lists all the fields for the current InfoWorks WS Pro object
type, as selected from the Table to Import Data into dropdown.
Any field shown in red type is required for import. You must map at
least these required fields.
You cannot change any of the fields in this column.
|
|
Import Fields
|
This column allows you to map fields in the external data to the InfoWorks WS Profields listed in the Object Fields column.
- You can map the fields manually by choosing an
external field in the dropdown list for each InfoWorks WS Pro field in the
Object Fields column. You must map the required
fields before you can import data.
- You can try to map fields automatically by clicking
the Auto-Map button. InfoWorks WS Pro will
attempt to map the fields. The mapping is based on the names used for
fields when data is exported to GIS from InfoWorks WS Pro.
- When importing data from an Oracle database, to
import spatial data, map the Oracle spatial data field to the Geometry
Object field (highlighted in blue) in the Object Fields column.
|
|
Default Values
|
This column allows you to set values of fields directly as well as from
external data.
On import:
- If an external data field has not been mapped,
the field for which the default value has been set will be assigned the
value entered in the Default Values column.
- If both an external data field has been mapped
and a default value has been entered, the external data will be used where
available. Where the external data contains a null value or a blank, the
default value will be used instead.
|
|
Flag Fields
|
This column is displayed only if you have ticked the Import
Flags from GIS checkbox.
Cells in this column are greyed out for data that cannot have a flag.
|
|
Units
|
This column is displayed only if you have chosen the Customoption for units behaviour.
You can choose the units for each field in the dropdown lists. Fields which
do not require units information are greyed out.
|
|
|
Updating and Delete Options
|
The updating options allow you to decide how to handle duplicate objects
in the external data.
|
Prompt
|
These options set the action to be followed when an object is encountered
in the external data with the same name as an object already in the model.
Note: When importing arrays (for example, Reservoir:
Depth Volume data), existing array data will be overwritten unless
the Merge option is selected, in which case data
will be appended to the existing array.
|
You will be asked whether or not you want to overwrite the current object every time a duplicate object is found in the external data.
|
|
Merge
|
Fills in any blank fields in the existing object with data from the imported
object. Does not change any existing data.
|
|
Overwrite
|
Replaces data in the existing object with data from the imported object.
(If the imported object does not contain data for a field, the existing
data in that field will not be changed.)
|
|
Ignore
|
Ignores the imported object if it is a duplicate.
|
| Replace |
Replaces the object. |
|
Update Based on Asset ID
|
If this option is checked, InfoWorks WS Pro will look for duplicate objects
using the Asset ID field and not the usual
object identifier. Note: When updating link objects using Object
ID, the Link Suffix field of the object is
used (in addition to the connected node IDs), to check for duplicate links.
If connected node IDs match those of an existing link, but a link
suffix is not provided, the Open Data Import Centre will create a new
link object by incrementing the link suffix. |
|
Only update existing objects
|
If this option is checked, InfoWorks WS Pro will only update existing objects.
No new objects will be created on import. |
|
Delete missing objects
|
If this option is checked, InfoWorks WS Pro will search for missing objects
of the relevant type and delete them at the end of the import process.
(A missing object is an object that is in the InfoWorks WS Pro Table
to Import Data Into but is NOT in the external Data
Source table.) If the Update Based on Asset ID option is checked,
the Asset ID field will be used to search
for missing objects and not the usual object identifier. All missing objects found will be listed and a prompt for confirmation
of deletion will be displayed before any objects are deleted. |
|
|
Use auto-name option for generated nodes
|
If checked, uses the automatic
node name generation functionality for naming nodes that are generated
when importing disconnected links. (See Using the open data import centre for more information.)
This option will be enabled only when automatic naming is switched on
and an object for which nodes may be generated has been selected from
the Table to Import Data Into section.
|
|
Import multi-parts
|
The Open Data Import Centre provides limited support for the import of polygons with multi-parts and complex shapes.
The option is enabled only when a polygon type table is selected and the data source selected is a GIS layer (from a file or from the GeoPlan).
Polygons will be imported in the following way:
|
GIS multi-part polygon
|
Do not import multi-parts: Imported as one polygon
|
Import multi-parts: Imported as three separate polygons
|
|
GIS polygon with hole
|
Do not import multi-parts: Imported as one polygon
|
Import multi-parts: Imported as polygon with umbilical cord between two shapes
|
When importing multi-part polygons, the ID and area of the polygons will be generated automatically, regardless of the mappings entered in the Assignment Grid.
A maximum of 10 fields may be mapped in the Assignment Grid when using this option.
|
|
Import
|
Imports data based on the current settings.
|
|
Close
|
Quits the importer.
|
Show image
