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
Here I post the question that arose from the meeting 01 August 2024.
According to the simplification of GML3 used in 3dCityDB most of the variety of geometrical objects from GML3 is represented with BRepAggregate and Polygon (TIN, Point and _Curve remain untouched).
In case we decide that in CityRDF it is viable to have only those geometries, what SHACL rules can check the consistency of the simplification in each particular case?
Will it be practically feasible in terms of performance: generate simpler CityRDF with longer SHACL rules list or have larger/complex CityRDF geometries without SHACL?
The text was updated successfully, but these errors were encountered:
nataschake
changed the title
CityGML geometry simplifications in 3dCityDB and their possible re-use in ShapeChange conversion
CityGML geometry simplifications in 3dCityDB
Dec 18, 2024
Here I post the question that arose from the meeting 01 August 2024.
According to the simplification of GML3 used in 3dCityDB most of the variety of geometrical objects from GML3 is represented with BRepAggregate and Polygon (TIN, Point and _Curve remain untouched).
In case we decide that in CityRDF it is viable to have only those geometries, what SHACL rules can check the consistency of the simplification in each particular case?
Will it be practically feasible in terms of performance: generate simpler CityRDF with longer SHACL rules list or have larger/complex CityRDF geometries without SHACL?
The text was updated successfully, but these errors were encountered: