Home / RevitMep / Multiplatform Interoperability: Working with 2D and 3D Data

Multiplatform Interoperability: Working with 2D and 3D Data

This chapter introduces you to the best practice techniques used in importing data into your
Revit database, either directly into the project file or via a loadable family. The chapter also covers which data to use and when in the project life cycle to use it. It is easy to select a button that performs the import but, more importantly, why are you doing it? For that matter, should you actually be doing it?
Revit works very well with file types other than native RVT project files. Many of the issues you will encounter are due to the differences between existing CAD technologies, which for the most part rely on elements—lines, arcs, and circles, while the newer BIM technologies are founded on object-based parametric databases. These two types of databases are very different,
so when you have to start working with other consultants who use other data types, you may experience issues such as the following:
Loss of Performance Typically, importing another file format into Revit is a bad idea. Yes, you can do it—but like eating too much candy, your file size will start to bloat and slow you down. Keep your project file lean, and minimize its intake of sweets whenever you can!
Difficulties Displaying and Printing Data Exactly the Same One of the most annoying problems are issues with fonts either not being installed or, in the case of legacy DWG data, not being fully supported and therefore never displaying in the same way as the original.
Data Loss Many issues can cause data loss in your final documentation. These can range from linked files being unloaded, to workset visibility being incorrectly set, to printer driver problems.
The other question we must ask is: Is 2D really2D? An AutoCAD 2D DWG file can show up in a 3D view. Do you want it to?
In this chapter, you will learn to do the following:
Decide which type of data you want to use on a project •u
Link data consistently and in the correct location •u
Prepare data prior to import

Leave a Reply

Your email address will not be published. Required fields are marked *