IGIS_Spot_Elevation_QAP_Version_3.3.pdf

Army IGI&S Program

Geospatial Data Layer

Quality Assurance Plan (QAP)

Spot Elevation

SDSFIE 3.1 Gold: SpotElevation

SDSFIE 3.1 Army Adaptation: SpotElevation

Final

Version 3.3

January 10, 2017

IGI&S Program Geospatial Data Layer QAP – Spot Elevation

TABLE OF CONTENTS

DOCUMENT CHANGE HISTORY

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

DOCUMENT CHANGE HISTORY

Development

Step Description Date Completed

0.1 OACSIM IGI&S & Proponent Draft October 15, 2014

0.2 Proponent Initial Review October 23, 2014

0.3 Community Review Period November 30, 2014

0.4 OACSIM IGI&S & Proponent Final Review December 18, 2014

1.0 N/A1 N/A

2.0 N/A1 N/A

3.0 N/A1 N/A

3.1 Published January 2, 2015

3.2 Published (Update) January 4, 2016

3.3 Published (Update) January 10, 2017

SUMMARY OF CHANGES

Version 3.1 updated to Version 3.2

Annual Review Conducted

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

Version 3.2 updated to Version 3.3

Annual Review Conducted

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 No versions 1.0, 2.0, or 3.0 exist as August 2014 all QAPs were standardized at version 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 2

1.2 Feature Description

A spot elevation indicates a specific point’s elevation relative to a reference surface or datum on a topographic map or other geospatial record. Spot elevations are often used to designate the highest point on a mountain or hill or other elevations of note, such as road junctions or low points such as bottoms of depressions. On USGS maps, spot elevations are typically indicated by an ‘X’ or a triangle. Spot elevations are typically established through ground surveys, LiDAR or, photogrammetric surveys or through queries of digital elevation models. Army mapping convention uses black markings to designate surveyed spot elevations and red-brown markings to designate non-surveyed spot elevations.

1.3 Characterization

The Data Steward will provide a point location for each location where spot elevations have been established through ground surveys, photogrammetry, or digital elevation model queries. The spot elevation data layer should contain point features representing elevations at points that support local mission requirements or are otherwise important. The spot elevation data layer should not include benchmarked or monumented geodetic control points, as these will be stored in the control monument point 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

U.S. Army Corps of

Engineers (USACE)

- EM 1110-1-1005, Control and Topographic Surveying

Federal Geographic Data

Committee (FGDC)

- Content Standards for Framework Land Elevation Data

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

Army Publishing Directorate and FGDC websites.

Army Publishing Directorate website:

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

FGDC website:

Website: http://www.fgdc.gov/

3.0 REPRESENTATION

3.1 Geographic Representation

Spot elevation features should be stored in the SDSFIE 3.1 Army Adaptation SpotElevation feature type, which was created to store points on the surface of the earth of known elevation.

The SDSFIE 3.1 Army Adaptation utilizes this feature type’s default geometry of point. Use of alternate geometries is not allowed for the SpotElevation feature type. If an installation requires the use of a subclass to the SpotElevation feature type to properly store spot elevation features, a new subclass must be created in accordance with the Army IGI&S Program SDSFIE

Implementation Guidance.

The spot elevation geospatial data layer will include discrete points that represent established spot elevations derived from surveys, topographic maps, or elevation dataset queries.

3.2 Positional Accuracy

All spot elevation features must have the associated level of positional accuracy as stated in the source documentation or resultant survey adjustments. Spot elevation accuracy varies depending on the method used to measure or calculate the point and the scale and accuracy of the associated product used as the source to determine a spot elevation. The vertical accuracy for spot elevations has traditionally been, and currently still is, defined relative to the required contour interval for the map being produced. For example, a map with desired contour interval of 1 foot might require spot elevations to be collected to an accuracy of 0.5 foot or better depending on the project requirements. Spot elevation accuracy requirements can be different for different surfaces, such as natural ground or hard ground features. Independent, equal, or higher accuracy survey methods are often used to verify and check vertical accuracy for spot elevations and other map features. Each spot elevation feature must have a horizontal and vertical accuracy associated with it. 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. In some cases, horizontal accuracy and vertical accuracy will have different accuracy values depending on the method used to establish them.

http://www.apd.army.mil/ http://www.fgdc.gov/ http://www.fgdc.gov/standards/standards_publications/index_html

3.3 Logical Consistency

