Hi
I wonder how to define this properties:
GUID, Locked, Description, Layer and Element ID
to be included in a separate pset in the IFC export?
Example from my IFC_Mapping_overrides.set:
"Length" : "IfcPositiveLengthMeasure" = StructuralQuantities/@Length# "ObjectID" : "IfcIdentifier" = ObjectProperties/@Element ID ObjectProperties should be = ________??
"BSAB-E" : "IfcLabel" = ObjectClassification/@BSAB "Comment" : "IfcLabel" = ObjectIdentity/@Notes# "TypeDescription" : "IfcLabel" = ObjectGeneral/@Description ObjectGeneral should be = ________??# "IfcGUID" : "IfcLabel" = ObjecProperites/@GUID ObjectProperties should be = ________?? "TypeID" : "IfcLabel" = ObjectIdentity/@Mark# "Locked" : "IfcBoolean" = ObjectExtended/@Locked ObjectExtended should be = ________?? "FireRating" : "IfcLabel" = ObjectFireResistance/@Rating
Cannot find this properties listed in the definition editor and when I look in the actual model there is listed as above (marked with yellow). Example:
Best regards
Anton
[AUTOMATED MESSAGE; if there is a link below, please follow that if you wish to respond to this Communities message.]
RE: BIP - IFC pset
The GUID is a dataGroup property generated by the application, we have recently enhanced IFC Export GUID stability so the GUIDs are consistent across versions when the same elements are re-exported.
Layer (DGN Level?), Element ID, [Element] Description and Locked are all DGN element properties generated by the application.
Did this answer your question?
Verify it as the answer or Reject it as the answer
View online
You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here. Flag this post as spam/abuse.
Hi Anton,
What does your DataGroup Mapping for these components look like?
Hi Steve and Marc. Anton is a colleague of mine and we still haven't sorted this out. Do you mean how we mapped for instance walls? How would that help us?
Regards,
Robert
Hi Robert,
This thread is a few years old so I had to go back an re-read it... I think I asked about mapping at the time because Anton's image showed a property set applied to walls, so I was curious whether any of those properties were being explicitly mapped during IFC Export.
That said, going back to the four items from the OP: Element ID, Level, Locked and Description. None of these are DataGroup properties but rather base MicroStation element properties so would not appear within the DataGroup System. I'm not aware of any way to "extract" their values to auto-populate elsewhere, so I'd imagine you've have to create a custom schema (*.xsd file) to define those four properties and manually populate their values where needed. However, I also don't know if/how they would translate over to IFC unless explicitly mapped, and assuming there is an equivalent in the IFC format.
Ok. Is there somewhere I can get any further information on how to do this? We have projects running now that require these properties in the IFC:s upon delivery.
(And just a correction from the original post, rather than element ID, I think we need the GUID).
Regarding the GUID, we are delivering this as mentioned above, just a quick test below, I'm looking at the other properties that you asked about now:
On the left the original user file exported and viewed in Solibri Model Viewer 9, on the right an export from a DGN containing a reference of a copy of the original file. The GUID is consistent:
If the same element was copied it would be anew element with a different GUID:
Marc