Loading breaks on inconsistent semantics

[balazsdukai]

(reported via email)

If we look at the 'semantics' of a particular geometry, we see 4 surface types (indexed [0,1,2,3]). It seems that it is now standard that all surface types are always included in all geometries.
In the values list only index [0,1,2] are used, this means that the 4th surface type (index 3) should (formally) not be included in this geometry.
The cjio.citymodel.load() function throws an error when i try to load the cityjson form 3d BAG.

On the cjio package.
These problems do occur when using the python package (what they call the cjio 'API'). Most cli function seem to work ok.
We would realy like to use the 3D BAG data using the cjio api. We use the data in apps we make on the Viktor Platform
Now we are parsing the cityJSON files ourself, which is tedious.
We would really like to use existing pyhton packages such as the cjio 'API'.

The python code i use, that throws the error is:

import json
from pathlib import Path

from cjio import cityjson

path = Path(__file__).parent / '3dbag_v210908_fd2cee53_6212.json'
cm = cityjson.load(path)