Good day ​@iii4625!
 

While I wasn’t able to find explicit support for IfcOpeningElement in the 2025.0 documentation, I’m happy to say that this feature (element) type will be supported in the FME 2025.1 version.
 

The 2025.0 beta version is already available on the downloads page, and the official FME 2025.1 version is set to be released soon, sometime in July. We don’t recommend using a beta version in production, however you can test your workflows with the feature type support there!
 

I’m sorry if there was any misunderstanding or miscommunication on supported features.

Hope this information helps! 🙂 Let me know if you have any issues navigating to the beta builds or if you have any other lingering questions.

(internal note: FMEENGINE-86672)

Hi ​@desiree_at_safe,

Thank you for your prompt and helpful response regarding IfcOpeningElement support in FME 2025.1. 

Following up on my testing, I've noticed another issue with the IFC_API reader. It also seems to be unable to read features of the types IfcRoad and IfcRoadPart.

Could you confirm whether support for these element types is planned for FME 2025.1 or later versions?  Additionally, are there any other known issues or missing features compared to the IFC reader?  

Thank you again for your assistance.

Hello ​@iii4625,

FME 2025.1 should be able to read IfcRoad and IfcRoadPart features (elements). However, if you'd be willing to share a sample of the IFC data you're testing, we would be really appreciative of that.

And while I haven't found known issues or missing features in the new IFC_API reader compared to the original IFC reader, the new version will have more extended functionality and will generally be a more refined reader.

Thank you kindly for your detailed testing! This kind of feedback is really valuable for improving the product! 😊

Hope this answers those questions! Let me know if you have any other questions or concerns

I tested this sample

http://www.bim-times.com/ifc/IFC4_3/buildingsmart/UT_SpatialStructure_4.html

IFC_API reader result:

IFC reader(deprecated) result:

Hi ​@iii4625,

  Thank you for the example and sharing those screenshots!

Regarding your observation about the difference between the old and new writers: IfcFacilityPart is defined as an abstract entity in the IFC schema and cannot be instantiated directly. Think of it as an umbrella category designed to group more specific types. Because of this, FME reads it as the generic type IfcBuildingElementProxy, which is what you're seeing in the first image.

However, there is a workaround. You can modify the IFC file to replace IfcFacilityPart with a more specific entity, such as IfcRoadPart. I’ve attached a sample workspace (using the data you provided) that demonstrates how this can be done entirely within FME, using the 2025.1 Beta build 25595.

In the workspace:

1. I saved the IFC file as a text file then read it using the Text File Reader.

2. Used an AttributeManager to replace IfcBuildingElementProxy with fcRailwayPart and IfcRoadPart.

3. Wrote out a new IFC file.

4. Then read that new file back in to confirm that RailwayPart and RoadPart appear as distinct feature types.

Let me know if this helps!