Note that I'm discussing the GUID used in IFC, not MicroStation's element IDs.
Jon,
Thank you for explaining.
Jon Summers said:The DGN file is exported to a new IFC file. What happens to the IFC GlobalId properties?
When exported, the existing GlobalId of the dgn element is ignored and new IFCGUIDs are created in my test case.
Jon Summers said:Can a consumer correlate objects in the original IFC with those in the exported IFC by comparing their IFC GUIDs
Because the IFCGUIDs are different, correlating objects based on IFCGUIDs would not be accurate.
Best Regards,
RJ.
Raguram Jayaram said:may I please request additional information
Sure!
That's what I mean by round trip.
Regards, Jon Summers LA Solutions
I was discussing your query with our team.
I was told, the platform open reference ignores GUIDs and we have no official import for building elements (Design Transfer View).
Please accept my apologies for my incorrect answer regarding the import, and if my reply caused any inconvenience / trouble.
My apologies, may I please request additional information on your thoughts about
Jon Summers said:to round-trip the IFC GUID between third-party apps. and OBD.
Raguram.
It’s positive to see that the updated IFC exporter stabilises the IFC GUID allocation. The implication of the update suggests that the IFC GUID is stored in the DGN file in order to allow its persistence on subsequent export. If that is the case we have what we need to round-trip the IFC GUID between third-party apps. and OBD. Can you confirm that to be the situation?