Datasets
Table of contents
Datasets converted from CityGML
| dataset | CityGML file (size) | CityJSON file (size) | textures | details |
| Den Haag | [GML] (23MB) | [JSON] (2.9MB) | none | 'Tile 01', Buildings (in LoD2) and Terrain are merged |
| Montréal | [GML] (56MB) | [JSON] (5.4MB) | none | tile 'VM05'. Buildings in LoD2 |
| New York | [GML] (590MB) | [JSON] (105MB) | none | tile 'DA13'. Buildings in LoD2 |
| Rotterdam | [GML] (16.0MB) | [JSON] (2.6MB) | [ZIP] | neighbourhood 'Delfshaven'. Buildings in LoD2 |
| Vienna | [GML] (37MB) | [JSON] (5.3MB) | none | Buildings in LoD2 |
| Railway | [GML] (45MB) | [JSON] (4.3MB) | [ZIP] | CityGML demo. Buildings, Railway, Terrain, Vegetation (with Implicit Geometries), Water, Tunnels |
It should be observed that on average CityJSON compresses ~6X a CityGML, and that without any loss of information (see details).
Generating automatically your own area
It is possible to generate automatically a 3D city model in CityJSON with 3dfier, just follow that simple tutorial.
All USA buildings
The project Open City Model has converted all buildings in the USA to LoD1 buildings and offers them in CityJSON.
Watch out: the coordinates are in (lat, long, meters), which means that there’s a mix of units (degrees and meters) and several viewers and processing software do not like this very much…