I have existing dgn elements and cells (not authored in AECOsim, no parts/family definitions).
I am attaching my own user definitions as instance data.
My question is how to add object dimension data to my user definition. Ideally I want to attach object dimensions Length/Width/Height.
Currently my definition file requires manual input of these fields via schedule or properties. I want this to be done automatically, by reading the RAW property data of the existing cell or element.
The high range minus low range values can give me XYZ values. Hopefully these can be utilized.
How can the above data be incorporated into my AECOsim/OpenBuildings Definition File?
Thanks
The only way maybe through some sort of VBA. You might want to post to our programming forum:
https://communities.bentley.com/products/programming/
Hi Stuart,
These values are stored in the ECschema used by the MicroStation platform AECOsim/OpenBuildings is built upon. Instance Data properties are stored in the DataGroup Catalog, the values of the properties are stored on each element instance.
Generally the Catalog cannot use every ECschema property, although there are a few exceptions where connections can be made.
Exactly what is your objective here?
If it is to report on these properties and their values alongside those of Instance Data, the Reports tool can be used instead of the Catalog Schedules: CONNECT Edition - Reports: EC and DataGroup in the same report. This produces structured output for post processing in Excel.
Regards
Marc
Thanks Marc
My objective is to read the data directly in the model properties. Not via reports. I want to create instance data that will automatically populate Width, Length, Height & Volume for all elements within a .dgn file. (Not XYZ Origin) The objective is that is data attached to the elements is then exported to .IFC format
I have been able to do this with CONNECT item types using the syntax expressions, and subtracting one value from the next and so on..
this.GetElement().RangeLow .x
this.GetElement().RangeHigh .x
The CONNECT item types don't seem to show when converted into .IFC format.
The objective was to utilize instance data in AECOsim as these are pulled through into IFC format.