MicroStation Tip: Rendering Material Assignments in Google Earth

Published on July 7, 2015

Written by: Bob Mecham
Credit to: Margaret Valletta – McFarland Johnson

I was providing professional guidance to Margaret on a 3D rendering project.  She wanted to take her 3D MicroStation model and export it to Google Earth.  I shared with her one of my previous tips MicroStation V8i SS3 with Google Earth and Map that showed how to export your DGN file to Google Earth.

trimble sketchup model microstation render

MicroStation Rendering of Trimble Sketchup file


In Margaret’s situation she had a 3D model that she downloaded from 3D Warehouse. The 3D models had material assignments already assigned to the model.

If you followed my previous tip the export would have looked like this in Google Earth.

Google Earth Export

Google Earth Export

To make sure the file is exported with the rendering assignments applied there is a setting that needs to be changed.

1. From the Geographic Toolbar select the Google Earth Tools Settings icon.  The Google Earth Tools Settings dialog will appear.

google earth settings microstation

2. From the Google Earth Tools Settings dialog change the Output Format to KML and Collada.

microstation google earth kml collada export rendering

Then export the Google Earth KML file again and the model will keep its rendering assignments.

microstation rendering in google earth

Google Earth Rendering


Terrain Element                            Coordinate System for the New Drawing                                Adjacent Elements
OpenRoads Tip: Change Profile                 Civil 3D Tip: Converting Civil 3D                                         MicroStation Tip:
Symbology of your Terrain                              Parcels to GIS Shapefiles                                             Aligning Patterns

Tags: , , ,
Like this article? Share it!

Leave a Comment

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Privacy Policy