318 Copyright © 2012 Open Geospatial Consortium.
Fig. 105: 3D model of a shopping mall, which consists of two buildings indoor and a hallway outdoor that connects the buildings.
Fig. 106: Example of generating a grid map b from spatial data a, when the grid map is flooring material.
I.3 Overview of the CityGML ADE
This section describes the implementation of the spatial master database explained in section I.2 by using CityGML. Specifically, this section shows UML diagrams and XML schemas for the data model of the Robotics
application schema that was implemented as two independent ADEs. The reason for preparing two ADEs is that there are two types of information which is needed for Ubiquitous Network Robots service. One ADE is for
more general information which can be used not only for robots service but also for indoor service. The other ADE is for information which is focused on robots service. The first ADE is the CityGML Standard Opening
ADE
, which is a schema extending the _Opening, Door, and Window classes of CityGML. The second ADE is the UNR Ubiquitous Network Robots ADE, which is a schema adding classes such as Storey and attributes such
as door type and floor materials that are essential for ubiquitous network robots. The purpose of this section is to provide an example showing how CityGML can be extended using multiple
ADEs. As the semantics of the specific attributes and object types, which are implemented as codelists, result from the Japanese national research project for Ubiquitous Network Robots services, they are not explained in
detail here. This section explains the Standard Opening ADE and UNR ADE. ADE details are explained in the CityGML Wiki see
http:www.citygmlwiki.orgindex.phpCityGML-ADEs . The XML Schema definition of
both ADEs together with example datasets and code lists can be additionally obtained from http:schemas.opengis.netcitygmlexamples2.0aderobotics-ade
.
a b
Plastic tile Carpet
Metal Concrete
Undefined
Copyright © 2012 Open Geospatial Consortium. 319
Fig. 107: CityGML Robotics application schema – Standard Openings and UNR models including Door and Window light yel-
low=CityGML modules, light blue=CityGML Standard Opening ADE, light orange=UNR ADE. Prefixes are used to indicate XML namespaces associated with model elements. The prefix
stdOp
is associated with the CityGML Standard Opening ADE source:Institute for Geodesy and Geoinformation Science, Technical University Berlin, and the prefix
unr
is associated with the UNR ADE source: Central Research Laboratory, Hitachi, Ltd.. The CityGML model elements are associated with the recommended CityGML prefixes.
Fig. 108: CityGML Robotics application schema – UNR Storey model light yellow=CityGML module, light orange=UNR ADE. Prefixes
are used to indicate XML namespaces associated with model elements. The prefix
unr
is associated with the UNR ADE source: Central Research Laboratory, Hitachi, Ltd.. The CityGML model elements are associated with the recommended CityGML prefixes.
Feature
core::_CityObject
+unr::surfaceMaterialType : unr::PhysicalMaterialTypeType +unr::surfaceJointType : unr::JointTypeType
+unr::surfaceRoofType : unr::RoofTypeType +unr::surfaceInOutdoorType : unr::InOutdoorTypeType
Feature
bldg::_BoundarySurface
Feature
bldg::WallSurface
Feature
bldg::RoofSurface
Feature
bldg::GroundSurface
Feature
bldg::ClosureSurface
Feature
bldg::CeilingSurface
Feature
bldg::InteriorWallSurface
Feature
bldg::FloorSurface
+unr::openingMaterialType : unr::PhysicalMaterialTypeType +unr::openingRoofType : unr::RoofTypeType
+unr::openingJointType : unr::JointTypeType Feature
bldg::_Opening
+stdOp::doorOperationType : stdOp::DoorOperationTypeType +unr::autoType : unr::AutoTypeType
Feature
bldg::Door
+stdOp::windowOperationType : stdOp::WindowOperationTypeType Feature
bldg::Window
+class : gml::CodeType [0..1] +function : gml::CodeType [0..]
+usage : gml::CodeType [0..] Feature
bldg::Room
CodeList
unr::PhysicalMaterialTypeType
CodeList
unr::JointTypeType
CodeList
unr::RoofTypeType
CodeList
unr::InOutdoorTypeType
CodeList
unr::AutoTypeType
Enumeration
stdOp::WindowOperationTypeType
Enumeration
stdOp::DoorOperationTypeType
0..1 boundedBy
0..2
opening
Feature
core::_CityObject
Feature
core::_Site
Feature
bldg::_AbstractBuilding
Feature
bldg::Building
+name : gml::CodeType [0..] Feature
grp::CityObjectGroup
Feature
bldg::BuildingPart
+heightAboveGround : gml::LengthType [0..1] +heightToCeilling : gml::LengthType [0..1]
unr::Storey
consistsOfBuildingPart parent
0..1
0.. groupMember
The storey number is given as storeyNo_ in the
gml:name attribute of CityObjectGroup.
Door and Window are extended with attributes indicating how to
open doors and windows.