Importing Revit files into Infraworks

Importing your Revit model into Infraworks is a simple workflow and can be done in 3 ways.

1. Native Revit file imported via the cloud processing tool in Infraworks / or the local processing tool.
2. Exporting Revit via FBX (Revit always exports FBX units as feet) and importing FBX into Infraworks.
3. Export Revit via DWG (metric Revit files export as metric. Great for massing options) and importing into Infraworks.

My preferred workflow is using FBX, why this method? 

• Exporting is done by FBX as it is sent to from Revit to Infraworks. Infraworks does allow RVT files (via the cloud / or local processing if you have Navisworks Manage installed) to be imported but I found that if you can create an FBX file (with LOD used) of the exact model you require. Ie turning off all internal elements (furniture) in a saved 3d view making a smaller FBX file (hence a smaller AIM model). Similar workflow when exporting Navisworks from Revit, controlling the output.

• The Basepoint in Revit is the model setout point of the exported FBX. You need to record the coordinates of the Basepoint as this will be used to position the FBX file in the correct location. This is based on the fact that you have set the model up with the correct coordinate which related to the site which is known the coordinate system.

The above image of the Revit model showing that the model has being rotated to True North and that the base point is located in the PCG94 grid system.

Import FBX file which has not been configured

The known coordinates system is inputted. Ie PCG94 in this example. 

The x been the E/W from Revit 53800.6077, The Y been the N/S from Revit 264989.7382 and the Z been the Elev from Revit 17. Before recording the values, I change the Revit unit to Meter. 

FBX location define in the configuration

Before recording the values, I change the Revit unit to Meter. 

Revit Units Set to Meters

• The Result of the building FBX file is imported into Infrawork using the Base point as the setout for the file. The model appears in the correct location but incorrectly rotated. What was not done during the configuration of the FBX file was input the True North rotation from Revit base point

• The strange part to get the model to be correctly rotated is to take the Revit rotation to true north and minus that from 360. Eg. 360°- 207.332°  is = to 152.668. using the value you input that into the configuration of the rotation for the Z.

The Z value of the Revit ration to True North - 360.

The short video below is a workflow that I've used to export Revit to FBX which then imported into Infraworks.

Copying Coordinates System

A couple of years ago I wrote about how to create a local grid system for Perth coast Grid PCG94. You can copy the user definition of grid system from PC to PC using the following workflow, which Civil 3d, Map 3d and Infraworks access to the copied grid system.

The PC that does not have the defined Local grid system will need to configure Civil 3d or Map 3d to allows a definition of the grid system to be copied from PC to PC. The copied coordinates system will now be available in Infraworks. 

• Set your workspace to Planning and Analysis
• On the Map Setup Tab - Coordinate System click on the options (Small little arrow in bottom right-hand corner)

The AutoCAD Map 3d option dialogue box and find the Coordinates system tab.

Coordinate System Definitions Stored in Drawings select Prompt User or Automatically add.

Now open a .dwg that contains the user-defined coordinate system from the other PC that has the defined coordinate system. The defined coordinate system will now be available on the PC that previously missing the user-defined coordinate system including
Infraworks.

You can download a sample .dwg that contains Perth Costal grid here PCG94

Infrastructure BIM model

I've finished up working at DoT and haven't really had time to blog / document about the work flows from the project. The project was a business case for a tack slab through the heart of a CDB. My involvement was looking at the cost impact of existing services and infrastructure. This was done by traditional feature survey and laser scanning of the 22km (500gb of point cloud data) alignment to create a BIM model of existing services, using AS5488 (SUE) classification of subsurface utility information as a base line. Majority of the existing in-ground services where modelled to class C with a couple of major services to class B. The model consisted not only of the existing infrastructure but the proposed light rail infrastructure which was created with multiple software's. 

The simple definition of the BIM process to create the model would be similar to a carpenters set of tools, with each piece of software having its own key use. Similar to how a carpenter uses specific tools to construct a house. 

The exchange process between different platforms was done via landxml. 
A simple list of the software's used and their function. 

• Bentley Rail used for the rail design
• 12d used for the road design
• Civil 3d for the existing surface and existing utilities 

The large data set of the point cloud was processed using Recap which reduced the file size of the point cloud data from about 500gb down to 150gb. Which had the point cloud data set usable on a 22km alignment. 

All of the above was placed into navisworks to run multiple rules to determine the impact of the light rail on the existing infrastructure with the results exported to excel to be processed and costed. 

