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
In GeoSPARQL, I can represent and load 3D geometries in GML or WKT. But these geometries are boxes without texture. When I obtain textures, I cannot store them in relation to their corresponding 3D geometries with a standardized relationship. Originally reported by me in #438, including many insightful comments by others.
Actor
Data Expert
Preconditions
One or more 3D objects in a GeoSPARQL dataset.
Textures that belong to these 3D objects, stored in separate files.
Information about how the textures apply to the objects, e.g. where the texture should start and end (otherwise the front door would appear on the back of a building).
Postconditions
The 3D objects in my GeoSPARQL dataset have textures. Geospatial and texture data is fully integrated.
Steps
I have 3D GeoSPARQL objects in my triple store.
I have textures for these objects in separate files.
I can integrate the textures into my GeoSPARQL dataset. Either by linking to the files, or by integrating the file content into a (binary) literal.
When I query my data, I can show the 3D objects on a map, together with their textures. The triple store knows how the textures should be applied to the 3D objects, as long as I have specified sufficient information for how this should be done.
The text was updated successfully, but these errors were encountered:
In short, CityGML adds additional semantics on top of GML. This allows you to specify if a particular geometry is a wall or a floor, etc. And the Appearance module, in particular, allows you to add texture information to such descriptions.
GeoSPARQL specifically can be used to query geometry layer (including texture coordinates) of such descriptions and SPARQL can be used for anything else.
Triply Use Case 2: Support for textures
Description
In GeoSPARQL, I can represent and load 3D geometries in GML or WKT. But these geometries are boxes without texture. When I obtain textures, I cannot store them in relation to their corresponding 3D geometries with a standardized relationship. Originally reported by me in #438, including many insightful comments by others.
Actor
Preconditions
Postconditions
Steps
The text was updated successfully, but these errors were encountered: