Previously We saw how to do with Microstation Geographics V8, and the alternative of importing .shp files.
Let's see how the world changed in the case of version 8.9 known as Bentley Map XM. The way to handle it is very robust, in the sense that Microstation can now read, edit, call a reference ... not only a shape but also an mxd and more.
1. Open a .shp file
This is done simply with "file / open" and choosing the shp format. This opens read-only, but as if it were a dwg or dgn.
Bentley did very well this alternative to open files directly, because in addition to the .dgn, .dxf and .dwg that he was already doing, you can open cells (.cel), libraries (.dgnlib), redline (.rdl), 3D Studio files (.3ds), SketchUP (.skp), Mapinfo (.mif and .tab native format) among others.
Once the shape is opened, the objects can be touched as if it were a common map.
When viewing the properties table, you can read the associated .dbf database ... wow!
Also when using the "review attributes" command, the xfm features table is displayed, equivalent to the dbf data.
2. Call Reference
Making reference file / map manager can be called in different ways:
- As picture:
Here you can call ESRI files, such as .mxd, .lyr and .shp. The advantage of calling it from here is that it supports the theming associated with the mxd while the simple shp leaves with a flat color. Also by being called as an image, the transparency control can be easily managed.
- As Attributes:
This is a special panel, in which you can choose feature classes separately to display them in different views, or in stored fences.
- As a reference map:
Called as a reference, you can control the snap option, although an interesting aspect is that as a reference it also supports Mapinfo files (.tab and .mif).
So once you bring them in, through the panel of map manager can be turned off or on features, groups of features, layers or feature classes.
3. Save an .shp file
The file can be saved in different formats, dgn, dwg, dxf, dgnlib (dgn library) or rdl (redline dgn).
The data is stored in xml format, inside the dgn; that is, the dgn contains the data ... the marvel of the implementation known as xfm features.
4. Importing via Interoperability:
The option called interoperability is an alternative that allows you to connect to data served via datasource: ODBC, OLEDB and Oracle as an ArcSDE or ArcServer service.
One of the advantages of doing this is that you can choose a feature class separately, assigning the type of attribute to be imported such as line type, fill, transparency, etc. also if you have a project, the target attributes are chosen.
This is done via "file / imoprt / gis data"
In the same way you can export a service ... which is understood should see an ESRI user ... that I have not tried but one of these days I will have time.
Not bad, considering that you have the ability to edit CAD and interoperability with ESRI formats.