Dynamically link IFC

[noynpe]

When adding support for IFC 4.3, dear Autodesk, please aim a bit higher than you normally do with IFC implementation.

In a perfect world I would be able to link an IFC file to Civil 3D, much like I can in Revit. When linking I would like the option to generate civil elements from the IFC file, eg. TIN surface, alignments and feature lines. These civil elements should be tied to the IFCGUID so that updating the link will also update the civil elements.

Just imagine the possibilities for inter disciplinary collaboration this would open up, both within a single company but also between companys as many projects involve many stakeholders. 

This would allow a landscape architect to use a curbstone stake out line, coming from the road engineer in a different company, to produce their cut/fill adjustments to the terrain. And have it automatically update whenever the road engineer does minor adjusmtents. This is one small example, but the opportunities for more seamless workflows are endless.

I would think that civil elements from a linked IFC model would be generated as some sort of DREF within the drawing.

As many software platforms (and user routines) often disregards the need for preservation of the IFCGUID (eg. creating new elements with a Dynamo script), there would be a need for checking IFCGUIDS upon synchronization of the IFC, at least on elements that are used as targets or part of other civil elements in the drawing. For example a pop up window with all elments with missing/altered IFCGUID and the option to pick select replacements for them.

Good implementation of the IFC file standard is crucial, especially to the Scandinavian market.

[nigel_peters]

We released the IFC 4x3 Extension for Civil 3D 2022 earlier this month (available via Autodesk Desktop App or from manage.autodesk.com select product updates and search for “IFC”).

The extension supports importing of IFC 4, 4x1, 4x2, 4x3 files and exporting of IFC 4, 4x3 RC 4 and 4x3 schema versions in both text and zip formats.

The exporter supports AutoCAD Ploylines, DBPoints, Block references, Solids and Civil 3D Cogo Points & Groups, Feature Lines, Alignments, Surfaces, Volume Surfaces, Bridge Parts, Pressure & Gravity Pipe Networks, Corridors (with or without corridor solids). The exporter handles exporting of the following meta data with each entity; UDP, Generic Parameters, Part Data and Property Set data. There is support for mapping (with entity level overrides) of both meta data. These mapping rules are user customizable via configuration files.

The Importer imports all data into the current drawing, supports importing all the AutoCAD objects and creates Civil 3D objects for Cogo Points & Groups, Feature Lines, Surfaces, Volume Surfaces and Sites. The other complex Civil Objects (Pipes, Bridges and Corridors etc) that can be exported are imported as AutoCAD Solids (IFC format treats these as solved geometry). All meta data including the objects IFC GUIID are imported as property set data.

Both the importer and exporter handle management and retention of the IFC Guids and can be run used via AcCoreConsole as a batch process.

Civil does not really have the Revit concept of Linking but you can acheive something simular by importing a IFC file into a empty drawing and xref (or dref depending on workflow) the file to your master file.