J-4 Navy GIS deliverable specifications_2021 04 19.pdf

N62742-21-R-1800 Attachment J-4

Section J-4

GIS Data Deliverable Specifications

I. Overview

The GeoReadiness Center (GRC) is the single, authoritative source and distribution point for all geospatial facility data within the region. The GRC houses the most current geospatial information for the entire Region and provides access to the comprehensive data set and analysis tools to Regional and DOD decision makers/managers, sponsored contractors, and other sponsored individuals via a secure government Internet site.

II. Data Collection

A. Where field data collection is stipulated in the contract, the contractor shall utilize Global

Positioning System (GPS) in accordance with the applicable Geospatial Positioning Accuracy Standards published by the Federal Geographic Data Committee (FGDC). The contractor shall use survey grade GPS unless otherwise determined or authorized by the government. GPS data collection activities will be based on a post-processed environment using an accurately sighted base station. Base station files for post processing acquired locally (off-site CORS Continuous Operating Reference Station) will be verified for accuracy.

All survey-grade data collected shall be provided to the Government in a digital format with an attached Survey Report identifying survey method, equipment list, calibration documentation, survey layout, description of control points, control diagrams, quality control report and field survey data.

A digital Survey Control Database (consisting of a survey marker database and a survey traverse database) will be produced for all survey control points established under this contract, including the horizontal and vertical order and coordinate location of each point.

B. Where digitizing/conversion is stipulated in the contract, the contractor shall digitize/convert features from designated sources (including remotely sensed data, hardcopy scans and vector data) to support various GIS applications.

Digitizing/conversion routines will ensure that 90 percent of all features will measure within 0.01 inches when reproduced at the scale of original imagery or data source.

C. The contractor shall employ appropriate QA/QC standards to ensure that data is topologically correct, accurate and complete (to include):

1. All facilities with a property record card shall have the iNFADS NFA populated in the feature’s FACILITYIDFK attribute.

2. Spatial data topology shall be delivered in a "GIS-ready" state.

3. No erroneous overshoots, undershoots, dangles or intersections in the line work.

4. Point and line features will be snapped together where appropriate to support networks. For example, do not break linear features for labeling or other aesthetic purposes.

5. Lines should be continuous and point features should be digitized as points. For example, point features, such as ESA-listed species location should not be drawn using only a circle (polygon) to represent its location. Preferably, and where appropriate, use an attribute block symbol that has an insertion point in the center of the ESA listed species (i.e. plant, tree, nest, etc.).

6. No sliver polygons.

7. Digital representation of the common boundaries for all graphic features must be coincident, regardless of feature layer.

8. If raster-based GIS data, such as digital orthophotographs, is required by the project, then the appropriate coverage and resolution will be determined by the

TOCOR.

All deliverables should include an accuracy report in the metadata. The contractor shall include a summary of the methods used to correct inconsistencies and any remaining errors in the metadata under the ‘Logical Consistency Report’ and ‘Completeness Report’ sections.

III. Deliverable Requirements

A. Specific criteria for geospatial data deliverables shall be as follows:

a) Geodatabase Criteria: Geospatial data shall be delivered as an ArcGIS v.10.7.1 file geodatabase or as otherwise specified. File geodatabases are relational databases that contain geographic information. File geodatabases contain feature classes and tables. The names of these geodatabases should reflect the location of the geographic information it contains at the appropriate level of detail (region, special area, activity). The general naming convention format of file geodatabase is as follows: Location_yyyymmdd.gdb.

Location = Location of the geographic information, defined to the appropriate level of detail. Names begin at the regional level, using the 2-digit country code from iNFADS (e.g. HI=Hawaii, GQ=Guam, JA=Japan, etc.) and may narrow into an area of interest within the region (e.g. Pearl Harbor, Yokosuka, Apra Harbor, etc.). The location can be further narrowed down to the activity level where the geodatabase can be identified by the activity’s UIC (N68032, N58003, etc.)

yyyymmdd = Date that the geodatabase was created or amended, as expressed in year (yyyy), month (mm), and date (dd).

Examples of file geodatabase naming conventions include:

HI_20021015.gdb MASIRAH_20030228.gdb GQApraHarbor_20031114.gdb JAKantoPlainN57002_20040630.gdb

Specific transmittal instructions will be provided to the Contractor when the data is ready to be delivered. Any digital media, such as a CD-ROM or DVD-ROM, delivered to the Government shall have an external label listing a short description of contents, a sequence number, if there are multiple volumes, and the date of creation. A transmittal sheet, containing the information included on the external labels, total number of volumes being delivered, a list of file names and file descriptions on each volume, and certification that all delivery media is free of known computer viruses must accompany the media.

b) If individual task order is managed by a non-Navy component, deliverable must be in that component’s specific deviation of SDSFIE. Data model and standards shall be supplied by that component.

c) If individual task order is managed by the Navy, the Navy Data Model (NDM) shall be used. Data Collection Guide (DCG) chapters for each of the feature classes in the NDM are available from the regional GRC, and the contractor shall comply with these standards, mandated by NAVFAC Headquarters.

