You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IFCs are able to encode this data, but many IFC files do not include all this information. GeoSPARQL should include a profile for IFC, that allows users to quickly check whether an IFC is eligible for GeoSPARQL inclusion. The profile should check for the information properties that are used in GeoSPARQL to place a 3D object in a correct way. If the profile is followed, translation from IFC to GeoSPARQL is guaranteed to work (assuming the entered values in the IFC are correct).
Such profiles are called "Informatieleveringsspecificaties" or "ILS" in The Netherlands.
Actor
Data Expert (who may not be a Geodata Expert)
Preconditions
I have an IFC file.
I have some GeoSPARQL data.
Postconditions
I have integrated my IFC 3D data into my GeoSPARQL data. I was able to do this in a modern triple store, without having to write any code.
Steps
I have an IFC file.
I use the GeoSPARQL profile for ILS to determine whether my IFC will automatically translate to GeoSPARQL 3D.
The profile indicated that my ILS lacks a geospatial reference.
I update my ILS to include a geospatial reference (or I ask the geospatial expert who gave me the ILS to change this for me).
When I use the GeoSPARQL profile for ILS again, I now pass all the profile checks. I can therefore add my ILS to a triple store that automatically stores it as GeoSPARQL 3D.
When I query my data, I can confirm that the ILS data now appears at the right spot, at the right height, in the right size, under the right angle, and with the correct textures applied.
I now upload a batch of 100 IFC files. 5 minutes later, I have a whole neighborhood of 3D buildings in my triple store, that others can query.
The text was updated successfully, but these errors were encountered:
ILS are text documents, but they can have machine-interpretable specifications: IDS. An IDS could include specifications on how to make IFC data interoperable with geoSPARQL.
IfcOWL is a web ontology for IFC, but it does not use GeoSPARQL. Not all IFC geometry can be easily mapped to GeoSPARQL, but some of it might.
Triply Use Case 8: GeoSPARQL profile for IFC
Description
A lot of 3D data is stored in IFC. In the future, GeoSPARQL will have the ability to detect or configure the following aspects of 3D BIM data:
IFCs are able to encode this data, but many IFC files do not include all this information. GeoSPARQL should include a profile for IFC, that allows users to quickly check whether an IFC is eligible for GeoSPARQL inclusion. The profile should check for the information properties that are used in GeoSPARQL to place a 3D object in a correct way. If the profile is followed, translation from IFC to GeoSPARQL is guaranteed to work (assuming the entered values in the IFC are correct).
Such profiles are called "Informatieleveringsspecificaties" or "ILS" in The Netherlands.
Actor
Preconditions
Postconditions
Steps
The text was updated successfully, but these errors were encountered: