5 - GIS Data Format Specifications 3.1.1.pdf

PDF 95 KB Posted

Attached to
SVC A&E_MABE250004 Hilo Boundary Survey Federal contract opportunity
Solicitation number
W50SLF25QA007
Issued by
Department of the Army National Guard

About this file

This document is a Geographic Information System (GIS) Data Format Specifications document for the Air National Guard (ANG), detailing precise technical requirements for GIS data deliverables. The specifications mandate that all GIS data must be developed using ESRI ArcGIS software, specifically in ESRI personal or file geodatabase formats, and must conform to Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) version 3.1.1. All geospatial data must be delivered in the applicable Universal Transverse Mercator (UTM) Coordinate System using World Geodetic System of 1984 (WGS 84) as the earth datum, with units in meters.

Key technical requirements include providing metadata consistent with the Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata, using ArcGIS metadata generation tools to produce XML format files, and delivering uncompressed data on CD-ROM or DVD-ROM with a README.TXT file. Electronic media must be permanently labeled with contract number, operating system version, sequence number, filenames, and contracting firm name. The contractor must ensure all deliverables meet ANG's data review methodology, with the government reserving the right to request changes to data structure and content to ensure compliance with SDSFIE standards.

View the file

Other files for this federal contract opportunity

Other files attached to SVC A&E_MABE250004 Hilo Boundary Survey, newest first.
File Type Posted
2 - Performance Work Statement PWS - MABE250004 Hilo Boundary Survey.pdf PDF
4 - Maps - Hilo.pdf PDF
4 - Lease - Hilo.pdf PDF
1- Solicitation_W50SLF25QA007.pdf PDF
3 - Service Contract ACT WD 2015-5691_Hawaii County.txt TXT text file
6 - Information Regarding Availabiliy of Utitlity Services.docx DOCX document

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

GEOGRAPHIC INFORMATION SYSTEM (GIS) DATA FORMAT SPECIFICATIONS

This document specifies the required format for electronic GIS files delivered to the Air National Guard (ANG) as part of an associated Performance Work Statement (PWS).

SECTION 1 DATA SPECIFICATIONS

1.1. Digital Content

Any GIS data prepared for the ANG will serve as the source of hard copy deliverables defined within the associated PWS.

1.2. Air National Guard (ANG) Enterprise-Standard Software Applications

The ANG utilizes the following software application and standardized templates to create, edit and manage GIS data. All GIS data deliverables created for the ANG shall be delivered in a format consistent with the standards listed below:

Functional Area Software Application Enterprise GIS ESRI ArcGIS (current USAF and ANG approved version*)

ANG Data Standard Version

SDSFIE SDSFIE 3.1.1*

Metadata FGDC Content Standard for Geospatial Metadata

(CSDGM) Version 2

* contact the ANG GIO for current version at usaf.jbanafw.ngb-a4.mbx.a4-geohelp@mail.mil

1.3. Geospatial Data Deliverable Standard

1.3.1. Geospatial Data Format - Geographic data must be provided in a format that does not require post-production work before being loaded to the ANG Enterprise System. The Contractor shall validate any deviation from this specification in writing with the Government. GIS data and related datasets shall be developed and delivered in an ESRI personal geodatabase or an ESRI file geodatabase format.

1.3.2. Geospatial Data Standards - The Contractor shall develop all geographic information utilizing Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE).

1.3.2.1 The contractor shall refer to the associated PWS for any required attribution related to OSD, USAF, ANG and Federal requirements. For additional reference, a copy of the SDSFIE guidelines may be obtained by visiting the SDSFIE website at http://www.sdsfieonline.org.

1.3.2.2. The Contractor shall submit a written request for approval of any deviations from the Government’s established GIS standard. No deviations from the Government’s established GIS standard will be accepted unless prior written approval of such mailto:usaf.jbanafw.ngb-a4.mbx.a4-geohelp@mail.mil http://www.sdsfieonline.org/ deviation has been received from the Government.

1.3.3. Map Documents – All Geospatial data delivered shall have an associated ESRI ArcMap document (.mxd). The ESRI ArcMap document shall be saved with reference to the data delivered. All reference to data shall be stored as a relative path.

1.4. Geospatial Data Projection

