1、“h i: MIL-STD-600006 MC = 9999933 0333976 4 NOT MEASUREMENT MIL-STD-600006 13 APRIL 1992 MILITARY STANDARD VEXTOR PRODUCT FORMAT AMSC N/A AREA MCGT ON S-T 8. Approved for public release; distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license f
2、rom IHS-,-,- -_ 3 lIL-STD-b0000b MC W 9999933 0333977 b MIL-STD- 600 O O 6 FOREWORD I 1. This military standard is approved for use by all e Departments and Agencies of the Department o Defense. and any pertinent data which may be of use in improving this document should be addressed to: DMA (PRS),
3、8613 Lee Highway, Fairfax, Virginia 22031-2137, by using the Standardization Document Proposal (DD Form 1426) appearing at the end of this document or by letter. 2. Beneficial comments (recommendations, additions, deletions) ii Provided by IHSNot for ResaleNo reproduction or networking permitted wit
4、hout license from IHS-,-,-MIL-STD-600006 CONTENTS EAC;E PARAGRAPH 1. 1.1 1.2 1.3 1.4 SCOPE . Scope. Applicability . Classification Version control 2. APPLICABLE DOCUMENTS . 2.1 Government documents. . 2.1.1 Specifications, standards, and handbooks. . 2.1.2 Other Government documents, drawings, and p
5、ublications. . 2.2 Non-Government publications. 2.3 Order of precedence. 3. 4. 4.1 4.2 4.3 4.4 DEFINITIONS . GENERAL REQUIREMENTS General . VPF characteristics . Relationship between VPF and specific products. . VPF hierarchy . 5. DETAILED REQUIREMENTS . 5.1 General . 5.2 VPF data model 5.2.1 Data o
6、rganization . 5.2.1.1 Directory . 5.2.1.2 Tables . 5.2.1.3 VPF table components 5.2.1.4 Indexes . 5.2.1.5 Narrative tables 5.2.1.6 Attribute tables 5.2.2 VPF data model components . 5.2.2.1 Primitives 5.2.2.1.1 Nodes . 5.2.2.1.2 Edges . 5.2.2.1.3 Faces . 5.2.2.1.4 Text 5.2.2.2 Feature classes . 5.2.
7、2.2.1 Feature definition 5.2.2.2.2 Feature table joins . 5.2.2.2.3 Feature class types . 5.2.2.2.4 Constructing feature classes 5.2.2.3 Coverage 5.2.2.3.1 VPF topology 5.2.2.3.2 Value description tables 5.2.2.3.3 Tiled coverages . 5.2.2.3.4 Cross-tile keys . 5.2.2.4 Library . 5.2.2.4.1 Tile referenc
8、e coverage . 2 2 2 2 2 3 4 16 16 16 17 17 20 20 20 20 20 21 23 24 24 24 25 26 26 28 29 29 29 29 30 30 33 33 38 30 40 41 28 38 iii Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-. _I_ Mhb MIL-STD-b0000b MC 9999933 0333979 T = MIL-STD-60006 CONTENTS P
9、ARAGRZU?“ 5.2.2.4.2 5a2.2.4,3 5.2.2.4.4 5.2.2.4.5 5.2.2.4.6 5.2.2.5 5.2.3 5.2.3.1 5.2.3.2 5.3 5.3.1 5.3.1.1 5.3.1.2 5.3.2 5.3.2.1 5.3.2.2 5.3.2.3 5.3.2.4 5.3.2.5 5.3.3 5.3.3.1 5.3.3.2 5.3.3.3 5.3.4 5.3.4.1 5.3.4.2 5.3.4.3 5.3.5 5.3.5.1 5.3.5.2 5.3.5.3 5.3.5.4 5.3.5.5 5.3.6 5.3.6.1 5.3.6.2 5.3.7 5.3.
10、8 5.3.9 5.4 5.4.1 5.4.1.1 5.4.1.2 5.4.1.3 5.4.2 5.4.3 5.4.4 5.4.5 5.4.6 5.5 Library attributes Library coordinate system . Data quality reference coverage . Database Types of data quality information . Data quality encoding . implementation General implementation information Table definitions . Rese
11、rved table names and extensions . Primitives Node primitives . Edge primitive Face primitive Text primitive Minimum bounding rectangle table Feature class . Feature tables Feature join tables . Feature-to-primitive relations on tiled coverages Coverage Coverage relationships Feature class schema tab
12、le Value description table . Library . Library header table Geographic reference table Coverage attribute table Tile reference coverage . Tile attributes . Database Library attribute table . Database header table . Data quality Narrative table . Names placement coverage VPF encapsulation . Table def
13、inition Header Record list . Variable-length index file Spatial index files . Thematic index files Allowable field types . Naming conventions Triplet id field type . Library reference coverage Names placement coverage Data quality Data syntax requirements PAGE 41 41 42 42 42 42 43 44 44 44 44 44 46
14、49 51 53 55 55 57 57 58 59 59 59 59 61 62 62 62 62 65 65 65 64 67 67 90 70 70 90 91 73 73 74 76 78 78 80 4a ai iv Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-600006 CONTENTS *PARAGRAPH 5.5.1 5.5.2 5.5.3 5.5.4 5.5.5 5.5.6 6 . 6.1 FIGURES 1
15、 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 TABLES PAGE Integer numbers . 81 Real numbers 82 Date and time syntax 83 Text syntax . 84 Coordinate syntax . 89 Coordinate strings 89 NOTES . 90 Intended use 90 Relationship between VPF and specific products Vector product format s
16、tructure . Byte stream . Table types . VPF structural levels- Geometric and cartographicprimitives . Primitive directory contents Feature class structural scheme . Coverage contents Levels of topology in VPF coverages . Level O topological primitives and their attributes . Level 1 and Level 2 topolo
17、gical primitives and their attributes . Level 3 topological primitives and their attributes . A tiling scheme . Face cross-tile matching Library directory . Database directory Node, edge,.and face primitives . Table structure . Examples of the triplet id Integer number syntax . Real number syntax Da
18、te and time synt.ax . Latin alphabet primary code table (ASCII) . Lacifi alphabet supplementary code table of accents, diacritical marks, and special characters Usage of accents and diacritical marks 1 . a 19 20 22 20 27 27 31 33 34 35 36 37 39 40 41 43 48 71 80 81 83 04 86 87 88 Directory structure
19、 . 21 VPF table structure . 23 City attribute table 25 State attribute table . 25 V Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-. TABfiEC. 5 5 7 a 9 10 1.1 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
20、42 43 44 45 46 47 48 49 50 SJ 52 MIL-STD-b0000b MC W 9999933 0333783 W MIL-STD-600006 CONTENTS Feature table structure . Feature class schema table Feature class schema table and simple feature class . Columns required to define topology in VPF coverages VPF data quality information Table definition
21、 example Field types . Key types . Optional/mandatory conditions . Reserved file names . Reserved directory names Reserved table name extensions Entity node definition Entity node records . Connected node definition Connected node records Edge table definition . Edge record example . Face table defi
22、nition . Face record example . Ring table definiticil Ring record example . Text primitive structure table Text primitive record example . Minimum bounding rectangle definition . Face bounding rectangle record example Feature table . definition Feature join table definition . Feature class schema de
23、finition . Feature class schema exampke Value description table definition Integer value description record example Library header table Coverage attribute table definition . Coverage attribute table example Tile reference area feature table definition Tile area feature record example Library attrib
24、ute table entity definitions Data quality table definition . Text header example ; Geographic reference table Library attribute table example Database header table de?inition Narrative table definition Header field definitions Components of variable-length index file . Spatial index file header reco
25、rd layout . Structure of the bin array record . PAGE 29 3% 32 35 43 44 45 46 46 47 47 47 49 49 %O 50 52 52 53 53 54 54 55 56 56 56 57 58 60 60 61 6. 1 63 64 65 65 66 66 67 69 .68 69 70 72 73 74 75 75 e vi Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,
26、-,-MIL-CTD- 60000 6 e 53 54 55 56 57 CONTENTS IIIABLES PAGE Structure of the bin data record 75 Thematic index file header record layout 77 Structure of index directory record . 78 Allowable field types . 79 Type byte definitions . 89 APPENDIXES A B C D E F G H Introduction to the WF data model 91 W
27、inged-edge topology 96 Tiling 129 Data quality 132 Spatial indexing . . 139 Coding for rnetadata tables 151 Sample VPF database . 154 Feature class relations . 104 e vi Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-STDb0000b MC 77977II 0133783
28、 I iy” i3 MIL-STD-600006 1. SCOPE 1.1 Scope. The vector product format (VPF) is a standard format, structure, and organization for large geographic databases that are based on a georelational data model and are intended for direct use. VPF is designed to be compatible with a wide variety of applicat
29、ions and products. VPF allows application software to read data directly from computer-readable media without prior conversion to an intermediate form. VPF uses tables and indexes that permit direct access by spatial location and thematic content and is designed to be used with any digital geographi
30、c data in vector format that can be represented using nodes, edges, and faces. VPF defines the format of data objects, and the georelational data model provides a data organization within which software can manipulate the VPF data objects. A product specification corresponding to a specific database
31、 product determines the precise contents of feature tables and their relationships in the database. In this context, each separate product or application is defined by a product specification and implemented by using VPF structures. . The information contained in this 1.2 BgDliCabJlJty II standard s
32、hall be used by the Military Departments, Office of the Secretary of Defense, Organizations of the Joint Chiefs of Staff and the Defense Agencies of the Department of Defense (collectively known as DoD Components) in preparing and accessing digital geographic data required or specified to be in vect
33、or product format. , This standard is UNCLASSIFIED. The 1.3 Wsificatim II procedures and processes presented in this standard may be used for classified processing with the addition of appropriate security provisions. 1 Provided by IHSNot for ResaleNo reproduction or networking permitted without lic
34、ense from IHS-,-,- MIL-STD-bOO-OOb-MC m 9999933 O333984 3 m MIL-STD*660006 2. APPLSCABLE. DOCUMENTS 2.1.1 SPecifLcationsst.-. The following specifications, standards; hkid handbooks form a part o this document to the extent specified herein. Un-less otherwise specified, the issues of these documents
35、 ake those listed in the issue of the Department of Defense .Endex of. Specifications and Standards (DODISS) and Suplementi thereto, cited in the solicitation (see 6.2) SPECIFICATIONS i. MILITARY MIL-D-89009 - Digital ehart of the World Database HANDBOOKS MI 1; ITARY MIL-HDBK-O - DOD oSsary 0.f Mapp
36、ing, Chartln9 and Geodesy (MC NPODS), 5801 Tabor Avenue, Philadelphia, PA 19120-50S$9.) 2.1.2 This section owing documents - , 2.2 Don Gover- orm a part of this document to the e specified herein. Unless otherwise specifed, the issues a the documents which are DOD adopted are those listed in the iss
37、ue of the DODICS cited in the solicitation .rm.at sm. 19 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-_I_ - .- - _- I MIL-STD-600006 MC 9999933 0334002 T 9 4 2 MIL-STD-600006 5. DETAILED REQUIREMENTS 5.1 -. This section describes the necessary com
38、ponents of vector product format,. conceptual components of the VPF data model (see appendix A for an overview describing the data model). Section 5.3 contains definitions of the data structures implemented ir1 VPF, The encapsulation of VPF field types, table construction, and ii=i each file is cont
39、ained in exactly one directory. File names must be unique within a directory. A file referenced by a directory is said to be contained in that directory. A file contained in a directory may be referenced by a special form of its name called a pathname (because it contains the location path to the fi
40、le). A pathname has the following form: where : indicates that the enclosed name element is to be replaced with the actual text string indicated. VPF uses the backslash character () as the generic pathname directory separator. For platforms requiring a different separator, software will replace the
41、backslash with the appropriate separator character. For example, if a file named ROADS.LFT is contained in a directory named URBANAREAS, and the separator is (), the resulting pathname would be: URBANAREASROADS.LFT Directories are themselves files, so they may be contained in other directories. They
42、 are referenced by pathname the same way as other files. Thus, if URBANAREAS is contained in LIBRARY1, the resulting pathname would be: LIBRARYlURBANAREAS Finally, pathnames may be combined. Since the directory that contains a file can be contained within a directory itself, it is necessary to have
43、a form of file name that uniquely identifies that file contained within that directory (file names, while unique within a directory, are not unique between directories). For our example, that form would be: 5.2.1.2 UbJes. In the VPF data model, the table is the organizational structure for all data
44、content. All tables in a VPF database share a common basic structure; this structure, which is described in the VPF table components section below (5.2.1.3), is mandatory for a3.1 VPF tables. 21 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD
45、-600006 MC W 999991iL 01i34004 3 c 1 MIL-STD-600006 By definition, a VPF table must include at least the basic structure. Optionally, a VPF tabie can also include two additional structures: the narrative table and the varfabie- length index file. n the VPF data model, all geographic phenomena are mo
46、deled by VBF tables or by tables derived from a VPF table. A table derived from a VPF table is one that possesses all the properties of a WF table but also has additional properties that support other speeifie functions. The primitive table and the attribute table are examples of derived VPF tables.
47、 A derived table can also be further specialized to satisfy a particular need. derived from the attribute table, for example. Figur 4 graphically shows a VPF table and three derived tables. The VPF table is drawn with an oval; all derived tables are differentiated from VPF tables and from each other
48、 by being drawn with other distinct shapes. A feature table may be Opt onal Mandatory U 1 T . II I FIGURE 4. mBR denotes -ndmg ree mg eachcolumn must have a name that is unique within the table Data contents in VPF tables are organized into rows and columns. All rows in a table share the same column
49、 definitions. Each row in the table is defined by a row identifier (row id). Table 2 depicts the principal components of a VPF table. This document describes the column definitions for all the WF standard-specified columns, and the table organization for those columns. Data columns and tables described in this document are labeled either mand
