@LaurensJN could your plugin work to import and use Cityjson files from '3D basisvoorsiening'. If so, this would be really a great feature for Blender.
The Cityjson (1 subtile of the 4) converted to .ml gives a file of about 3.7 GB. That's too big to handle.
Buildings are not good. Needs LOD2.2 from BAG.
In FZKviewer this tools like this
Target Area
There seems to be not an option to isolate a selection and delete the rest
Atempt to export the ENTIRE tile.
Cancelled the proces at 9%. The ifc blow up to 5 GB and counting..! This is not the way
The whole idea of CityJSON is a compact schema that reduces the metadata overhead found in for example CityGML that is much more verbose. IFC is, like CityGML, a very verbose schema & therefore it is expected that file size explodes if you convert big CityJSON files. There is no other way, except for further tiling the CityJSON file into smaller parts (not super easy but possible with the CJIO python module), or removing elements that you don't need.
There is always a trade-off between reduced file size (only geometry, preferably topology to even reduce file size more) and full metadata. It's your call what is most important to you. If you are looking for the geometry only, CJIO provides different exports for CityJSON: ['obj', 'jsonl', 'stl', 'glb', 'b3dm']. I guess exports to obj file would reduce the file size and is widely supported (you can for example import it in blender). See here how to use it: https://cjio.readthedocs.io/
@magicalcloud_75 said:
@LaurensJN could your plugin work to import and use Cityjson files from '3D basisvoorsiening'. If so, this would be really a great feature for Blender.
If we disregard file sizes, the converter works for any CityJSON file, so yes. It might be not too useful, because these kind of files contain mostly infrastructure / land use etc. There is no support in IFC4 (yet) for these kind of classes. However, if IFC4.3 becomes a real standard, there could be some advantages to convert CityJSON basisvoorziening to IFC.
"contain mostly infrastructure / land use "
That's exactly what i would like to use it for. Consider a medium to large infrastructure project. The correct building shape is not so relavant. Getting the true height to the mm. of ground level is also not that important. Dataset 3D Basisvoorziening however could be useful to get a fast view that the site is about.
If IFC4.3 has the ability to get IFC work together with Cityjson, we should use it. By 'we' i mean , people and stakeholders in general!
Dooooo..
It just reminded me Up3date is already able to import cityjson.
https://github.com/cityjson/Up3date
Still, there is much to gain. The import proces is about 2 hours for 1.5 GB! Which i find not acceptabel values
Maybe Blender 3.0 does it faster but i doubt it.