Public comment requested: IndoorGML v1.1
The Open Geospatial Consortium (OGC) is seeking public comment on the v1.1 update to the IndoorGML standard.
The goal of IndoorGML is to represent and allow for exchange of the location information required to build and operate indoor spatial services such as indoor navigation systems. Several standards, such as CityGML, KML, and IFC, have been published to describe 3D geometry and semantics of buildings for outdoor/indoor spaces, but they lack some important features that are specific to indoor spaces. IndoorGML aims to provide complementary and additional encoding features for indoor space. In this respect, IndoorGML is a complementary standard to CityGML, KML, and IFC.
IndoorGML v1.1 introduces a new feature for level (i.e. storey or floor) information as an additional attribute of cell space to respond to the requirements from many indoor spatial applications. IndoorGML v1.1 is fully compatible with the previous version IndoorGML v1.0.
The OGC IndoorGML Encoding Standard was developed to provide a common schema framework for interoperability between indoor spatial applications. These cover a broad spectrum of application areas such as indoor location services, indoor web map services, indoor emergency control, indoor IoT sensors, guiding services for visually handicapped persons in indoor space, and indoor robotics. Cross-platform, vendor-neutral communication of indoor spatial information is essential to meet the market demands of these applications.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists.opengeospatial.org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template