103
© 2016 Open Geospatial Consortium
Table 3-25: MModelSignature Directory Structure
Director y
Level Directory
Name Description
Level 1 606_MModelSignature
The name of the directory is composed of the dataset code followed by an underscore
and the dataset name.
Level 2 9_Kind
The numeric code assigned to the DIS Entity Kind followed by an underscore and
the name of this kind as per Annex M
28
. Level 3
9_Domain The numeric code assigned to the DIS
Domain followed by an underscore and the name of the domain as per Annex M.
Level 4 9_Country
The numeric code assigned to the DIS Country followed by an underscore and the
name of this country as per Annex M.
Level 5 9_Category
The numeric code assigned to the DIS Category followed by an underscore and
the name of this category as per Annex M.
Level 6 9_9_9_9_9_9_9
All 7 fields of the DIS Entity type concatenated and separated by an
underscore.
Level 7 LOD
Character L followed by the LOD number corresponding to the Significant Size for
positive levels of detail. Characters LC followed by the LOD number
corresponding to the Significant Size for negative levels of detail.
3.5.3.1 Naming Convention
Requirement 63
28
Volume 2 CDB Core: Model and Physical Structure: Informative Annexes
104
© 2016 Open Geospatial Consortium
http:www.opengis.netspeccdbcore1.0mmodelsignature-name
The names of all MModelSignature files SHALL adhere to the following naming convention:
● D606_Snnn_Tnnn_LOD_MMDC.xxx where ‘xxx’ is any necessary extension to uniquely identify the table or file. In the case in
which multiple tables or files are necessary to store the model signature content, then the same base name SHALL be used and the necessary name extensions applied as required
by the database or file storage technology.
The following table defines each field of the file names and Table 5-10 provides the values of the Component Selectors to complete the name.
Table 3-26: MModelSignature Naming Convention
Field Description
D606 Character D followed by the 3-digit code assigned to the dataset.
Snnn Character S followed by the 3-digit value of Component Selector 1
Tnnn Character T followed by the 3-digit value of Component Selector 2
LOD This field is identical to the name of the LOD directory level 7 where
the file is stored. MMDC The Moving Model DIS Code is the same as directory level 6
xxx ‘xxx’ is any necessary extension to uniquely identify the table or file. In
the case in which multiple tables or files are necessary to store the model signature content, then the same base name SHALL be used and the
necessary name extensions applied as required by the database or file storage technology.
3.5.3.2 Examples
The following example illustrates the directory structure that would store LOD 4 of the RCS Signature of the M1A2 SEP Abrams tank.
\CDB\MModel\606_MModelSignature\1_Platform\1_Land\ 225_United_States\1_Tank\1_1_225_1_1_8_0\L04
Where \CDB\MModel is the root of all moving model datasets, \606_MModelGeometry is the directory containing the RCS signature of all moving models, \1_Platform is the directory
105
© 2016 Open Geospatial Consortium
containing all DIS Entity of Kind 1 named Platform, \1_Land is the directory containing all DIS platforms of Domain 1 named Land, \225_United_States is the directory containing all
DIS land platforms of Country 225 called United_States, \1_Tank is the directory containing all DIS land platforms of Category 1 named Tank, \1_1_225_1_1_8_0 is the directory containing
all levels of detail of the RCS signature of the M1A2 SEP Abrams tank, and \L04 is the directory containing the files representing LOD 4 of RCS signature of the tank.
For ShapeFiles an example of files found in the above directory are:
D606_Sxxx_Txxx_L04_1_1_225_1_1_8_0.shp D606_Sxxx_Txxx_L04_1_1_225_1_1_8_0.shx
D606_Sxxx_Txxx_L04_1_1_225_1_1_8_0.dbf D606_Sxxx_Txxx_L04_1_1_225_1_1_8_0.dbt
3.5.4 MModel Complete Examples
