Skip to content

3D city model

A georeferenced three-dimensional digital representation of urban terrain, buildings, infrastructure, vegetation and related semantic objects.

Version
v1 · 2026-09-08 · History
Domain-specific #
3158
Origin domain
geospatial modeling
Subdomain
geospatial modeling

Core Idea

Geometric detail, semantic richness, temporal currency and coordinate reference must be stated, and a visualization mesh alone may lack the object identity needed for a city model. Survey, mapping and design data are aligned in a common coordinate system, reconstructed as 3D geometry and linked to typed urban objects and attributes for visualization and analysis. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

3D city model belongs to geospatial modeling and is useful where the analyst can specify the typed geospatial modeling carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the modeled urban extent and time, coordinate reference and vertical datum, terrain and object classes, geometry topology texture and semantics, levels of detail, source datasets and accuracy, identifiers and relationships, update and version policy, interoperability schema and intended analytical uses are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the modeled urban extent and time, coordinate reference and vertical datum, terrain and object classes, geometry topology texture and semantics, levels of detail, source datasets and accuracy, identifiers and relationships, update and version policy, interoperability schema and intended analytical uses are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to 3D city model. 3D city model compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed geospatial modeling carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the modeled urban extent and time, coordinate reference and vertical datum, terrain and object classes, geometry topology texture and semantics, levels of detail, source datasets and accuracy, identifiers and relationships, update and version policy, interoperability schema and intended analytical uses are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of geospatial modeling because they reuse the typed geospatial modeling carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Survey, mapping and design data are aligned in a common coordinate system, reconstructed as 3D geometry and linked to typed urban objects and attributes for visualization and analysis., and type the carrier, state every parameter and convention in the definition, test that the modeled urban extent and time, coordinate reference and vertical datum, terrain and object classes, geometry topology texture and semantics, levels of detail, source datasets and accuracy, identifiers and relationships, update and version policy, interoperability schema and intended analytical uses are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for 3D city modelParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.3D city modelDOMAINPrime abstraction: Representation — is a kind ofRepresentationPRIME

Current abstraction 3D city model Domain-specific

Parents (1) — more general patterns this builds on

  • 3D city model is a kind of Representation Prime

    The proposed strict upward parent is prime:representation.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

3D city model sits in a crowded region of the domain-specific corpus (34th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Cartography, Geopolitics & Spatial Representation (11 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08