Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Queries regarding the IFCtoLBD converter #104

Closed
AJAY31797 opened this issue Apr 5, 2024 · 3 comments
Closed

Queries regarding the IFCtoLBD converter #104

AJAY31797 opened this issue Apr 5, 2024 · 3 comments

Comments

@AJAY31797
Copy link

AJAY31797 commented Apr 5, 2024

Hi Team,

I am a researcher trying to use the IFCtoLBD converter to convert an IFC file (containing information about a 4D BIM) to RDF for some of my research work. I used the latest version (IFCtoLBD_Desktop_2024) to convert an IFC file to LBD. I had a few queries regarding the results. It would be a great help if you could answer them.

  1. The geometry of the building elements, as represented in the resulting LBD file, looks something like this:
    image

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)?

  1. To my understanding, the elements are connected to bounding boxes using a property lbd:containsInBoundingBox, as shown below.
    image

Am I correct in interpreting this? If yes, why are there more objects than objects in this property (this would mean that there is more than one bounding box for the same object)? If not, what exactly is lbd:containsInBoundingBox doing?

  1. Are the bounding boxes axis aligned?

  2. 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. (I have raised this query earlier as well).

  3. In the UI of the converter, I see this option called "Include IFC Based Elements" (screenshot attached). What exactly does it do differently from the "Create and link ifcOWL" option?

image

Thanks in advance,
Ajay

@VladimirAlexiev
Copy link

@jyrkioraskari , @maximelefrancois86 feedback?

  1. Yes. But check coordinates for reasonableness. See coordinates discrepancy for Malgrat building #98 and Missing GeoSPARQL WKT coordinate system #97
  2. x lbd:containsInBoundingBox y means that x is "bigger" than y and BB(x) includes BB(y), so it can be multivalued
    • I think it's ok to have a beam within the volume of a wall
    • But a second wall within the volume of the first wall? That is doubtful
  3. I think it uses "mm" for the coordinates, and they are aligned along the building axes.
    I suspect they are not geo-referenced, i.e. not northing/easting.
    I don't know of any northing/easting CRS to use "mm", they all use "m".
    Not being geo-referenced is a major problem for any land-use related case
  4. lbd is made-up on the spot.

@VladimirAlexiev
Copy link

@AJAY31797 Is that your question on StackOverflow? I posted an answer: https://stackoverflow.com/questions/77205257/incorrect-result-in-shacl-validation/78322960#78322960

@AJAY31797
Copy link
Author

Many Thanks, @VladimirAlexiev, for the response. Yes, that query on StackOverflow was mine. Sorry if my questions seem silly; I am new to this field and trying to understand the concepts.
Thanks for the answers again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants