IFC 4 issue with Door type

[daviddelven]

Hello,

IfcDoorStyle should be deprecated detract from IfcDoorType.

(http://www.buildingsmart-tech.org/ifc/IFC4/final/html/schema/ifcarchitecturedomain/lexical/ifcdoorst...)

Am I do something wrong with IFC2x4 Schema management in ArchiCAD 21 ?

Thanks mates.

[felcunha]

Hello David,
Do you mean IFC4, and what is your precise need ?
(if you prefer you can formulate your question also in Spanish, maybe I'll understand it better).

[Laszlo Nagy]

I will bring this to the attention of the IFC team at GS HQ.

[daviddelven]

Thank you, Laszlo!

And Felipe Ribeiro Cunha, indeed, I mean IFC4 (or a.k.a. IFC2x4) schema release. English is already fine, here. Let the Spanish away in this forum 😉

[Laszlo Nagy]

Hi David,

I have received info from GS HQ. They said that information on the User Interface is coming from IFC2x3. For technical reasons they cannot continually switch UI elements based on the version of IFC selected, I am told.
However, when the actual IFC4 Export/Import occurs, it correctly works with IfcDoorType, and not with IfcDoorStyle as the IFC2x3-based UI suggests.

[daviddelven]

Thank you, Laszlo!

Good to know about it. We hope there's some alignment update with IFC releases in UI, from time to time, to avoid some misunderstandings.

I will publish your answer on my professional network.

😉

[Anonymous]

Hello

However, when the actual IFC4 Export/Import occurs, it correctly works with IfcDoorType, and not with IfcDoorStyle as the IFC2.3-based UI suggests.

That may work on IfcDoorType. What about IfcBuildingElementProxyType? PROVISIONFORVOID is possible in IFC 4. However, this cannot be selected in the type assignment of the IFC translator.


Thanks

Caspar

[Laszlo Nagy]

Caspar wrote:
Hello

However, when the actual IFC4 Export/Import occurs, it correctly works with IfcDoorType, and not with IfcDoorStyle as the IFC2.3-based UI suggests.

That may work on IfcDoorType. What about IfcBuildingElementProxyType? PROVISIONFORVOID is possible in IFC 4. However, this cannot be selected in the type assignment of the IFC translator.
Thanks
Caspar

I got the following info from the developers:
At the moment IFC4 can only be supported in "compatibility" mode, since IFC4 itself is still under certification.
However, there is a question for you:
Why do you need support of PROVISIONFORVOID for IFC4 export. This is an entity type that usually MEP programs generate (these Voids, I mean), and they are imported into ARCHICAD. So it is understandable in case of import, but why do you need it in case of export from ARCHICAD?

[stefan]

I was trying to export an IFC4 file with this type for the indication of openings to be coordinated. It is a recommended practise in the Dutch USO (Uniform Openings/Voids Specification).

As the internal scheme uses Ifc2x3 no IFC4 classes or types can be selected.