IGIS_Elevation_Contours_QAP_Version_3.3.pdf

Army IGI&S Program

Geospatial Data Layer

Quality Assurance Plan (QAP)

Elevation Contour

SDSFIE 3.1 Gold: ElevationContour

SDSFIE 3.1 Army Adaptation: ElevationContour

Final

Version 3.3

January 10, 2017

IGI&S Program Geospatial Data Layer QAP – Elevation Contour

TABLE OF CONTENTS

DOCUMENT CHANGE HISTORY

SUMMARY OF CHANGES

1.0 FEATURE DEFINITION

1.1 Geospatial Data Layer Roles and Responsibilities

1.2 Feature Description

1.3 Characterization

2.0 POLICY AND REGULATIONS

3.0 REPRESENTATION

3.1 Geographic Representation

3.2 Positional Accuracy

3.3 Logical Consistency

3.4 Completeness

3.5 Temporal Representation

3.6 Spatial Reference

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

4.1 Feature Specific Sources and Toolsets

5.0 HQDA SOURCE DATABASES

6.0 SPECIFICATIONS FOR GRAPHIC ENTITIES AND ATTRIBUTES

6.1 Database Storage

6.2 Attribute Tables

6.2.1 SDSFIE 3.1 Army Adaptation Acceptable Values Clarification

DOCUMENT CHANGE HISTORY

Development

Step Description Date Completed

0.1 OACSIM IGI&S & Proponent Draft October 30, 2009

0.2 Proponent Initial Review November 1, 2009

0.3 Community Review Period November 30, 2009

0.4 OACSIM IGI&S & Proponent Final Review January 31, 2010

1.0 Published February 1, 2010

1.1 Published (Update) April 1, 2010

2.0 Published (Update) June 1, 2011

3.0 Published (Update) February 1, 2014

3.1 Published (Update) August 11, 2014

3.2 Published (Update) January 4, 2016

3.3 Published (Update) January 10, 2017

SUMMARY OF CHANGES

Version 1.0 updated to Version 1.1

1. To relocate Real Property Unique Identifier (RPUID) attribute in SDSFIE 2.610 – Required Populated

Attributes table from HQIIS section to IGI&S section.

2. To update Figure 1.7 – Existing Data Model “As Is” to reflect attribute section change in the SDSFIE 2.610

- Required Populated Attribute table.

Version 1.1 updated to Version 2.0

Annual Review Conducted

1. Added table and figure numbers and corresponding references

2. Updated format to reflect migration to proposed SDSFIE 3.0 Gold Army Adaptation

3. Updated attribute information to remove SDSFIE 2.6 “Army Adaptation” attributes

4. Updated attribute information to align with HQIIS

Version 2.0 updated to SDSFIE 3.1 Army Adaptation

1. Updated format to re-align section and table numbering to minimize confusion with section references

2. Updated content and attribution to reflect migration to SDSFIE 3.1 Army Adaptation

3. Updated content to reflect changes to HQDA Business Systems

Version 3.0 updated to Version 3.1

1. Updated to align with final SDSFIE 3.1 Army Adaptation.

Version 3.1 updated to Version 3.2

1. Updated minor formatting errors. No content changes were made.

Version 3.2 updated to Version 3.3

1. Updated to improve standardization with other QAPs.

2. Updated to remove references to the SDSFIE 2.6 Gold model to reflect full migration to SDSFIE 3.1.

1.0 FEATURE DEFINITION

1.1 Geospatial Data Layer Roles and Responsibilities

Table 1 - Roles and Responsibilities

IGI&S Proponent: OACSIM Operations Directorate (DAIM-OD)

Installation Functional SME: DPW or equivalent

Data Steward: DPW or equivalent

Prioritization: Army CIP Priority 1

1.2 Feature Description

A contour line (also called isoline or isogram) joins points of equal elevation (height) above a reference level, such as mean sea level. Contours are used to illustrate changes in elevations associated with terrain features such as valleys and hills, as well as allow map users to infer relative gradients, slope, aspect, or flow. The gradient of the function is always perpendicular to the contour lines. When the lines are close together the length of the gradient is large: the variation is steep.

