"CityGML 2.0编码标准文档及翻译计划"

需积分: 0 115 浏览量更新于2024-01-14 收藏 8.75MB PDF 举报

CityGML是一种用于表示三维城市和地理信息的编码标准。该标准由Open Geospatial Consortium（OGC）制定，并于2012年发布。它旨在提供一个统一的数据模型和编码规范，以便不同的应用程序和系统能够共享、交换和分析城市地理信息。 CityGML的核心概念是将城市空间信息按照层次化的方式进行组织和存储。它定义了一组对象类和属性，用于描述城市中的建筑物、道路、土地利用、水体等要素。通过这些对象类和属性，用户可以描述和分析城市的不同方面，如建筑物的几何形状、材质、用途等。 CityGML还支持多种不同的编码模式，包括XML（基于文本的编码模式）、GML（地理标记语言）和二进制编码模式。这使得CityGML可以满足不同应用场景和需求的要求。与其他类似的标准相比，CityGML具有以下几个优势和特点： 1. 多层次的数据模型：CityGML提供了一个层次化的数据模型，允许用户从整体到局部地描述城市空间信息。这种层次结构使得信息的组织和管理更加灵活和高效。 2. 多维数据表示：CityGML不仅可以描述城市的几何形状和拓扑关系，还可以表示其他属性信息，如地物的用途、材质、历史背景等。这种多维数据表示使得用户可以更全面和准确地分析城市信息。 3. 可扩展性和互操作性：CityGML的数据模型和编码规范是开放和可扩展的，可以轻松地集成和扩展到其他地理信息系统和应用程序中。这使得用户可以方便地与其他系统进行数据交换和共享。 4. 开放标准：CityGML是一个开放标准，任何人都可以免费获取并使用。这使得用户可以自由地使用和开发符合CityGML标准的应用程序和工具。目前，CityGML已经在全球范围内得到广泛应用，尤其在城市规划、城市管理、建筑设计和仿真等领域。它为用户提供了一个统一的数据模型和编码规范，使得不同应用程序和系统能够无缝集成和共享城市地理信息。同时，CityGML也为搞三维GIS和BIM GIS的同仁们提供了一个参考和指导，促进了相关技术的发展和应用。总之，CityGML是一个用于表示和编码城市地理信息的标准。它提供了一个统一的数据模型和编码规范，使得不同应用程序和系统能够共享和交换城市空间信息。通过CityGML，用户可以更全面、准确地描述和分析城市信息，促进了城市规划和管理的发展。

xvi

or built structures can be represented. This coherent model structure facilitates the similar understanding of

semantic entities and helps to reduce software implementation efforts. Both the Bridge and the Tunnel model

introduce further concepts and model elements which are specific to bridges and tunnels respectively.

Additions to existing thematic modules

 CityGML Core module (cf. chapter 10.1)

Two new optional attributes have been added to the abstract base class core:_CityObject within the

CityGML Core module: relativeToTerrain and relativeToWater. These attributes denote the feature’s

location with respect to the terrain and water surface in a qualitative way, and thus facilitate simple and

efficient queries (e.g., for the number of subsurface buildings) without the need for an additional digital

terrain model or a model of the water body.

 Building module (cf. chapter 10.3)

o LOD0 representation

Buildings can now be represented in LOD0 by footprint and/or roof edge polygons. This al-

lows the easy integration of existing 2D data and of roof reconstructions from aerial and satel-

lite imagery into a 3D city model. The representations are restricted to horizontal, 3-

dimensional surfaces.

o Additional thematic boundary surfaces

In order to semantically classify parts of the outer building shell which are neither horizontal

wall surfaces nor parts of the roof, two additional boundary surfaces are introduced:

OuterFloorSurface and OuterCeilingSurface.

o Additional relations to thematic boundary surfaces

In addition to _AbstractBuilding and Room, the surface geometries of BuildingInstallation and

IntBuildingInstallation features can now be semantically classified using thematic boundary

surfaces. For example, this facilitates the semantic differentiation between roof and wall sur-

faces of dormers which are modeled as BuildingInstallation.

