• 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.

Name:

*

Gerhard Gröger

Organization:

*

Institute of Geodesy and Geoinformation, University of Bonn

Email:

*

[email protected]

Document

Name/Version:

*

City Geography Markup Language (CityGML) Encoding Standard / 2.0

OGC Project

Document:

*

12-019

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:

*

[CityGML SWG] Add Metadata to CityGML

Source:

*

Special Interest Group 3D (SIG 3D)

Work item code:

Category:

*

B (Addition of feature)

Reason for

change:

*

CityGML currently lacks a standardized specification of metadata. Metadata are crucial to assess the suitability of CityGML data sets for specific applications, and to interpret spatial data. The CR 13-029 (Meta data for city model) is restricted to metadata for a whole dataset. But also metadata at the level of a single feature or even a single attribute or geometry value is required. Hence, this change request complements/generalizes CR 13-029.

Summary of

change:

*

Add a specification for metadata to CityGML. Metadata defined in ISO 19115 (gml encoding: ISO 19139) should be selected and extended to

(2)

meet the needs of 3D city models. Metadata defined in the INSPIRE Building model which facilitate the interpretation of generalized 3D geometries (at the level of single geometries or attribute values) should be adapted.

Consequences if

not approved:

CityGML datasets enhanced with metadata at the level of features, attributes, or geometry values are currently not interoperable, since there is no standardized metadata model for 3D city models.

Clauses affected:

*

Multiple

Additional

Documents

affected:

Supporting

Documentation:

ISO 19115 ISO 19139

INSPIRE Data Specification on Buildings v. 3 rc 3 – Draft Technical Guidelines, Identifier D2.8.III.2_v3.0rc3.

Comments:

Status:

Assigned

Assigned To:

CityGML SWG

Disposition:

Referred

Referensi

Dokumen terkait

b) Test method: Verify that the ISO 19139 metadata element MD_Metadata.dataQualityInfo.DQ_DataQuality.report.result.DQ_ConformanceResult is correctly mapped to

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

Reason for change:  Application Domain Extensions (ADE) defined in CityGML (see clauses 6.12, 10.11, Annex G of OGC 08-007-r1) propose an extension mechanism which enables

There is an overlap between some themes in CityGML and the data themes identified by Inspire annexes, such as transportation networks, land use, terrain models or buildings.

"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

However, if a specific application has information needs to be modelled and exchanged which are beyond the scope of the CityGML data model, this application data can also

At the moment there is no general agreed set of meta data to identify the source, the actual creation time, the defined CityGML profile etc. of a city