Structured city geometry for digital-twin programs.

CityGML preparation, semantic building models, format conversion and validation for urban digital infrastructure.

THE OUTCOME

We convert spatial source data into interoperable 3D city content with explicit schemas, attributes and validation evidence.

Request a pilot ↗︎
BEST FIT

A focused production service.

  • Municipal 3D data programs
  • CityGML conversion and validation
  • Project-specific 3D data exchange requirements
DELIVERABLES

What arrives.

Final scope follows your project specification and accepted calibration sample.

01

CityGML building models

✓
02

LOD-aligned 3D geometry

✓
03

Semantic attribute enrichment

✓
04

2D-to-3D data conversion

✓
05

Schema and geometry validation

✓
06

PLATEAU-oriented production support

✓
PRODUCTION WORKFLOW

Controlled from input to acceptance.

Each stage has an explicit output, responsible reviewer and defined check.

01

Source assessment

Available footprints, elevation, imagery, BIM and registry data are mapped to the target model.

02

Geometry construction

Models are generated and refined at the appropriate level of detail for the intended use.

03

Semantic enrichment

Attributes and object relationships are populated against the required application schema.

04

Validation

Schema, geometry, coordinates, identifiers and completeness are checked with reproducible reports.

FORMATS TO CONFIRM IN PILOTCityGMLCityJSON3D TilesGeoPackageOBJIFC
SPECIFICATIONS TO AGREEOGC CityGMLPLATEAU specificationsCityJSONClient application schema
INPUTS AND ACCEPTANCE

Define a handoff your team can verify.

Provide source footprints and elevations, the target model and version, required level of detail, semantic fields, coordinate system and a sample accepted by the receiving platform.

  • Validate the agreed schema, identifiers and required attributes
  • Check geometry and semantics against the selected level of detail
  • Test a representative export in the receiving software
SCOPE LIMITA valid exchange file does not prove fitness for every simulation or planning use. Model detail and inferred geometry must be declared. Confirm each target format through the pilot.DELIVERY EVIDENCEAgree the output inventory, source references, validation results and exception log. Set review deadlines and correction responsibilities in the written scope.
COMMON QUESTIONS

Before a pilot.

Can you support Japan’s PLATEAU ecosystem?+

PLATEAU-related work needs the applicable specification, language requirements and sample data reviewed first. Confirm feasibility, schema version, validation tools and acceptance criteria during scoping.

Can you convert existing GIS buildings to 3D?+

Usually. Suitability depends on the available heights, roof information, terrain and required level of detail.

Do you build visualization applications?+

Our primary service is structured data production. Viewer integration and web delivery can be scoped with implementation partners when required.

CALIBRATE BEFORE YOU SCALE

Define the source, output and review boundary.

Share a representative area, the working template and the acceptance conditions your team will use.

Start with a short brief. Fields marked optional can be left blank; you do not need to have a specification ready.

Send a description only. Do not include source-data links, passwords, controlled data or personal information about other people. Data transfer and any confidentiality requirements should be agreed separately.