Import Microstation DGN File(s)
Use the Map > Import > Microstation DGN File(s) menu option (IMPORTDGN GX), to import a Microstation DGN file into an Oasis montaj map. Information about the plotted objects and about the "attribute" data may be stored to a new or current database, while the graphical objects are plotted to a new map or to the current map. This import does NOT support the newer DGN V8 format.
Use the Add to 3D > Imports > Microstation DGNFile(s) menu option (IMPORTDGN GX, to add a Microstation DGN file to a 3D View.
Microstation DGN Import dialog options (3D View)
Microstation DGN file(s) |
Select one or more Microstation DGN (*.dgn) files to import. Script Parameter: IMPORTDGN.FILES (Separate files with the "|" character. |
Import Microstation DGN File(s) dialog options (Map)
Microstation DGN file(s) |
Select one or more Microstation DGN (*.dgn) files to import. Script Parameter: IMPORTDGN.FILES (Separate files with the "|" character. |
Create map element database? |
Select whether to import information about the individual graphical elements to a new database. Script Parameter: IMPORTDGN.DBOUT (0: no (default), 1: yes) |
Current Map |
Click this button to import the file(s) to the current map. Script Parameter: IMPORTDGN.MAPOUT (Option: 0: Current Map) |
New Map |
Click this button to import the file(s) on a new map. Script Parameter: IMPORTDGN.MAPOUT (Option: 1 : New Map) |
Import to a New Map dialog options
Create a New Map dialog options
Map name |
Specify the name of the new map. Automatically pre-populated with the same name as the input Microstation DGN file name. Script Parameter: IMPORTDGN.MAP |
Create a New Database dialog options
DGN file |
Not editable. Set to the input Microstation DGN file name. |
Database name |
Specify the name of the new database. Automatically pre-populated with the same name as the input Microstation DGN file name. |
Application Notes
-
If the Microstation DGN file(s) are imported to a current map, the imported data will be projected onto the plane of the current data view. If the view is a normal "plan" view, then the Z-dimension information will be lost. If the view is a "section" view (such as those created for drillhole sections in Target), the data is projected horizontally onto that plane. If imported to a 3D View, the objects are plotted as in the original files.
-
A Microstation DGN file contains a list of geographic "elements" each of which may have a corresponding set of "attribute" data. Each DGN element has its analogue in an Oasis montaj map. The linkage between the feature and the data is maintained by writing the X and Y location values for each shape to the Oasis montaj database, along with the data. Use the shadow cursor, as normal, to find the correspondence between rows in the database and features on the map.
-
There is no simple way to import attribute data into a "flat file" format, since the storage format can differ between different elements in the same DGN file; e.g. two polygon objects could be linked to completely different databases with different sets of attributes. In addition, the links themselves can be chained, so that one link with one set of data leads to another set of attribute data. Instead, some basic information about the linkage is displayed as channel data (see below). Only information on the first linkage is returned.
-
DGN file elements are written to the "DGN" view in a map. The group name is the same as the Microstation DGN file’s name, with the particular levels appended; e.g. "DGN_MyMap_023". There is no fixed convention to which levels display what objects. In fact, in many files the majority of objects are put into one or two levels, while the small remaining elements are scattered among many levels!
-
All DGN files will be imported into the same map. A separate "group line" in the database is created for each DGN file.
-
The DGN import has been implemented using the Open-source DGNLib library, written by Frank Warmerdam: http://gdal.velocet.ca/projects/dgn/.
Database Channels Created
X, Y |
Geometric center of the plotted object, found by taking the mid-point in X and Y. |
ID |
Index to the element in the DGN file (starting at 0). |
Type |
The object type. The following is a listing of the types of elements imported:
|
Level |
The level of the object in the file, a number from 0 to 255. Not all levels are present, and only those objects actually plotted are represented in the database. |
Group |
The "graphics group". It is not known what this corresponds to, but it may be an alternate way to sort the data. |
Xmin, Xmax, Ymin, Ymax |
The minimum and maximum bounds of the object in X and Y. |
AtBytes |
The number of bytes of attribute data linked to. If the attribute data is not stored inside the DGN file, but as a link to an external database, this value is likely to be 48. |
LinkType |
Types of attribute linkage. Some indicate a type of database, other internally stored attributes. The following are known types:
|
EntityNum |
The index of the attribute data in the linked database table. Although the actual data is not imported, this may be useful in determining which attribute data in the linked database is being pointed to. |
MSLink |
If defined, then the attribute data contains a link to yet more attribute data? |
LinkSize |
Number of bytes of data in the linked database? |
Got a question? Visit the Seequent forums or Seequent support
© 2023 Seequent, The Bentley Subsurface Company
Privacy | Terms of Use