1、METRIC MIL-PRF-32118 20 March 2003Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Director, National Imagery and Mapping Agency, ATTN: ETA, Mail Stop P-24, 4600 Sangamore Road, Bethesda, MD 2081
2、6-5003 by using the Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document or by letter. AMSC N/A AREA MCGT DISTRIBUTION STATEMENT A. Approved for public release; distribution unlimited. PERFORMANCE SPECIFICATION VECTOR PRODUCT FORMAT (VPF) DATABASE UPDATE
3、 (VDU) This specification is approved for use by all Departments and Agencies of the Department of Defense 1. SCOPE 1.1 Scope. This specification defines requirements for the National Imagery and Mapping Agencys (NIMA) Vector Product Format (VPF) Database Update (VDU). This specification further def
4、ines the tables that are necessary to build an “update layer“ for NIMA Vector Product Format (VPF) data sets that require tracking and accountability for changes made to the underlying VPF data set. 1.2 Purpose. The purpose of this specification is to assure uniformity of treatment among all element
5、s engaged in a coordinated production program for generating VPF update layers for those NIMA VPF products that require them. 1.3 Classification. Requirements for updating Vector Product Format (VPF) data sets can be classified as follows: - No update to VPF data is required (this specification is n
6、ot applicable in this situation). - Update of VPF geospatial data is required, but no tracking of changes is required (section 3.2 applies/VDU update layer is not required). - Update of VPF geospatial data and tracking of changes are required (sections 3.2 and 3.3 both apply/VDU update layer is requ
7、ired). 2. APPLICABLE DOCUMENTS 2.1 General. The documents listed in this section are specified in Sections 3 and 4 of this specification. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort
8、 has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements documents cited in Sections 3 and 4 of this specification whether or not they are listed. Provided by IHSNot for ResaleNo reproduction or networking permitted without l
9、icense from IHS-,-,-MIL-PRF-32118 2 2.2 Government documents. 2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed
10、 in the Department of Defense Index of Specifications and Standards (DoDISS) and the supplement thereto, cited in the solicitation (see 6.2). STANDARDS DEPARTMENT OF DEFENSE MIL-STD-2407 - Vector Product Format (Unless otherwise indicated, copies of the above specifications, standards, and handbooks
11、 are available from the DoD Single Stock Point for Military Specifications, Standards and Related Documents (DODSSP), 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094, or at the DODSSP web site at www.dodssp.daps.mil) 2.3 Order of precedence. In the event of a conflict between the text o
12、f this document and the references cited herein (except for related associated specifications or specification sheets) the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained. 3. REQUIREME
13、NTS 3.1 First Article When specified (see 6.2), a sample shall be subjected to first article inspection in accordance with 4.2. 3.2 Binary patch update methodology. Vector Product Format (VPF) data shall be updated by means of binary patch methodology. The binary patch contains instructions on how t
14、o update the data files in the old data set to be a binary equivalent of the new data set. The generated binary patch can then be disseminated over the Internet or wrapped into a Web-based control that automates the update process. 3.2.1 Library level patches. Binary patches shall be distributed at
15、the VPF library level, so individual libraries in a VPF data set may be updated to suit a users requirements, and keep the binary patches to a manageable size. 3.2.2 Cumulative update. To avoid the situation where new binary patches are applied to previously applied binary patches, the binary patch
16、shall be cumulative and contain all of the updates made to the VPF data since the original data set was issued by NIMA. Some users may have missed applying a previously issued patch and a cumulative patch will ensure that the binary patch is applied to a consistent, baselined data set in the field.
17、Therefore it is important that the binary patches only be applied to the original base data set and not to versions of the data sets to which previous patches have already been applied. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32118 3
18、3.3 VPF Database Update (VDU) Update Layer. For libraries that require tracking and accountability for changes made to the base data, an update layer shall be created and distributed along with the patch update. A VDU update layer is a VPF coverage that can be added to the underlying VPF data set. I
19、t contains features and attribution that provide indications of the changes that have been made to the geospatial data, and the sources of the changes. This stand-alone update layer is not intended to be a self-contained VPF data set because although it contains the tables and relations typically fo
20、und in a VPF data set at the coverage level, it lacks the data base tables and library structure mandated in MIL-STD-2407 (see Section 3.6.2). When an update layer is required, it shall be based on the geographical extent of the initial data library. Not all VPF products have a requirement for maint
21、aining a separate record of changes made to the data set and these do not require a VDU update layer, even though the base geospatial data may be updated by binary patch methodology. 3.3.1 Significance of changes in VDU Update Layer . Generally, a VDU record of changes is required for systems used f
22、or safety of navigation applications, such as the ECDIS-N that uses DNC data. The VDU update layer contains only those changes that are significant for the user, for example, safety of navigation information - announced by Notices to Mariners, Notices to Airmen (NOTAM), etc. The VDU update layer has
23、 been designed to be as small as possible because many users are operating under constrained bandwidth environments. 3.3.2 Changes not included in VDU Update Layer. Minor changes are frequently made to the underlying data files during VPF product maintenance. Although contributing to the overall qua
24、lity of the VPF product, these changes do not in themselves constitute a significant change. To minimize the size of the VDU update layer, these minor changes should not be included in the VDU update layer. 3.4 Operating systems supported. The binary patch file update of VPF base data and the VDU up
25、date layer shall support hosting on Windows (NT, 2000, XP), Solaris, and HP-UX platforms. 3.5 Security. 3.5.1 Security Classification. The security classification of the products generated by the use of these specifications will be the lowest category practicable. When it is necessary to assign a se
26、curity classification to the product, it shall be in accordance with established national security procedures. 3.6 Relationship of base product to VDU update layer. When a VDU update layer is implemented in a VPF data set, the following changes are required to the base VPF product. 3.6.1 Coverage at
27、tribute table (cat). A coverage attribute table (cat) identifies the coverage name, description, and level of topology for each coverage found in a VPF library. Only those coverages that actually exist within a specific library are listed in that librarys coverage attribute table. Products implement
28、ing the VDU update layer will not have a VDU Update (upd) coverage in the coverage attribute table when the VPF data set is initially issued by NIMA. However, if an update layer is required for a product, the following changes will need to be made to the base VPF data set: a. Edit the coverage attri
29、bute table to add a row for the upd coverage at topology level 3. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32118 4 b. Add the update.doc table containing the appropriate edition number information at the library level c. Add the upd co
30、verage itself. 3.6.2 Other mandatory tables in VPF data base. Since the upd coverage is embedded in an existing VPF library when the binary patch is applied, other tables required for VPF compliance at the database level and library level are not included in the VDU update layer, because they alread
31、y exist in the data set (exception see section 3.15). 3.7 VDU Update (upd) Coverage. In addition to the coverages defined for a particular VPF data set by the product specification, an additional layer is required in the product to support user review of data updates. 3.7.1 The upd coverage The upd
32、coverage is a VPF coverage distributed with the binary patch update information for each VPF library, and is designed to flag and provide additional information about significant changes made since the last database edition of the baseline product. Typically this will include features that are signi
33、ficant for safety of navigation. It will contain information such as Notice to Mariners number and accompanying text, current and previous feature IDs, and coverage and feature class information. The update layer is expected to change with each VDU update, so changes to the update layer shall be con
34、tained within the library patch. In order to minimize the impact of the upd coverage on library patch sizes, an efficient VPF implementation of the Update Layer is required. 3.8 Update coverage tiling. The upd coverage is untiled and 2-dimensional (2D). 3.9 Topology. The upd coverage has level 3 top
35、ology (see MIL-STD-2407). 3.10 Update coverage change indicators. The upd coverage shall contain both minimum bounding rectangles (MBR) and points to indicate features that have changed. This allows application software to key on either the MBR or point feature. User display systems utilizing VPF da
36、ta sets will then be able to read this layer and step users through a review process, highlighting spatial and feature updates. 3.10.1 Minimum bounding rectangle. In order to display changes to a user for review, the update layer shall provide a MBR around line and area features that have changed. 3
37、.10.2 Change points. In addition to the MBR around area and line features, point features shall be used as location indicators for area, line, and point feature changes. Therefore, changes to area and line features are indicated by both an MBR and a point. The point shall be placed within the area f
38、eature or on the line feature. 3.11 Complex feature construct. The upd coverage is implemented as a VPF-compliant coverage within each VPF data set library. In order to support an efficient VPF implementation, the VDU update layer uses the VPF complex feature implementation. This allows producers of
39、 VPF update layers to retain attributes at the complex feature level and use both an update area feature table (updatea.aft) and an update point feature table (updatep.pft) to point to multiple spatial components. Provided by IHSNot for ResaleNo reproduction or networking permitted without license f
40、rom IHS-,-,-MIL-PRF-32118 5 The complex feature type is not strictly required to indicate the relationship between two features, but rather is implemented in order to minimize the size of the data set, given the requirement that both area and point features are required for the same change, and data
41、 set size is a critical design limitation. FIGURE 1 shows the relationship between the complex feature table, area and point feature tables, and their required join tables. updatec.cft id edition_number coverage feature_class old_feature_id new_feature_id prim_type update_text updatea.cjt updatep.cj
42、t updatea.aft id id updatep.pft id updatec.cft_id updatec.cft_id id updatea.aft_id updatep.pft_id end_id FIGURE 1 Feature-level table architecture. 3.12 Links between upd coverage features and data features. To facilitate tracking of change information contained in the upd coverage with the features
43、 in the data coverages affected by the change, the updatec.cft contains the coverage, feature class, and feature ID information of the changed feature, both before and after the change has been made. 3.13 Types of change indicators. The type of change shall be indicated by the old and new feature ID
44、s as follows: Action Old ID New ID Addition: null populated Deletion: populated null Change: populated populated 3.14 Update coverage tables. The following tables are required only if an update coverage is required for the specific VPF product being updated. The table headers depicted in the followi
45、ng tables show all possible columns allowed by MIL-STD-2407. The actual structure of the table headers implemented in the upd coverage shall conform to the product to which the upd coverage is being added. Area Feature Table Area Complex Join Table Point Complex Join Point Feature Table Complex Feat
46、ure Table Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32118 6 TABLE 1 Update Character value description table (char.vdt). Thematic Layer: Update Coverage Name: upd Feature Table Description: Update Character Value Description Table Table
47、 Name: char.vdt Header lengthL; Update Value Character Value Description Table;-; id=I,1,P,row identifier,-,-,-,: table=T,12,N,name of the feature table,-,-,-,: attribute=T,16,N,column name,-,-,-,: value=T,5,N,unique value of attribute,-,-,-,: description=T,*,N,description of value,-,-,-,: 1 updatec
48、.cft prim_type cnd Connected Node 2 updatec.cft prim_type end Entity Node 3 updatec.cft prim_type edg Edge 4 updatec.cft prim_type fac Face 5 updatec.cft update_text N_P Unpopulated 6 updatec.cft update_text N_A Not Applicable 7 fca type P Point/Node Feature 8 fca type A Area Feature 9 fca type C Co
49、mplex Feature Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-32118 7 TABLE 2 Update complex feature table (updatec.cft). Thematic Layer: Update Coverage Name: upd Feature Table Description: Update Complex Feature Table Table Name: updatec.cft Thematic Index ID Number 1 Header lengthL; Update Complex Feature Table;-; id=I,1,P,Row Identifier,-,-,-,: edition_number=F,1,N,Edition number of library,-,-
