Import CityJSON workflows
Converion time.. :)
I have CityJSON converted to (DXF) coming from FME
Tried FBX, IFC2x3 and IFC4, nothing comes to display in Blender.
Anyone have an idea why none iof thes imports seem to work?
Also, the default DXF show no objects
FBX?
IFC? sites?
Comments
Can you share a file?
Either a georeference so objects are miles away from scene center, or a scale issue or a view near / far clip issue.
Also pay attention at coordinate system (projection) or you may face with up to several meter offset / deformations.
I uploaded a DXF [m] with the CityJSON file to this drive.
The json file is about 50 MB. We (in NL) have a serious hurdle to take work with json GIS as open format to use in 'bim'.
I see very limited possibilities to convert it to something 3D worakble. Only one 'commercial workflow '
Should be a smooth ifc json brigde if you aks me, Thanks for tips & advice. Maybe you can take a look
https://drive.google.com/drive/folders/1fp3KCp3oPqykUqSWmQBsWF-g39gywJGH?usp=sharing
The CAD drawing
https://drive.google.com/file/d/128OQ7CI2yLbYIoc-Mt0NBhcaK8AGL6M0/view?usp=sharing
In DWG this kind of work is slow as hell. Blender speed needed badly :)
My conclusion is that sofar only one commercial software able to work with CityJSON files is FME. I asked someone to translate it to DXF so i can work with it.
Maybe other countries have other more accessable formats or datasets. In the Netherlands CityJSON was the choice so we have to deal with that. As community we could make it part of a combined effort to convert this kind of gis geometry into other suitable 3D formats to work with.
News!
https://www.ogc.org/pressroom/pressreleases/4376
and as part of a challenge
https://community.osarch.org/discussion/comment/4761/#Comment_4761
CityJSON looks pretty straightforward to support. We can probably hack together an importer in a day. Unfortunately right now it's a little down in the priority list.
I just came across this. Some work has been done. Great stuff
https://github.com/cityjson/Up3date
https://pdok.mapconverter.app/
The targeted DXF download fills a real need for most CAD/GIS closed AEC software for the Netherlands. More cities will be added later. The other route, using Blender, is a big area download file of about 200-700 mb json file that leads to about 2.6 GB blend file (second screenshot) . I was able to get a view (15000 m field view)but only the option 'building objects' on import allows a zoom to object (?)
My question now is this. What is a normal filesize for Blender to work smooth? I was thinking the power of blender maybe able to crack this import further. So, what tools or script do we have to make this more compact and usable as groundmap? Clipping, deleting metadata, remeshing, etc.
Thanks!
Original downloads for cityjson NL
https://3d.kadaster.nl/basisvoorziening-3d/
OGC seeks public comment on new CityJSON Community Standard
https://www.ogc.org/pressroom/pressreleases/4381?utm_content=buffer4f60a&utm_medium=social&utm_source=twitter.com&utm_campaign=buffer
Big challenge i experience is the filesize it brings. The dutch government makes it way to big.
@magicalcloud_75 I was under the impression that it was an alternative syntax to CityGML. Given that CityGML is XML and this is JSON, JSON should be a smaller filesize than the equivalent data in XML.
https://www.mdpi.com/2220-9964/9/9/502
Yes that's correct. So if it is converted 600 mb dutch Kadaster files turn into 2.5 Gb blender file. These cityjson shouldn't be more than say 50 mb to be able to work with?
Blender is able to manage such huge datasets by linking files instead of actually append objects right in the scene. As long as snap to Kadaster is not required, may be an option.
Segregate different mesh / building elements into different files would be a good idea. How does one do this efficient after importing and habing a 3 GB? Some smart script that can split it up into parts/area's? I was looking for a way select meshes with a specific color. Than copy paste them in a seperate file. These kind of things can bring me further. thx