enabling WKT (was are geometries always represented as EXPRESS lists?)

jyrkioraskari / IFCtoLBD

IFCtoLBD converts IFC (Industry Foundation Classes STEP formatted files into the Linked Building Data ontologies.

Apache License 2.0

80 stars 21 forks source link

enabling WKT (was are geometries always represented as EXPRESS lists?) #94

Closed VladimirAlexiev closed 7 months ago

VladimirAlexiev commented 7 months ago

Hi @jyrkioraskari and @maximelefrancois86 ! A stupid question: does this convert geometries to the dreaded EXPRESS lists as per IFCowl, or to a more practical representation similar to GeoSPARQL?

I ran IFCtoLBD_Desktop_2024.jar (run_2024.bat from the latest release) with default options:

And I got stuff like this:

inst:REAL_List_219311
        rdf:type  express:REAL_List .

inst:REAL_219312  rdf:type  express:REAL ;
        express:hasDouble  "1."^^xsd:double .

inst:REAL_List_219309
        list:hasContents  inst:REAL_219312 ;
        list:hasNext      inst:REAL_List_219310 .

inst:REAL_219313  rdf:type  express:REAL ;
        express:hasDouble  "0."^^xsd:double .

inst:REAL_List_219310
        list:hasContents  inst:REAL_219313 ;
        list:hasNext      inst:REAL_List_219311 .

Should I change some options, or maybe I need to use the command line https://github.com/jyrkioraskari/IFCtoLBD#command-line-usage ?

jyrkioraskari commented 7 months ago

For practical reasons, we have both presentations. On the user interface, select "Bounding Boxes as WKT". Please, comment if you find inconsistencies there.

I updated the command line user interface to include the --hasWKT, --hasHierarchicalNaming, and --hasPerformanceBoost options. So, --hasWKT should give you the GeoSPARQL version. The change was added to the source code. I will provide the compiled version in the next release.

VladimirAlexiev commented 7 months ago

Thanks @jyrkioraskari !

What does the WKT include: floor plans with Z coordinates for each floor?
https://github.com/jyrkioraskari/IFCtoLBD#command-line-usage shows this. Can you please fix the description of the second option? By default, that option is disabled on the UI, but ifcOWL geometries are still output?
```
   --hasGeolocation   Geolocation, i.e., the latitude and longitude are
                       added.
  --ifcOWL           Geolocation, i.e., the latitude and longitude are
                       added.
```

How about this option: is it necessary to enable WKT output?

  --hasGeometry      The bounding boxes are generated for elements.

cc @nataschake.

jyrkioraskari commented 7 months ago

Thank you! The --ifcOWL description is fixed.

By default, the 3D WKT bounding boxes are created for all BIM elements that have geometry. Most of the models have elevation properties for the floors. The floor plans shown on the repository were created using the element's OBJ property and the intersection calculation with the plane, which offers the full 2D geometry connected to the elements.

VladimirAlexiev commented 7 months ago

Jyrki, thanks! I'll close this one, but I think the options can be explained better.

We'll experiment more, raise further issues, and report experience. BTW will you be at OGC's Digital Building Permit conference in Barcelona in about 2 weeks?

@nataschake OPEN SEPARATE issues! Don't lump all kind of stuff into this issue.