How to debug or enable more verbose error message for 3d-buildings-tiler running on-premise?
I run this command and get the error
3d-buildings-tiler -I CityGML -i "$(pwd)"/lod4.gml -o ./processed --verbose --citygml.printCommand
Reading CityGML [====================] 100% 2.3 seconds
[ ] 0/1(0%) 0.0 seconds
Error: Internal Error
Sqlite3: string or blob too big
No errors when run citygmlswayze command, so I assume valid citygml file.
The lod4 CityGML file size about 3GB.
Using version Cesium-ion-3D-Tiling-Pipeline-Linux-4.5.0 running on OS Ubuntu linux.
For other citygml file issue (filesize about 4GB), I got [1] 2235708 segmentation fault (core dumped) /home/user/Cesium-ion-3D-Tiling-Pipeline-Linux-4.5.0/bin/citygmlswayze
It may be a problem with how the tiler is handling the textures. A good way to check is to move the textures to a separate folder, so that they cannot be located by the tiler. The tiler will ignore any textures it cannot find.
Image above when i run conversion for a file LOD3. I noticed from my side when i run a file more than 800MB, the “string or blob too big” will appear. How can i do to solve the problem?
This seems like the same issue as the one we discussed in one of our previous threads: for some datasets, it appears that the tiler attempts to create a too-large texture blob in the sqlite3 database that is generated as an intermediate step of the pipeline. Unfortunately, a fix for this is not yet available, but if you selectively exclude some number of textures (by moving them to another directory), tiling should be successful—albeit with those textures missing.
This is, of course, not an ideal workaround, both because it results in missing textures and because it requires some trial and error. We are seeking to resolve this problem.
If this seems like a different problem, however (for example, if moving the texture files does not help), please let me know and I will open a new ticket.