o Additional use of implicit geometries

Implicit geometries (cf. chapter 8.3) are now available for the representation of _Opening,

BuildingInstallation, and IntBuildingInstallation in addition to BuildingFurniture. A prototyp-

ical geometry for these city objects can thus be stored once and instantiated at different loca-

tions in the 3D city model.

 Generics module (cf. chapter 10.12)

Two generic attributes have been added to the Generics module: MeasureAttribute and

GenericAttributeSet. A MeasureAttribute facilitates the representation of measured values together with

a reference to the employed unit. A GenericAttributeSet is a named collection of arbitrary generic at-

tributes. It provides an optional codeSpace attribute to denote the authority organization who defined

the attribute set.

 LandUse module (cf. chapter 10.10)

The scope of the feature type LandUse has been broadened to comprise both areas of the earth’s surface

dedicated to a specific land use and areas of the earth’s surface having a specific land cover with or

without vegetation.

 Attributes class, function, and usage (all modules)

In order to harmonize the use of the attributes class, function, and usage, this attribute triplet has been

complemented for all feature classes that at least provided one of the attributes in CityGML 1.0.

Additions to the CityGML code list mechanism

In CityGML, code lists providing the allowed values for enumerative attributes such as class, function, and

usage can be specified outside the CityGML schema by any organization or information community according to

their specific information needs. This mechanism is, however, not fully reflected in the CityGML 1.0 encoding

schema, because in a CityGML 1.0 instance document a corresponding attribute cannot point to the dictionary

with the used code list values. This has been corrected for CityGML 2.0: All attributes taking values from code

lists are now of type gml:CodeType following the GML 3.1.1 mechanism for the encoding of code list values (cf.

OpenGIS

Encoding Standard

OGC 12-019

OGC® City Geography Markup Language (CityGML)

Encoding Standard

1 Scope

This document is an OGC Encoding Standard for the representation, storage and exchange of virtual 3D city and

landscape models. CityGML is implemented as an application schema of the Geography Markup Language

version 3.1.1 (GML3).

CityGML models both complex and georeferenced 3D vector data along with the semantics associated with the

data. In contrast to other 3D vector formats, CityGML is based on a rich, general purpose information model in

addition to geometry and appearance information. For specific domain areas, CityGML also provides an exten-

sion mechanism to enrich the data with identifiable features under preservation of semantic interoperability.

Targeted application areas explicitly include urban and landscape planning; architectural design; tourist and

leisure activities; 3D cadastres; environmental simulations; mobile telecommunications; disaster management;

homeland security; vehicle and pedestrian navigation; training simulators and mobile robotics.

CityGML is considered a source format for 3D portraying. The semantic information contained in the model can

be used in the styling process which generates computer graphics represented e.g. as KML/COLLADA or X3D

files. The appropriate OGC Portrayal Web Service for this process is the OGC Web 3D Service (W3DS). An

image-based 3D portrayal service for virtual 3D landscape and city models is provided by the OGC Web View

Service (WVS).

Features of CityGML:

 Geospatial information model (ontology) for urban landscapes based on the ISO 191xx family

 GML3 representation of 3D geometries, based on the ISO 19107 model

 Representation of object surface characteristics (e.g. textures, materials)

 Taxonomies and aggregations

o Digital Terrain Models as a combination of (including nested) triangulated irregular networks

(TINs), regular rasters, break and skeleton lines, mass points

o Sites (currently buildings, bridges, and tunnels)

o Vegetation (areas, volumes, and solitary objects with vegetation classification)

o Water bodies (volumes, surfaces)

o Transportation facilities (both graph structures and 3D surface data)

o Land use (representation of areas of the earth’s surface dedicated to a specific land use)

o City furniture

o Generic city objects and attributes

o User-definable (recursive) grouping

 Multiscale model with 5 well-defined consecutive Levels of Detail (LOD):

o LOD0 – regional, landscape

o LOD1 – city, region

o LOD2 – city districts, projects

o LOD3 – architectural models (outside), landmarks

o LOD4 – architectural models (interior)

 Multiple representations in different LODs simultaneously; generalisation relations between objects in

different LODs

 Optional topological connections between feature (sub)geometries

 Application Domain Extensions (ADE): Specific “hooks” in the CityGML schema allow to define ap-

plication specific extensions, for example for noise pollution simulation, or to augment CityGML by

properties of the new National Building Information Model Standard (NBIMS) in the U.S.

2 Conformance

Conformance targets addressed by this International standard are CityGML instance documents only. Future

revisions of this International Standard may also address consumers or producers as conformance targets.

Clauses 8 to 10 of this International standard specify separate CityGML XML Schema definitions and normative

aspects, i.e. CityGML modules, which shall be used in CityGML instance documents in accordance with clause

7. Implementations are not required to support the full range of capabilities provided by the universe of all

CityGML modules. Valid partial implementations are supported following the rules and guidelines for CityGML

profiles in chapter 7.2.

CityGML instance documents claiming conformance to this International Standard shall:

a) conform to the rules and requirements specified in clauses 7 to 10;

