errors on exporting CityGML in 3D Database about importer-exporter HOT 7 CLOSED

Please provide (an excerpt of) your CityGML dataset, if possible, so that we can try and reproduce the issue.

from importer-exporter.

strijp-s.zip
thanks

from importer-exporter.

Ok, I did the following:

1. Set up a new 3DCityDB 4.0 using EPSG 28992
2. Imported your dataset strijp-s.xml
3. Exported the database content into a new file

I cannot reproduce your issue. I get all data exported correctly: test.zip

Maybe you were using some filter settings on the CityGML export tab due to which no buildings were exported? Or did you receive any error messages during export?

Nevertheless, note that your CityGML dataset does not validate against the schema. Simply click the "Just validate" button on the CityGML import tab of the Importer/Exporter to get a list of the issues.

from importer-exporter.

thanks, here is another problem, I want to turn the CityGML format to glTF, based on the document, I need to import CithGML and Export CityGML first. But when I export the glTF and open it with Google Earth, the location is nor right. When i import the test file and validate, it shows some errors. Therefore, are these errors cause the problem? Thanks

from importer-exporter.

In your first post I see that you have used the CRS with EPSG code 25833. @clausnagel used 28992. Have you changed it as well?

from importer-exporter.

Well, did a KML/COLLADA export and loaded it into Google Earth. The position of the buildings looks fine.

@FxKu is right, I used EPSG:28992 to set up the database, simply because this reference system is used in your original dataset strijp-s.xml. Make sure to not mix up reference systems.

The validation errors are mostly due to incorrect gml:id values (in your case, a gml:id must not start with a number). The 3DCityDB can correctly handle the data. However, the error should be fixed in your data.

And there are a lot of falsely oriented polygons in your dataset. If you visualize it in Google Earth, it will look like these polygons are missing, which leaves holes in the buildings. You can force their visualization by checking Ignore surface orientation in the "Preferences -> KML/COLLADA/glTF Export -> Rendering -> Building" settings (which is what I did for the above screenshot). But again, this issue should be fixed in your data in the first place.

from importer-exporter.

@clausnagel @FxKu ，thanks for your help, I'll set up the database at the first step.

from importer-exporter.