Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Improving the usability and discoverability of ...

Avatar for Hugo Ledoux Hugo Ledoux
September 29, 2026
2

Improving the usability and discoverability of CityJSON Extensions

Paper presented at the 3DGeoInfo 2026 conference in Sofia, Bulgaria

Avatar for Hugo Ledoux

Hugo Ledoux

September 29, 2026

More Decks by Hugo Ledoux

Transcript

  1. Improving the usability and discoverability of CityJSON Extensions Solar potential

    Hugo Ledoux TUDelft Noise simulation 3DGeoInfo 2026 | Sofia, Bulgaria | 2026-09-29 Tree properties Energy properties
  2. CityJSON Extensions ≅ CityGML ADEs ADE Application Domain Extension •

    • • • • Since v0.4 of CityGML (2007) GML schemas for <= v2 v3.0+ at UML level Any extension to the core model is allowed Software support has been… not great 2
  3. ADEs <2018 overview (Biljecki, Kumar, and Nagel, 2018) Biljecki et

    al. Open Geospatial Data, Software and Standards (2018) 3:13 https://doi.org/10.1186/s40965-018-0055-6 Open Geospatial Data, Software and Standards R EV I EW Open Access CityGML Application Domain Extension (ADE): overview of developments Filip Biljecki1* , Kavisha Kumar2 and Claus Nagel3 Abstract The Application Domain Extension (ADE) is a built-in mechanism of CityGML to augment its data model with additional concepts required by particular use cases. The goal of this paper is to provide an overview of the ADE mechanism and a literature review of developments since its introduction a decade ago. The discovery of publications found that currently there are 44 ADEs supporting a wide range of applications, but also application-agnostic purposes such as harmonisation with national geographic information standards. We hope this paper to double as a reference material for the developers of new ADEs. Keywords: CityGML, ADE, 3D GIS, 3D city modelling Introduction The CityGML standard [1] of the Open Geospatial Consortium (OGC) is the staple open data model and format for the storage and exchange of semantic 3D city models. It is used in several countries around the world for a wide spectrum of application domains [2]. While CityGML is intended to be a universal and application-independent geographic information model, the advent of dozens of applications and burgeoning use in different geographic contexts and software [3, 4] requires some additional information that is not readily available in the CityGML data model [5]. An example of such a case is the application of 3D city models in the energy domain: a method employed to estimate the energy demand of a building may necessitate specific and less common information such as building occupancy [6], an attribute that CityGML does not envisage by default. The developers of CityGML have foreseen situations such as this one, and thus for this purpose two ways to support augmenting the CityGML data model beyond its initial scope are offered: through (i) generic objects and attributes, and (ii) using the Application Domain Extension (ADE) mechanism. The former method has been used in practice but it has certain disadvantages (discussed later), thus the latter *Correspondence: [email protected] 1 Department of Architecture, National University of Singapore, Singapore, Singapore Full list of author information is available at the end of the article method is preferred by developers and it is consequently the topic of this paper. ADE is a mechanism for enriching the data model with new feature classes and attributes, while preserving the semantic structure of CityGML, and it is an important component of the standard since its early versions. Its main purpose is supporting additional requirements by certain use cases, which is accomplished by specifying extensions to the data model. As this paper will show, ADE is employed for a few dozen different purposes, and in spite of being around for a decade there has not been any general publication so far focused solely on this integral and important concept of CityGML. This paper is intended to bridge that gap by giving an overview of the ADE mechanism, its developments, and discussing the current landscape of available implementations. Section CityGML ADE gives a general review of the ADE concept—mostly by condensing the relevant parts of the current version (2.0) of the CityGML standard [1], while Section Modelling a CityGML ADE briefly presents different approaches to model an ADE. Section ADE literature review provides a literature review of publicly available ADEs, while Section Discussion discusses the main findings and observations. Another aspiration of the paper is to serve as a reference for the developers of new ADEs. © The Author(s). 2018 Open Access This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made. Biljecki et al. Open Geospatial Data, Software and Standards (2018) 3:13 Page 6 of 17 Table 1 List of identified ADEs 1 ADEa Purpose Websited XSDb UML Originc Further reading Energy ADE Application URL-1 • • Europe [14–17] Italy [20] • Spain [21–23, 42] 2 Energy Efficiency ADE Application 3 Energy Efficiency ADE (ii) Application 4 Noise ADE Application 5 Extended Noise ADE Application • URL-2 6 Road Traffic Noise ADE Application 7 Robotics ADE Application URL-3 URL-4 8 UtilityNetworkADE Application 9 CAFM ADE Application 10 Immovable Property Taxation ADE Application 11 Cadastre ADE Application 12 CityGML–LADM ADE Application 13 Cultural Heritage ADE Application 14 Cultural Heritage ADE (ii) Application 15 Cultural Heritage ADE (iii) Application 16 Heritage house ADE Application 17 Intervention ADE Application 18 BCH Management ADE Application 19 Indoor N&P ADE Application 20 Indoor ADE Application 21 i-SCOPE Application 22 HydroADE Application 23 AR ADE Application 24 Collada FX ADE Application 25 ENC ADE 26 Air Quality ADE URL-5 • • • • Germany [1, 24] Netherlands [25] • • India [26, 89] Japan [1, 27] • • Germany [28–30] Germany [34, 35] • • Turkey [36] Netherlands [37] • • • URL-6 • • • • • • • • • • • • • Mixed [38–40] Spain [21–23, 42] Italy [43] Italy [44] Malaysia [46] Spain [21] Belgium [45] India [47] Korea [48–50] Europe [53] Germany [54] Canada [55] Germany [56] Application Germany [57] Application Italy [58] 27 IMGeo ADE Generic 28 CityGML-TRKBIS Generic 29 INSPIRE ADE Generic 30 ACRoofADE Generic 31 CityGML iTINs ADE Generic 32 Vegetation Objects ADE Generic 33 Dynamizers Generic 34 Dynamic ADE Generic URL-7 • • URL-8 • • • • • • • • • Netherlands [13, 61, 62] Turkey [60, 64] Germany [65, 66] China [68] Netherlands [9, 69] Mexico [70] Germany [71] Spain [22, 23] 35 Geodata Join ADE Generic Germany [72] 36 Topo ADE Generic China [73] 37 Transport ADE Generic Netherlands [74] 38 Traffic Sign ADE Generic Spain [75] 39 3D-GEM Generic Netherlands [76] 40 New LOD ADE Generic Netherlands [77] 41 Semantic City Model Generic 42 GeoBIM Generic 43 PANTURA ADE Generic 44 3D Metadata ADE Generic • • • China [79] URL-9 • • Netherlands [80] Netherlands [81] URL-10 • • Netherlands Total: 18 Only 10/44 have .xsd 30 a In lieu of a name of untitled ADEs a custom name has been composed in some instances. b Not all authors published the XSD online. However, papers usually contain excerpts of the developed XSD, so here we make an assumption that the file is available upon request. c This denotes the region of origin where the work has been incepted or where most of the work is carried out (e.g. predominant authors of research papers). However, it should be noted that the work around many ADEs has international collaborators and its influence spans multiple countries. d The websites have been checked in June 2018. The URLs are given at the end of the paper 3
  4. New or significantly updated CityGML ADEs since 2018 Table 1.

    Overview of CityGML ADEs proposed or substantially developed after the review of Biljecki et al. (2018). ADE Purpose CityGML version Reference(s) 1 Energy ADE Urban energy modelling Agugiaro (2025) 2 EnvPlan ADE Wilhelm et al. (2021) Yes (schema + data) 3 FWE ADE 2.0 FEW ADE (Montréal) — Padsala et al. (2021) URL-1 Braun et al. (2021) Yes (schema) 4 No 5 GRextADE 2.0 Liamis and Mimis (2022) No 6 Grotto ADE 3.0 Yang et al. (2024) No 7 IfcADE 3.0 Biljecki et al. (2021) No 8 Pedestrian ADE 3.0 3.0 No 2.0 OGC (2020) No 2.0 Siew et al. (2021) No 12 Property Valuation ADE Public Safety Features ADE Strata ADE (SmartKADASTER) Sve-Test ADE Saeidian et al. (2026) URL-3 El Yamani et al. (2024) Yes (schema + data) 9 3.0 Eriksson et al. (2020) No 13 Utility Network ADE Integration of BIM and environmental planning Food/Water/Energy modelling at building and land-use level Food–Energy–Water nexus for a Montréal case study Greek national extension for 3D city models and cadastre management Cultural heritage: semantic modelling of Buddhist niches and grotto components Retaining IFC semantics when converting BIM to CityGML 3D modeling of pedestrian mobility space 3D indoor/outdoor variables for property valuation Indoor public safety (firefighter preplanning) in OGC pilot 3D strata parcels and legal units in Malaysia National building standard for Sweden, linking BIM and national registers Multi-utility networks 2.0 3.0 (inprogress) 2.0 URL-2 Yes (schema) 14 Akahoshi et al. (2020) Yes (schema + data) 15 Urban Planning ADE (i-UR) Vegetation ADE 3.0 (inprogress) 2.0 3.0 16 VicULA ADE Petrova-Antonova et (2024) Saeidian et al. (2023) URL-4 10 11 Urban planning in Japan (PLATEAU) Detailed and harmonised vegetation modelling Underground legal/physical spaces; 3D underground parcels and rights 3.0 and Schema/examples public? Padsala al. Yes (schema + data) 7/16 have .xsd CityGML v3 has 2 with *.xsd No Yes (schema + data) 4
  5. CityJSON Extensions aimed at solving the issues that “there is

    no system for broadly sharing ADEs and related technologies” and calls for “a platform that aggregates knowledge and resources related to ADE development from various countries and cities [to] enable the reuse of these resources in next-generation development, and facilitate the spread of the standard.” { 1 "type": "CityJSONExtension", "name": "noise", "description": "Extension to model the noise", "url": "https://cityjson.github.io/extensions/ → ω→ noise/2.0.0/noise.ext.json", "version": "2.0.0", "versionCityJSON": "2.0", "extraAttributes": {...}, "extraCityObjects": { "+NoiseBuilding": { "allOf": [ { "$ref": "cityobjects.json#/_AbstractBu → ω→ ilding" }, { "properties": { "type": { "enum": ["+NoiseBuilding"] ω→ }, "attributes": { "properties": { "buildingLDenMin": {"type": ω→ "number"} } } }, "required": ["type"] } ] } }, "extraRootProperties": {}, "extraSemanticSurfaces": {} 2 3 4 5 6 7 2. Related work 2.1 ADEs for CityGML v2.0 and earlier 8 9 10 11 12 ADEs were already possible with CityGML v1.0 (released in 2008) through GML substitution groups and generic application properties, and a few early extensions were developed by research groups and SIG3D members. However, the concept was formalised and better documented with CityGML v2.0 (Gröger and Plümer, 2012), and almost all named ADEs—including the 44 reviewed by Biljecki et al. (2018)—are specified against v2.0. When v2.0 was released, earlier v1.0-era ADEs were generally migrated and re-published as v2.0 extensions. 13 14 15 16 17 18 19 20 ADEs are defined as extensions to the CityGML data model, are implemented as XML Schema Definition (XSD) schemas, and define custom data types and constraints. Practitioners have to define their own XSD schemas, and those should be made available for understanding and validating a dataset. Van den Brink et al. (2013) illustrate how complex developing an ADE can be in practice, requiring expertise in UML modelling, XSD design, and the CityGML data model itself. It should be mentioned that the CityGML data model prescribes a finite set of attributes for its main classes, and that if extra attributes are required they must be defined in an ADE. In Table 1, I extend the survey of Biljecki et al. (2018) with ADEs that have been substantially improved or newly released 21 22 23 24 25 26 27 28 29 } Figure 1. Example of a CityJSON Extension file: noise.ext.json 2.3 CityJSON Extensions 5
  6. 8

  7. 9

  8. 10

  9. CityJSON Extensions: most *.ext.json are publicly available Table 2. Known

    CityJSON Extensions, from the public registry and the scientific literature. Extension Purpose Reference(s) Schema public? In registry? 1 2 3 4 5 6 7 8 9 10 Energy (space heating) LCC (topology) Perception Noise MultiRoofs Quality Shed Point clouds Historical cities Dynamizer Space heating demand calculation Linear cell complex topology Visual perception of buildings Noise emission simulation EU roof modelling project Data quality modelling Template/example Point cloud support Historical city models Dynamic data integration Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes No No Yes 11 12 Spatial planning val3dity 3D spatial plans (LADM) Geometry validation reports Tufan et al. (2022) Vitalis et al. (2019) Lei et al. (2024) — — — — Nys et al. (2021) Vaienti et al. (2022) Boumhidi et al. (2024), Jeddoub (2026) Guler (2023) – Yes Yes No Yes { "type": "CityJSON", "version": "2.0", file may reference any reachable URL (see line 10 of Fig ure 3), and practitioners remain free to host their Extension 12 elsewhere. However, the registry offers several advantages ove
  10. Some thoughts since I’m still on time… 1. If you

    work on Extensions (or ADEs) please make the schemas + example datasets publicly available 2. Make a PR to the Extension registry 3. Your favourite LLM can now just learn from the specs of CityJSON and the examples, so making a new Extension should be even easier val3dity Extension was vibe-coded I was told! 18