Public comment requested: adoption of CityJSON v1.1 as Community Standard

Status: 
Please note:  This Request is scheduled to close on 9 September 2022.
Open Date: 
Wednesday, 2022-08-10
Closing Date: 
Friday, 2022-09-09

The Open Geospatial Consortium (OGC) seeks public comment on an updated version (v1.1) of the CityJSON Community Standard. The proposed update contains significant improvements over v1.0, including support for the OGC CityGML data model version 3.0 and support for handling large CityJSON files through streaming. 

CityJSON defines ways to describe, in a JSON encoding, most of the common 3D features and objects found in cities (such as buildings, roads, rivers, bridges, vegetation, and city furniture) and the relationships between them. It also defines how to encode different standard levels of detail (LoDs) for the 3D objects in JSON, which allows users to represent different resolutions of objects for different applications and purposes. A list of applications and use-cases for CityJSON is available on the CityJSON website.

The aim of CityJSON is to offer an alternative to the GML encoding of CityGML, which can be verbose and therefore complex to work with. CityJSON aims at being easy-to-use, both for reading datasets, and for creating them. It was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. It was also designed to be compact, typically compressing publicly available CityGML files by 6x.

A CityJSON file describes both the geometry and the semantics of the city features of a given area. A CityJSON object, representing a city, is as ‘flat’ as possible, i.e., the hierarchy of CityGML has been flattened out and only the city objects which are ‘leaves’ of this hierarchy are implemented. This considerably simplifies the storage of a city model, and furthermore does not mean that information is lost.

CityJSON v1.0 was accepted as an OGC Community standard in August 2021. CityJSON version 1.0 is a JSON-based encoding for a subset of the OGC CityGML data model version 2.0.0.

Comment: 

Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template

Subscribe: 

You may wish to be added to the distribution list to receive comments as they are submitted


Subscribing to the the list will also allow you to view comments already received, which can be found in the List Archives.