Microstation, from the 8.9 version (XM) brings a series of functionalities to interact with Google Earth. In this case I want to refer to the import of the three-dimensional model and its image, something similar to what it does AutoCAD Civil 3D.
These functions are activated by:
or in case Microstation is in Spanish, which in practice costs to adapt:
This is a functionality of any platform running on Microstation, such as PowerCivil, Bentley Map, Bentley Coax, etc. The sixth and seventh icons serve, one to synchronize the view of Google Earth based on the one we have in Microstation and the other to do the inverse. The fourth icon is to bring the Google image to the map.
1. The dgn file
To start, this function requires that the dgn file is 3D, in case we have a file built with seed 2D what should be done is:
File> export> 3D
Then we open the file that we have exported. The other characteristic that you must have is a geographic reference system. This changed a bit after Microstation 8.5, but it usually recognizes a system assigned with those versions although sometimes it only mentions that it is A UTM system but it does not define the zone. In case you do not have it, it is done using the first bar icon that I showed at the beginning of the post and choosing the system that interests us within the library. In this case we must assign a projected system (northing, easting ...) and choose the World (UTM) option with WGS84 datum, since it is the system that uses Google Earth.
To not be fighting so much, you can assign the system to the favorites and thus should not be searched every time we require it.
In the case of Google Earth, it is convenient to hide the compass, the status bar, grid or any other element that does not interest us. It is also possible with the option of Historical images that came from Google Earth 5, turn off coverages of years that do not interest us, often the most recent are less visible. Once ready, we must choose the area of interest, and make the synchronization between Google Earth and Microstation.
There is a panel that facilitates some configurations, but in practice they are not so useful because the vertical reference system used by Google Earth is quite simplified, with some exceptions in some areas of the United States and Puerto Rico. So it makes little sense to choose the altitude deviation; what is important here is to define whether a triangulated mesh or a grid will come; the option "see terrain" must always be active.
2. Import image
To import the image just choose the fourth button of the bar and click on the screen. As a result, the captured grid will arrive.
To see the image, we make: Tools> render> View, And with this we raised a panel in which we decided some configurations of the type of rendering, line visibility and brightness of the image.
To see the model in isometric, we do it with the tool that is on the View, and we place an isometric or we rotate it freely. See that it is possible to even render only one fenced area with fence or an area based on an object. And if we choose the option stereo, We can see the work with stereoscopic lenses -Of those we forgot to return when leaving the cinema-. The panel I show below differs a bit depending on the application, because in this case I'm using PowerCivil Which has more rendering options.
The image comes in grayscale and quality is little less than lousy as it is only one Print sreen; It improves when using the Google Pro version and keeping Google Earth in DirectX mode. In the case of the digital model, you can not improve more than what Google offers, however this seems a very practical way out for complementary work with Stitchmaps, With which you can download a higher quality image and With this one can be geo-referenced.
Although to be shown occupy is rendered as it is a digital model and not an image, every time a change is applied to the rendering, an image is generated in the same directory, which can be loaded separately with the raster manager.
Clarifying a couple of questions: Do not bring 3D buildings, because these are not part of the digital model and you can improve the accuracy of the model by making smaller captures. See the example of San Sebastian, where the quality of information is a luxury; On the right is the same capture made with different levels of approach.
Until now, PlexEarth Takes the merit as the best integration tool between Google Earth and a CAD platform.