Can't export to tiled CityGML files about importer-exporter HOT 8 CLOSED

The dataset can be downloaded here. At the end of the CityGML tree, there are two elements with the tag app:appearanceMember which gave me errors while importing because they link to texture files that aren't present. So I removed them manually before importing the dataset. But removing them did not have any effect on the exporting issue.

I built the database with the CRS EPSG 25832 and the height CRS EPSG 7837.
For the export, I used the bounding box bbox=287000.0,5618000.0,303000.0,5638000.0 and tiled it into 20 rows and 16 columns. (BTW: It would be great if there was an option to just give the tile size and the number of rows and columns would be calculated based on that and the bounding box)

from importer-exporter.

Thanks for providing the dataset. We can reproduce the issue and will work on a bugfix.

There is another workaround you can use. The issue is caused by the global appearances in the file. The CityGML specification recommends avoiding global appearances in favor of local appearances whenever possible. So, you can use
citygml-tools to automatically convert the global appearances. Simply use the to-local-apps command of citygml-tools:

$ citygml-tools to-local-apps /path/to/your/city.gml

Afterwards, load the resulting file into the 3DCityDB and re-export applying your tiling scheme. I just tested locally and it worked fine.

from importer-exporter.

Seems to be Docker-related. At least I have never experienced this issue with "normal" PostgreSQL installations. @BWibo, have you come across this issue before?

As a workaround in the meantime, you can let the Importer/Exporter write temporary data to a local file rather than using temporary database tables. Go to "Preferences -> General -> Cache" and pick "Use local folder". More information can be found in the online documentation.

from importer-exporter.

Changing the setting in the preferences didn't change anything.
Neither did installing PostgreSQL directly on Windows and running the provided scripts to set up the database.
The import of the data into the database still worked fine, so I guess the database is set up correctly.

from importer-exporter.

Okay, there seems to be something fishy with the imported dataset. I can't reproduce the error with another dataset. My bad for not checking that prior to opening an issue. Sorry!

from importer-exporter.

Thanks for your update. Would be great if you could share (part of) the dataset so that we can debug the issue and find a fix.

from importer-exporter.

That workaround works indeed, thank you!

from importer-exporter.

Fixed with 4484b4f. The fix will be included in the next release. If you need the fix earlier, you can build the Importer/Exporter from master or use the edge Docker image.

from importer-exporter.