Skip to content

Invalid Cases

Deliberately broken cases that software should reject.

This section contains 4 cases. Each item links to the full case page.

Cases

  • invalid_cityjsonfeature_root_id_unresolved: Hand-written invalid CityJSONFeature where the root id does not match any CityObject in the same feature. Must be rejected.
  • invalid_missing_type: Synthetic invalid CityJSON fixture that omits the required top-level type field. Valid JSON, but must be rejected at schema validation before any geometry or data access.
  • invalid_out_of_range_vertex_index: Synthetic invalid CityJSON fixture with a boundary that references a vertex index outside the available vertex array. Valid JSON, but must be rejected during geometry validation.
  • invalid_u64_f64_bounds: Synthetic invalid CityJSON fixture that uses stored vertex values above u64::MAX and transform values outside the f64 range. The input remains syntactically valid JSON, but implementations that coerce the numeric fields into bounded integer or float types should reject it.