Contour lines are the most common method of showing relief and elevation on a standard topographic map. The four most common types of contour lines (Figure 1) used on a standard topographic map are as follows:

Figure 1 – Types of Contour Lines

(1) Index Contour – A contour line accentuated by a heavier line weight to distinguish it from intermediate contour lines. Index contours are usually shown as every fifth contour, with their assigned values, to facilitate reading elevation.

(2) Intermediate Contour – The contour lines falling between the index contour lines are called intermediate contour lines. These lines are finer and do not have their elevations given. There are normally four intermediate contour lines between index contour lines.

(3) Supplementary Contour – These contour lines are shown as dashes. They show changes in elevation of at least one-half the contour interval. These lines are normally found where there is very little change in elevation, such as on fairly level terrain.

(4) Depression Contour – A closed contour, inside of which the ground or geologic structure is at a lower elevation than the surrounding area, and distinguished on a map from other contour lines by hachures marked on the down slope or down dip side.

1.3 Characterization

The Data Steward will provide a line geospatial data layer depicting elevation contour lines connecting points of equal vertical elevation and representing fixed elevation intervals. Elevation refers to a spatially referenced vertical position above or below a reference surface. The elevation data in this geospatial data layer is intended to model the land surface properly.

Vertical escarpment, such as cliffs can be represented with a single contour if too steep to be represented by multiple contours. A depression is a contour around a basin or a sink and should be represented with hachured lines. Break lines are used to represent a sudden or drastic change in terrain slope. Physical examples of break lines are ridgelines, streams, and lake shorelines, and will be captured in separate geospatial data layers, not the elevation contour geospatial data layer.

2.0 POLICY AND REGULATIONS

Table 2 - Geospatial Data Layer Applicable Documents

Program(s) Driver(s)

Office of the Assistant

Chief of Staff for

Installation Management

(OACSIM)

- AR 115-13, Installation Geospatial Information and Services

U.S. Army Infantry

School

- FM 3-25.26, Map Reading and Land Navigation

The most recent version of the Army documents listed above can be obtained from the Army

Publishing Directorate website.

Website: http://www.apd.army.mil/

3.0 REPRESENTATION

3.1 Geographic Representation

Elevation contour features should be stored in the SDSFIE 3.1 Army Adaptation

ElevationContour feature type, which was created to store a line of constant value indicating elevation relative to some reference system and unit of measure. The SDSFIE 3.1 Army

Adaptation utilizes this feature type’s default geometry of line. Use of alternate geometries is not allowed for the ElevationContour feature type. If an installation requires the use of a subclass to the ElevationContour feature type to properly store elevation contour features, a new subclass http://www.apd.army.mil/ must be created in accordance with the Army IGI&S Program SDSFIE Implementation

Guidance.

The elevation contour geospatial data layer will include linear features consisting of a series of individual segments connected by nodes. A node is a logical breakpoint in the linear feature.

Contour lines should be collected at minimum of 10 feet; however, the preferred standard is a 2 foot interval in the cantonment and at a 5 foot interval in the training areas.

3.2 Positional Accuracy

Elevation contour features must, at a minimum, meet a level of positional accuracy for depiction on a 1:1,200 scale cartographic product. The minimum absolute horizontal accuracy for elevation contour features is 1.0 foot. The horizontal accuracy must be compiled, tested, and reported in accordance with Part 3 of the Federal Geographic Data Committee's Geospatial Positioning

Accuracy Standards: the National Standard for Spatial Data Accuracy (NSSDA). Spatial accuracy must be reported at the 95% confidence level. The spatial accuracy standard is available at http://www.fgdc.gov/standards/standards_publications/index_html. Vertical accuracy is not currently tested for the elevation contour geospatial data layer.

3.3 Logical Consistency

