In its most common implementation, which is the one generally used to disseminate and exchange data, CityGML datasets consist of a set of XML files and possibly some accompanying image files that are used as textures. Each text file can represent a part of the dataset, such as a specific region, a specific type of object (such as a set of roads), or a predefined LoD. The structure of a CityGML file is a hierarchy that ultimately reaches down to individual objects and their attributes. These objects have a geometry that is described using GML.
Another important implementation of CityGML is the one of 3D City DB, which stores CityGML in a database.1
The OGC Members adopted version 1.0.0 of CityGML as an official OGC Standard in August 2008.2 In late 2011, the OGC Members approved version CityGML 2.0.0. CityGML 3.0 GML Encoding Specification is supposed to be published early 2019,3 while CityGML 3.0 Conceptual Model draft is already publicly available at the official Github repository.
"Home". 3dcitydb.net. http://www.3dcitydb.net/ ↩
"OGC(R) Adopts CityGML Encoding Standard". OGC®. 19 August 2008. Archived from the original on 19 November 2008. Retrieved 27 September 2008. https://web.archive.org/web/20081119094900/http://www.opengeospatial.org/pressroom/pressreleases/899 ↩
"Archived CityGML 3.0 Development Repo". GitHub. 24 August 2021. https://github.com/opengeospatial/CityGML-3.0 ↩