Revit 2023.1.1 classifications settings are not exported propperly

[EtiennevdBa]

Dear Revit/ifc team,

when i create a IFC file in Revit 2023.0.2 with the default exporter the classifications settings are exported propperly when i export a IFC file in Revit 2023.0.2 with the opensource exporter 23.1.1.0 the classifications setting are not exported correctly

These issues are also in Revit 2023.1.1 with and without the opensource exporter. are there more people with these issues?

Kind regards,

Étienne

[AngelVelezSosa]

I believe this is a known issue with Solibri that has already been fixed.

[EtiennevdBa]

I believe this is a known issue with Solibri that has already been fixed.

Dear AngelVelezSosa,

thanks for your response. It's not Solibri related, when i open the IFC file in BIMvision i'm having the same issue. Here is the same project in BIMvision with the classifications settings propperly exported:

Here it is not propperly exported:

Also tried the new 23.2.3.0 exporterd, same result:

Here are my classification settings within the IFC exporter: what i don't understand is even with a filled in 'documentation location' there is other information in the IFC file.

If there is more information needed, please let me know.

[AngelVelezSosa]

I'll ask @WawanSolihin to check, but I think this might still be a viewer issue (#546, I think?)

[benjaminchvn]

Hi,

I am facing the same issue with classification, with Revit 2023.1 and IFC exporter 23.2.1.0. Here are my classification settings : I tested with a simple wall with "ClassificationCode" shared type parameter filled this way :

Here is the incorrect result with BIM Vision : This is the same in Solibri :

It seems, as @EtiennevdBa noticed that IfcClassificationReference.Name and IfcClassificationReference.Location are not set up properly during export

[benjaminchvn]

Here is also the comparison of correct (with Revit 20) and incorrect export (with Revit 2023.1 and IFC exporter 23.2.1.0) with BIMCollab :

[louistrue]

@benjaminchvn @EtiennevdBa Have a look here: https://github.com/Autodesk/revit-ifc/issues/546 It's a mix of Revit doing something unusual and nearly all viewers having a bug where they dont read IfcClassification.Name but IfcRelAssociatesClassification.Name instead, which isn't the correct place to read the Classification Name from according to the IFC schema...

[WawanSolihin]

There seems to be a real regression bug also in Revit IFC exporter:

1. The classification reference name is not set correctly (It takes the classification name instead. "MyClassif" in the above example)
2. IfcClassificationReference.Location picks up the wrong value (from the default or previous value of Uniformat.
3. In IFC4 export it may not export the classification

I will log a defect on this issue.

[benjaminchvn]

Thanks ! Hope this can be fixed. I was also wondering if there is any way to override the Defaut Classification (Uniformat) associated with the use of built-in Revit assembly code (Name, Source and Edition) : So far the only way I have found is to manually edit the IFC in notepad....

[EtiennevdBa]

@benjaminchvn well, editing the IFC in notepad is quite fun. I hope that there will be a fix soon :)

[JOuellette-Autodesk]

https://jira.autodesk.com/browse/REVIT-200324

[WawanSolihin]

Thanks ! Hope this can be fixed. I was also wondering if there is any way to override the Defaut Classification (Uniformat) associated with the use of built-in Revit assembly code (Name, Source and Edition) : So far the only way I have found is to manually edit the IFC in notepad....

What exactly are you trying to override this?

[benjaminchvn]

Hi, in this case I am using Assembly code in Revit to fill in Uniformat classification code, but version II 2015, so source and edition are not correct.

[WawanSolihin]

Hmm, currently the Uniformat classification information is hardcoded based on the version Revit has internally and therefore cannot be overridden.

[xpt5]

If it sheds some light over the issue, the problem also can be found with Revit 2022.1.1 and the following Ifc Exporter versions:

• v 22.6.0.0
• v 22.5.1.0

BUT in the v..22.5.0.0 there isn't any issue with the Uniformat Classification export.

[canpolatbaris]

Hi, I have the same issue in Revit 2022 (IFC Exporter 22.6.0.0) and Revit 2023 (IFC Exporter 23.2.3.0). I don't think this is a viewer issue.

Also, I exported one of the old projects, which had the right classification assignment before, and could not export classification in the right way. I tried previous versions one by one, and version IFC.for.Revit.2023.1.0.0.msi exports classification for the same model properly.

[WawanSolihin]

It has been fixed in the development version, but it did not make it for 22.6. I can bring it forward to 2022 and if you do not mind unsigned build, it can be done soon.

[WawanSolihin]

