Graham, David (CAE Inc.) - Group Chair,
Liang, Steve (University of Calgary) - Co-Chair,
Lokuta, Michael (CAE Inc.) - Co-Chair
Purpose of the Standards Working Group
The purpose of this SWG is to maintain and improve the OGC CDB Standard and Best Practices documents. The SWG will achieve this objective by evaluating and resolving submitted Change Request Proposals (CRPs) and comments received during OGC OAB reviews and CDB adoption votes, recommendations from OGC Engineering Reports, and interactions and discussions in the OGC Technical Committee and its subgroups.
Modern simulations used for individual, crew, and collective training and mission rehearsal are increasingly networked together to compose rich federations of virtual and constructive simulations. Standards have been previously developed and widely adopted for the network protocols and information exchanged in simulation federations, but the synthetic environment (including geospatial content) within which simulation learners are immersed has traditionally been locally generated within each simulator using closely coupled, highly optimized, and generally proprietary data models and encoding formats.
The modeling and simulation end-user community increasingly requires “plug and play” synthetic environment database re-use and a common synthetic environment local representation to enhance realism and “fair fight” concepts in military simulation. Cost benefits by re-using complex curated synthetic environments are one major objective. In military simulation communities, heterogeneous simulations within Live (using real-world vehicles), Virtual (simulations with human-in-the-loop vehicle controllers), Constructive (simulations within which entity dynamics are computer controlled), and Gaming [LVC-G] are being composed on demand; such federations are severely limited by the current common practice using local proprietary data models and formats.
There is evidence of multiple implementations. CAE and its wholly-owned subsidiary Presagis have delivered hundreds of simulation ‘channels’ based on CDB to customers in the U.S. Canada, U.K., Germany, Turkey, Israel, Singapore, Australia, Brunei and others. FlightSafety International (FSI) has independent CDB implementations of CDB based Image Generators and CDB content creation tools. Lockheed-Martin and Rockwell-Collins have provided for database creation tools that can work with CDB as either an input or output format. CACI performs services contract(s) for U.S SOCOM that create CDB content for mission rehearsal. Since the approval of the first CDB SWG Charter, there have been CDB related deliverables in OGC Testbeds, Interoperability Experiments, and Concept Development Studies.
This SWG is focused on processing Change Request Proposals (CRPs) that propose changes and/or enhancements to the OGC CDB Standard.
The Scope of Work (SOW) will be to collect all outstanding CRPs, to evaluate each of the proposals, and to make edits to the standard and Best Practices documents based on the CRPs and related decisions of the SWG membership. The SWG, at their discretion, may also ask the membership for any additional change requests that have not been previously submitted.
The SWG may announce cut-off dates for the submission of CRPs that are to be addressed in the next revision in accordance with the OGC TC Policy and Procedures. Additional CRPs submitted after the cut-off date may be addressed at the discretion of the SWG based on criticality of the change and available time and resources.
The SWG may decide to address selected CRPs immediately in a corrigendum or minor revision or extension of the current standard.
The deliverables of this SWG will be revisions of the OGC CDB standard and Best Practices documents for consideration by the OGC membership for adoption. As part of the CRP review process, the SWG will decide whether each recommendation will be a minor revision or a major revision.
During the period of time of the first and second approved Charters of the CDB SWG, the original CDB industry standard was used as the starting point from which to create OGC CDB 1.0 which was submitted and approved; the first minor revision, OGC CDB 1.1 was developed and approved, and the Multi-Spectral Imagery Extension was developed and approved.
The following tasks are proposed for approval according to the OGC Technical Committee Policies and Procedures:
Development of an optional Extension to OGC CDB to provide for encoding of CDB vector data in OGC Geopackage.
Development of a profile of the OGC Geopackage standard to be used with OGC CDB vector data encoding.
Development of a Best Practices Document to describe conversion of CDB vector data from .SHP to GPKG, and from GPKG to .SHP, including discussion and links to available open-source tools and libraries.
Development of CDB V1.2, a Minor Revision to CDB, to incorporate CRP’s and provide a mechanism for discovery of the vector encoding format being used within a CDB dataset and/or tile.
Continuous development over time of CDB V2.0, a major revision to the OGC CDB Standard and Best Practices.
The timeline for new tasks 1. through 4., above, is for the SWG to complete its work and recommend those numerated tasks as revisions to standards and best practices to the OGC TC for adoption by-or-before Summer of Calendar Year 2020.
The timeline for development of the major revision, CDB 2.0, is dependent on emerging requirements, available resources, and scope freeze, and at the time of drafting of this re-charter is 'to-be-determined.'
The target audience/participants of OGC CDB includes: Government agencies tasked with standards requirements enforcement in procurements; Industry/application developers; Academic institutions; GIS tool and software vendors; Providers of geospatial data commonly incorporated within simulations and; Users/consumers of modeling and simulation synthetic environments.
The SWG will allow open participation to the maximum extent permissible within the OGC TC Policies and Procedures. As a minimum, regular technical input and comment will be solicited from simulation experienced companies, agencies, academic and other institutions, and individuals who may not be OGC members.