IFC-properties

Question

Hi 
 We're getting greater demands on our delivered IFCs and the information in them. In Sweden we have a pset called BIP which don't come with the Swedish dataset. It has been discussed on the forums here, but never got a complete solution. For instance a thread on how to map levels, GUID and other properties to a certain pset, or my own post on how to export the classification description to a pset. 
 https://communities.bentley.com/products/building/building_analysis___design/f/aecosim-speedikon-forum/151018/bip---ifc-pset https://communities.bentley.com/products/building/building_analysis___design/f/aecosim-speedikon-forum/195998/classification-description-in-ifc/ 
 It seems there's a lot of information in OBD that can't be exported and gathered under one pset. 
 1. Is the GUID and other mentioned properties possible to remap to a specific pset. In that case, how? 
 Apart from BIP, clients sometimes want their own information, displayed in certain ways. For instance, the construction phase on elements are named as "new construction" or "existing to remain" for the datasets definitions. Often the clients only want something like "N", "E" or similar. 
 2. Is it possible to create some kind of remapping of property values. To have "new construction" become "N" during export? 
 Regards, 
 Robert

Marc Thomas · Answer

Hi Robert, 
 Regarding modifying values during IFC export: 
 Our IFC export tools are obviously aimed at maximizing fidelity of exported data, changing values is not part of it's function. 
 Within the OpenBuildings UI to solution would be to change the content of the property's pop-down list, but that would obviously introduce inconsistency and another thing to mange at your end. 
 But, as IFC is a text file and highly structured it is possible to make simple edits using find and replace to achieve you objective. The IFC format stores all property values in IFCPROPERTYSINGLEVALUE entries, in this example the Construction Phase 'New Constuction' is defined: 
 # 1828 =IFCPROPERTYSINGLEVALUE('Phase',$,IFCTEXT('New Construction'),$); 
 This occurs once, the reference number at the start of the line is then referenced by all objects that have that particular value, e.g.: 
 #2429=IFCPROPERTYSET('2_t2T1UHebQpSr2YYHX$wb',#30,'Construction Phase',$,(# 1828 )); 
 Changing the initial definition then affects all subsequent instances, so modifying this example: 
 #1828=IFCPROPERTYSINGLEVALUE('Phase',$,IFCTEXT('N'),$); 
 Results in: 
 
 I hope this is a simple and immediately usable solution in this case?