Before switching to a 3DCityDB database, the process building-server-processdb.py of building-server used to compute the bounding boxes of the tile it creates by using the geometry of each feature of the tile.
Since switching to a 3DCityDB database, the building-server-processdb.py process uses the precomputed bounding boxes of the CityGML files imported in the database which are false. This leads to this type of result when displaying the bounding boxes of the tiles in the client (branch 3dCityDB of building-server):
This image also shows that the resulting tree is wrong.
It should look like (branch 3d-tiles of building server):
To answer this issue we can either modify the tile bounding boxes creation process of building-server or create an utility that computes and replace the bounding boxes of the city objects in a 3DCityDB database.
Before switching to a 3DCityDB database, the process building-server-processdb.py of building-server used to compute the bounding boxes of the tile it creates by using the geometry of each feature of the tile.
Since switching to a 3DCityDB database, the building-server-processdb.py process uses the precomputed bounding boxes of the CityGML files imported in the database which are false. This leads to this type of result when displaying the bounding boxes of the tiles in the client (branch 3dCityDB of building-server):
This image also shows that the resulting tree is wrong.
It should look like (branch 3d-tiles of building server):
To answer this issue we can either modify the tile bounding boxes creation process of building-server or create an utility that computes and replace the bounding boxes of the city objects in a 3DCityDB database.