cjval: schema-validation of CityJSON + CityJSONSeq datasets

A Rust library and binaries to validate the syntax of CityJSON objects (CityJSON + CityJSONSeq).

It validates against the CityJSON schemas and additional functions have been implemented (because these checks cannot be expressed with JSON Schemas).

The following error checks are performed:

1. JSON syntax: is it a valid JSON object?
2. CityJSON schemas: validation against the schemas (CityJSON v1.0 + v1.1 + v2.0)
3. Extension schemas: validate against the extra schemas if there's an Extension (those are automatically fetched from a URL)
4. parents_children_consistency: if a City Object references another in its "children", this ensures that the child exists. And that the child has the parent in its "parents"
5. wrong_vertex_index: checks if all vertex indices exist in the list of vertices
6. semantics_array: checks if the arrays for the semantics in the geometries have the same shape as that of the geometry and if the values are consistent
7. textures: checks if the arrays for the textures are coherent (if the vertices exist + if the texture exists)
8. materials: checks if the arrays for the materials are coherent with the geometry objects and if the material exists

It also verifies the following, these are not errors but warnings since the file is still considered valid and usable, but they can make the file larger and some parsers might not understand all the properties:

1. extra_root_properties: if CityJSON has extra root properties, these should be documented in an Extension. If not this warning is returned
2. duplicate_vertices: duplicated vertices in "vertices" are allowed, but they take up space and decrease the topological relationships explicitly in the file. If there are any, cjio has the operator clean to fix this automatically.
3. unused_vertices: vertices that are not referenced in the file, they take extra space. If there are any, cjio has the operator clean to fix this automatically.

A Rust library + 2 binaries

cjval is a Rust library, and has 2 different binaries:

1. cjval to validate a CityJSON file or a CityJSONSeq stream (it downloads Extensions automatically if the file contains some)
2. cjvalext to validate a CityJSON Extension file

Installation/compilation

To install the binaries on your system easily

1. install the Rust compiler
2. cargo install cjval --features build-binary

To compile the project (and eventually modify it)

1. install the Rust compiler
2. git clone https://github.com/cityjson/cjval.git
3. cargo build --release --features build-binary (this will ensure the binaries are compiled too)
4. ./target/release/cjval myfile.json

Web application

The code is used at https://validator.cityjson.org, it is compiled as a WebAssembly (WASM code here) and a simple GUI was built.

CLI Usage

For CityJSON files

The CityJSON schemas are packaged with the binary, so it suffices to:

cjval myfile.city.json --verbose

(the latest schemas of a X.Y version will be automatically fetched)

--verbose is used to get a detailed report per error check.

If the file contains one or more Extensions, eg:

{
  "type": "CityJSON",
  "version": "2.0",
  "extensions":
  {
    "Potato":
    {
      "url": "https://www.cityjson.org/extensions/potato.ext.json",
      "version": "1.0"
    }
  }
...  

then cjval will download the Extension schema files automatically.

If instead you want to use your own local Extension schema(s), you can pass them as argument with the -e flag and this will overwrite the automatic download:

cjval myfile.city.json -e ./myextensions/generic.ext.json

For CityJSONSeq

To validate a stream of CityJSONFeature, you need to 'cat' the file:

cat mystream.city.jsonl | cjval --verbose

Or you can use cjseq to generate the stream from a CityJSON file:

cjseq cat -f myfile.city.json | cjval --verbose

and you'll get a short report per line (which is one CityJSON followed by several CityJSONFeature).

--verbose is used to get a detailed report per line, if not used then only lines with errors are reported.

Contributors

• @hugoledoux
• @josfeenstra (started the project for an MSc Geomatics course at TU Delft, original code)