This Video below and what has been described above is only a snippet of what was done. On the bottom of the screen each service is colour coded.

Some of workflows I've blogged about already and have many more work flows to come.



Western Australia Data request for Infraworks

Creating an Infraworks model in Western Australia, data can be obtain from Landgate.

Example of such data available are:

• Cultural features - buildings, general facility (eg library), industrial (eg pipeline), mine, place (eg town), tower (eg communications tower)
• Ground surface data – elevation (eg contours, spot heights), fuzzy land (eg gully, dune), morphology (eg embankment, crater)
• Hydrography - coastal flat, framework (eg coastline, marine construction), fuzzy water (eg swamp, lagoon), inland flat, inland water
• Transport – bridge, tunnel, general transport (eg cycleway, wharf), rail segment, road, transport facility (eg airport, bus stop)

Below is an Example request form for obtaining data from landgate. Form can be found here 

Below is an example of data received from landgate after a request. There is plenty of data available to create a Infraworks model.

Below is an example of data from landgate in Infraworks

Creating DWF from Infraworks

Infraworks does not have a simple export to DWF. I came across this workflow because at the last minute some needed a model in a file format that was small and simple to use. A presentation with a 3d model  of the proposed building works vs 50 slides, I know which one I rather see. 

The short video below is a work flow that I've used to export Infraworks to DWF, with the help of 3ds MAX.

Key workflow points

• Exporting is done by sending the model to 3ds MAX by the send to 3ds function. (3ds need to be installed on the PC for the function to be available)
• 3ds MAX now has the selected region of the model and exporting dwf is as simple as export to dwf. 

Exporting Infraworks to Navisworks

Navisworks has never had a simple work flow of adding surface imagery without the use of 3ds Max. Infraworks add a easy. 

The short video below is a work flow that I've used to export Infraworks (before R4, in R4 the DDS texture mapping has been resolved) to Navisworks, with the help of a image convert like xnconvert

Key workflow points

• Exporting is done by FBX as there is no direct export from Infraworks to Navisworks.
• The FBX file when appended to Navisworks create a folder with all the associated images
• The associated images need to be converted from .DDS to .JPEG and remapped when appending the .nwc.

Navisworks need to have the follwing setting set for the images to be processed.

• Ensure that the Convert Textures is checked.

  
Another setting is to have the on which general Navisworks will prompt you to turn on. Is Presenter (OpenGL).

Coverage Area - Transparency

 Infraworks Coverage areas are great for defining work area / easement but some time you would like the area to be transparent. This is possible in Infraworks by changing the Alpha channel of the colour that defines your coverage area.

 The pink coverage area defines the area of work.

The colour setting of the Coverage area is set with an Alpha channel of 250, by changing the alpha channel the transparency of the coverage area changes.

 

 The Alpha channel is set to 100 in the image above to give a result in the image below of a transparent appearing coverage area.

Magic of PI and rotation of City furniture

Infraworks can take a 2d block in CAD software and create a 3d model with the easy of converting the block into to a GIS data set. 
The workflow for Infraworks City Furniture that is from a SDF with a value the represents it orientation in space. Mapexported angle are convert from Degrees to radian during the export process.  Infraworks does not have the following expression Functions:

• PI (3.141592653589793)

or

• RAD2DEG

Therefore to convert radian to degree is a bit of rough approach.

PI as a fraction is 245850922/78256779= 3.141592653589793
Radians to Degrees is "Segment Orientation" x (180 / PI)

A survey file with multiple blocks that represent each feature on a site. I want those site features in my Infraworks model. You can do a simple mapexport from Civil 3d or Map 3d and create a SDF file with each block classified by either layer name or block name. This simple process is great for feature elements that don't had a rotation. If survey file has not got the rotation that represents its true orientation a manual process will need to be done in Civil 3d or Map 3d. Below is a survey block of a traffic light with a rotation that represents it orientation.

Mapexport with the rotation of the block exported. The exported values for rotation end up in radians.

 Example of the traffic lights imported into Infraworks as City furniture with the Z rotation not yet assigned. Notice the traffic lights not oriented correctly.

PI or RAD2DEG are not recognised as expression values therefore to convert radian to degree is a bit of rough approach.

PI as a fraction is 245850922/78256779= 3.141592653589793
Radians to Degrees is "Segment Orientation" x (180 / PI)

In in the expression editor this would looks like

 ROTATION  *  (180 / (245850922/78256779))

Example of the traffic lights imported into Infraworks as City furniture with the Z rotation assigned. the traffic lights are now orientated correctly