You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used cjio to first upgrade a CityJSON file from v1.0 to v1.1, then to filter only lod 2, which converted many metadata information using the MetadataExtended extension. However, the "spatialRepresentationType" property is not converted correctly. According to the schema of MetadataExtended, type of this property needs to be an array of strings, but it was converted as string.
When I change the value to ["vector"], my file becomes valid so I guess there is a problem in cjio upgrade about this.
The text was updated successfully, but these errors were encountered:
I just realized that all information in "+metadata-extended" object is only included once I filter LoD. Before this, there is only "presentLoDs" in "+metadata-extended", but once I use cjio to filter LoD2, many other properties are added (image below) that are not present in the original file.
While this does not create a problem, there is one error I've gotten related to this: In "cityfeatureMetadata", a property called "BuildingParts" is included which is not specified in the schema of MetadataExtended extension. Additional properties are not allowed in the schema so this gives an error.
I include the files in the zip below, both before LoD filter (multipart_v11.json) and after (multipart_v11_lod2.json)
I used cjio to first upgrade a CityJSON file from v1.0 to v1.1, then to filter only lod 2, which converted many metadata information using the MetadataExtended extension. However, the "spatialRepresentationType" property is not converted correctly. According to the schema of MetadataExtended, type of this property needs to be an array of strings, but it was converted as string.
When I change the value to ["vector"], my file becomes valid so I guess there is a problem in cjio upgrade about this.
The text was updated successfully, but these errors were encountered: