Customize the IFC hierarchy generated by IFC 4.3 Extension for Civil 3D

[p.germanier]

Revit hierarchy - Used in BIM projects : 

> IfcProject
>> IfcSite
>>> IfcBuilding
>>>>IfcBuildingStorey

... objects ...

Civil hierarchy - Generated with IFC 4.3 Extension for Civil 3D :

> IfcProject

>> IfcSite

... objects ...

Allow IfcBuilding/IfcRoad/IfcRailway/IfcBridge/IfcTunnel and IfcBuildingStorey/IfcCivilStorey to be added in configuration of exportation.

Ifc_Hierarchy_with_C3D_IfcInfraExport.png

Ifc_Hierarchy_with_Revit_export.png

Ifc_Spatial_Structure.png

[nigel_peters]

Thanks for your idea, some of it is already implement, the spatial in a IFC file depends of the workflow and exchange requirements. 

The exported creates this general form of Spatial Structure

 >IFCProject

>>IFCAlignments

>>IFCSite   for all siteless entities in C3D Prospector

[>>>IFCAnySpatialStructuralElement]     Optional mapping each unique foldername in the prospector

[>>>>IFCGeographicElements]                   For surfaces in matching foldername 

[>>>>IFCBridgeElements]                            For bridges in matching foldername

[>>>>  etc}

>>>IFCGeographicElements                        For surfaces not in a mapped foldername

>>>IFCBridgeElements

>>>Etc

>>IFCSite   for each Site in C3D Folder

We support user mappable spatial structure elements for Bridges, Pipe Networks, Sites, Cogo Point Groups, Corridors, Corridor Baselines, Corridor Base Line Regions, Assemblies and Sub Assemblies.

The item that is missing looks like the ability to define the IFC spatial structure type and name for the Site-Less objects in the Civil 3D this is an oversight and I will add it to the roadmap.

[f_furger]

We are facing the same problem.

If there are elements (independent of an axis) in a model, they must be assigned to an axis (and therefore also to a side) via an assignment.

The problem is encountered in all areas of the infrastructure:

• If you want to assign exportet corridor solids to the axis "back"
• If you want to assign individually created structures to a pipe network (and its axis and side)
• If you create other elements (custom, such as a street lamp), these should also be assigned to an axis and side

The issue was discussed with Autodesk support and there is a real need for action. We had many requests from various customers regarding this hierarchy problem.

Thanks very much and regards from Switzerland! 

[rosmarie.ruettimann]

Is urgently needed. Would be a nice Christmas present 😉

[nigel_peters]

Rosmarie,

We are looking extending the spatial structure support for Civil3D Prospector folders to treat AutoCAD Layer Groups in the same way. We have just started the work but this would allow you to create a layer group for all the elements you want with in a single structure. 

[osamah.naji]

Hello everyone
I've read all of your comments
I would like to draw your attention to the fact that the hierarchy of the IFC file from the Civil 3D program is quite similar to the files exported from the Revit program.
However, in order to obtain the same hierarchy, the components in the Civil 3D file must be externally sourced(XREF), and only then will all paragraphs of the hierarchy be activated.
I would like to add that the hierarchy in Civil 3D is as follows if it does not contain an external source
> IfcProject
>>>>> IfcBuilding
... objects ...
Where IfcSite and IfcBuildingStorey are canceled
Here I will disagree with Mr. P.germanier about the IfcSite
Here I draw your attention to the fact that (IfcSite) and (IfcBuildingStorey) can be controlled through the export window according to picture 2
Through the export window I can easily control the name of the IfcBuildingStorey, but the issue remains with the IfcSite, which is often (Freiflächen - Außenanlagen), which unfortunately I have to change via the editor program.

 

 

The biggest issue I have is that it is not possible to assign an entity or type to 3D objects drawn with standard CAD commands such as extrusion and others, unless they are 3D Standard objects within the same program instance, except through specialized external programs, which is very frustrating considering that the IFC entities for version 4.3 do not cover everything, especially in the field of trains and railways.

When working on a BIM project, most executive engineers may find that they have a problem with the architect. Unfortunately, most architects try to implement BIM projects according to personal opinion without fully understanding the BIM mechanism.
Most architects focus on the hierarchical structure of the data within the IFC files to fit the programs they use to explore the IFC files, for example IFC file browsers.
Unfortunately, this hierarchical structure varies depending on the program that examines the IFC file, as each program shows a different hierarchical arrangement of data for the same IFC file.
It should be noted that this hierarchy is not important in the BIM process, as the BIM process culminates when the server is properly linked to the IFC file data (attributes).
The linking process can only be completed when new, independent lists are created in the IFC files.

This is where the biggest problem arises, as most architects do not understand the relationship between the server and the IFC files that contain this data. They tend to store the data within a fixed hierarchy or the so-called structure tree of the data in the IFC files, which makes it easier for them to investigate overlaps and collisions within the official 3D structure of IFC files and according to the programs used for these purposes.

[Eliane_VoserQ6N22]

Beim Export vom 3D-Profilkörper ins IFC 4.3 wird automatisch mit der IFC-Struktur erstellt, jedoch werden die Eigenschaften der Profilkörper nicht mitgeliefert.
Exportier man nun die 3D-Profilkörper in Volumenkörper um und erstellt den IFC-Export 4.3, dann wird die IFC-Struktur nicht richtig mitgeliefert, jedoch die Eigenschaften sind vorhanden.

Dieses Problem sollte unbedingt gelöst werden, sonst empfehle ich den Export von IFC 4.3 nicht weiter.