Triply Use Case 7: Place 3D data in the correct size

[wouterbeek]

Triply Use Case 7: Place 3D data in the correct size

Description

3D BIM data typically uses distances/sizes in millimeter. When I load the 3D object into my GeoSPARQL dataset, I want the distances and sizes to be stored correctly.

Actor

• Data Expert (who may not be a Geodata Expert)

Preconditions

• I have a 3D BIM object.
• I have some GeoSPARQL data.

Postconditions

• I have integrated my 3D BIM object into my GeoSPARQL data, where the 3D object has the right size (length, depth, height, proportions).

Steps

1. I have a 3D BIM object that I convert to a 3D GeoSPARQL.
2. I have 2D data in GeoSPARQL that uses CRS IRI http://www.opengis.net/def/crs/EPSG/0/28992, which is specific to The Netherlands.
3. Upon ingesting the 3D data, I have some way of recognizing or specifying the size, so that millimeters in the "engineering CRS" translate correctly to meters in the "geospatial CRS".
4. When somebody queries my data, they can see the 3D GeoSPARQL object in the correct size (i.e. not too small or too big).

[FransKnibbe]

Related to issue #586 : if GeoSPARQL could supply semantics for georeferencing 3D geometry that uses a local CRS, that would probably include a property for a scaling factor. I can imagine QUDT provides suitable semantics for specifying a scale for length units.