CityGML Change Request - Description of Storey
All Fields marked with * are mandatory.
Change Request 74
#:
Assigned OGC 10-057
Document #:
Name: *Nobuhiro Ishimaru
Organization: *Hitachi, Ltd.
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:
Source:
*CityGML Change Request - Description of Storey
*Hitachi
Work item code:
Category:
*
Reason for *
change:
It is necessary for indoor routing, facility management, floor planning, and so on.
Summary of *
change:
Clarify the description of Storey by any of the followings.
1) Add Storey class to Fig.25, and modify the clause 10.3.6.
2) Define individual fixed attribute "storey number" in clause 10.3.6.
Consequences if Utilization of 3D building model for indoor routing and the rest is not possible.
not approved:
Clauses affected: *
10.3 Building model, 10.3.6 Modelling building storeys using CityObjectGroups
1 of 2
Additional
Documents
affected:
Supporting See 09-067r2 OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report
Documentation:
Comments:
Status:
Disposition:
2 of 2
Change Request 74
#:
Assigned OGC 10-057
Document #:
Name: *Nobuhiro Ishimaru
Organization: *Hitachi, Ltd.
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:
Source:
*CityGML Change Request - Description of Storey
*Hitachi
Work item code:
Category:
*
Reason for *
change:
It is necessary for indoor routing, facility management, floor planning, and so on.
Summary of *
change:
Clarify the description of Storey by any of the followings.
1) Add Storey class to Fig.25, and modify the clause 10.3.6.
2) Define individual fixed attribute "storey number" in clause 10.3.6.
Consequences if Utilization of 3D building model for indoor routing and the rest is not possible.
not approved:
Clauses affected: *
10.3 Building model, 10.3.6 Modelling building storeys using CityObjectGroups
1 of 2
Additional
Documents
affected:
Supporting See 09-067r2 OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report
Documentation:
Comments:
Status:
Disposition:
2 of 2