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 11: Represent the same information at different LOD levels
Note: In this issue, LOD standards for "Levels of Detail" and not for "Linked Open Data".
Description
When I load one building, I want to see all the details. But when I load a while city, seeing all the details is not useful and will crash my web browser.
Thanks for marking up by 3D GeoSPARQL data into different LODs, I can offer one dataset that allows 3D data to be viewed at the level of a country, province, city, neighborhood, street, building, or room. At each zoom level, a corresponding LOD may be used, so that applications can guarantee a consistent experience of performance when moving between these different levels.
Actor
Agencies that publish large quantities of 3D data (city- or country-level agencies).
Users of such city- or country-level datasets.
Preconditions
Large quantities of 3D GeoSPARQL data.
Web browser that do not have unlimited hardware resources.
Postconditions
A fluent performance experience when navigating large quantities of 3D GeoSPARQL data, by zooming in and out.
Steps
As a nation-wide publication office, I have high-LOD 3D geodata about many building in the country in which I operate.
In a batch job, I generate lower resolution / lower LOD versions of my geodata. GeoSPARQL 3D allows me to store these lower LOD levels, with standardized properties.
My users can set the LOD per zoom level, so that zooming works in a performant way.
The text was updated successfully, but these errors were encountered:
GeoSPARQL already has the ability to indicate the spatial resolution of a geometry (geo:hasSpatialResolution and geo:hasMetricSpatialResolution), and therefore the ability to represent a Feature with multiple geometries that each have a different optimal visualisation resolution, but the ability to use a standard data structure to encode ranges of resolution could be useful. Such a thing could be used to encode the LODs of CityGML, but it is imaginable that similar standard LODs are nice to have for geometric data at other scales, e.g. microscopic or astronomic scales.
Also. an indication of LODs is useful to have at the dataset level (dataset metadata). A property like dcat:spatialResolutionInMeters can only describe one LOD for a dataset.
Triply Use Case 11: Represent the same information at different LOD levels
Note: In this issue, LOD standards for "Levels of Detail" and not for "Linked Open Data".
Description
When I load one building, I want to see all the details. But when I load a while city, seeing all the details is not useful and will crash my web browser.
Thanks for marking up by 3D GeoSPARQL data into different LODs, I can offer one dataset that allows 3D data to be viewed at the level of a country, province, city, neighborhood, street, building, or room. At each zoom level, a corresponding LOD may be used, so that applications can guarantee a consistent experience of performance when moving between these different levels.
Actor
Preconditions
Postconditions
Steps
The text was updated successfully, but these errors were encountered: