Search Our Content Library

Workflow Processes:

• Exchange Data with InfraWorks

  This Process steps through the tasks of exchanging model data between InfraWorks Model and Civil 3D. InfraWorks Models can be opened directly in Civil 3D (SQLITE file) or by using an IMX file. IMX Files can be exported from InfraWorks, then opened in the same fashion as a SQLITE InfraWorks Model.
  To open and InfraWorks model directly you will need to have both InfraWorks and Civil 3D installed on your workstation. You will need to know the location of the locally cached SQLITE file to open it. IMX files do not require that InfraWorks is installed your system.

  NOTES:
  You must have a matching year version of Autodesk Civil 3D installed locally in order to import Autodesk Civil 3D DWG drawing files into InfraWorks. For example, users with InfraWorks 2020 must have Autodesk Civil 3D 2020 installed to enable data exchange between the two applications. See About Exchanging Data Between Autodesk Civil 3D and InfraWorks

  REFERENCES:
  To learn more about this process view the video:
  Import InfraWorks Model into Civil 3D
  Import Civil 3D Drawing into InfraWorks

• Execute Dynamo Script in Civil 3D

  Dynamo scripts can be executed in Dynamo or by using the Dynamo Player. The recommended and most intuitive option to execute Dynamo scripts is to use the Dynamo Player. The Dynamo Player is suited for consumers who are not familiar with navigating and executing Dynamo graphs. Using the Dynamo Player, users can use node inputs in to guide them through options and presets for execution of the script.
  REFERENCES:
  To learn how to assign Inputs to Dynamo nodes see:
  Define Inputs for Dynamo Player
  Reorder Inputs in Dynamo Player

• Import Point Cloud from Recap

  To display Point Clouds in Civil 3D they must be converted to readable point cloud files. Autodesk ReCap converts raw scan data to scan files (RCS files), and project files (RCP files) that reference multiple RCS files. Both these formats can be attached to an AutoCAD drawing.

  NOTES:
  Autodesk ReCap and ReCap Pro are installed separately from the Autodesk website.

  REFERENCES:
  To learn how to process a Point Cloud in Recap enroll into the following training:
  Introduction to ReCap

• Exchange Data with Revit

  This Process steps through the tasks to create a Shared Reference Point between Civil 3D and Revit. Using a Shared Reference Point you can import, export, link, and reference data between the 2 platforms using a “real world” coordinate system. Leveraging the coordinate systems in Civil 3D you can export a Shared Coordinate System XML File that can be imported into Revit to created a Shared Coordinate System. Once the Shared Coordinate System has been made active in the Revit model you can more easily exchange data with to/from Civil 3D.

• Import Civil 3D Model to Navisworks

  Autodesk AutoCAD and Autodesk Civil 3D drawing files can be imported directly into Navisworks and used for review and analysis of 3D solids, Pipe Networks, and Pressure Networks. A common task that you can perform in Navisworks is a Clash Detection, where you can identify interferences between Pipe and Pressure networks. Navisworks can also be used to render a drawing file and create realistic looking models for presentations.

  This process will outline the quick steps that you can follow to export Pipe Networks, Pressure Networks, and Corridor Solids. These Civil 3D object can be exported in a single drawing file, however, we recommend parsing the data into separate files that you can better manage in Navisworks. This can be easily accomplished through good layer management.

• Import from ORD to Civil 3D

  Exchanging data between OpenRoads Designer and Civil 3D is not an automatic process and often results is data loss. Understanding the limitations in the conversion between DGN to DWG will help you recognize and repair missing data. Intelligent features, like those created in OpenRoads Designer and Civil 3D are not supported in the file conversion. For these objects you will need to use LandXML as a common exchange format to copy data between platforms, where applicable. For many advanced intelligent features, like corridors, there is no conversion or exchange format available to share the data between the platforms. In these cases the design features will need to be recreated in the other platform if needed.

  An approach that you can take to get ORD data into Civil 3D is to start with the intelligent features. Export these features from OpenRoads Designer, then import them into a Civil 3D drawing. Verify the data that was imported, and add any data that was not carry over via the LandXML file (i.e. superelevation data). To get additional geometry from the Microstation Design file into your Civil 3D drawing, you can externally reference the design file and copy nested objects as needed into your Civil 3D drawing. To get all of the CAD geometry into the Civil 3D drawing you can import the DGN.

  NOTES:
  The DGN to DWG conversion is not perfect and will require manual corrections.. It is recommended that you complete your project work in either the DGN or DWG, and avoid going back and forth between the platforms.

  REFERENCES:
  About Importing Microstation DGN Files
  DGN Import Conversion Table
  Commands for Importing and Exporting Microstation DGN Files

• Export from Civil 3D to ORD

  Exchanging data between Civil 3D and OpenRoads Designer not an automatic process and often results is data loss. Understanding the limitations in the conversion between DWG to DGN will help you recognize and repair missing data. Intelligent objects in Civil 3D are not supported in the DGN file conversion. For these objects you will need to use LandXML as a common exchange format to copy data between platforms, where applicable. For many advanced intelligent objects, like corridors, there is no conversion or exchange format available to share the data between the platforms. In these cases the design features will need to be recreated in the other platform if needed.

  An approach that you can take to export Civil 3D that you want to replicate in ORD is to export all Civil 3D objects to LandXML files. Export the Civil 3D drawing to a native AutoCAD drawing to explode Civil 3D objects and ready the drawing for opening in ORD.

  NOTES:
  The DGN to DWG conversion is not perfect and will require manual corrections.. It is recommended that you complete your project work in either the DGN or DWG, and avoid going back and forth between the platforms.

  REFERENCES:
  About Exporting Microstation DGN Files
  DGN Export Conversion Table
  Commands for Importing and Exporting Microstation DGN Files

• Migrate Civil 3D Project to BIM 360

  This Process steps through the tasks to migrate a Civil 3D project from a local folder location into BIM 360. It is recommended that you create new projects in BIM 360, but if you would like to move your existing projects from a local server to BIM 360, it is recommended to move the whole project by dragging the top folder and dropping it into the destination BIM 360 folder on the connected drive using Windows Explorer. By using this method, most of the file references in the project can be copied to the same folder in BIM 360 and the path can be maintained.
  Moving a Civil 3D project into BIM 360 involves more than just moving/importing the project files into cloud storage. There is file maintenance that is needed to keep drawing files lean and to eliminate corruption that builds up over time. These best practices that should already be implemented in your workflows, but are especially important for collaboration.
  External References are essential to Civil 3D projects and are commonly used in all design drawings. If you want to move these drawings into BIM 360, you need to resolve all of the references so they are located in relative paths, and use the XREF type of Overlay. When the drawing files are moved to cloud storage absolute paths will no longer be valid for team members outside of your organization. And Overlays address challenges that can arise with nested references. All broken and/or unresolved links should also be solved prior to migrating projects to BIM 360, or more effort is needed to correct these when the project lives in BIM 360.
  When you have finished with the file maintenance of your Civil 3D project, you can remove any redundant files from the project folders. This includes *.bak and *.recover files that my reside in the project folders. These files only create excess baggage for the BIM 360 project. It is easier to remove these files before copying the Civil 3D project to BIM 360.

  Once you have all of the Civil 3D project files ready for migration, the BIM 360 project needs to be setup. This will require Account Admin and Project Admin permissions in BIM 360. Using the Account Admin module in BIM 360, a new project will need to be created. A Project Admin will then need to activate the services for the project, then create the project folders. The Project Admin will need to align the project folders in BIM 360 to the local project folders, then copy all of the project files into BIM 360. When all project files have been uploaded into BIM 360 you’ll need to inspect the files and cleanup any Related Data folders that were created.

  NOTES:
  The maximum number of characters that can be used for folder and file name path in BIM 360 are as follows:
  Folder Character Limit: 244
  Folder and File Character Limit: 260

  For more information about BIM 360 Collaboration see Civil 3D online help:
  Best Practices for Working with Autodesk Collaboration for Civil 3D
  Tips for Working with Autodesk Collaboration for Civil 3D

• Migrate Civil 3D Project to Unified Platform

  This Process steps through the tasks to migrate a Civil 3D project from a local folder location into the Unified Platform. The Common Data Environment (CDE) for the Unified Platform is Autodesk Docs, which is equivalent of BIM 360 Docs. It is recommended that new projects get created in the UP, but if you need to migrate an existing project from a local folder/server to a Unified Project, you should move the whole project by dragging the top folder and dropping it into the destination Autodesk Docs folder using Windows Explorer. By using this method you will presumably move all drawing references and preserve relative path file links.
  Moving a Civil 3D project into Autodesk Docs involves more than just moving/importing the project files into cloud storage. There is file maintenance that is needed to keep drawing files lean and to eliminate corruption that builds up over time. These best practices should already be implemented in your workflows, but are especially important for collaboration.
  External References are essential to Civil 3D projects and are commonly used in all design drawings. If you want to move these drawings to the Unified platform, you’ll need to ensure all drawing references are set to relative paths and are attached as Overlays. When the drawing files are moved to cloud storage absolute paths will no longer be valid for team members outside of your organization. Overlay XREFs will help to address challenges that can arise with nested references. All broken and/or unresolved links should also be solved prior to migrating projects to the Unified platform, or more effort is needed to correct these when the project lives in the Unified platform.
  When you have finished with the file maintenance of your Civil 3D project, you can remove any redundant files from the project folders. This includes *.bak and *.recover files that my reside in the project folders. These files only create excess baggage for the Unified project. It is easier to remove these files before copying the Civil 3D project to the Unified Platform.

  Once you have all of the Civil 3D project files ready for migration, the Unified project needs to be setup. This will require Account Admin and Project Admin permissions in the Unified platform. Using the Account Admin tools in the Unified Platform, a new project will need to be created. A Project Admin will then need to activate the cloud services, invite members to the project, and create the project folders. The Project Admin will need to align the project folders in the UP to the local project folders, then move all the project files. When all project files have been uploaded into the Unified platform you’ll need to inspect the files and cleanup any Related Data folders that were created.

  NOTES:
  The maximum number of characters that can be used for folder and file name path in Autodesk Construction Cloud are as follows:
  Folder Character Limit: 244
  Folder and File Character Limit: 260

  For more information about Civil 3D Cloud Collaboration see Civil 3D online help:
  Best Practices for Working with Autodesk Collaboration for Civil 3D
  Tips for Working with Autodesk Collaboration for Civil 3D