d) If new data is being created, the contractor shall provide the GRC with a data dictionary identifying all of the SDSFIE entity types, attributes, and/or domain values associated with the new feature (s), the geographic area(s) covered by the data and spatial extent information prior to the creation and/or editing of geospatial data.

e) ArcSDE Criteria: The contractor shall coordinate with the Regional GRC to determine the appropriate ArcSDE requirements for enabling geospatial data deliverables to be incorporated into the Navy’s regional geodatabase.

f) Spatial Reference Criteria: The contractor shall coordinate with the Regional GRC to determine the appropriate coordinate system, datum, and units of measure applicable to the area of interest.

g) Metadata Criteria: The contractor shall provide metadata compliant with the Federal Geographic Data Committee (FGDC) Content Standard for Digital Geospatial Data (CSDGM) for each feature class in XML format. Details on the metadata standard can be found at http://www.fgdc.gov/metadata/geospatial-metadata-standards. At a minimum, the following CSDGM elements shall be included as part of the deliverable:

1.0 Identification Information – basic information about the data set

1.2 Description – a characterization of the data set, including its intended use and limitations

1.2.1 Abstract - a brief narrative summary of the data set

1.2.2 Purpose – a summary of the intentions with which the data set was developed

1.3 Time Period - time period(s) for which the data set corresponds to the current-ness reference

1.3.1 Current-ness Reference – the basis on which the time period of content information is determined

1.6 Keywords – words or phrases summarizing an aspect of the data set

1.9 Point of Contact - contact information for an individual or organization that is knowledgeable about the data set

2.0 Data Quality Information – a general assessment of the quality of the data set

2.4.1 Positional Accuracy – an assessment of the accuracy of the positions of spatial objects

2.4.1.1 Horizontal Positional Accuracy Report – an explanation of the accuracy of the horizontal coordinate measurements and a description of the tests used

2.4.2.1 Vertical Positional Accuracy Report (if applicable) – an explanation of the accuracy of the vertical coordinate measurements and a description of the tests used

2.5.1 Source Information – list of sources and a short discussion of the information contributed by each

2.5.1.1 Source Citation – reference for a source data set

2.5.2 Process Step – information about a single event

2.5.2.1 Process Description – an explanation of the event and related parameters or tolerances

2.5.2.3 Process Date – the date when the event was completed

4.0 Spatial Reference Information – the description of the reference frame for, and the means to encode, coordinates in the data set

4.1 Horizontal Coordinate System Definition – the reference frame or system from which linear or angular quantities are measured and assigned to the position that a point occupies

4.2 Vertical Coordinate System Definition (if applicable) – the reference frame or system from which vertical distances (altitudes or depths) are measured

h) Map Packages (.MPK) Criteria: All ArcGIS project files (i.e., MXD) shall be delivered with all related source files in a specific file, i.e. MPK, including feature classes referenced, extensions, graphics, photos, source code (non-encrypted) based on version of ArcGIS Desktop specified for the task order. Embedded file path information shall include only relative paths. A readme file shall be included with instruction to load the MXD and any environment variables needed to capture the path information. The Contractor may also be requested to provide a map package (.mpk). A map package contains a map document (MXD) and the data referenced by the layers it contains, packaged into one convenient, portable file.

B. Specific criteria for non-geospatial data deliverables shall be as follows:

Acceptable database formats for non-spatial data tables include: dBase (dbf), Oracle 11, Access (gdb), or Excel worksheets (.xlsx). Relational Oracle 11g format. All database information shall include the following minimum metadata: A complete data dictionary of the database, an Entity Relationship Diagram, as well as proper citation for all primary and secondary data sources used to populate the database data elements.

IV. Government Review

The Government shall review the submitted data and documentation upon completion of all stated work. Missing or incomplete items will be documented and forwarded to the contractor for completion. Failure to adhere to any of the stated delivery specifications could result in rejection of deliverables and nonpayment. Contractors should, at a minimum, submit data and documentation samples at 25% and 75% project completion to avoid the rejection of final deliverables.

Any questions regarding data collection efforts, deliverable formats or specifications should be addressed to the regional GRC Manager.

V. Government Furnished Materials

The Government will provide the contractor access to necessary geospatial data, reports, schematics, or other pertinent information either through the regional NAVFAC GRC, or a data copy. All contractors must have PKI/SoftCert to access any Navy assets. In order to access the GRC data directly, the contractor must have a valid security clearance, current annual IAA training and fully completed SAAR-N form signed by the NTR and GRC manager.

When requesting data from the GRC, the contractor shall identify the current SDSFIE feature classes or datasets they require. The government POC will be contacted prior to the release of any information to verify requirements. A limited-use/non-disclosure agreement may need to be completed prior to the release of any data.

The contractor must verify with the GRC that they are working with the most recent version of the dataset/feature classes at the beginning of each contract and must delete any copies of data in their possession at the end of each contract.

All data used and developed under contract is intellectual property of the U.S. Government, and shall be turned over to the U.S. Navy upon completion of this amendment.