I bring forward the fix for the classification issue. There are pre-release (not signed) versions for Revit 2022 and Revit 2023 that you may want to test it out. In my testing they seem to work well. For Revit 2022: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v22.6.1.0 For Revit 2023: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v23.2.4.0

[EtiennevdBa]

I bring forward the fix for the classification issue. There are pre-release (not signed) versions for Revit 2022 and Revit 2023 that you may want to test it out. In my testing they seem to work well. For Revit 2022: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v22.6.1.0 For Revit 2023: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v23.2.4.0

@WawanSolihin Thanks for the pre-release. i've tested them to and its better, but the Name is missing

This is how it was before

[WawanSolihin]

It works well in my test. I attached the sample file here. Assembly.0.2 (as identified by Solibri) shows the result as expected. (The Solibri version I use: 9.12)

Classification-test--2022.zip

[benjaminchvn]

I bring forward the fix for the classification issue. There are pre-release (not signed) versions for Revit 2022 and Revit 2023 that you may want to test it out. In my testing they seem to work well. For Revit 2022: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v22.6.1.0 For Revit 2023: https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v23.2.4.0

Hi thank you for this pre-release. I have been testing out on both Uniformat (using Assembly code in Revit) and custom classification using a shared parameter, it seems to work fine.

[EtiennevdBa]

It works well in my test. I attached the sample file here. Assembly.0.2 (as identified by Solibri) shows the result as expected. (The Solibri version I use: 9.12)

Classification-test--2022.zip

@WawanSolihin, thanks for your reply, i'm using solibri 9.13.1 will check tonight with a different Solibri version. keep you posted.

[canpolatbaris]

It has been fixed in the development version, but it did not make it for 22.6. I can bring it forward to 2022 and if you do not mind unsigned build, it can be done soon.

thank you, I will start my tests today...

[koenmeinema]

Here it still doesn't work well.

Following input in Revit 2022:

Gives me this output in BIMcollab Zoom 6.4:

Where it should be like this: "property name" | "assembly code", "assembly description"

For instance, in this case: Uniformat Classification | 22.20, binnenwanden - constructief, algemeen (verzamelniveau)

[AngelVelezSosa]

What does it look like in other systems? I want to distinguish between "problem in Revit" and "problem in BIMcollab".

[koenmeinema]

This is the output in Navisworks. The value in the tab name should again be "Uniformat Classification".

[EtiennevdBa]

It works well in my test. I attached the sample file here. Assembly.0.2 (as identified by Solibri) shows the result as expected. (The Solibri version I use: 9.12)

Classification-test--2022.zip

@WawanSolihin thanks for te sample, i don't know what i'm doing wrong but the assembly description is still missing in my IFC. I've setup a sample Revit/IFC file with the export settings + the assembly code file i'm using. Made in Revit 2023.1.1 and the IFC exporter 23.2.4.0 pre-release. both in Solibri 9.13.1.25 and BIMvision 2.27.0 (64) i'm having these issues. sample Assembly codes_classification.zip

when i open your sample file in Solibri 9.13.1.25 it looks a bit different then you have but that is the result i'm looking for

[kowibo]

I'm sorry to say, but for me the Classification problem still exists with the newest prereleases IFC_v22.6.1.0 and IFC_v23.2.4.0. It should be as it was exported with IFC_v22.5.0.0 (latest version it worked well in). See image below: Classification (Property) is 'Uniformat Classification' for each element in the IFC. That's fine. But all versions after v22.5.0.0 (both in R22 and R23) have an export like these (exported with v23.2.4.0): The problem is that de Property Field that determines the Classification Format acts like a Value (it changes each time a IFC element is selected: part of the Value is added to this field). In this way we have no Classification at all.

[AngelVelezSosa]

I'm sorry, I'm missing the difference - what line is the problem?

[koenmeinema]

@AngelVelezSosa it's the same problem as i tried to describe earlier. It's the name of the property which should be "Uniformat Classification" and not "vloeren; constructief, vrijdagende vloeren:23:21"

[kowibo]

First Column 'Property', last Row.

Previous versions of de IFC Exporter have here a fixed Parameter Name: "Uniformat Classification". This has nothing tot do with the content of the Value of this Parameter (second Column 'Waarde").

Newer versions of the IFC Exporter seem to add a part of the Value in this Parameter: "vloeren; constructief, vrijdragend vloeren 23.21". That's strange. How can you classify when de Name of the Parameter changes each time the Value of that Parameter changes?

I think the new exporters must be compared with the previous v.22.5.0.0 at this point.