CityJSON for information models

Presentation given at the webinar "buildingSMART Finland -- Different Scales of Modeling"

https://buildingsmart.fi/kalenteri/bsf-kaupunkiryhman-tietoisku-mallintamisen-eri-mittakaavat-klo-9-11-30/

Transcript

1. Hugo Ledoux buildingSMART Finland Different Scales of Modeling in pyjamas at home 2020-12-08 for city information models
2. 2 International standard (from OGC) for representing and storing 3D city models
3. CityGML files are very complex 3 • files are deeply nested, and large • many “points of entry” • many diff ways to do one thing ➡ few software packages correctly CityGML ➡ no parsers in JavaScript ➡ I personally get each time I get a new file it makes life of your developers very unpleasant
4. 4 Data model a GML encoding 2 encodings
5. Why an alternative encoding? Read this. 5
6. CityJSON v1.0 6 1. "Building" 2. "BuildingPart" 3. "BuildingInstallation" 4. "Road" 5. "Railway" 6. "TransportSquare" 7. "TINRelief" 8. "WaterBody" 9. "PlantCover" 10. "SolitaryVegetationObject" 11. "LandUse" 12. "CityFurniture" 13. "GenericCityObject" 14. "Bridge" 15. "BridgePart" 16. "BridgeInstallation" 17. "BridgeConstructionElement" 18. "Tunnel" 19. "TunnelPart" 20. “TunnelInstallation” 21. “CityObjectGroup” • all modules mapped • software for full conversion CityGML <-> CityJSON • several software already • Extensions (ADEs) are also possible, and simplified
7. Same information as CityGML, but in JSON format 7 { "type": “CityJSON", "version": “1.0”, "metadata": { "referenceSystem": "urn:ogc:def:crs:EPSG::7415", }, "CityObjects": { "id-1": { "type": "Building", "attributes": { "measuredHeight": 22.3, "roofType": "gable", "owner": “Elvis Presley" }, "geometry": [ { "type": "MultiSurface", "boundaries": [ [[0, 3, 2, 1]], [[4, 5, 6, 7]], [[0, 1, 5, 4]] ] } ] } }, "vertices": [ [23.1, 2321.2, 11.0], [111.1, 321.1, 12.0], ... ], "appearance": { "materials": [], "textures":[], "vertices-texture": [] } } human-readable file computers prefer this over XML ready for the web ~6X compacter than CityGML
8. Specifications give all the gory details 8
9. Python parser is simple 9 CityJSON makes developers happy (and thus productive)
10. Compression factor == ~6X 10 Compression (v0.6) file CityGML size (original) CityGML size (w/o spaces) textures? CityJSON CityJSON compressed compression factor CityGML demo "GeoRes" 4.3MB 4.1MB yes 582KB 524KB 8.0 CityGML v2 demo "Railway" 45MB 34MB yes 4.5MB 4.3MB 8.1 Den Haag "tile 01" 23MB 18MB no, material 3.1MB 2.9MB 6.2 Montréal VM05 56MB 42MB yes 5.7MB 5.4MB 7.8 New York LoD2 (DA13) 590MB 574MB no 110MB 105MB 5.5 Rotterdam Delfshaven 16MB 15MB yes 2.8MB 2.6MB 5.4 Vienna 37MB 36MB no 5.6MB 5.3MB 6.8 5
11. One example: Zürich LoD2 buildings 11 CityGML = 3.0GB (but 1GB of spaces/CRs/tabs!) CityJSON = 292MB Compression == 7.1X
12. Whole Netherlands in 3D is available in CityJSON 12 ~1000 tiles of 5km X 6.25km 10M buildings (in LoD1; soon in LoD2!)
13. CityJSON software? We have that.
14. Overview of current software 14
15. citygml4j 15 full conversion CityGML <-> CityJSON
16. web-viewer == ninja! 16
17. azul 17
18. Safe FME has CityJSON support 18
19. cjio (CityJSON/io) 19
20. cjio (CityJSON/io) 20 $ cjio myfile.json assign_epsg 7415 subset -cotype Buidling compress save out.json pip install cjio
21. CityJSON is ready for machine learning 21 new!
22. thank you. h.ledoux@tudelft.nl 3d.bk.tudelft.nl/hledoux Hugo Ledoux https://cityjson.org