revit-ifc icon indicating copy to clipboard operation
revit-ifc copied to clipboard

PR: IfcBuilding attributes export from RVT 2025

Open MisunMartin opened this issue 1 year ago • 8 comments

Problem Description

I have discovered that export from RVT 2025 does not include these mapped attributes of IfcBuilding:

  • Long name
  • Description
  • Object Type

Using shared parameters, does not work at all at RVT 2025 using latest release of Plugin (25.2.0.5)

  • BuildingLongName
  • BuildingDescription
  • BuildingObjectType

In RVT2024 it works prefectly well!

In RVT2025 there is one extra parameter in Export Setup that is not in 2024. Is that possible that this is the case of incorrect export? image

Attached RVT24 + RVT25 files + IFCs of both in 2x3 and 4x3: RVT-IfcBuilding-Bug.zip

Revit Version

2024.0.x

IFC for Revit Addon Version

24.x.x

Windows Version

11 22H2

MisunMartin avatar Nov 08 '24 07:11 MisunMartin

I have the same issue! and no fix after all these months 😢

Lazarica-t avatar Mar 12 '25 19:03 Lazarica-t

Those parameters got renamed to: FacilityDescription FacilityLongName FacilityObjectType

But it is likely an oversight that the "old" parameters don't still work. We should support both, at least for a small amount of time, even if it is a small performance hit. I'll file an item to correct this, but in the meantime try the new names.

AngelVelezSosa avatar Mar 12 '25 19:03 AngelVelezSosa

@AngelVelezSosa they are working for me. I think these parameters should also be added in the shared parameters file.. I didn't see any Facility parameters in there

Lazarica-t avatar Mar 12 '25 20:03 Lazarica-t

Agreed on that also.

AngelVelezSosa avatar Mar 12 '25 23:03 AngelVelezSosa

This issue is also reported in Jira as "REVIT-237041" and is currently in the "Open" status.

ArtemHnatko avatar May 27 '25 12:05 ArtemHnatko

Ideally both names should be supported. I don't understand why this was changed. The entity is still IfcBuilding in the schema and they should remain aligned.

If there is any need to align with other schemas (I'm guessing COBie was a driver), then there should be support for mapping entity attributes and not just property sets. Then we won't be constrained to the built-in parameters in project information.

Otherwise, these should be added to the shared parameter file to create a consistent reference between parties.

Is there any progress on this item? @ArtemHnatko, is the Jira ticket still open?

BarrieSharp avatar Jul 14 '25 15:07 BarrieSharp

It was changed to be IFC4.3 friendly. The old ones shouldn't have been removed and will be re-added. That said, of course it does add time to export to look in a bunch of other places.

AngelVelezSosa avatar Jul 14 '25 16:07 AngelVelezSosa

It was changed to be IFC4.3 friendly. The old ones shouldn't have been removed and will be re-added. That said, of course it does add time to export to look in a bunch of other places.

Isn't it still IfcBuilding in IFC4.3? We always get told to use IFC 2x3 TC1. If it changed for IFC4.3, could it be schema version dependant, so it only checks for one or the other? Does checking both have a noticeable impact?

BarrieSharp avatar Jul 14 '25 16:07 BarrieSharp