A Note about Folder Path Example

143 © 2016 Open Geospatial Consortium

5.1.10 Configuration Metadata

The Configuration metadata file provides the means of defining CDB Configurations. The syntax of the file is given below. The complete XML schema is provided in CDBMetadataSchemaConfiguration.xsd delivered with the standard. Configuration Comment An optional comment describing this CDB Configuration. Comment Version Folder path=... Comment An optional comment describing this CDB Version. Comment Specification version=... Extension name=... version=... Version -- Other versions as needed -- Configuration A Configuration is a list of one or more Version elements. A Version has a mandatory Folder element to provide the path to the CDB Version. The other three 3 elements have the same definitions as that of section 5.1.6, Version Metadata.

5.1.10.1 A Note about Folder Path

The use of a relative path to a CDB Version ensures a greater form of interoperability between operating systems and file systems. However, the CDB standard does not prevent the use of absolute paths 30 . A relative path is expressed relative to the root of the CDB Version containing the Configuration file.

5.1.10.2 Example

Assume that we want to assemble two CDB Versions into a single CDB Configuration. The first CDB Version is located in CDBmyVersion and has the following Version.xml file. Version PreviousIncrementalRootDirectory name=CDBtheVersion Comment This is the comment describing myVersion. Comment Specification version=3.2 Version The second CDB Version complies with version 3.0 of the Specification, is located in CDBtheVersion , and has the following Version.xml file. 30 On Windows, the path can even be specified using the UNC notation. 144 © 2016 Open Geospatial Consortium Version Comment This is the comment describing theVersion. Comment Version The resulting CDB Configuration is stored in CDBmyConfiguration and its Configuration.xml file could look like this: Configuration Comment This is an example of a CDB Configuration referring to two CDB Versions. Comment Version Folder path=..myVersion Comment This is the comment describing myVersion. Comment Specification version=3.2 Version Version Folder path=..theVersion Comment This is the comment describing theVersion. Comment Specification version=3.0 Version Configuration Notice the use of relative paths to refer to the CDB Versions. Also notice the addition of the Specification element to the second Version to explicitly state that it contains data complying with version 1.0 31 of the standard.

5.2 Navigation Library Datasets

The NavData dataset represents the navigation portion of a CDB. It supports several simulation subsystems such as the Instrument Landing System ILS, Inertial NavigationGlobal Positioning System, and Microwave Landing System Communications. The dataset also provides descriptions of airspaces, airways, heliports, helipads, gates, runways, approaches, and terminals. The dataset also provides information regarding climb procedures out of airports. Requirements Class - Navigation Data 81-84 req corenav-data Target type Operations Dependency Currently Shapefile format, dBASE 31 Was Version 3.0 in the OGC Best Practice.