Spot elevation features should be discrete points that depict the geographic locations of all established spot elevations. Some mission requirements may require using spot elevations that are outside the installation’s site(s) boundary. These spot elevations may be captured in this geospatial data layer as well. In cases where spot elevation points coincide with geodetic control points, the survey-verified control point elevation should be utilized as a check on the spot elevation accuracy. Not all geodetic control points are flush with the ground and as a result may not represent the actual natural ground surface.

3.4 Completeness

This geospatial data layer must include all spot elevation features within the installation’s site(s) boundary or the boundary of land owned, leased, or held by the installation. This geospatial data layer may also contain supplementary spot elevation points located outside the installation’s site(s) boundary if additional points are dictated by mission requirements.

The spot elevation geospatial data layer should contain attribute fields in accordance with the current OACSIM approved Army Adaptation to the current SDSFIE version. Although all attribute fields must exist in the attribute table, only those attribute fields listed in Table 4 -

Required Populated Attributes, are required to be populated.

3.5 Temporal Representation

The spot elevation geospatial data layer should reflect existing conditions. The spot elevation geospatial data layer should be updated when surface conditions on the installation change or when new elevation data is made available.

3.6 Spatial Reference

The bounding coordinates to capture the north, south, east, and west-most spatial extents of the spot elevation 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 and vertical datums to be utilized should match existing installation data layers. Care should be taken when combining spot elevations from different data sources that the horizontal and vertical datums are defined for each data source.

4.0 VALID SOURCES AND SOURCE SELECTION CRITERIA

Information for the spot elevation 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 spot elevation 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 spot elevation geospatial data layer.

4.1 Feature Specific Sources and Toolsets

The following sources of data should be considered for capturing new geospatial data 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. The horizontal and vertical datum should be verified prior to using any of the geospatial data from these sources. Mixing of data from different datums may introduce uncertainty or possible errors if not properly identified.

Photogrammetric Mapping – Photos taken during a photogrammetric survey can be used to obtain spot elevations.

Ground Surveys – Surveys conducted with a Total Station or GPS Receiver can be used to obtain spot elevation data. Ground surveys are labor intensive but can provide very accurate geospatial data.

LiDAR or Radar Measurements – A spot elevation can be developed from DEMs developed from a collection of LiDAR or radar measurements taken from aerial or satellite platforms. When airborne sensors like IFSAR or LiDAR are used, the basic product is typically called a reflective surface DEM. DEMs can be classified as digital terrain models (DTMs), also known as bare earth DEMs. When derived from airborne

LiDAR/IFSAR, DTMs must be computed through interpolation of the ground surface under vegetation. The data capture parameters must be noted in the metadata.

National Elevation Dataset (NED) – DEM data developed by the U.S. Geological

Survey is available on the Internet via the Seamless Data Distribution System or as individual quad tiles from other distribution services. The data must be reprojected and/or resampled to meet the required representation specifications.

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: SpotElevation

SDSFIE 3.1 Army Adaptation

Functional Theme: Common and Cross Functional

Feature Type: SpotElevation

6.2 Attribute Tables

In order to comply with DoD and Army IGI&S Program geospatial data standards, all attributes must exist in the SpotElevation 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, 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

X Coordinate coordinateX The x component of a point or the geometric centroid of the polygon or polyline.

Numeric 4228451.859 Point

Y Coordinate coordinateY The y component of a point or the geometric centroid of the polygon or polyline.

Numeric 289649.8159 Point

Elevation Unit of

Measure elevationUOM The unit of measure for the elevation value(s).

See Business Rule Appendix in QAP General Guidance FT Point

Type of Spot Elevation elevationType Discriminator. The type of spot elevation.

Predefined Domain:

Ground, NA, Roof, TBD Ground Point

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 Point

Spot Elevation

Description sdsFeatureDescription A narrative describing the feature. User Defined

Bare Earth

Ground Point

Spot Elevation

Name sdsFeatureName The common name of the feature. User Defined Gravel Point

Elevation spotElev The elevation at the selected point.

Up to 8 Position Number

(Whole Number) 50257 Point

Spot Elevation

Identifier spotElevationIDPK

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

<Site Identifier> plus <Unique Spot Elevation

Identifier>>

498002459 Point

Valid Source validSource The appropriate geospatial data source as defined by the Army QAPs.

See Required Foundation and Common Attributes in

QAP General Guidance

Imagery Point