Contour line features should be validated to verify that they do not intersect with each other or self-intersect. Contour lines should form a continuous loop with no gaps except at the edge of a map. Contour lines should align with hydrographic features such as streams and lakes. Although contour features should be located within an installation’s site(s) boundary, mission requirements may require using contours that are outside the installation’s site(s) boundary. These contours may be captured in the elevation contours geospatial data layer as well.

3.4 Completeness

The elevation contour geospatial data layer should include all applicable contour lines that fall between the maximum and minimum elevation for a defined contour interval for that installation.

The elevation contour data source and vertical datum must be noted in the corresponding feature metadata.

3.5 Temporal Representation

The elevation contours geospatial data layer will reflect existing conditions. Updates to this geospatial data layer should occur as changes to the earth’s surface due to human or natural activities take place. At a minimum, the elevation contours geospatial data layer will be reviewed annually.

3.6 Spatial Reference

The bounding coordinates to capture the north, south, east, and west-most spatial extents of the elevation contour geospatial data layer will be based on one of the following: a) Universal

Transverse Mercator (UTM) Zone, meters or b) local State Plane Coordinate System, feet. At a minimum, feature types within the database should have a spatial reference with a precision of

1,000. The horizontal datum to be utilized is World Geodetic System 1984 (WGS84), and the http://www.fgdc.gov/standards/standards_publications/index_html vertical datum shall be Mean Sea Level (MSL) as determined by the Earth Gravitational Model

2008 (EGM2008) Geoid.

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

Information for the elevation contour geospatial data layer must be obtained and/or validated at the installation level from the Installation Directorate of Public Works (DPW), or equivalent.

The DPW will have overall responsibility for completing and updating the spatial, attribute and metadata features of the elevation contour geospatial data layer in accordance with this QAP. In all cases, the Data Steward should work with the SME to identify the most reliable source for the elevation contour geospatial data layer.

4.1 Feature Specific Sources and Toolsets

Contour line features can be collected from existing digital sources or extracted from digital elevation data such as digital terrain elevation data (DTED), digital elevation models (DEMs) or

LiDAR (Light Detection and Ranging) data. More than one source may contribute to the elevation contour line features in a given elevation contours geospatial data layer.

The following sources of data will be considered for capturing new geospatial data collection efforts or updating existing geospatial data. These sources are to be used in conjunction with the sources listed in the Valid Sources and Source Selection Criteria section of the QAP General

Guidance document: https://www.us.army.mil/suite/doc/43327385.

Other Digital Sources – Utilize elevation contour line features extracted from existing data sets such as National Elevation Dataset, Digital Terrain Elevation Data, Digital

Elevation Models, and LiDAR from sources such as USGS and NGA. These sources should be evaluated for accuracy and completeness.

Note – Although the National Elevation Dataset (NED) will be available to installations, it is the least preferred source of elevation data. The NED should not supersede existing installation data. Rather the NED should be used in the absence of other data and until data can be collected using a preferred source.

5.0 HQDA SOURCE DATABASES

The Headquarters Department of the Army (HQDA) source database is the authoritative, auditable source of information where data is recorded. Properly utilizing HQDA source databases is crucial to maintaining accurate and relevant information. Maintaining duplicative databases is inefficient, undermines the reliability of the information, and creates unsustainable business processes. Departments within HQDA are currently collaborating to ensure business systems are interoperable to ensure reduced redundancy. At this time, there are no authoritative

HQDA source databases for this feature. The SDSFIE Army Adaptation geodatabase is the database of record for this IGI&S geospatial data layer.

https://www.us.army.mil/suite/doc/43327385

6.0 SPECIFICATIONS FOR GRAPHIC ENTITIES AND

ATTRIBUTES

The DoD I&E community has been operating in compliance with the SDSFIE data model since

FY07. The SDSFIE 3.1 Army Adaptation is the current geospatial data standard for the Army

IGI&S community. Further guidance pertaining to the implementation of the SDSFIE 3.1 Army

Adaptation can be found in the guide listed below.

