• Tidak ada hasil yang ditemukan

Change Requests | OGC

N/A
N/A
Protected

Academic year: 2017

Membagikan "Change Requests | OGC"

Copied!
2
0
0

Teks penuh

(1)

All Fields marked with

*

are mandatory.

Change Request

#:

70

Assigned OGC

Document #:

10-053

Name:

*

Claus Nagel

Organization:

*

Special Interest Group 3D (SIG 3D)

Email:

*

[email protected]

Document

Name/Version:

*

City Geography Markup Language (CityGML) Encoding Standard / 1.0.0

OGC Project

Document:

*

08-007r1

If this is a revision of a previous submission and you have a Change Request Number, then check here:

Enter the CR number here:

Enter the Revsion Number that you are revising here:

Title:

*

Thematic module for walls in cities

Source:

*

Special Interest Group 3D (SIG 3D)

Work item code:

Category:

*

Reason for

change:

*

The semantic data model of CityGML 1.0 lacks a model for the representation of walls in cities. However, walls are essential features of cities and it should be possible to adequately represent them in virtual 3D city and landscape models. "City wall" should be broadly defined to not only comprise ancient fortifications, but also smaller walls such as garden walls or fences. As for CityGML 1.0, the only possibility to model and exchange walls in cities is to use a GenericCityObject as proxy or to define a corresponding ADE. Both approaches face disadvantages.

First, GenericCityObjects are simple in structure. However, the representation of city walls requires a semantically rich model. Comparable to buildings, walls can be decomposed into individual parts. Each part may contain interior structures such as rooms, interior installations like pipes, or room furniture. The boundary

(2)

surfaces of city walls can be further classified as, for example, wall or roof surfaces. Outdoor built structures such as staircases or balconies might be attached to the city wall. Further thematic classes are needed, for example, to represent gates or towers. Second, city walls are not specific to just a single application domain. Several ADEs could emerge proposing different semantic models. What is required is a common and standardized thematic module on city walls in CityGML.

Summary of

change:

*

Incorporate a new thematic module providing a data model for the representation of walls in cities into the CityGML standard. "City wall" should be broadly defined to not only comprise ancient

fortifications, but also smaller walls such as garden walls or fences. This extension can be realized without breaking backwards compatibility.

Consequences if

not approved:

City walls as relevant features of urban and regional models cannot be modeled and exchanged in a standardized way. This leads to a

significant lack in semantic interoperability since either

GenericCityObjects as proxies or several non-standardized ADEs will have to be used for modeling city walls.

Clauses affected:

*

7, 10

Additional

Documents

affected:

Supporting

Documentation:

Comments:

Status:

Disposition:

Referensi

Dokumen terkait

The geometric concepts of the SFA-CA and their respective correspondences to concepts of Spatial schema are described as follows. ⎯ The SFA-CA deals only with at most

For example, the format should include a fixed content structure (e.g., a single root CityGML document and a fixed subfolder structure for different types of related files), and

* The code list encoding in CityGML provides no mechanism to point to the dictionary with the used code list values (and it does not use the GML mechanism) → noone can interpret

page 32 line 6 = > \"The dual graph denoting cell adjacency within the subspace layer (see dotted edges between the nodes of the subspace) now contains the

"A bounding rectangle, encoded as specified in OGC 06-131r3, indicating that all resources which intersect that BBOX shall be retrieved from some data

The GMLCOV schema has a definition for a type called "AbstractDiscreteCoverageType" which is not specified as abstract=true. Furthermore, this type is used unchanged as

where an attribute or role is intended to redefine one originally defined on a parent class, this should be indicated in the model using a tagged value "ownedBy" that

The proposed change will allow the creation of a GetCapabilities request that return only a given sub-set of the layers. Summary