N3943019S2133_AppendixC_GeospatialDataRequirements_030819.pdf

BAA SOLICITATION

APPENDIX C

GEOSPATIAL DATA REQUIREMENTS

August 2018

C-1 REFERENCES

a) U. S. Navy Data Agreement (Appendix B)

b) Contributing Data to OBIS-SEAMAP. http://seamap.env.duke.edu/about/provider_faq

c) US Navy Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) Data Models and Guidance.

https://www.sdsfieonline.org/Components/USN

d) North American Profile (NAP) of ISO 19115: 2003, Geographic Information – Metadata.

http://www.fgdc.gov/nap/metadata

e) Geospatial Positioning Accuracy Standards, Part 4: Architecture, Engineering, Construction, and Facilities Management (FGDC-STD-007.4-2002), Federal Geographic Data Committee (FGDC), 2002.

http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4

f) Geospatial Positioning Accuracy Standards, Part 1: Reporting Methodology (FGDC-

STD-007.1-1998), FGDC, 1998.

http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part1/index_html

g) Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy (FGDC-STD-007.3-1998), FGDC, 1998.

https://www.fgdc.gov/standards/projects/accuracy/part3/chapter3

C-2 GENERAL SPECIFICATIONS

With regards to all digital files prepared for this contract, including source data acquired, source code generated and/or used, and related materials, including that furnished by the government, the contractor shall adhere to reference (a).

Specifically, for all geospatial data produced under this contract, the Contractor will adhere to the requirements as specified in Section C-3. In addition, the Contractor must submit all source survey data to Ocean Biogeographic Information System Spatial Ecological Analysis of Megavertebrate Populations (OBIS-SEAMAP). Data sets should be designated for the Navy’s partner contribution page (http://seamap.env.duke.edu/partner/NAVY) and attributed to the original collector with acknowledgement of appropriate the U.S. Navy Command(s) as the funding source. Reference (b) provides information on submitting data to OBIS-SEAMAP.

C-3 GEOSPATIAL DATA REQUIREMENTS

C-3.1 Data Standards

Data standards facilitate the development, sharing, and use of geospatial data. The Contractor shall ensure that all geospatial data delivered is consistent with reference (c), unless otherwise directed by the Government.

Geospatial data shall be delivered in a single file geodatabase format and accompanied by a data inventory spreadsheet unless otherwise directed by the government. The data will be compatible with ArcGIS 10.3 and must be importable to an Oracle multi-user geodatabase using ArcSDE.

Digital map files (.mxd files) shall be delivered in ArcGIS 10.3 format and the associated data layers shall be sourced by a relative file pathway to the file geodatabase. The contractor shall provide an inventory spreadsheet that contains a field for File geodatabase name, Feature dataset, Feature class, feature label name, feature legend designation, data source, and a comment field.

In addition, all geospatial data delivered by the Contractor shall adhere to the following criteria:

a) precise geographic coordinates in decimal degree format with four decimal precision;

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

c) reference the GRS 1980 spheroid and the North American Datum 1983 (WGS-84); and

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

C-3.2 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 contractor shall provide metadata in accordance with Content Standard for Digital Geospatial Metadata (CSDGM), reference (c), the current U.S. federal metadata standard.

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 reference (d). All metadata shall be in XML format. The Contractor shall reference the North American Profile of ISO 19115 2003 metadata style sheet in ArcCatalog when populating Service-level and Feature Class-level metadata. The Contractor is required to supply metadata for all fields within this style sheet.

C-3.3 Mapping Guidelines

The Contractor shall comply with FGDC Geospatial Positioning Accuracy Standards, Part 4:

Architecture, Engineering, Construction, and Facilities Management, reference (e), which provides accuracy standards for engineering drawings, maps, and surveys. Map or drawing scales will be determined by the COR, given specific project requirements.

C-3.4 GPS Surveys

The Contractor shall comply with the FGDC Geospatial Positioning Accuracy Standards, Part 1:

Reporting Methodology, reference (f), 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 COR, 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. All metadata shall comply with the metadata format requirements as described in this document. Metadata must include an accuracy statement at the 90% or 95% confidence interval. Accuracy statements shall include the method of determination, as specified in the FGDC Geospatial Positioning Accuracy Standards, Part 3: National Standard for Spatial Data Accuracy, reference (g).

C-3.5 Data Integrity

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

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

b) 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;

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

f) attribute information and labeling must be consistent throughout a GIS project.