DTFAAC15R01685_Attachment1_AppD.pdf

Screening Information Request DTFAAC‐15‐R‐01685 Attachment 1 Appendix D

APPENDIX D

GEOSPATIAL DATA REQUIREMENTS

Data Standards

Data standards facilitate the development, sharing, and use of geospatial data. Geospatial data shall be delivered in a single file geodatabase format, unless otherwise directed by the Government, that is compatible with Oracle using ArcGIS 9.3.1, or higher, and must be importable to an Oracle 10g multiuser geodatabase using ArcSDE 9.3.1, or higher. Digital map files (.mxd files) shall be delivered in ArcGIS

9.3.1 format and the associated data layers shall be sourced by a relative file pathway to the file geodatabase. In addition, all geospatial data delivered by the Contractor shall adhere to the following criteria:

(1) Precise geographic coordinates in decimal degree format with four decimal precision;

(2) units of nautical miles (nm) for expansive marine areas and statute miles (mi) for expansive land areas;

(3) projected in the Universal Transverse Mercator (UTM) coordinate system;

(4) reference the GRS 1980 spheroid and the North American Datum 1983 (WGS‐84); and

(5) contain a projection file, if appropriate, based on format.

Metadata Standards

The term “metadata” is defined as data about data. The term is often used to refer to information that allows either: (1) discovery of data, (2) understanding the provenance and quality of the data, or/and (3) analysis of the data via a set of machine readable instructions that describe the data and its relationships. The Content Standard for Digital Geospatial Metadata (CSDGM), version 2 (FGDC‐STD‐ 001‐1998), reference (c), is the current US Federal metadata standard, and the Contractor shall provide metadata according to this standard until such time as it is officially superseded with ISO 19115:2003, Geographic Information Metadata. Within the United States, the FGDC references the North American Profile (ANSI 453), reference (d), which is a profile of ISO 19115:2003 for use by North American organizations to describe their geospatial data, and related Web services. ANSI 453 supports interoperability of geospatial information as it provides a common framework for the description and representation of metadata.

The Contractor shall ensure that metadata is provided for all geospatial data delivered, including data furnished by the Government, a third party, or generated as a result of this project, and is compliant with current FGDC metadata standards (http://www.fgdc.gov/standards/projects/FGDC‐ standards/projects/fgdc‐endorsed‐standards ). All metadata shall be in XML format. The Contractor shall reference the FGDC ESRI metadata style sheet when populating Service‐level and Feature Class‐ level metadata. The Contractor is required to supply metadata for all fields within this style sheet.

Screening Information Request DTFAAC‐15‐R‐01685 Attachment 1 Appendix D

Mapping Guidelines

The Contractor shall comply with the FGDC Geospatial Positioning Accuracy Standards, Parts 1‐5.

Specifically, Geospatial Positioning Accuracy Standards, Part 4: Architecture, Engineering, Construction, and Facilities Management, reference (e), provides accuracy standards for engineering drawings, maps, and surveys. Map or drawing scales will be determined by the COTR, given specific project requirements.

GPS Surveys

The contractor shall comply with the FGDC Geospatial Positioning Accuracy Standards when conducting GPS surveys and collecting geospatial data. Specifically, the Contractor shall ensure that the horizontal accuracy for planning grade GPS data collection shall be sub‐meter, unless otherwise specified. Every effort shall be made to capture feature locations without using offsets, unless obstructions are present.

If offsets are used, the Contractor shall ensure that they are agreed to by the Government and documented, per direction of the NTR, given specific project requirements.

Data sets derived from GPS data collection efforts (mapping or survey grade) shall include metadata to record descriptions of the receiver and other equipment used during collection and processing, base stations used for differential corrections, software used for performing differential corrections, estimated horizontal and vertical accuracies obtained, and conversion routines used to translate the data into final geospatial data delivery format (see Section on Data Standards). All metadata shall comply with the metadata format requirements as described in this document (see section on Metadata Standards). Metadata must include an accuracy statement at the 90% or 95% confidence interval.

Accuracy statements should include the method of determination, preferably from a recognized standard, such as the FGDC Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy, reference (f).

Data Integrity

The Contractor shall employ appropriate QA/QC standards to ensure that data is topologically correct, accurate and complete, including:

(1) no erroneous overshoots, undershoots, dangles or intersections in the line work;

(2) point and line features shall be snapped together where appropriate to support networks, e.g. do not break linear features for labeling or other aesthetic purposes;

(c) lines should be continuous and point features should be digitized as points;

(d) no sliver polygons; and

(e) digital representation of the common boundaries for all graphic features must be coincident, regardless of feature layer.