├── FME workspace └── IFC2CityGML3.fmw ├── LICENSE ├── Readme.md ├── images ├── FZKHaus.jpg ├── FZKHaus_BuildingConstructiveElements.jpg ├── FZKHaus_BuildingInstallations_Doors_Windows.jpg └── FZKHaus_Rooms.jpg ├── input └── AC20-FZK-Haus.ifc ├── output └── FZK-Haus_CityGML3.gml └── xsds ├── CityGML_3.0.xsd ├── appearance.xsd ├── bridge.xsd ├── building.xsd ├── cityFurniture.xsd ├── cityGMLBase.xsd ├── cityObjectGroup.xsd ├── construction.xsd ├── dynamizer.xsd ├── generics.xsd ├── landUse.xsd ├── pointCloud.xsd ├── relief.xsd ├── transportation.xsd ├── tunnel.xsd ├── vegetation.xsd ├── versioning.xsd └── waterBody.xsd /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2019 Chair of Geoinformatics, Technical University of Munich 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /Readme.md: -------------------------------------------------------------------------------- 1 | # ifc-to-citygml3 2 | An FME workspace for converting IFC data sets to CityGML 3.0 data sets. 3 | 4 | 5 | ## FME workspace 6 | The FME workspace was originally created using FME 2019.0 (Build 19238), but was last executed using FME 2020.2 (Build 20806).
7 | Opening the workspace with other FME versions might lead to errors. 8 | 9 | The FME workspace makes use of the generic GML Writer to create the CityGML 3.0 data sets. 10 | 11 | The CityGML 3.0 XML schemata required by the FME workspace are provided in the 'xsds' folder.
12 | The XML schemata are equivalent to release 3.0.0-draft.2020.09.17.1 available in the [OGC CityGML 3.0 Encodings GitHub repository](https://github.com/opengeospatial/CityGML-3.0Encodings). 13 | 14 | Please note that CityGML 3.0 has not yet been published (but is quite stable now). Therefore, the XML schemata may be still subject to change.
15 | 16 | 17 | ## Test data sets 18 | The workspace was tested using the "FZK Haus" data set from: http://www.ifcwiki.org/index.php?title=KIT_IFC_Examples
19 | The data set is provided in the 'input' folder of this repository.
20 | The CityGML 3.0 data set created by the FME workspace is available in the 'output' folder. 21 | 22 | 23 | ## Mapping of IFC objects to CityGML 3.0 objects 24 | The table below shows the mapping of IFC objects to the corresponding objects in CityGML 3.0.
25 | The mapping makes use of the class 'BuildingConstructiveElement' that was newly introduced to CityGML 3.0 to allow for representing constructive elements from BIM datasets given in the IFC standard (e.g. the IFC classes 'IfcWall', 'IfcRoof', 'IfcBeam', 'IfcSlab', etc.) in CityGML. 26 | 27 | | IFC objects | CityGML 3.0 objects | 28 | | ------------------- | --------------------------- | 29 | | IfcProject | CityModel | 30 | | IfcSite | LandUse | 31 | | IfcBuilding | Building | 32 | | IfcBuildingStorey | Storey | 33 | | IfcSpace | BuildingRoom | 34 | | IfcWallStandardCase | BuildingConstructiveElement | 35 | | IfcBeam | BuildingConstructiveElement | 36 | | IfcSlab | BuildingConstructiveElement | 37 | | IfcMember | BuildingConstructiveElement | 38 | | IfcDoor | Door | 39 | | IfcWindow | Window | 40 | | IfcRailing | BuildingInstallation | 41 | | IfcStair | BuildingInstallation | 42 | 43 | 44 | ## Results 45 | Below are some screenshots of the transformed 'FZKHaus' data set visualised using the FME Data Inspector 2019.0. 46 | 47 | FZKHaus represented in CityGML 3.0: 48 | ![FZKHaus represented in CityGML 3.0](images/FZKHaus.jpg "FZKHaus represented in CityGML 3.0") 49 | 50 | FZKHaus - Rooms: 51 | ![FZKHaus - Rooms](images/FZKHaus_Rooms.jpg "FZKHaus - Rooms") 52 | 53 | FZKHaus - BuildingInstallations, Doors, and Windows: 54 | ![FZKHaus - BuildingInstallations, Doors, and Windows](images/FZKHaus_BuildingInstallations_Doors_Windows.jpg "FZKHaus - BuildingInstallations, Doors, and Windows") 55 | 56 | FZKHaus - BuildingConstructiveElements: 57 | ![FZKHaus - BuildingConstructiveElements](images/FZKHaus_BuildingConstructiveElements.jpg "FZKHaus - BuildingConstructiveElements") 58 | -------------------------------------------------------------------------------- /images/FZKHaus.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/tum-gis/ifc-to-citygml3/ba47b63d87b7beee75fb2790e17413d90a49031b/images/FZKHaus.jpg -------------------------------------------------------------------------------- /images/FZKHaus_BuildingConstructiveElements.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/tum-gis/ifc-to-citygml3/ba47b63d87b7beee75fb2790e17413d90a49031b/images/FZKHaus_BuildingConstructiveElements.jpg -------------------------------------------------------------------------------- /images/FZKHaus_BuildingInstallations_Doors_Windows.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/tum-gis/ifc-to-citygml3/ba47b63d87b7beee75fb2790e17413d90a49031b/images/FZKHaus_BuildingInstallations_Doors_Windows.jpg -------------------------------------------------------------------------------- /images/FZKHaus_Rooms.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/tum-gis/ifc-to-citygml3/ba47b63d87b7beee75fb2790e17413d90a49031b/images/FZKHaus_Rooms.jpg -------------------------------------------------------------------------------- /xsds/CityGML_3.0.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 7 | 8 | 9 | CityGML is an OGC Standard. 10 | Copyright (c) 2012 Open Geospatial Consortium. 11 | To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ . 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /xsds/appearance.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Appearance module supports the modelling of the observable surface properties of CityGML features in the form of textures and material. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfAbstractSurfaceData acts as a hook to define properties within an ADE that are to be added to AbstractSurfaceData. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfAbstractTexture acts as a hook to define properties within an ADE that are to be added to AbstractTexture. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ADEOfAppearance acts as a hook to define properties within an ADE that are to be added to an Appearance. 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | ADEOfGeoreferencedTexture acts as a hook to define properties within an ADE that are to be added to a GeoreferencedTexture. 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | ADEOfParameterizedTexture acts as a hook to define properties within an ADE that are to be added to a ParameterizedTexture. 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | ADEOfX3DMaterial acts as a hook to define properties within an ADE that are to be added to an X3DMaterial. 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | AbstractSurfaceData is the abstract superclass for different kinds of textures and material. 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | Indicates whether the texture or material is assigned to the front side or the back side of the surface geometry object. 98 | 99 | 100 | 101 | 102 | Augments AbstractSurfaceData with properties defined in an ADE. 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | AbstractTexture is the abstract superclass to represent the common attributes of the classes ParameterizedTexture and GeoreferencedTexture. 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | Specifies the URI that points to the external image data file. 128 | 129 | 130 | 131 | 132 | Specifies the MIME type of the external point cloud file. 133 | 134 | 135 | 136 | 137 | Indicates the specific type of the texture. 138 | 139 | 140 | 141 | 142 | Specifies the behaviour of the texture when the texture is smaller than the surface to which it is applied. 143 | 144 | 145 | 146 | 147 | Specifies the color of that part of the surface that is not covered by the texture. 148 | 149 | 150 | 151 | 152 | Augments AbstractTexture with properties defined in an ADE. 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | AbstractTextureParameterization is the abstract superclass for different kinds of texture parameterizations. 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | An Appearance is a collection of surface data, i.e. observable properties for surface geometry objects in the form of textures and material. 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | Specifies the topic of the Appearance. Each Appearance contains surface data for one theme only. Examples of themes are infrared radiation, noise pollution, or earthquake-induced structural stress. 191 | 192 | 193 | 194 | 195 | Relates to the surface data that are part of the Appearance. 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | Augments the Appearance with properties defined in an ADE. 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | Color is a list of three double values between 0 and 1 defining an RGB color value. 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | Color is a list of four double values between 0 and 1 defining an RGBA color value. Opacity value of 0 means transparent. 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | A GeoreferencedTexture is a texture that uses a planimetric projection. It contains an implicit parameterization that is either stored within the image file, an accompanying world file or specified using the orientation and referencePoint elements. 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | Indicates whether the georeference from the image file or the accompanying world file should be preferred. 253 | 254 | 255 | 256 | 257 | Relates to the 2D Point geometry that represents the center of the upper left image pixel in world space. 258 | 259 | 260 | 261 | 262 | Specifies the rotation and scaling of the image in form of a 2x2 matrix. 263 | 264 | 265 | 266 | 267 | Specifies the URI that points to the surface geometry objects to which the texture is applied. 268 | 269 | 270 | 271 | 272 | Augments the GeoreferencedTexture with properties defined in an ADE. 273 | 274 | 275 | 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | 284 | 285 | 286 | 287 | 288 | A ParameterizedTexture is a texture that uses texture coordinates or a transformation matrix for parameterization. 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | Relates to the texture coordinates or transformation matrices used for parameterization. 298 | 299 | 300 | 301 | 302 | Augments the ParameterizedTexture with properties defined in an ADE. 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | 312 | 313 | 314 | 315 | 316 | 317 | 318 | TexCoordGen defines texture parameterization using a transformation matrix. 319 | 320 | 321 | 322 | 323 | 324 | 325 | 326 | 327 | Specifies the 3x4 transformation matrix that defines the transformation between world coordinates and texture coordinates. 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | TexCoordList defines texture parameterization using texture coordinates. 343 | 344 | 345 | 346 | 347 | 348 | 349 | 350 | 351 | Specifies the coordinates of texture used for parameterization. The texture coordinates are provided separately for each LinearRing of the surface geometry object. 352 | 353 | 354 | 355 | 356 | Specifies the URIs that point to the LinearRings that are parameterized using the given texture coordinates. 357 | 358 | 359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 | 369 | 370 | TextureAssociation denotes the relation of a texture to a surface geometry object. 371 | 372 | 373 | 374 | 375 | 376 | 377 | 378 | 379 | Specifies the URI that points to the surface geometry object to which the texture is applied. 380 | 381 | 382 | 383 | 384 | Relates to the texture coordinates or transformation matrices used for parameterization. 385 | 386 | 387 | 388 | 389 | 390 | 391 | 392 | 393 | 394 | 395 | 396 | 397 | 398 | 399 | 400 | TextureType enumerates the different texture types. 401 | 402 | 403 | 404 | 405 | Indicates that the texture is specific to a single surface. 406 | 407 | 408 | 409 | 410 | Indicates that the texture is characteristic of a surface and can be used repeatedly. 411 | 412 | 413 | 414 | 415 | Indicates that the texture type is not known. 416 | 417 | 418 | 419 | 420 | 421 | 422 | WrapMode enumerates the different fill modes for textures. 423 | 424 | 425 | 426 | 427 | Indicates that the texture is applied to the surface "as is". The part of the surface that is not covered by the texture is shown fully transparent. [cf. COLLADA] 428 | 429 | 430 | 431 | 432 | Indicates that the texture is repeated until the surface is fully covered. [cf. COLLADA] 433 | 434 | 435 | 436 | 437 | Indicates that the texture is repeated and mirrored. [cf. COLLADA] 438 | 439 | 440 | 441 | 442 | Indicates that the texture is stretched to the edges of the surface. [cf. COLLADA] 443 | 444 | 445 | 446 | 447 | Indicates that the texture is applied to the surface "as is". The part of the surface that is not covered by the texture is filled with the RGBA color that is specified in the attribute borderColor. [cf. COLLADA] 448 | 449 | 450 | 451 | 452 | 453 | 454 | X3DMaterial defines properties for surface geometry objects based on the material definitions from the standards X3D and COLLADA. 455 | 456 | 457 | 458 | 459 | 460 | 461 | 462 | 463 | Specifies the minimum percentage of diffuseColor that is visible regardless of light sources. 464 | 465 | 466 | 467 | 468 | Specifies the color of the light diffusely reflected by the surface geometry object. 469 | 470 | 471 | 472 | 473 | Specifies the color of the light emitted by the surface geometry object. 474 | 475 | 476 | 477 | 478 | Specifies the color of the light directly reflected by the surface geometry object. 479 | 480 | 481 | 482 | 483 | Specifies the sharpness of the specular highlight. 484 | 485 | 486 | 487 | 488 | Specifies the degree of transparency of the surface geometry object. 489 | 490 | 491 | 492 | 493 | Specifies which interpolation method is used for the shading of the surface geometry object. If the attribute is set to true, vertex normals should be used for shading (Gouraud shading). Otherwise, normals should be constant for a surface patch (flat shading). 494 | 495 | 496 | 497 | 498 | Specifies the URI that points to the surface geometry objects to which the material is applied. 499 | 500 | 501 | 502 | 503 | Augments the X3DMaterial with properties defined in an ADE. 504 | 505 | 506 | 507 | 508 | 509 | 510 | 511 | 512 | 513 | 514 | 515 | 516 | 517 | 518 | -------------------------------------------------------------------------------- /xsds/bridge.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Bridge module supports representation of thematic and spatial aspects of bridges, bridge parts, bridge installations, and interior bridge structures. 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | ADEOfAbstractBridge acts as a hook to define properties within an ADE that are to be added to AbstractBridge. 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | ADEOfBridge acts as a hook to define properties within an ADE that are to be added to a Bridge. 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | ADEOfBridgeConstructiveElement acts as a hook to define properties within an ADE that are to be added to a BridgeConstructiveElement. 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | ADEOfBridgeFurniture acts as a hook to define properties within an ADE that are to be added to a BridgeFurniture. 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | ADEOfBridgeInstallation acts as a hook to define properties within an ADE that are to be added to a BridgeInstallation. 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | ADEOfBridgePart acts as a hook to define properties within an ADE that are to be added to a BridgePart. 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | ADEOfBridgeRoom acts as a hook to define properties within an ADE that are to be added to a BridgeRoom. 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | AbstractBridge is an abstract superclass representing the common attributes and associations of the classes Bridge and BridgePart. 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | Indicates the specific type of the Bridge or BridgePart. 112 | 113 | 114 | 115 | 116 | Specifies the intended purposes of the Bridge or BridgePart. 117 | 118 | 119 | 120 | 121 | Specifies the actual uses of the Bridge or BridgePart. 122 | 123 | 124 | 125 | 126 | Indicates whether the Bridge or BridgePart can be moved to allow for watercraft to pass. 127 | 128 | 129 | 130 | 131 | Relates the constructive elements to the Bridge or BridgePart. 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | Relates the installation objects to the Bridge or BridgePart. 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | Relates the rooms to the Bridge or BridgePart. 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | Relates the furniture objects to the Bridge or BridgePart. 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | Relates the addresses to the Bridge or BridgePart. 188 | 189 | 190 | 191 | 192 | Augments AbstractBridge with properties defined in an ADE. 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | A Bridge represents a structure that affords the passage of pedestrians, animals, vehicles, and service(s) above obstacles or between two points at a height above ground. [cf. ISO 6707-1] 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | Relates the bridge parts to the Bridge. 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | Augments the Bridge with properties defined in an ADE. 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | A BridgeConstructiveElement is an element of a bridge which is essential from a structural point of view. Examples are pylons, anchorages, slabs, beams. 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | Indicates the specific type of the BridgeConstructiveElement. 258 | 259 | 260 | 261 | 262 | Specifies the intended purposes of the BridgeConstructiveElement. 263 | 264 | 265 | 266 | 267 | Specifies the actual uses of the BridgeConstructiveElement. 268 | 269 | 270 | 271 | 272 | Augments the BridgeConstructiveElement with properties defined in an ADE. 273 | 274 | 275 | 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | 284 | 285 | 286 | 287 | 288 | A BridgeFurniture is an equipment for occupant use, usually not fixed to the bridge. [cf. ISO 6707-1] 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | Indicates the specific type of the BridgeFurniture. 298 | 299 | 300 | 301 | 302 | Specifies the intended purposes of the BridgeFurniture. 303 | 304 | 305 | 306 | 307 | Specifies the actual uses of the BridgeFurniture. 308 | 309 | 310 | 311 | 312 | Augments the BridgeFurniture with properties defined in an ADE. 313 | 314 | 315 | 316 | 317 | 318 | 319 | 320 | 321 | 322 | 323 | 324 | 325 | 326 | 327 | 328 | A BridgeInstallation is a permanent part of a Bridge (inside and/or outside) which does not have the significance of a BridgePart. In contrast to BridgeConstructiveElements, a BridgeInstallation is not essential from a structural point of view. Examples are stairs, antennas or railways. 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | Indicates the specific type of the BridgeInstallation. 338 | 339 | 340 | 341 | 342 | Specifies the intended purposes of the BridgeInstallation. 343 | 344 | 345 | 346 | 347 | Specifies the actual uses of the BridgeInstallation. 348 | 349 | 350 | 351 | 352 | Augments the BridgeInstallation with properties defined in an ADE. 353 | 354 | 355 | 356 | 357 | 358 | 359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | 368 | A BridgePart is a physical or functional subdivision of a Bridge. It would be considered a Bridge, if it were not part of a collection of other BridgeParts. 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | 377 | Augments the BridgePart with properties defined in an ADE. 378 | 379 | 380 | 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | 390 | 391 | 392 | 393 | A BridgeRoom is a space within a Bridge or BridgePart intended for human occupancy (e.g. a place of work or recreation) and/or containment (storage) of animals or things. A BridgeRoom is bounded physically and/or virtually (e.g. by ClosureSurfaces or GenericSurfaces). 394 | 395 | 396 | 397 | 398 | 399 | 400 | 401 | 402 | Indicates the specific type of the BridgeRoom. 403 | 404 | 405 | 406 | 407 | Specifies the intended purposes of the BridgeRoom. 408 | 409 | 410 | 411 | 412 | Specifies the actual uses of the BridgeRoom. 413 | 414 | 415 | 416 | 417 | Relates the furniture objects to the BridgeRoom. 418 | 419 | brid:BridgeFurniture 420 | 421 | 422 | 423 | 424 | 425 | 426 | 427 | 428 | 429 | 430 | 431 | 432 | 433 | Relates to the installation objects to the BridgeRoom. 434 | 435 | brid:BridgeInstallation 436 | 437 | 438 | 439 | 440 | 441 | 442 | 443 | 444 | 445 | 446 | 447 | 448 | 449 | Augments the BridgeRoom with properties defined in an ADE. 450 | 451 | 452 | 453 | 454 | 455 | 456 | 457 | 458 | 459 | 460 | 461 | 462 | 463 | 464 | -------------------------------------------------------------------------------- /xsds/cityFurniture.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The CityFurniture module supports representation of city furniture objects. City furniture objects are immovable objects like lanterns, traffic signs, advertising columns, benches, or bus stops that can be found in traffic areas, residential areas, on squares, or in built-up areas. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfCityFurniture acts as a hook to define properties within an ADE that are to be added to a CityFurniture. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | CityFurniture is an object or piece of equipment installed in the outdoor environment for various purposes. Examples include street signs, traffic signals, street lamps, benches, fountains. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | Indicates the specific type of the CityFurniture. 33 | 34 | 35 | 36 | 37 | Specifies the intended purposes of the CityFurniture. 38 | 39 | 40 | 41 | 42 | Specifies the actual uses of the CityFurniture. 43 | 44 | 45 | 46 | 47 | Augments the CityFurniture with properties defined in an ADE. 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | -------------------------------------------------------------------------------- /xsds/cityObjectGroup.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The CityObjectGroup module supports grouping of city objects. Arbitrary city objects may be aggregated in groups according to user-defined criteria. A group may be further classified by application-specific attributes. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfCityObjectGroup acts as a hook to define properties within an ADE that are to be added to a CityObjectGroup. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | A CityObjectGroup represents an application-specific aggregation of city objects according to some user-defined criteria. Examples for groups are the buildings in a specific region, the result of a query, or objects put together for visualization purposes. Each member of a group may be qualified by a role name, reflecting the role each city object plays in the context of the group. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | Indicates the specific type of the CityObjectGroup. 33 | 34 | 35 | 36 | 37 | Specifies the intended purposes of the CityObjectGroup. 38 | 39 | 40 | 41 | 42 | Specifies the actual usages of the CityObjectGroup. 43 | 44 | 45 | 46 | 47 | Relates to the city objects that are part of the CityObjectGroup. 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | Relates to a city object to which the CityObjectGroup belongs. 63 | 64 | 65 | 66 | 67 | Augments the CityObjectGroup with properties defined in an ADE. 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | Role qualifies the function of a city object within the CityObjectGroup. 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | Describes the role the city object plays within the CityObjectGroup. 93 | 94 | 95 | 96 | 97 | Relates to the city objects that are part of the CityObjectGroup. 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | -------------------------------------------------------------------------------- /xsds/dynamizer.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Dynamizer module supports the injection of timeseries data for individual attributes of CityGML features. Timeseries data can either be retrieved from external Sensor APIs (e.g. OGC SensorThings API, OGC Sensor Observation Services, MQTT, proprietary platforms), external standardized timeseries files (e.g. OGC TimeseriesML or OGC Observations & Measurements), external tabulated files (e.g CSV) or can be represented inline as basic time-value pairs. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfAbstractAtomicTimeseries acts as a hook to define properties within an ADE that are to be added to AbstractAtomicTimeseries. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfAbstractTimeseries acts as a hook to define properties within an ADE that are to be added to AbstractTimeseries. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ADEOfCompositeTimeseries acts as a hook to define properties within an ADE that are to be added to a CompositeTimeseries. 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | ADEOfDynamizer acts as a hook to define properties within an ADE that are to be added to a Dynamizer. 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | ADEOfGenericTimeseries acts as a hook to define properties within an ADE that are to be added to a GenericTimeseries. 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | ADEOfStandardFileTimeseries acts as a hook to define properties within an ADE that are to be added to a StandardFileTimeseries. 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | ADEOfTabulatedFileTimeseries acts as a hook to define properties within an ADE that are to be added to a TabulatedFileTimeseries. 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | AbstractAtomicTimeseries represents the attributes and relationships that are common to all kinds of atomic timeseries (GenericTimeseries, TabulatedFileTimeseries, StandardFileTimeseries). An atomic timeseries represents time-varying data of a specific data type for a single contiguous time interval. 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | Specifies the phenomenon for which the atomic timeseries provides observation values. 111 | 112 | 113 | 114 | 115 | Specifies the unit of measurement of the observation values. 116 | 117 | 118 | 119 | 120 | Augments AbstractAtomicTimeseries with properties defined in an ADE. 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | AbstractTimeseries is the abstract superclass representing any type of timeseries data. 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | Specifies the beginning of the timeseries. 146 | 147 | 148 | 149 | 150 | Specifies the end of the timeseries. 151 | 152 | 153 | 154 | 155 | Augments AbstractTimeseries with properties defined in an ADE. 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | 169 | 170 | 171 | A CompositeTimeseries is a (possibly recursive) aggregation of atomic and composite timeseries. The components of a composite timeseries must have non-overlapping time intervals. 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | Relates to the atomic and composite timeseries that are part of the CompositeTimeseries. The referenced timeseries are sequentially ordered. 181 | 182 | 183 | 184 | 185 | Augments the CompositeTimeseries with properties defined in an ADE. 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | A Dynamizer is an object that injects timeseries data for an individual attribute of the city object in which it is included. The timeseries data overrides the static value of the referenced city object attribute in order to represent dynamic, i.e. time-dependent, variations of its value. 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | Specifies the attribute of a CityGML feature whose value is overridden or replaced by the (dynamic) values specified by the Dynamizer. 211 | 212 | 213 | 214 | 215 | Specifies the beginning of the time span for which the Dynamizer provides dynamic values. 216 | 217 | 218 | 219 | 220 | Specifies the end of the time span for which the Dynamizer provides dynamic values. 221 | 222 | 223 | 224 | 225 | Relates to the timeseries data that is given either inline within a CityGML dataset or by a link to an external file containing timeseries data. 226 | 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | 240 | Relates to the sensor API that delivers timeseries data. 241 | 242 | 243 | 244 | 245 | Augments the Dynamizer with properties defined in an ADE. 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | A GenericTimeseries represents time-varying data in the form of embedded time-value-pairs of a specific data type for a single contiguous time interval. 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 270 | Indicates the specific type of all time-value-pairs that are part of the GenericTimeseries. 271 | 272 | 273 | 274 | 275 | Relates to the time-value-pairs that are part of the GenericTimeseries. 276 | 277 | 278 | 279 | 280 | Augments the GenericTimeseries with properties defined in an ADE. 281 | 282 | 283 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | A SensorConnection provides all details that are required to retrieve a specific datastream from an external sensor web service. It comprises the service type (e.g. OGC SensorThings API, OGC Sensor Observation Services, MQTT, proprietary platforms), the URL of the sensor service, the identifier for the sensor or thing, and its observed property as well as information about the required authentication method. 297 | 298 | 299 | 300 | 301 | 302 | 303 | Indicates the type of Sensor API to which the SensorConnection refers. 304 | 305 | 306 | 307 | 308 | Specifies the phenomenon for which the SensorConnection provides observations. 309 | 310 | 311 | 312 | 313 | Specifies the unit of measurement of the observations. 314 | 315 | 316 | 317 | 318 | Specifies the unique identifier of the sensor from which the SensorConnection retrieves observations. 319 | 320 | 321 | 322 | 323 | Specifies the name of the sensor from which the SensorConnection retrieves observations. 324 | 325 | 326 | 327 | 328 | Specifies the unique identifier of the observation that is retrieved by the SensorConnection. 329 | 330 | 331 | 332 | 333 | Specifies the datastream that is retrieved by the SensorConnection. 334 | 335 | 336 | 337 | 338 | Specifies the base URL of the Sensor API request. 339 | 340 | 341 | 342 | 343 | Specifies the type of authentication required to be able to access the Sensor API. 344 | 345 | 346 | 347 | 348 | Specifies the name of the MQTT Server. This attribute is relevant when the MQTT Protocol is used to connect to a Sensor API. 349 | 350 | 351 | 352 | 353 | Names the specific datastream that is retrieved by the SensorConnection. This attribute is relevant when the MQTT Protocol is used to connect to a Sensor API. 354 | 355 | 356 | 357 | 358 | Specifies the complete URL to the observation request. 359 | 360 | 361 | 362 | 363 | Specifies the complete URL to the sensor description request. 364 | 365 | 366 | 367 | 368 | Relates the sensor to the city object where it is located. 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | 377 | 378 | 379 | 380 | A StandardFileTimeseries represents time-varying data for a single contiguous time interval. The data is provided in an external file referenced in the StandardFileTimeseries. The data within the external file shall be encoded according to a dedicated format for the representation of timeseries data, for example, the OGC TimeseriesML or OGC Observations & Measurements standard. The data type of the data has to be specified within the external file. 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | Specifies the URI that points to the external timeseries file. 390 | 391 | 392 | 393 | 394 | Specifies the format used to represent the timeseries data. 395 | 396 | 397 | 398 | 399 | Specifies the MIME type of the external timeseries file. 400 | 401 | 402 | 403 | 404 | Augments the StandardFileTimeseries with properties defined in an ADE. 405 | 406 | 407 | 408 | 409 | 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 | 420 | A TabulatedFileTimeseries represents time-varying data of a specific data type for a single contiguous time interval. The data is provided in an external file referenced in the TabulatedFileTimeseries. The file shall contain table structured data using an appropriate file format like comma-separated values (CSV), Microsoft Excel (XLSX) or Google Spreadsheet. The timestamps and the values are given in specific columns of the table. Each row represents a single time-value-pair. A subset of rows can be selected using the idColumn and idValue attributes. 421 | 422 | 423 | 424 | 425 | 426 | 427 | 428 | 429 | Specifies the URI that points to the external timeseries file. 430 | 431 | 432 | 433 | 434 | Specifies the format used to represent the timeseries data. 435 | 436 | 437 | 438 | 439 | Specifies the MIME type of the external timeseries file. 440 | 441 | 442 | 443 | 444 | Indicates the specific type of the timeseries data. 445 | 446 | 447 | 448 | 449 | Indicates the number of lines at the beginning of the tabulated file that represent headers. 450 | 451 | 452 | 453 | 454 | Indicates which symbol is used to separate the individual values in the tabulated file. 455 | 456 | 457 | 458 | 459 | Indicates which symbol is used to separate the integer part from the fractional part of a decimal number. 460 | 461 | 462 | 463 | 464 | Specifies the number of the column that stores the identifier of the time-value-pair. 465 | 466 | 467 | 468 | 469 | Specifies the name of the column that stores the identifier of the time-value-pair. 470 | 471 | 472 | 473 | 474 | Specifies the value of the identifier for which the time-value-pairs are to be selected. 475 | 476 | 477 | 478 | 479 | Specifies the number of the column that stores the timestamp of the time-value-pair. 480 | 481 | 482 | 483 | 484 | Specifies the name of the column that stores the timestamp of the time-value-pair. 485 | 486 | 487 | 488 | 489 | Specifies the number of the column that stores the value of the time-value-pair. 490 | 491 | 492 | 493 | 494 | Specifies the name of the column that stores the value of the time-value-pair. 495 | 496 | 497 | 498 | 499 | Augments the TabulatedFileTimeseries with properties defined in an ADE. 500 | 501 | 502 | 503 | 504 | 505 | 506 | 507 | 508 | 509 | 510 | 511 | 512 | 513 | 514 | 515 | A TimeValuePair represents a value that is valid for a given timepoint. For each TimeValuePair, only one of the value properties can be used mutually exclusive. Which value property has to be provided depends on the selected value type in the GenericTimeSeries feature, in which the TimeValuePair is included. 516 | 517 | 518 | 519 | 520 | 521 | 522 | Specifies the timepoint at which the value of the TimeValuePair is valid. 523 | 524 | 525 | 526 | 527 | Specifies the "Integer" value of the TimeValuePair. 528 | 529 | 530 | 531 | 532 | Specifies the "Double" value of the TimeValuePair. 533 | 534 | 535 | 536 | 537 | Specifies the "String" value of the TimeValuePair. 538 | 539 | 540 | 541 | 542 | Specifies the geometry value of the TimeValuePair. 543 | 544 | 545 | 546 | 547 | Specifies the "URI" value of the TimeValuePair. 548 | 549 | 550 | 551 | 552 | Specifies the "Boolean" value of the TimeValuePair. 553 | 554 | 555 | 556 | 557 | Specifies the "ImplicitGeometry" value of the TimeValuePair. 558 | 559 | 560 | 561 | 562 | 563 | 564 | 565 | 566 | 567 | 568 | 569 | 570 | 571 | 572 | Specifies the "Appearance" value of the TimeValuePair. 573 | 574 | 575 | 576 | 577 | 578 | 579 | 580 | 581 | 582 | 583 | 584 | 585 | 586 | 587 | 588 | 589 | 590 | 591 | 592 | 593 | 594 | TimeseriesComponent represents an element of a CompositeTimeseries. 595 | 596 | 597 | 598 | 599 | 600 | 601 | Specifies how often the timeseries that is referenced by the TimeseriesComponent should be iterated. 602 | 603 | 604 | 605 | 606 | Specifies how much extra time is added after all repetitions as an additional gap. 607 | 608 | 609 | 610 | 611 | Relates a timeseries to the TimeseriesComponent. 612 | 613 | 614 | 615 | 616 | 617 | 618 | 619 | 620 | 621 | 622 | 623 | TimeseriesTypeValue enumerates the possible value types for GenericTimeseries and TimeValuePair. 624 | 625 | 626 | 627 | 628 | Indicates that the values of the GenericTimeseries are of type "Integer". 629 | 630 | 631 | 632 | 633 | Indicates that the values of the GenericTimeseries are of type "Double". 634 | 635 | 636 | 637 | 638 | Indicates that the values of the GenericTimeseries are of type "String". 639 | 640 | 641 | 642 | 643 | Indicates that the values of the GenericTimeseries are geometries. 644 | 645 | 646 | 647 | 648 | Indicates that the values of the GenericTimeseries are of type "URI". 649 | 650 | 651 | 652 | 653 | Indicates that the values of the GenericTimeseries are of type "Boolean". 654 | 655 | 656 | 657 | 658 | Indicates that the values of the GenericTimeseries are of type "ImplicitGeometry". 659 | 660 | 661 | 662 | 663 | Indicates that the values of the GenericTimeseries are of type "Appearance". 664 | 665 | 666 | 667 | 668 | 669 | -------------------------------------------------------------------------------- /xsds/generics.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Generics module supports application-specific extensions to the CityGML conceptual model. These extensions may be used to model and exchange additional attributes and features not covered by the predefined thematic classes of CityGML. Generic extensions shall only be used if appropriate thematic classes or attributes are not provided by any other CityGML module. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfGenericLogicalSpace acts as a hook to define properties within an ADE that are to be added to a GenericLogicalSpace. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfGenericOccupiedSpace acts as a hook to define properties within an ADE that are to be added to a GenericOccupiedSpace. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ADEOfGenericThematicSurface acts as a hook to define properties within an ADE that are to be added to a GenericThematicSurface. 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | ADEOfGenericUnoccupiedSpace acts as a hook to define properties within an ADE that are to be added to a GenericUnoccupiedSpace. 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | CodeAttribute is a data type used to define generic attributes of type "Code". 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | Specifies the name of the CodeAttribute. 72 | 73 | 74 | 75 | 76 | Specifies the "Code" value. 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | DateAttribute is a data type used to define generic attributes of type "Date". 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | Specifies the name of the DateAttribute. 100 | 101 | 102 | 103 | 104 | Specifies the "Date" value. 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | DoubleAttribute is a data type used to define generic attributes of type "Double". 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | Specifies the name of the DoubleAttribute. 128 | 129 | 130 | 131 | 132 | Specifies the "Double" value. 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | A GenericAttributeSet is a named collection of generic attributes. 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | Specifies the name of the GenericAttributeSet. 156 | 157 | 158 | 159 | 160 | Associates the GenericAttributeSet with an authority that maintains the collection of generic attributes. 161 | 162 | 163 | 164 | 165 | Relates to the generic attributes that are part of the GenericAttributeSet. 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | A GenericLogicalSpace is a space that is not represented by any explicitly modelled AbstractLogicalSpace subclass within CityGML. 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | Indicates the specific type of the GenericLogicalSpace. 189 | 190 | 191 | 192 | 193 | Specifies the intended purposes of the GenericLogicalSpace. 194 | 195 | 196 | 197 | 198 | Specifies the actual uses of the GenericLogicalSpace. 199 | 200 | 201 | 202 | 203 | Augments the GenericLogicalSpace with properties defined in an ADE. 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | A GenericOccupiedSpace is a space that is not represented by any explicitly modelled AbstractOccupiedSpace subclass within CityGML. 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | Indicates the specific type of the GenericOccupiedSpace. 229 | 230 | 231 | 232 | 233 | Specifies the intended purposes of the GenericOccupiedSpace. 234 | 235 | 236 | 237 | 238 | Specifies the actual uses of the GenericOccupiedSpace. 239 | 240 | 241 | 242 | 243 | Augments the GenericOccupiedSpace with properties defined in an ADE. 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | A GenericThematicSurface is a surface that is not represented by any explicitly modelled AbstractThematicSurface subclass within CityGML. 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | Indicates the specific type of the GenericThematicSurface. 269 | 270 | 271 | 272 | 273 | Specifies the intended purposes of the GenericThematicSurface. 274 | 275 | 276 | 277 | 278 | Specifies the actual uses of the GenericThematicSurface. 279 | 280 | 281 | 282 | 283 | Augments the GenericThematicSurface with properties defined in an ADE. 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | 298 | 299 | A GenericUnoccupiedSpace is a space that is not represented by any explicitly modelled AbstractUnoccupiedSpace subclass within CityGML. 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | Indicates the specific type of the GenericUnoccupiedSpace. 309 | 310 | 311 | 312 | 313 | Specifies the intended purposes of the GenericUnoccupiedSpace. 314 | 315 | 316 | 317 | 318 | Specifies the actual uses of the GenericUnoccupiedSpace. 319 | 320 | 321 | 322 | 323 | Augments the GenericUnoccupiedSpace with properties defined in an ADE. 324 | 325 | 326 | 327 | 328 | 329 | 330 | 331 | 332 | 333 | 334 | 335 | 336 | 337 | 338 | 339 | IntAttribute is a data type used to define generic attributes of type "Integer". 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 | 348 | Specifies the name of the IntAttribute. 349 | 350 | 351 | 352 | 353 | Specifies the "Integer" value. 354 | 355 | 356 | 357 | 358 | 359 | 360 | 361 | 362 | 363 | 364 | 365 | 366 | 367 | MeasureAttribute is a data type used to define generic attributes of type "Measure". 368 | 369 | 370 | 371 | 372 | 373 | 374 | 375 | 376 | Specifies the name of the MeasureAttribute. 377 | 378 | 379 | 380 | 381 | Specifies the value of the MeasureAttribute. The value is of type "Measure", which can additionally provide the units of measure. [cf. ISO 19103] 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | 390 | 391 | 392 | 393 | 394 | 395 | StringAttribute is a data type used to define generic attributes of type "String". 396 | 397 | 398 | 399 | 400 | 401 | 402 | 403 | 404 | Specifies the name of the StringAttribute. 405 | 406 | 407 | 408 | 409 | Specifies the "String" value. 410 | 411 | 412 | 413 | 414 | 415 | 416 | 417 | 418 | 419 | 420 | 421 | 422 | 423 | UriAttribute is a data type used to define generic attributes of type "URI". 424 | 425 | 426 | 427 | 428 | 429 | 430 | 431 | 432 | Specifies the name of the UriAttribute. 433 | 434 | 435 | 436 | 437 | Specifies the "URI" value. 438 | 439 | 440 | 441 | 442 | 443 | 444 | 445 | 446 | 447 | 448 | 449 | 450 | -------------------------------------------------------------------------------- /xsds/landUse.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The LandUse module supports representation of areas of the earth’s surface dedicated to a specific land use. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfLandUse acts as a hook to define properties within an ADE that are to be added to a LandUse. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | A LandUse object is an area of the earth's surface dedicated to a specific land use or having a specific land cover with or without vegetation, such as sand, rock, mud flats, forest, grasslands, or wetlands. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | Indicates the specific type of the LandUse. 33 | 34 | 35 | 36 | 37 | Specifies the intended purposes of the LandUse. 38 | 39 | 40 | 41 | 42 | Specifies the actual uses of the LandUse. 43 | 44 | 45 | 46 | 47 | Augments the LandUse with properties defined in an ADE. 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | -------------------------------------------------------------------------------- /xsds/pointCloud.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The PointCloud module supports representation of CityGML features by a collection of points. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfPointCloud acts as a hook to define properties within an ADE that are to be added to a PointCloud. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | A PointCloud is an unordered collection of points that is a sampling of the geometry of a space or space boundary. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | Specifies the MIME type of the external point cloud file. 33 | 34 | 35 | 36 | 37 | Specifies the URI that points to the external point cloud file. 38 | 39 | 40 | 41 | 42 | Indicates the coordinate reference system used by the external point cloud file. 43 | 44 | 45 | 46 | 47 | Relates to the 3D MultiPoint geometry of the PointCloud stored inline with the city model. 48 | 49 | 50 | 51 | 52 | Augments the PointCloud with properties defined in an ADE. 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | -------------------------------------------------------------------------------- /xsds/relief.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Relief module supports representation of the terrain. CityGML supports terrain representations at different levels of detail, reflecting different accuracies or resolutions. Terrain may be specified as a regular raster or grid, as a TIN, by break lines, and/or by mass points. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfAbstractReliefComponent acts as a hook to define properties within an ADE that are to be added to AbstractReliefComponent. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfBreaklineRelief acts as a hook to define properties within an ADE that are to be added to a BreaklineRelief. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ADEOfMassPointRelief acts as a hook to define properties within an ADE that are to be added to a MassPointRelief. 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | ADEOfRasterRelief acts as a hook to define properties within an ADE that are to be added to a RasterRelief. 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | ADEOfReliefFeature acts as a hook to define properties within an ADE that are to be added to a ReliefFeature. 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | ADEOfTINRelief acts as a hook to define properties within an ADE that are to be added to a TINRelief. 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | An AbstractReliefComponent represents an element of the terrain surface - either a TIN, a raster or grid, mass points or break lines. 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | Indicates the Level of Detail of the terrain component. 98 | 99 | 100 | 101 | 102 | Indicates the geometrical extent of the terrain component. The geometrical extent is provided as a 2D Surface geometry. 103 | 104 | 105 | 106 | 107 | Augments AbstractReliefComponent with properties defined in an ADE. 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | A BreaklineRelief represents a terrain component with 3D lines. These lines denote break lines or ridge/valley lines. 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | Relates to the 3D MultiCurve geometry of the MassPointRelief. This association role is used to represent ridge or valley lines. 133 | 134 | 135 | 136 | 137 | Relates to the 3D MultiCurve geometry of the MassPointRelief. This association role is used to represent break lines. 138 | 139 | 140 | 141 | 142 | Augments the BreaklineRelief with properties defined in an ADE. 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | A MassPointRelief represents a terrain component as a collection of 3D points. 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | Relates to the 3D MultiPoint geometry of the MassPointRelief. 168 | 169 | 170 | 171 | 172 | Relates to the 3D PointCloud of the MassPointRelief. 173 | 174 | 175 | 176 | 177 | Augments the MassPointRelief with properties defined in an ADE. 178 | 179 | 180 | 181 | 182 | 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | A RasterRelief represents a terrain component as a regular raster or grid. 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | Relates to the DiscreteGridPointCoverage of the RasterRelief. 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | Augments the RasterRelief with properties defined in an ADE. 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | A ReliefFeature is a collection of terrain components representing the Earth's surface, also known as the Digital Terrain Model. 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | 239 | Indicates the Level of Detail of the ReliefFeature. 240 | 241 | 242 | 243 | 244 | Relates to the terrain components that are part of the ReliefFeature. 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | Augments the ReliefFeature with properties defined in an ADE. 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 270 | 271 | 272 | 273 | 274 | 275 | A TINRelief represents a terrain component as a triangulated irregular network. 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | 284 | Relates to the triangulated surface of the TINRelief. 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | Augments the TINRelief with properties defined in an ADE. 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | 311 | -------------------------------------------------------------------------------- /xsds/tunnel.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Tunnel module supports representation of thematic and spatial aspects of tunnels, tunnel parts, tunnel installations, and interior tunnel structures. 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | ADEOfAbstractTunnel acts as a hook to define properties within an ADE that are to be added to AbstractTunnel. 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | ADEOfHollowSpace acts as a hook to define properties within an ADE that are to be added to a HollowSpace. 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | ADEOfTunnel acts as a hook to define properties within an ADE that are to be added to a Tunnel. 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | ADEOfTunnelConstructiveElement acts as a hook to define properties within an ADE that are to be added to a TunnelConstructiveElement. 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | ADEOfTunnelFurniture acts as a hook to define properties within an ADE that are to be added to a TunnelFurniture. 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | ADEOfTunnelInstallation acts as a hook to define properties within an ADE that are to be added to a TunnelInstallation. 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | ADEOfTunnelPart acts as a hook to define properties within an ADE that are to be added to a TunnelPart. 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | AbstractTunnel is an abstract superclass representing the common attributes and associations of the classes Tunnel and TunnelPart. 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | Indicates the specific type of the Tunnel or TunnelPart. 112 | 113 | 114 | 115 | 116 | Specifies the intended purposes of the Tunnel or TunnelPart. 117 | 118 | 119 | 120 | 121 | Specifies the actual uses of the Tunnel or TunnelPart. 122 | 123 | 124 | 125 | 126 | Relates the constructive elements to the Tunnel or TunnelPart. 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | 139 | 140 | Relates the installation objects to the Tunnel or TunnelPart. 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | 153 | 154 | Relates the hollow spaces to the Tunnel or TunnelPart. 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | 165 | 166 | 167 | 168 | Relates the furniture objects to the Tunnel or TunnelPart. 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | 182 | Augments AbstractTunnel with properties defined in an ADE. 183 | 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | A HollowSpace is a space within a Tunnel or TunnelPart intended for certain functions (e.g. transport or passage ways, service rooms, emergency shelters). A HollowSpace is bounded physically and/or virtually (e.g. by ClosureSurfaces or GenericSurfaces). 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | Indicates the specific type of the HollowSpace. 208 | 209 | 210 | 211 | 212 | Specifies the intended purposes of the HollowSpace. 213 | 214 | 215 | 216 | 217 | Specifies the actual uses of the HollowSpace. 218 | 219 | 220 | 221 | 222 | Relates the furniture objects to the HollowSpace. 223 | 224 | tun:TunnelFurniture 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 | 236 | 237 | 238 | Relates the installation objects to the HollowSpace. 239 | 240 | tun:TunnelInstallation 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | Augments the HollowSpace with properties defined in an ADE. 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 270 | A Tunnel represents a horizontal or sloping enclosed passage way of a certain length, mainly underground or underwater. [cf. ISO 6707-1] 271 | 272 | 273 | 274 | 275 | 276 | 277 | 278 | 279 | Relates the tunnel parts to the Tunnel. 280 | 281 | 282 | 283 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | Augments the Tunnel with properties defined in an ADE. 295 | 296 | 297 | 298 | 299 | 300 | 301 | 302 | 303 | 304 | 305 | 306 | 307 | 308 | 309 | 310 | A TunnelConstructiveElement is an element of a Tunnel which is essential from a structural point of view. Examples are walls, slabs, beams. 311 | 312 | 313 | 314 | 315 | 316 | 317 | 318 | 319 | Indicates the specific type of the TunnelConstructiveElement. 320 | 321 | 322 | 323 | 324 | Specifies the intended purposes of the TunnelConstructiveElement. 325 | 326 | 327 | 328 | 329 | Specifies the actual uses of the TunnelConstructiveElement. 330 | 331 | 332 | 333 | 334 | Augments the TunnelConstructiveElement with properties defined in an ADE. 335 | 336 | 337 | 338 | 339 | 340 | 341 | 342 | 343 | 344 | 345 | 346 | 347 | 348 | 349 | 350 | A TunnelFurniture is an equipment for occupant use, usually not fixed to the tunnel. [cf. ISO 6707-1] 351 | 352 | 353 | 354 | 355 | 356 | 357 | 358 | 359 | Indicates the specific type of the TunnelFurniture. 360 | 361 | 362 | 363 | 364 | Specifies the intended purposes of the TunnelFurniture. 365 | 366 | 367 | 368 | 369 | Specifies the actual uses of the TunnelFurniture. 370 | 371 | 372 | 373 | 374 | Augments the TunnelFurniture with properties defined in an ADE. 375 | 376 | 377 | 378 | 379 | 380 | 381 | 382 | 383 | 384 | 385 | 386 | 387 | 388 | 389 | 390 | A TunnelInstallation is a permanent part of a Tunnel (inside and/or outside) which does not have the significance of a TunnelPart. In contrast to TunnelConstructiveElement, a TunnelInstallation is not essential from a structural point of view. Examples are stairs, antennas or railings. 391 | 392 | 393 | 394 | 395 | 396 | 397 | 398 | 399 | Indicates the specific type of the TunnelInstallation. 400 | 401 | 402 | 403 | 404 | Specifies the intended purposes of the TunnelInstallation. 405 | 406 | 407 | 408 | 409 | Specifies the actual uses of the TunnelInstallation. 410 | 411 | 412 | 413 | 414 | Augments the TunnelInstallation with properties defined in an ADE. 415 | 416 | 417 | 418 | 419 | 420 | 421 | 422 | 423 | 424 | 425 | 426 | 427 | 428 | 429 | 430 | A TunnelPart is a physical or functional subdivision of a Tunnel. It would be considered a Tunnel, if it were not part of a collection of other TunnelParts. 431 | 432 | 433 | 434 | 435 | 436 | 437 | 438 | 439 | Augments the TunnelPart with properties defined in an ADE. 440 | 441 | 442 | 443 | 444 | 445 | 446 | 447 | 448 | 449 | 450 | 451 | 452 | 453 | 454 | -------------------------------------------------------------------------------- /xsds/vegetation.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Vegetation module supports representation of vegetation objects with vegetation-specific thematic classes. CityGML’s vegetation model distinguishes between solitary vegetation objects like trees, and vegetation areas which represent biotopes like forests or other plant communities. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfAbstractVegetationObject acts as a hook to define properties within an ADE that are to be added to AbstractVegetationObject. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfPlantCover acts as a hook to define properties within an ADE that are to be added to a PlantCover. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ADEOfSolitaryVegetationObject acts as a hook to define properties within an ADE that are to be added to a SolitaryVegetationObject. 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | AbstractVegetationObject is the abstract superclass for all kinds of vegetation objects. 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | Augments AbstractVegetationObject with properties defined in an ADE. 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | A PlantCover represents a space covered by vegetation. 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | Indicates the specific type of the PlantCover. 84 | 85 | 86 | 87 | 88 | Specifies the intended purposes of the PlantCover. 89 | 90 | 91 | 92 | 93 | Specifies the actual uses of the PlantCover. 94 | 95 | 96 | 97 | 98 | Specifies the average height of the PlantCover. 99 | 100 | 101 | 102 | 103 | Specifies the minimum height of the PlantCover. 104 | 105 | 106 | 107 | 108 | Specifies the maximum height of the PlantCover. 109 | 110 | 111 | 112 | 113 | Augments the PlantCover with properties defined in an ADE. 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | A SolitaryVegetationObject represents individual vegetation objects, e.g. trees or bushes. 130 | 131 | 132 | 133 | 134 | 135 | 136 | 137 | 138 | Indicates the specific type of the SolitaryVegetationObject. 139 | 140 | 141 | 142 | 143 | Specifies the intended purposes of the SolitaryVegetationObject. 144 | 145 | 146 | 147 | 148 | Specifies the actual uses of the SolitaryVegetationObject. 149 | 150 | 151 | 152 | 153 | Indicates the botanical name of the SolitaryVegetationObject. 154 | 155 | 156 | 157 | 158 | Distance between the highest point of the vegetation object and the lowest point of the terrain at the bottom of the object. 159 | 160 | 161 | 162 | 163 | Specifies the diameter of the SolitaryCityObject's trunk. 164 | 165 | 166 | 167 | 168 | Specifies the diameter of the SolitaryCityObject's crown. 169 | 170 | 171 | 172 | 173 | Specifies the diameter of the SolitaryCityObject's root ball. 174 | 175 | 176 | 177 | 178 | Specifies the vertical distance between the lowest point of the SolitaryVegetationObject's root ball and the terrain surface. 179 | 180 | 181 | 182 | 183 | Augments the SolitaryVegetationObject with properties defined in an ADE. 184 | 185 | 186 | 187 | 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | -------------------------------------------------------------------------------- /xsds/versioning.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The Versioning module supports representation of multiple versions of CityGML features within a single CityGML model. In addition, also the version transitions and transactions that lead to the different versions can be represented. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfVersion acts as a hook to define properties within an ADE that are to be added to a Version. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfVersionTransition acts as a hook to define properties within an ADE that are to be added to a VersionTransition. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | Transaction represents a modification of the city model by the creation, termination, or replacement of a specific city object. While the creation of a city object also marks its first object version, the termination marks the end of existence of a real world object and, hence, also terminates the final version of a city object. The replacement of a city object means that a specific version of it is replaced by a new version. 37 | 38 | 39 | 40 | 41 | 42 | 43 | Indicates the specific type of the Transaction. 44 | 45 | 46 | 47 | 48 | Relates to the version of the city object prior to the Transaction. 49 | 50 | 51 | 52 | 53 | Relates to the version of the city object subsequent to the Transaction. 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | TransactionTypeValue enumerates the three possible types of transactions: insert, delete, or replace. 66 | 67 | 68 | 69 | 70 | Indicates that the feature referenced from the Transaction via the "newFeature" association has been newly created; the association "oldFeature" is empty in this case. 71 | 72 | 73 | 74 | 75 | Indicates that the feature referenced from the Transaction via the "oldFeature" association ceases to exist; the association "newFeature" is empty in this case. 76 | 77 | 78 | 79 | 80 | Indicates that the feature referenced from the Transaction via the "oldFeature" association has been replaced by the feature referenced via the "newFeature" association. 81 | 82 | 83 | 84 | 85 | 86 | 87 | TransitionTypeValue enumerates the different kinds of version transitions. “planned” and “fork” should be used in cases when from one city model version multiple successor versions are being created. “realized” and “merge” should be used when different city model versions are converging into a common successor version. 88 | 89 | 90 | 91 | 92 | Indicates that the successor version of the city model represents a planning state for a possible future of the city. 93 | 94 | 95 | 96 | 97 | Indicates that the predecessor version is the chosen one from a number of possible planning versions. 98 | 99 | 100 | 101 | 102 | Indicates that the successor version reflects updates on the city model over time (historical timeline). It shall only be used for at most one version transition outgoing from a city model version. 103 | 104 | 105 | 106 | 107 | Indicates other reasons to create alternative city model versions, for example, when different parties are updating parts of the city model or to reflect the results of different simulation runs. 108 | 109 | 110 | 111 | 112 | Indicates other reasons to converge multiple versions back into a common city model version. 113 | 114 | 115 | 116 | 117 | 118 | 119 | Version represents a defined state of a city model consisting of the dedicated versions of all city object instances that belong to the respective city model version. Versions can have names, a description and can be labeled with an arbitrary number of user defined tags. 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | Allows for adding keywords to the city model version. 129 | 130 | 131 | 132 | 133 | Relates to all city objects that are part of the city model version. 134 | 135 | 136 | 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | Augments the Version with properties defined in an ADE. 149 | 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | 162 | 163 | 164 | VersionTransition describes the change of the state of a city model from one version to another. Version transitions can have names, a description and can be further qualified by a type and a reason. 165 | 166 | 167 | 168 | 169 | 170 | 171 | 172 | 173 | Specifies why the VersionTransition has been carried out. 174 | 175 | 176 | 177 | 178 | Indicates whether the set of city object instances belonging to the successor version of the city model is either explicitly enumerated within the successor version object (attribute clonePredecessor=false), or has to be derived from the modifications of the city model provided as a list of transactions on the city object versions contained in the predecessor version (attribute clonePredecessor=true). 179 | 180 | 181 | 182 | 183 | Indicates the specific type of the VersionTransition. 184 | 185 | 186 | 187 | 188 | Relates to the predecessor version of the VersionTransition. 189 | 190 | 191 | 192 | 193 | Relates to the sucessor version of the VersionTransition. 194 | 195 | 196 | 197 | 198 | Relates to all transactions that have been applied as part of the VersionTransition. 199 | 200 | 201 | 202 | 203 | Augments the VersionTransition with properties defined in an ADE. 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | -------------------------------------------------------------------------------- /xsds/waterBody.xsd: -------------------------------------------------------------------------------- 1 | 2 | 3 | The WaterBody module supports representation of the thematic aspects and 3D geometry of rivers, canals, lakes, and basins. It does, however, not inherit any hydrological or other dynamic aspects of fluid flow. 4 | 5 | 6 | 7 | 8 | 9 | 10 | ADEOfAbstractWaterBoundarySurface acts as a hook to define properties within an ADE that are to be added to AbstractWaterBoundarySurface. 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ADEOfWaterBody acts as a hook to define properties within an ADE that are to be added to a WaterBody. 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | ADEOfWaterGroundSurface acts as a hook to define properties within an ADE that are to be added to a WaterGroundSurface. 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | ADEOfWaterSurface acts as a hook to define properties within an ADE that are to be added to a WaterSurface. 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | AbstractWaterBoundarySurface is the abstract superclass for all kinds of thematic surfaces bounding a water body. 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | Augments AbstractWaterBoundarySurface with properties defined in an ADE. 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | A WaterBody represents significant and permanent or semi-permanent accumulations of surface water, usually covering a part of the Earth. 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | Indicates the specific type of the WaterBody. 97 | 98 | 99 | 100 | 101 | Specifies the intended purposes of the WaterBody. 102 | 103 | 104 | 105 | 106 | Specifies the actual uses of the WaterBody. 107 | 108 | 109 | 110 | 111 | Augments the WaterBody with properties defined in an ADE. 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | A WaterGroundSurface represents the exterior boundary surface of the submerged bottom of a water body. 128 | 129 | 130 | 131 | 132 | 133 | 134 | 135 | 136 | Augments the WaterGroundSurface with properties defined in an ADE. 137 | 138 | 139 | 140 | 141 | 142 | 143 | 144 | 145 | 146 | 147 | 148 | 149 | 150 | 151 | 152 | A WaterSurface represents the upper exterior interface between a water body and the atmosphere. 153 | 154 | 155 | 156 | 157 | 158 | 159 | 160 | 161 | Specifies the level of the WaterSurface. 162 | 163 | 164 | 165 | 166 | Augments the WaterSurface with properties defined in an ADE. 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | --------------------------------------------------------------------------------