Hi All
We have recently tested the IFC Export functionality in ORD 2018 Release 3. We have an expert in IFC who has spotted the following error, highlighted below:
"
Just to note a couple of aspects of the sample openroads IFC file that isn't compliant with the schema.
First, the project line has a reference to ($) which isn't valid.
#2=IFCPROJECT('1ltWbrLqb6OgXtpp_gmwDL',#3,'C1485-Corridor-N7-NB-Bridge','',$,'',$,($),#9);
The item that should be referenced is in the file, and I manually changed this line to:
#2=IFCPROJECT('1ltWbrLqb6OgXtpp_gmwDL',#3,'C1485-Corridor-N7-NB-Bridge','',$,'',$,(#22),#9);
It's nice that openRoads is already using new features of IFC4. The mapconversion line also needs an adjustment.
#30=IFCMAPCONVERSION($,#31,0.0,0.0,0.0,$,$,$);
The first attribute SourceCRS is not optional. This should also reference the IfcGeometricRepresentationContext
#30=IFCMAPCONVERSION(#22,#31,0.0,0.0,0.0,$,$,$);
This is causing incompatibilities with other packages. Is there an expert on IFC who we could discuss these kinds of issues with?
Did this ever get logged as a defect? I'm having problems importing ORD IFCs into other packages that are IFC 4 capable...
Regards,
Mark
OpenRoads Designer 2023 | Microstation 2023.1 | ProjectWise 2023
Just to check - are these other packages IFC v4.2 compatible?
Hi Mark,
That's the problem - the vast majority of them aren't so while I can appreciate the value of using the latest IFC schema, it is causing us issues using it for its purpose as an Open BIM format for exchange. The ability for us to dumb it down to IFC 2x3 is what we really need right now until the rest of the world catches up...
I would say that it is up to these other packages to update their support to IFC4.2.
In the meantime, of course, you could always use MicroStation CONNECT to view the IFC file.
This approach disables so many workflows that could be made with the use of IFC and slows down the BIM uptake in general... That's just mean :<