b) pass all relevant test cases of the abstract test suite in annex B.1;

c) satisfy all relevant conformance classes of the abstract test suite related to CityGML modules in annex

B.2.

3 Normative references

The following normative documents contain provisions which, through reference in this text, constitute provi-

sions of this part of OGC 12-019. For dated references, subsequent amendments to, or revisions of, any of these

publications do not apply. However, parties to agreements based on this part of OGC 12-019 are encouraged to

investigate the possibility of applying the most recent editions of the normative documents indicated below. For

undated references, the latest edition of the normative document referred to applies.

The following documents are indispensable for the application of the CityGML standard. The geometry model of

GML 3.1.1 is used except for some added concepts like implicit geometries (cf. chapter 8.2). The appearance

model (cf. chapter 9) draws concepts from both X3D and COLLADA. Addresses are represented using the

OASIS extensible Address Language xAL.

ISO 8601:2004, Data elements and interchange formats – Information interchange – Representation of dates

and times

ISO/TS 19103:2005, Geographic Information – Conceptual Schema Language

ISO 19105:2000, Geographic information – Conformance and testing

ISO 19107:2003, Geographic Information – Spatial Schema

ISO 19109:2005, Geographic Information – Rules for Application Schemas

ISO 19111:2003, Geographic information – Spatial referencing by coordinates

ISO 19115:2003, Geographic Information – Metadata

ISO 19123:2005, Geographic Information – Coverages

ISO/TS 19139:2007, Geographic Information – Metadata – XML schema implementation

ISO/IEC 19775:2004, X3D Abstract Specification

OpenGIS

Abstract Specification Topic 0, Overview, OGC document 04-084

OpenGIS

Abstract Specification Topic 5, The OpenGIS Feature, OGC document 99-105r2

OpenGIS

Abstract Specification Topic 8, Relations between Features, OGC document 99-108r2

OpenGIS

Abstract Specification Topic 10, Feature Collections, OGC document 99-110

OpenGIS

Geography Markup Language Implementation Specification, Version 3.1.1, OGC document 03-105r1

OpenGIS

GML 3.1.1 Simple Dictionary Profile, Version 1.0.0, OGC document 05-099r2

IETF RFC 2045 & 2046, Multipurpose Internet Mail Extensions (MIME). (November 1996)

IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax. (August 1998)

W3C XLink, XML Linking Language (XLink) Version 1.0. W3C Recommendation (27 June 2001)

剩余343页未读，继续阅读

飞天小贱

粉丝: 6

"CityGML 2.0编码标准文档及翻译计划"

CityGML-3.0Encodings:CityGML 3.0概念模型的编码

citygml4j：适用于CityGML的开源Java API

CityGML-3.0CM:CityGML 3.0概念模型

CityGML编码规范(2.0).pdf.pdf

OGC CityGML 2.0标准详解

三维数字城市citygml库源代码

CityGML三维城市模型编码标准的详细介绍

CityGML 2.0官方编码规范详解：模块化与空间模型

检索CityGML SRS维度和名称的JavaScript模块使用指南

CityGML三维建模及其应用研究

最新资源