Conformance requirements Change Requests | OGC
Copyright © 2012 Open Geospatial Consortium. 45
element GeoreferencedTexture. External georeference may be provided by the texture image file itself e.g. GeoTIFF or by an accompanying world file.
Referential integrity
5. The appearanceMember element type: AppearancePropertyType may contain an Appearance element
inline or an XLink reference to a remote Appearance element using the XLink concept of GML 3.1.1. In the latter case, the xlink:href attribute of the appearanceMember element may only point to a remote
Appearance element where remote Appearance elements are located in another document or elsewhere
in the same document. Either the contained element or the reference must be given, but neither both nor none.
6. The appearance property type: AppearancePropertyType of the element core:_CityObject may con-
tain an Appearance element inline or an XLink reference to a remote Appearance element using the XLink concept of GML 3.1.1. In the latter case, the xlink:href attribute of the appearance property may
only point to a remote Appearance element where remote Appearance elements are located in another document or elsewhere in the same document. Either the contained element or the reference must be
given, but neither both nor none.
7. The surfaceDataMember property type: SurfaceDataPropertyType of the element Appearance may
contain a _SurfaceData element inline or an XLink reference to a remote _SurfaceData element using the XLink concept of GML 3.1.1. In the latter case, the xlink:href attribute of the surfaceDataMember
property may only point to a remote _SurfaceData element where remote _SurfaceData elements are located in another document or elsewhere in the same document. Either the contained element or the
reference must be given, but neither both nor none.
8. The target property type: TextureAssociationType of the element ParameterizedTexture may contain a
_TextureParameterization element inline or an XLink reference to a remote _ TextureParameterization
element using the XLink concept of GML 3.1.1. In the latter case, the xlink:href attribute of the target property may only point to a remote _ TextureParameterization element where remote _ TexturePa-
rameterization elements are located in another document or elsewhere in the same document. Either
the contained element or the reference must be given, but neither both nor none. 9.
The target property type xs:anyURI of the element GeoreferencedTexture shall specify the gml:id of the target surface geometry object which may only be of type gml:AbstractSurfaceType or
gml:MultiSurface .
10. The uri attribute of the complex type TextureAssociationType shall specify the gml:id of the target sur-
face geometry object which may only be of type gml:AbstractSurfaceType or gml:MultiSurface. 11.
The ring attribute of the textureCoordinates property of the element TexCoordList shall specify the gml:id
of the target surface geometry object which may only be of type gml:LinearRing. 12.
The target property type xs:anyURI of the element X3DMaterial shall specify the gml:id of the target surface geometry object which may only be of type gml:AbstractSurfaceType or gml:MultiSurface.
46 Copyright © 2012 Open Geospatial Consortium.
9.8 Material model of previous CityGML versions [deprecated]
Since GML3 has no built-in concept for the representation of surface materials, previous versions of CityGML extend the GML3 geometry model by the class TexturedSurface, which allows for assigning appearance proper-
ties colors, shininess, transparency and textures to 3D surfaces. The definition of the appearance properties is adopted from the X3D specification. This approach for appearance modelling has been deprecated due to inher-
ent limitations. However, in order to provide a certain degree of backwards compatibility for already existing CityGML implementations, the approach has been incorporated into CityGML version 1.0 and version 2.0 as a
separate extension module called TexturedSurface. By this means, implementations may employ the old material model by supporting this module. Please note, that appearance information modelled according to the Textured-
Surface
mod ule can be converted without information loss to the concepts provided by CityGML’s Appearance
module that has been introduced in the previous clauses of this chapter. Thus, the use of the TexturedSurface module is strongly discouraged and implementations should only stick to the Appearance module instead.
Moreover, the TexturedSurface module is expected to be removed in future versions of CityGML.
For the TexturedSurface module, each surface or composite surface can be specialized to a TexturedSurface, which can be assigned Materials colors, shininess, transparency or SimpleTextures. Fig. 20 depicts the UML
diagram, for XML schema definition see annex A.14.
Fig. 20 : UML diagram of CityGML’s material model. Please note, that this approach for appearance modelling has been marked as deprecat-
ed and is expected to be removed in future CityGML versions. Prefixes are used to indicate XML namespaces associated with model elements. Element names without a prefix are defined within the CityGML
TexturedSurface
module.
The concept of positioning textures on surfaces complies with the 3D computer graphics standard X3D web 3D 2004, a successor of VRML97. CityGML adds the class TexturedSurface to the geometry model of GML3
because there has been no appropriate texturing concept in ISO 19107 and in GML3.
A texture is specified as a raster image referenced by an URI Uniform Resource Identifier and can be an arbi- trary resource, even on the internet. Textures are positioned by employing the concept of texture coordinates, i.e.
each texture coordinate matches with exactly one 3D coordinate of the TexturedSurface Fig. 17. The use of texture coordinates allows an exact positioning and trimming of the texture on the surface geometry.
The color of a surface is defined by RGB values. These have to be in the range of 0 to 1. The frontOpacity and the backOpacity define the level of transparency of each surface. Their values have also to be in the range of 0
to 1, where 1 means completely covering and 0 denotes a completely transparent surface. The colors can be differentiated in diffuseColor color when illuminated by a source of light, emissiveColor color when self-
illuminating and specularColorshininess color for shiny surfaces.
Copyright © 2012 Open Geospatial Consortium. 47
Textures can be qualified by the attribute textureType. The textureType differentiates between textures which are specific for a certain object specific and prototypic textures being typical for that object surface typical.
Textures may also be classified as unknown.
_Appearance is derived from gml:AbstractGMLType to be referenced in an appearance property. The attribute
gml:id is inherited, whose value may be referenced by a XLink. _Appearance is the parent class of Material and
SimpleTexture .
XML namespace
The XML namespace of the CityGML TexturedSurface module is identified by the Uniform Resource Identifier URI http:www.opengis.netcitygmltexturedsurface2.0. Within the XML Schema definition of the Textured-
Surface module, this URI is also used to identify the default namespace.