Army IGI&S Program SDSFIE Implementation Guidance:

https://www.us.army.mil/suite/doc/42118840

6.1 Database Storage

Table 3 – SDSFIE Database Storage

SDSFIE 3.1 Gold

Modeled Bin: Common and Cross Functional

Feature Type: ElevationContour

SDSFIE 3.1 Army Adaptation

Functional Theme: Common and Cross Functional

Feature Type: ElevationContour

6.2 Attribute Tables

In order to comply with DoD and Army IGI&S Program geospatial data standards, all attributes must exist in the ElevationContour feature type; however, not all of the attribute fields are required to be populated in every feature type. Table 4 identifies the attribute fields required to be populated for elevation contours, their definitions, acceptable values, and the authoritative data source from where the attribute value should originate. In addition to the attributes listed in

Table 4, the geometry-appropriate SDSFIE 3.1 Gold Foundational attributes must be present in the feature type schema. See the QAP General Guidance for more information about

Foundational and Common attributes.

GIS databases are the authoritative data source for only feature level latitude and longitude attribute data. Other feature level attribute data must be properly obtained from its appropriate authoritative data source, per guidance in this QAP, and not maintained in a GIS attribute table.

Departments within OACSIM are currently collaborating to ensure all vital data is stored and maintained in its proper business system. When connectivity with HQDA source databases is established, only those attribute fields whose source database is “IGI&S Generated” will be stored in the geospatial database. As such, attributes identified as belonging in HQIIS but not currently located in HQIIS, have been placed into a section in attribute table titled “Pending

HQIIS Interface”. These attributes should continue to be collected and maintained utilizing guidance in this QAP until new guidance is published indicating their placement in HQIIS.

https://www.us.army.mil/suite/doc/42118840

1SDSFIE 3.1 Army Adaptation attribute information corresponds to the SDSFIE 3.1 Army Adaptation published on 08/11/2014.

Table 4 - Required Populated Attributes

Common

Name

SDSFIE 3.1

Army Adaptation1

Attribute

Definition

SDSFIE 3.1

Army Adaptation

Acceptable Values1

Attributed

Example

Feature

Geometry

Type

IGI&S GENERATED

Elevation contourElevation Elevation being depicted by the specific contour line.

12 Position Number

(Accurate to 2 Decimal

Places)

1300 Line

Contour Identifier elevationContourIDPK Primary Key. A unique, user- defined identifier for each record or instance of an entity.

<Site Identifier> plus

<Unique Identifier Value> 498002459 Line

Contour Type elevContourType The type of elevation contour.

Predefined Domain:

See Table 5, “ContourType”

INDEX Line

Elevation Unit of

Measure elevationUOM The units of measurement for the contours. Feet (FT) FT Line

Installation Code installationID The code assigned by the Military Service or Agency used to identify the site or group of sites that make up an installation.

HQIIS PRNT_INSTL_CD

Value 51105 Line

Real Property Site

Unique Identifier rpsuid The unique identifier (UID) used to permanently identify a Site. HQIIS SITE_UID Value 4980 Line

6.2.1 SDSFIE 3.1 Army Adaptation Acceptable Values Clarification

The table below outlines the domain values and their definitions for specific attributes as cited in the Required Populated Attributes table (Table 4).

Table 5 –Acceptable Values Clarification

ContourType

APP_IND_DEP

Depression contours which are estimated at some multiple of the smallest standard interval.

APP_INDEX

Contours which are estimated at some multiple of the smallest standard interval.

APP_INTER Contours which are estimated at the smallest standard interval.

APP_INTER_DEP

Depression contours which are estimated at the smallest standard interval.

INDEX

Contours placed at some multiple of the smallest standard interval.

INDEX_DEP

Depression contours placed at some multiple of the smallest standard interval.

INTER Contours which represent the smallest standard interval.

INTER_DEP

Depression contours which represent the smallest standard interval.

Other Other. Must be described in the sdsFeatureDescription attribute.

TBD To be determined.

NA Not applicable.