Replies: 1 comment
-
Closing it here, as I've added it as an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am trying to use the IFCtoLBD converter for some of my research work. I downloaded the latest version (IFCtoLBD_Desktop_2024) for converting an IFC file to LBD. I have a few questions in understanding the results of the converter.
The geometry of the building elements, as represented in the resulting LBD file looks something like this:

Do the coordinates represented in the multipoint signify the two diagonally opposite coordinates of the bounding box? I remember the earlier version used to provide the Xmin, Xmax, Ymin, Ymax, Zmin, and Zmax coordinates separately. So, are the coordinates provided in the multipoint just (Xmin, Ymin, Zmin) and (Xmax, Ymax, Zmax)?
The elements are are connected to bounding boxes using a property lbd:containsInBoundingBox, as shown below.

I am not able to understand what exactly the lbd:containsInBoundingBox mean? Is it connecting the building element to its bounding box? If yes, why are there more objects than objects in this property? If no, what exactly is lbd:containsInBoundingBox doing?
Are the bounding boxes axis aligned?
What does the prefix 'lbd' refer to? Which ontology is it connecting with? The URI given in the generated LBD file is @Prefix lbd: https://linkedbuildingdata.org/LBD#. Searching this link leads to nowhere; it shows the DNS address not found.
Any help is appreciated.
Thanks,
Ajay
Beta Was this translation helpful? Give feedback.
All reactions