If I export with the sourgeforge IFC exporter
1. option checked "Export only schedules cointaining IFC, Pset or Common in the title"
2. calculated value parameter "opp" (=volume/thickness)
3. In the IFC export all the schedule parameters are exported "except" the parameter "opp".
Is it not possible to export a calculated value to IFC.
I want to select the element in the IFC viewer and then read out the value.
Regards,
Ramon van den Elsen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the attached file you see 2 examples,
One example in navisworks where you see on the "wall schedule IFC" tab that the parameter "opp" is not exported
One example in Revit wher you see the parameters, including the parameter "opp"
You are correct - the current IFC export does not support exporting calculated values. I believe there are some API limitations there - we need to take a look.
Regards,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Angel,
We are experiencing the same problem as Ramon.
We tried to export the calculated parameters to IFC the same way as Ramon.
Is it possible to export the calculated value to IFC if we create a shared parameter for ''opp'' to redirect the cell from the calculated value to the parameter so that it is connected to an element? and if this is possible, how can we do it?
Or do you see any other solution in the future that can solve the problem of calculated values not getting exported to IFC?
Thanks in advance,
Sincerely,
Jaco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think that's the case - if the calculated value is put into another shared parameter that isn't calculated, you can export it. One possibility perhaps would be via a script to set the shared parameter value. Other power users here may have better solutions!
Regards,
Angel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looks like it's possible to get the calculated value by iterating over each row in a schedule: https://apidocs.co/apps/revit/2019/d7f874df-30a8-cf03-f24c-c66f2be91a39.htm . Though I think thats a bit different than the current implementation that only looks at the schedule fields (headers) and figure out what parameters they represent.
What do you think Angel? Using schedules is a very user friendly way to create PSets and it ensures that the data in Revit always stays in sync with the IFC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is on our request list. Unfortunately, calculated fields in schedules work differently than other ones, so it isn't a trivial request. But we would like this to work at some point.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Autodesk,
If I export with the sourgeforge IFC exporter
1. option checked "Export only schedules cointaining IFC, Pset or Common in the title"
2. calculated value parameter "opp" (=volume/thickness)
3. In the IFC export all the schedule parameters are exported "except" the parameter "opp".
Is it not possible to export a calculated value to IFC.
I want to select the element in the IFC viewer and then read out the value.
Regards,
Ramon van den Elsen
In the attached file you see 2 examples,
One example in navisworks where you see on the "wall schedule IFC" tab that the parameter "opp" is not exported
One example in Revit wher you see the parameters, including the parameter "opp"
Hi Ramon,
You are correct - the current IFC export does not support exporting calculated values. I believe there are some API limitations there - we need to take a look.
Regards,
Angel
Hello Angel,
We are experiencing the same problem as Ramon.
We tried to export the calculated parameters to IFC the same way as Ramon.
Is it possible to export the calculated value to IFC if we create a shared parameter for ''opp'' to redirect the cell from the calculated value to the parameter so that it is connected to an element? and if this is possible, how can we do it?
Or do you see any other solution in the future that can solve the problem of calculated values not getting exported to IFC?
Thanks in advance,
Sincerely,
Jaco
Hi Jaco,
I think that's the case - if the calculated value is put into another shared parameter that isn't calculated, you can export it. One possibility perhaps would be via a script to set the shared parameter value. Other power users here may have better solutions!
Regards,
Angel
I have posted a similar request on github: https://github.com/Autodesk/revit-ifc/issues/60
Looks like it's possible to get the calculated value by iterating over each row in a schedule: https://apidocs.co/apps/revit/2019/d7f874df-30a8-cf03-f24c-c66f2be91a39.htm . Though I think thats a bit different than the current implementation that only looks at the schedule fields (headers) and figure out what parameters they represent.
Combined parameters on the other hand sould be more trivial to implement since there is a GetCombinedParameter method in the Revit API: https://apidocs.co/apps/revit/2019/fe772ceb-b239-4da3-e3c3-5fb4a42d1f88.htm
What do you think Angel? Using schedules is a very user friendly way to create PSets and it ensures that the data in Revit always stays in sync with the IFC.
This is on our request list. Unfortunately, calculated fields in schedules work differently than other ones, so it isn't a trivial request. But we would like this to work at some point.
Hello @angelvelezsosa
Are there any updates on this thread, or do we have to export calculated values as Revit Expressions?