Autodesk
Parameter mapping for all Ifc entity attributes
In the current solution, each time we want to use Ifc entity attributes, as Name, LongName, Tag, Description and Classification, we have to point to parameters, with the an Ifc prefix.
This means that our implementation can't use OOTB parameters and map them in the exporter parameter sets. Double the amount of parameters, because we can't point Mark and Type Mark, to Name. Can't point Comments and Type Comments to Description. Confuse users that come in, and aren't used to delivering IFC, thinking that something is missing in our setup, change annotations and schedules to the OOTB parameters, or don't even fill them in - and then..
In the end, we have an more verbose and confusing parameter list than needed to, and it's harder to implement IFC centered workflows than needed.
I know this have been brought up several times - but not giving up :)
No need to give up - we definitely still want to have a better UI for mapping that would include attributes in addition to property sets. Just some higher priority things first.
Thank you - and I perfectly understand. A initial solution via user defined property sets towards IfcRoot etc., without UI, would be very helpful for a first pass.
Can this be reopened? It's 2 years later and still not fixed as far as I am aware.
Getting type names correct is critical and most Revit users stick in in a random field like Type Mark, Mark, Keynote, Comment, or some new invented one... none of these is what Revit chose to expose through the UI: which is simply the family type name.
Users are still confused, IFC exports from Revit are still low quality as a result.
