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
Triply Use Case 5: Place 3D data at the correct height
Description
3D BIM data typically does not include the height at which the object starts. (E.g. the BIM file uses an "engineering CRS" which assumes that the building starts at height "0.0". When I load the 3D object into my GeoSPARQL dataset, I want it to start at the correct height. E.g. if the building lies on a mountain or lies beneath the sea level (which is common in The Netherlands), I want to be able to visualize this correctly.
Actor
Data Expert (who may not be a Geodata Expert)
Preconditions
I have a 3D BIM object.
I have some GeoSPARQL data.
I have a 3D tiles background layer.
Postconditions
I have integrated my 3D BIM object into my GeoSPARQL data, such that the object start at the correct height.
The object (nearly) touches my 3D tiles. When there is a mountain in my 3D tiles, the building does not fall into the mountain. When my 3D tiles are under the sea level, the building does not float in the air.
Steps
I have a 3D BIM object that I convert to 3D GeoSPARQL.
Related to issues #586 and #585: If it is possible to georeference 3D geometry from a BIM, and find and apply a suitable 3D geographic CRS, the the Z coordinates would have clear and correct values.
Triply Use Case 5: Place 3D data at the correct height
Description
3D BIM data typically does not include the height at which the object starts. (E.g. the BIM file uses an "engineering CRS" which assumes that the building starts at height "0.0". When I load the 3D object into my GeoSPARQL dataset, I want it to start at the correct height. E.g. if the building lies on a mountain or lies beneath the sea level (which is common in The Netherlands), I want to be able to visualize this correctly.
Actor
Preconditions
Postconditions
Steps
The text was updated successfully, but these errors were encountered: