GSModel Geometry File Naming Conventions GSModel Texture File Naming Conventions GSModel Material File Naming Conventions GSModel Descriptor File Naming Conventions Examples

121 © 2016 Open Geospatial Consortium These files are stored in archives whose names SHALL follow the naming convention defined in section 3.6.3.1 above; the files inside those archives SHALL follow the naming conventions defined here: LatLon_Dnnn_Snnn_Tnnn_LOD_Un_Rn_extra_tokens.xxx The extra tokens are described in the next sections.

3.6.3.2.1 GSModel Geometry File Naming Conventions

Requirement 69 http:www.opengis.netspeccdb1.0coregsmodelgeometry-archive-name The files from the GSModelGeometry and GSModelInteriorGeometry datasets SHALL have the following naming convention: LatLon_Dnnn_Snnn_Tnnn_LOD_Un_Rn_FeatureCode_FSC_MODL.flt The FeatureCode, FSC, and MODL tokens are as defined in section 3.3.8.1, Feature Classification, and section 3.3.8.2, Model Name.

3.6.3.2.2 GSModel Texture File Naming Conventions

Requirement 70 http:www.opengis.netspeccdb1.0coregsmodeltexture-archive-name The files from the GSModelTexture and GSModelInteriorTexture datasets SHALL have the following naming convention: LatLon_Dnnn_Snnn_Tnnn_LOD_Un_Rn_TNAM.rgb The TNAM token is as defined in section 3.3.8.4, Texture Name.

3.6.3.2.3 GSModel Material File Naming Conventions

Requirement 71 http:www.opengis.netspeccdb1.0coremsmodelmaterial-archive-name The files from the GSModelMaterial and GSModelInteriorMaterial datasets SHALL have 122 © 2016 Open Geospatial Consortium the following naming convention: LatLon_Dnnn_Snnn_Tnnn_LOD_Un_Rn_TNAM.tif The TNAM token is as defined in section 3.3.8.4, Texture Name.

3.6.3.2.4 GSModel Descriptor File Naming Conventions

Requirement 72 http:www.opengis.netspeccdb1.0coregsmodeldescriptor-archive-name The files from the GSModelGeometry and GSModelInteriorGeometry datasets SHALL have the following naming convention: LatLon_Dnnn_Snnn_Tnnn_LOD_Un_Rn_FeatureCode_FSC_MODL.flt The FeatureCode, FSC, and MODL tokens are as defined in section 3.3.8.1, Feature Classification, and section 3.3.8.2, Model Name.

3.6.3.2.5 Examples

All archives at LOD 7 that are located at latitude +62.3° and longitude -160.4° will be named: N62W162_Dnnn_S001_T001_L07_U38_R102.zip For each model dataset that uses an archive, the name of the archive will be: N62W162_D300_S001_T001_L07_U38_R102.zip Geometry N62W162_D301_S001_T001_L07_U38_R102.zip Texture N62W162_D302_S001_T001_L07_U38_R102.zip Signature N62W162_D303_S001_T001_L07_U38_R102.zip Descriptor N62W162_D304_S001_T001_L07_U38_R102.zip Material N62W162_D305_S001_T001_L07_U38_R102.zip Interior Geometry N62W162_D306_S001_T001_L07_U38_R102.zip Interior Texture N62W162_D307_S001_T001_L07_U38_R102.zip Interior Descriptor N62W162_D308_S001_T001_L07_U38_R102.zip Interior Material Examples of files found inside the above archives could be: N62W162_D300_S001_T001_L07_U38_R102_AL015_116_AcmeFactory.flt N62W162_D301_Snnn_Tnnn_L07_U38_R102_AcmeFactory.rgb 123 © 2016 Open Geospatial Consortium N62W162_D302_Snnn_Tnnn_L07_U38_R102_AL015_116_AcmeFactory.shp N62W162_D302_Snnn_Tnnn_L07_U38_R102_AL015_116_AcmeFactory.shx N62W162_D302_Snnn_Tnnn_L07_U38_R102_AL015_116_AcmeFactory.dbf N62W162_D303_S001_T001_L07_U38_R102_AL015_116_AcmeFactory.xml N62W162_D304_Snnn_Tnnn_L07_U38_R102_AcmeFactory.tif N62W162_D305_S001_T001_L07_U38_R102_AL015_116_AcmeFactory.flt N62W162_D306_S001_T001_L07_U38_R102_AcmeFactoryWall.rgb N62W162_D306_S001_T001_L07_U38_R102_AcmeFactoryFloor.rgb N62W162_D306_S001_T001_L07_U38_R102_AcmeFactoryCeiling.rgb N62W162_D307_S001_T001_L07_U38_R102_AL015_116_AcmeFactory.xml N62W162_D308_Snnn_Tnnn_L07_U38_R102_AcmeFactory.tif To complete the example, the name of the GSModel Composite Material Table GSModelCMT that is associated with the above geocell is: N62W162_D309_S001_T001_L00_U0_R0.xml Note that this file is located at LOD 0, hence the value 0 for UREF and RREF. This will be explained later in chapter 5. Finally, the geometry of the tiled 2D model corresponding to the above tile will be named: N62W162_D310_S001_T001_L07_U38_R102.flt

3.7 Navigation Library Dataset

The \CDB\Navigation\ folder is the root directory of the Navigation library which is composed of a single dataset. 1. NavData The purpose of the Navigation library is to include all of the information which is either not geographically located, or has a global geographical coverage and can be used as a lookup to the Navigation Tile-LODs.

3.7.1 Navdata Structure

The NavData dataset is assigned dataset code 400 and has a single level directory structure. Table 3-31: GTModelGeometry Entry File Directory Structure Director y Level Directory Name Description Level 1 400_NavDat The name of the directory is composed of the dataset