CityGML Error: Invalid File

Cesium ion
1

Hello!

I´m trying to upload a CityGML datset and encounter error “Error: Invalid File".
I thought this would go easy since I have a smaller sample from the same dataset that works fine.
I´m using the “Add data” function in the web browser interface, with default settings.

Asset with Invalid file error: 3644297
Asset, which is a subset from same source working fine: 2135870

The only difference apart from being a subset is the version of 3dCityDB Import/export tool used for export 4.3.0 vs 5.5.1. Its hard to troubleshoot since there is no reference to what makes the file “Invalid”.

Anyone have any tips?

2

Hi,

One of the things to look at would be if it is different CityGML versions. Currently Cesium ion doesn’t support CityGML version 3. Is the new output version 3?

3

Thanks for the response.
Its version 2.0, I´ve also tried with version 1.0.
I´ve done a number of tries during the day, experimenting with different versions of 3dCityDB importer/exporter tool. But I cant export a citygml dataset that can be uploaded.

I tried to upload a supersmall dataset here to use as example data, but since I´m a new user this functionality is not available to me.
The supersmall dataset has asset id 3649084, if thats helpful.

4

Hi,

I took a look at the logs of the assset 3649084 and it looks like the error for the invalid file states: Missing spatial reference system (srsName)

I do see the CRS under the CityObjectMember tag. I think you are running into an instance where ion isn’t detecting the SRS because it isn’t at the top level within the CityModel tag. I would suggest trying something like this: Citygml to 3d tiles - #4 by a.scalas

If that works, I will create an issue and bump the team to look at how to fix it

Thanks,
Ankit

5

Yes!
Thank you Ankit, this solved the issue!
Adding:

gml:boundedBy
<gml:Envelope srsName=“urn:ogc:def:crs:EPSG::5847” srsDimension=“3”>
<gml:lowerCorner>my coordinates</gml:lowerCorner>
<gml:upperCorner>my coordinates</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
(humm, the xml seems to be automaticaly formated to be links, not showing the angle brackets…..?)

I havent tested if the bounding cube is actually used or not. The bounding cube in asset preview differs though.

It would be great if this behavior was fixed, or at least documented, ideally with either a reference in the docs or a clearer hint in the error message.

Thanks again.