All geospatial data shall be developed in the applicable zone of the Universal Transverse Mercator (UTM) Coordinate System, using the World Geodetic System of 1984 (WGS 84) as the earth datum, and units of meters. This projection requirement applies to all GIS data layer deliverables.

1.5. Accuracy Standards

1.5.1. Map or drawing scales shall be determined by the Government and in accordance with those specifications outlined in a publication by the Federal Geographic Data Committee (FGDC) entitled “Geospatial Positioning Accuracy Standards Part 4: Standards for Architecture, Engineering, Construction (A/E/C) and Facility Management”. Documentation on these standards may be obtained online at http://www.fgdc.gov/standards/projects/FGDC-standards- projects/accuracy/part4/FGDCendorsed-standard.

1.5.2. Mapping accuracy for the agreed scales shall conform to the FGDC’s “Geospatial Positioning Accuracy Standards Part 3: National Standard for Spatial Data Accuracy”. Copies of the FGDC Accuracy Standards may be obtained online at http://www.fgdc.gov/standards/projects/FGDCstandards-projects/accuracy/part3/chapter3.

1.6. Metadata

1.6.1. For each digital file delivered containing geographic information the Contractor shall provide documentation consistent with the FGDC Content Standards for Digital Geospatial Metadata (CSDGM). Both ‘Mandatory’ and ‘Mandatory as Applicable’ fields shall be completed for each geographic dataset. The documentation shall include, but not limited to, the following:

ANG Summary Metadata Profile

CSDGM Element Number CSDGM Element Name

Section 1 -

1.1 Citation

1.1 Data Set Originator

1.1 Data Set Publication Date

1.1 Data Set Title

1.2 Description

1.2.1 Description, Abstract

http://www.fgdc.gov/standards/projects/FGDC-standards-http://www.fgdc.gov/standards/projects/FGDC-standards-http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part4/FGDC-endorsed-standard http://www.fgdc.gov/standards/projects/FGDCstandards-projects/accuracy/part3/chapter3 http://www.fgdc.gov/standards/projects/FGDC-standards-projects/accuracy/part3/chapter3

1.2.2 Description, Purpose

1.3 Time Period of Content

1.3 Time Period of Content

1.3.1 Time Period of Content, Currentness Reference

1.4 Status

1.4.1 Status, Progress

1.4.2 Maintenance and Update Frequency

CSDGM Element

Number CSDGM Element Name

1.7 Access Constraints

1.7 Access Constraints

1.8 Use Constraints

1.8 Use Constraints

1.9 Point of Contact

1.9 Contact Organization

1.9 Contact Person

1.9 Contact Position

1.9 Contact Address

1.9 Address Type

1.9 Address

1.9 City

1.9 State or Province

1.9 Postal Code

1.9 Country

1.9 Contact Voice Telephone

1.9 Contact Electronic Mail Address

1.9 Hours of Service

1.12 Security Information

1.12.2 Security Classification

Section 2 – Attribute Accuracy

2.3 Completeness

2.3 Completeness Report

2.4 Positional Accuracy

2.4.1.1 Horizontal Positional Accuracy Report

2.5 Lineage

2.5.1.1 Source Originator

2.5.1.1 Source Publication Date

2.5.1.1 Source Title

2.5.1.1 Geospatial Data Presentation Format

2.5.2.1 Process Description

Section 5 – Entity and Attribute

5.2 Overview Description

5.2.1 Entity and Attribute Overview

Section 6 – Distribution Information

6.2 Resource Description

6.2 Resource Description

6.4 Standard Order Process

6.4.2.1.1 Format Name

6.4.2.1.7 Transfer Size

Section 7– Metadata Reference 7.1-7.4 Metadata Date

7.1 Metadata Date

7.4 Contact Organization

7.4 Contact Person

7.4 Contact Position

CSDGM

Element Number CSDGM Element Name

7.4 Contact Address

7.4 Address Type

7.4 Address

7.4 City

7.4 State or Province

7.4 Postal Code

7.4 Country

7.4 Contact Voice Telephone

7.4 Contact Electronic Mail Address

7.4 Hours of Service

