Autodesk / revit-ifc

IFC for Revit and Navisworks (2019+)
474 stars 193 forks source link

INQ: Multiline text parameter in Revit not showing on IFC 4 exported from the Revit. #721

Open aslawone opened 9 months ago

aslawone commented 9 months ago

Inquiry description

I have a Multiline text parameter in Revit which I have filled in the values but the parameter nor the values are not showing on IFC (IFC 4) exported from the Revit. I have attached a picture showing the Revit and IFC (solibri). I hope someone could help. skjermbilde

Revit Version

2022.1.x

IFC for Revit Addon Version

24.x.x

Windows Version

10 22H2

AngelVelezSosa commented 8 months ago

What is the name of the parameter?

aslawone commented 8 months ago

What is the name of the parameter?

The name of the parameter is "AirFlowRateRange". Here is an attachment from Buildingsmart explaining the data: image

t-vasyi commented 8 months ago

Hi @aslawone , Try using next Revit parameters to export bounded property:

Pset_AirTerminalTypeCommon.AirFlowRateRange.SetPointValue
Pset_AirTerminalTypeCommon.AirFlowRateRange.UpperBoundValue
Pset_AirTerminalTypeCommon.AirFlowRateRange.LowerBoundValue

image

aslawone commented 8 months ago

@t-vasyi I have tried it too and it did not work: image

t-vasyi commented 8 months ago

@aslawone In 22.6.2 we had slightly different names for parameters. Could you try these (it works for me): image

Note that in 22.6.2 the 'AirFlowRateRange' parameter was obligatory and responsible for SetPointValue attribute

aslawone commented 8 months ago

@t-vasyi Thank you for your time. I am sorry that I could not understand how you did it. Could you elaborate? :) Do these 3 parameters you listed came under the parameter group Pset_AirTerminalTypeCommon in the IFC? I updated my exporter to 22.6.2 now and the parameters still not showing in the exported IFC.

AngelVelezSosa commented 8 months ago

You need to add "AirFlowRateRange", "AirFlowRateRange.UppoerBoundValue" and "AirFlowRateRange.LowerBoundValue" to Revit as the appropriate (not text) values. Then you can export AirFlowRateRange as part of Pset_AirTerminalTypeCommon and it will show up in IFC. If you can't get this to work, create a simple Revit file that shows your attempt and @t-vasyi can take a look and tell you what you are doing incorrectly.

aslawone commented 8 months ago

@AngelVelezSosa @t-vasyi Here is a video showing what I did under the IFC property name AirFlowRateRange and how is not showing on IFC.

https://github.com/Autodesk/revit-ifc/assets/36126076/d553bad1-6f85-4da5-a795-8615afb52f9f

t-vasyi commented 8 months ago

@aslawone The type of parameter you selected is 'Multiline Text' Could you try with the 'Air Flow' type? image

aslawone commented 8 months ago

@t-vasyi Here is the "Air Flow" Type

https://github.com/Autodesk/revit-ifc/assets/36126076/86ebb4f7-9f3c-4f56-9f75-2836f02500e2

t-vasyi commented 8 months ago

@aslawone In 22.6.2 we had slightly different names for parameters. Could you try these (it works for me): image

Note that in 22.6.2 the 'AirFlowRateRange' parameter was obligatory and responsible for SetPointValue attribute

Try removing 'Pset_AirTerminalTypeCommon.' from the parameters name If it doesn't work - it is unexpected

aslawone commented 8 months ago

@t-vasyi It did not work :(

t-vasyi commented 8 months ago

Can you share a simple .rvt file to investigate? (Ideally with the exported .ifc)

aslawone commented 8 months ago

@t-vasyi Here is a zip file for both IFC and RVT. Thank you

RVTIFC.zip

t-vasyi commented 8 months ago

Note that in 22.6.2 the 'AirFlowRateRange' parameter was obligatory and responsible for SetPointValue attribute

Renamed parameter 'AirFlowRateRange.SetPointValue' to 'AirFlowRateRange' RVTIFC(fixed).zip

aslawone commented 8 months ago

@t-vasyi Thank you very much for you time and help :) I am glad it has now worked! Please, is their anyway I can extend this to another property set called Pset_SoundGeneration with SoundCurve property name? The property data type is a Table. I am having a similar problem.

image

AngelVelezSosa commented 8 months ago

I believe we do also have magic code for tables, @t-vasyi can definitely help out what that.

t-vasyi commented 8 months ago

About IfcPropertyTableValue

  1. I attached the example of exporting Pset_AirTerminalTypeCommon.AirFlowrateVersusFlowControlElement table property. The parameter type must be 'Multiline Text'
  2. The property set 'PSet_SoundGeneration' cannot be exported in similar way because it isn't in the list of certified PSets for "IFC4RV". The list of certified entities can be found in IFCCertifiedEntitiesAndPSets.json

AirFlowrateVersusFlowControlElement.zip

aslawone commented 8 months ago

@t-vasyi Thank you very much :)