1.6.2. Metadata generation tools included in the ArcGIS suite of software shall be used in the production of the required metadata in XML format. The Contractor shall ensure that the metadata is delivered in XML format and can be easily imported into the ANG geospatial enterprise system. Copies of the FGDC metadata standard can be obtained online at http://www.fgdc.gov.

1.6.3. The metadata should be formatted from the installation perspective, not the Contractor perspective. For example, Point of Contact should be the installation POC currently associated with the data and NOT the Contractor’s Project Manager.

1.7. Data Transfer

1.7.1. Geographic data shall be delivered in uncompressed, unzipped format on a separate Compact Disc read-only memory (CD-ROM) or Digital Versatile Disc read-only memory (DVD-ROM). The contractor shall NOT include “working files” used to develop the final deliverables. The contractor shall include an ASCII text file titled README.TXT within each CD or DVD delivered to the Government. The README file will describe the contents of the disc (e.g. file names, file contents, etc.). With respect to geospatial data, README files should not be delivered in lieu of standard metadata.

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

1.7.2. All electronic media deliverables shall be permanently labeled and include, at a minimum, the following information:

1.7.2.1. The Contract Number (and Delivery Order Number if applicable) and date.

1.7.2.2. The format and version of operating system software.

1.7.2.3. The sequence number of the digital media.

1.7.2.4. A list of the filenames on the digital media (as space on the label permits).

1.7.2.5. The name of the contracting firm.

1.8. ANG Data Review Methodology

1.8.1. All digital geographic maps, related data, and text documents are reviewed using manual and automated QA/QC methodologies throughout the draft and final contract submittals.

1.8.2. For GIS data deliverables, the Government shall review the geographic data structure and may make recommendations on changes necessary to the structure prior to acceptance of data for subject content, system compatibility, and to ensure compliance with SDSFIE (including appropriate SDSFIE version). The Contractor will incorporate the necessary changes to data until the data meets the appropriate standards of acceptability.

1.9. Ownership

1.9.1. All text, electronic digital files, data, source code, and other products generated, modified, or developed under this contract shall become the property of the government. The information shall be returned to the government unless otherwise specified herein. The Contractor shall not use or distribute this material without specific permission of the Contracting Officer (KO) or the Contracting Officer’s Representative (COR). All notes on the deliverables shall be part of this contract.

1.9.2. The Government has the right to inspect the work and will have access to and the right to make copies of the above-mentioned items. By reference, the following DFAR clauses are included in this contract as a part of the requirements herein:

1.9.2.1. DFAR 252.227-7013, “Rights in Technical Data - Noncommercial Items.”

1.9.2.2. DFAR 252.227-7017, “Identification and Assertion of Use, Release, or Disclosure Restrictions.”

1.9.2.3. DFAR 252.227-7020, “Rights in Special Works.”

1.9.2.4. DFAR 252.227-7028, “Technical Data or Computer Software Previously Delivered to the Government”

1.9.2.5. DFAR 252.227-7037, “Validation of Restrictive Markings on Technical Data.”

1.9.2.6. DFAR 252.227-7025, “Limitations on the Use or Disclosure of Government-

Furnished Information Marked with Restrictive Legends.”

1.9.2.7. DFAR 252.227-7014, “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.”

SECTION 2 REFERENCES

2.1. Defense Installation Spatial Data Infrastructure (DISDI) Group, Spatial Data Standards for Facilities, Infrastructure and Environment, 2020.

2.2. Federal Geographic Data Committee (FGDC) Standard 001-1998, Content Standards for Digital Geospatial Metadata (CSDGM) Version 2.

2.3. FGDC Standard 007.3-1998, Geospatial Positioning Accuracy Standards, Part 3:

National Standard for Spatial Data Accuracy.

2.4. FGDC Standard 007.4-2002, Geospatial Positioning Accuracy Standards, Part 4:

Standards for Architecture, Engineering, and Construction (A/E/C) and Facility Management.

1.1. Digital Content
1.2. Air National Guard (ANG) Enterprise-Standard Software Applications
1.3. Geospatial Data Deliverable Standard
1.4. Geospatial Data Projection
1.5. Accuracy Standards
1.6. Metadata
1.7. Data Transfer
1.8. ANG Data Review Methodology
1.9. Ownership

File details come from the government source that posted it. Updated .