Sect J Atch 3 Geobase Requirements.pdf

SECTION J, ATTACHMENT 3

FA4407-11-R-0006

GEOBASE REQUIREMENTS

A. Introduction

1. This section establishes the requirements for geospatial data deliverables produced as part of the design-build contract. It includes description of the:

a. Coordinate System and Datum;

b. Data Quality Standard;

c. Deliverables;

d. SDSFIE-Compliant GIS Deliverable Specification; and

e. Metadata.

B. Coordinate System and Datum

1. All geospatial deliverables (CADD or GIS format), whether obtained via survey or any other data collection process, shall be measured in meters. The coordinate system for all geospatial data will be the Illinois State Plane Coordinate System 1202 East. The vertical datum will be North American

Vertical Datum 1988 (NAVD 88). The horizontal datum will be NAD83.

C. Data Quality Standard

1. As Built Survey - An as-built condition survey should be performed to capture the information listed in this section. All relevant features shall be identified on as-built drawings compliant with the A/E/C/ standard and the

SDSFIE and shall be surveyed to the level of accuracy specified below using conventional survey methods or the Global Positioning System (GPS).

2. Coordinate Accuracy - The Contractor shall use conventional surveying and other methods, such as a total station or GPS for field data collection at an accuracy level in accordance with “Geospatial

Positioning Accuracy Standards, Part 4: Architecture, Engineering Construction, and Facilities

Management” published by the FGDC and available at http://www.fgdc.gov/standards/standards_publications/index_html. Horizontal and vertical accuracy of features, where vertical coordinates are collected, shall be +/- 2cm.

3. Surveyor Certification Requirement - The surveyor shall verify the survey for accuracy and a statement will be provided to the government stating the level of accuracy for the data being reported

(in metric units). In addition to the accuracy statement, the following information should be provided in the metadata and survey report:

a. Coordinate system & datum used;

http://www.fgdc.gov/standards/standards_publications/index_html

b. Projection;

c. Units of measure (vertical and horizontal);

d. Attribute descriptions (GPS data dictionary—features, attributes and attribute values);

e. Source - Receiver type, antenna type, receiver settings, number of positions per point feature, correction method and any other relevant field procedures utilized;

f. Survey method;

g. Equipment list;

h. Calibration documentation;

i. Description of control points and control diagrams;

j. Field notes; and

k. Field-collected data (in addition to the post-processed final data used to prepare the geospatial data deliverable).

4. Utilities - Underground and aboveground utility lines shall be surveyed at a minimum of two points along every straight run, at every change of direction, at every tie in point, and at any change in line size.

5. Conventional Data Collection Procedures

a. The government has determined that the Contractor may use industry-accepted standard procedures for preparing drawings showing the location of site features as constructed. The

Contractor must include in the metadata a discussion of the methods used and the resulting horizontal and vertical accuracy of the data.

b. Government preference is for the contractor to certify that all features mapped are accurate within [+/- 0.5 meters] in accordance with “Geospatial Positioning Accuracy Standards, Part 4:

Architecture, Engineering Construction, and Facilities Management”. Published by the FGDC and available at http://www.fgdc.gov/standards/standards_publications/index_html.

D. Deliverables

1. The intent of the deliverable set is to provide the Installation with comprehensive geospatial information about the facility footprint and site features that exist outside the building(s). The electronic deliverables must be in the file format and data standard used by the Installation’s

Operations and Maintenance System.

2. The Installation requires deliverables in the following software formats:

http://www.fgdc.gov/standards/standards_publications/index_html

a. CADD Files

(1). AutoCAD, version (most current)

(2). The coordinate system, projection, datum(s) and units will be documented in the metadata.

(3). All CADD files will be georeferenced

b. GIS Files

(1). ESRI geodatabase or ESRI shapefile

(2). The coordinate system, projection, datum(s) and units will be defined for the layer and will be documented in the metadata.

(3). Where captured, vertical coordinate information will be stored as a feature attribute.

(4). All GIS and CADD data will be compliant with the SDSFIE and A/E/C Standard respectively.

3. 100% Design (Design Complete) - Final design deliverables for each design package shall consist of:

a. 100% complete drawings, specifications, calculations/design analysis, and a list of all comments and their resolution for that work package. All final design drawings will be in the A/E/C CADD Standard format, current version as agreed upon by the government and the contractor. The A/E/C CADD Standard is available at https://tsc.wes.army.mil/products/standards/aec/aecstdweb.asp. Metadata shall be delivered with each data file, and will meet the standard specified in this Appendix.

b. A corresponding SDSFIE-compliant GIS deliverable for the feature layers listed in Table

[M-1]. For each listed layer the contractor will provide either a GIS deliverable or a statement that no features in that layer will be constructed, be modified, or pose a design constraint for the project. The SDSFIE standard is available at http://www.sdsfie.org/Support/Downloads/tabid/75/Default.aspx. Metadata shall be delivered with each GIS data layer and will meet the standard specified in this Appendix.

4. As-Built (Construction Complete)

a. The contractor will provide a submittal of the CADD and GIS files that depict the as-built condition of the site. The data layers to be delivered, the coordinate accuracy of the features, the required attribution, and the metadata will meet the standards specified in this Appendix.

b. For each layer listed in Table 1, the contractor will provide either a GIS deliverable or a statement that no features in that layer were constructed or modified. The tie in to a utility main https://tsc.wes.army.mil/products/standards/aec/aecstdweb.asp http://www.sdsfie.org/Support/Downloads/tabid/75/Default.aspx line is considered a modification of the utility main line, and the portions of main lines that were exposed should therefore be included in the deliverable.

E. SDSFIE-Compliant Deliverable Specification

1. Geodatabase Template

a. Upon request, the government will provide the contractor with an SDSFIE-compliant GIS layer template to be used for populating the GIS deliverables required under the contract. The contractor shall populate the layers without modifying the template. The contractor shall ensure that layers to be delivered but not included in the template are fully compliant with the current

SDSFIE standard.

b. There may be circumstances in which SDSFIE compliance cannot be maintained. In such circumstances, proposed deviations with the standard must be communicated by the contractor and reviewed by the government.

2. Data Integrity Check - The contractor shall implement topology rules to assure the following:

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

b. Lines should all be continuous, i.e. do not create dashed lines with many small line segments;

c. Point features should be digitized as points, not graticules, cells, symbols or icons;

d. No sliver polygons;

e. All polygons completely close and have a single unique centroid; and

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

3. Required GIS Data Layers and Required Attributes - Table 1 lists the SDSFIE-compliant GIS data layers that are to be delivered as part of this contract. The list is based on a review of the type(s) of facility(s) being constructed. However, it is possible that some layers in the list will not be used.

Table 1. SDSFIE Layer Names and Required Attributes.

Note: Required attributes, where specified, are listed following the SDSFIE layer name. Vertical coordinate information is required for layers where “coord_z” is listed as a required attribute.

SEE ATTACHED SPREADSHEET

F. Metadata

1. The contractor shall prepare metadata conforming to Federal Geographic Data Committee (FGDC)

Content Standards for Digital Geospatial Metadata (CSDGM) most current version

(http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html ).

Metadata content will accompany all electronic geospatial data submissions. This includes both

CADD and GIS formats. A metadata file shall accompany, at minimum, each CADD file and each

GIS-format geospatial data layer delivered by the contractor. Metadata should be prepared to FGDC standards and delivered in XML format readable by software applications that use the FGDC XML format standard (such as ESRI ArcMap v9.x XML-format metadata files). The digital metadata files shall be provided to the Government along with each product deliverable.

2. Metadata Standard

In addition to the requirements described above, the guidance provided in Table 2 shall be followed when preparing metadata. This metadata minimum requirements profile has been compiled by the

Department of the Army. These minimum required components must be supplied by the contractor with each CADD file and each GIS-format geospatial data layer. This metadata requirements profile is the baseline standard for all Army Garrisons and for all Military Construction projects.

http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html

Table [2]. Required Metadata Information

Section 1 – Identification

CSDGM Element

Number

CSDGM Element Name Description Valid Values

1.1 Citation

1.1

(Citation 8.1)

Identification

(Data Set Originator)

The name of an organization that provided the data set.

This will contain the name of the service, a single space, followed by the installation or organization name.

Service names:

“USAF”

“USAFR”?

“USAFNG”?

Example values:

“USAF Scott AFB”

“USAF Center of Environmental Excellence”

“USAF Civil Engineer Support Agency”

1.1

(Citation 8.2)

Identification

(Data Set FDP Publication Date)

The date of release or current version of the file. This represents the date that a given overlay layer and associated metadata file were “locked” for approval by the base-level command authority (as described in Section

8.2).

Format:

yyyymmdd

Example values:

“20031128” (representing 28 Nov 03)

1.1

(Citation 8.4)

Identification

(Data Set Title)

The name by which the data set is referred. For all AF installation data the SDSFIE Entity Type name will be used. (To enhance ability to search all underscores will be replaced with spaces.)

Valid values:

SDSFIE Entity Type

Example Values firing line military range area noise contour line

1.2 Description

CSDGM Element

Number

CSDGM Element Name Description Valid Values

1.2.1 Description, Abstract A brief narrative of the data set. For all AF installation data the SDSFIE Entity Type Definition will be used.

Valid values:

SDSFIE Entity Type Definition

Example value:

The designated hazard area created by the weighted noise application.

1.2.2 Description, Purpose A summary of the intentions with which the data set was developed.

Valid value:

Free Text

Example Value:

1.3 Time Period of Content

1.3

(Citation 9.1.1)

Time Period of Content

(Single Calendar Date)

The latest date the data represented the actual conditions on the ground.

This field is used to capture neither the publication date of a study or of a hardcopy map nor the date the hardcopy was converted to digital format, but rather the latest date the conditions at the location were measured or derived.

If only the month and year are known, but not specific day within the given month, enter zeros (“0”) in the place of “dd” as shown.

Valid Values:

Date

Unknown

Format:

yyyymmdd

Example values:

“20070101” (representing 01 Jan 07)

“20061128” (representing 28 Nov 06)

“20050100” (representing Jan 05)

1.3.1 Time Period of Content, Currency

Reference

Reference for the Time Period of Content. For all Army

Installation data this value will be "Ground Condition."

Valid Values:

Ground Condition

CSDGM Element Name Description Valid Values

1.9 Point of Contact

The Point of Contact (POC) should be the mission knowledge expert who identified the data source, and shall not be the base-level GIS/mapping POC (unless the POC authoring the metadata file is the same person as the mission knowledge expert responsible for source selection). In the event the mission knowledge expert is a contractor, the organizational information should reflect the government office for which the contractor works, not the contractor company information.

The name of the individual/organization responsible for creating the metadata file is recorded in CSDGM element 7.4, Metadata Contact.

1.9

(Citation 10.1.1)

Point of Contact

(Contact Person)

Name of mission knowledge expert responsible for selecting the source for the given FDP layer

Example Values:

“John Smith”

“Joe Q Public”

1.9

(Citation 10.1.2)

Point of Contact

(Contact Organization)

Organization name (or office symbol for military organizations) of the mission knowledge expert.

Example Values:

“375 Civil Engineer”

1.9

(Citation 10.3)

Point of Contact

(Contact Position/Title)

Title of the mission knowledge expert. Example Values:

“Civ” – Civilian

“Contr” – Contractor

Military titles including:

“Capt”

“MSgt”

“Lt Col”

1.9

(Citation 10.4.1)

Point of Contact

(Address Type)

The type of address provided. Must be one of the following valid values:

Valid Values:

“mailing”

“physical”

“mailing and physical”

“po box”

Other (describe)

1.9

(Citation 10.4.2)

Point of Contact

(Address)

Address line for the mission knowledge expert. Example Values:

“375 CES/CEED”

“701 Hangar Drive”

“Scott AFB, IL 62225”

1.9

(Citation 10.4.3)

Point of Contact

(City)

The address city for the mission knowledge expert. Example Values:

“Washington” (for Washington DC)

“Honolulu”

CSDGM Element Name Description Valid Values

“San Diego”

1.9

(Citation 10.4.4)

Point of Contact

(State or Territory)

The address state or territory for the mission knowledge expert. Use accepted two-letter Postal state/territory codes for this field.

Example Values:

“DC” – Washington, DC

“VA” – Virginia

“GU” – Guam

1.9

(Citation 10.4.5)

Point of Contact

(Postal/ZIP Code)

The ZIP code for the mission knowledge expert. Nine digit ZIP codes, with dashes, preferred, but five digit zip codes will be accepted.

Example Values:

“22030-1260”

“80330”

1.9

(Citation 10.4.6)

Point of Contact

(Country)

Mission knowledge expert address country. Example Value:

“USA”

1.9

(Citation 10.5)

Point of Contact

(Telephone Number)

Mission knowledge expert Telephone number, including all applicable area codes and extensions.

Commercial numbers are preferred, and should be preceded with “COMM” as shown. However, if only DSN numbers are available, enter that number here and precede the number with “DSN” as shown:

Example Values:

COMM 123-456-7890

COMM 123-456-7890 ext: 345

DSN 123-456-7890

DSN 123-4567

1.9

(Citation 10.8)

Point of Contact

(EMAIL address)

The email address for the mission knowledge expert. Example Values:

“john.smith@basename.af.mil”

“john.smith@navy.mil”

Section 2 – Data Quality Information

Number

CSDGM Element Name Description Valid Values

2.3 Completeness Report

2.3 Completeness Report Information about omissions, selection criteria, If no omissions are present – Valid Value:

CSDGM Element Name Description Valid Values generalizations, definitions used, and other rules to derive the data set.

Use this field to record if any features (e.g., wetland polygon, floodplain polygon, APZ or ESQD clear zone, noise contour, or installation boundary element) were excluded from the data set for any reason.

“Complete data set”

If omissions are present – Valid Value:

Free text, describing any map features/elements that exist on the ground but have been omitted from the FDP data set due to classification constraints.

Example Values:

“Wetlands from 1999 restoration study not included because {provide justification}”

“New boundary from 2003 land transfer to

{jurisdiction] not shown as the boundary re-survey has not yet been performed.”

2.5 Lineage

The following section may be repeated numerous times in the event that multiple sources were selected and used to develop any given overlay layer. Most metadata management applications (including ESRI ArcCatalog and the USACE CorpsMet application) can accommodate numerous source citations.

2.5.1.1

(Citation 8.1)

Lineage, Source Citation

(Source Originator)

The name of the individual or organization that developed the source of the data set. Must be one of the following valid values:

Valid Values:

{Source originator name}

2.5.1.1

(Citation 8.2)

Lineage, Source Citation

(Source Publication Date)

The date when the source was published or otherwise made available for release.

If only the month and year are known, but not specific day within the given month, enter zeros (“0”) in the place of “dd” as shown.

Must be one of the following valid values:

Valid Values:

“Unknown”

“Unpublished material”

{date}

Date Format:

yyyymmdd

Example date values:

“20020101” (representing 01 Jan 02)

“20031128” (representing 28 Nov 03)

“19980100” (representing Jan 98, where the specific day is not provided)

2.5.1.1 Lineage, Source Citation The name by which the source of the FDP Layer is Valid Values:

CSDGM Element Name Description Valid Values

(Citation 8.4) (Source Title) known. This could be the name of a local study, a national data set, a standard business process by which the data are generated, etc.

{source name}

Example values:

”Short-Range Component”, Long-Range

Component’, “Summary Development Plan”

(Mead Sams)

2.5.2.1 Lineage, Process Description General description of the process used to convert the source identified in CSDGM metadata elements 2.5.1.1 and 2.5.1.6 to new format and delivery specifications as per Section 5.5.2. The purpose of this value is to help auditors understand the method used to convert the source and any potential error introduced, as per Sections

6.5 and 6.6.

This field is free text. Metadata authors are encouraged to use one or more of the following statements when describing the source conversion process:

Recommended Values:

"Scanned and verctorized source map using

ESRI ArcScan."

“Converted georeferenced GIS file to SDSFIE specifications”

“Converted georeferenced CADD file to

SDSFIE specifications”

“Georeferenced unregistered GIS file and converted to SDSFIE specifications”

“Georeferenced unregistered CADD file and converted to SDSFIE specifications”

“Registered digitization of hardcopy source”

“Heads-up digitization of hardcopy source at scale of 1:50,000”

“COGO data entry from source”

“Scanned and vectorized source map”

Other (specify)

Section 4 – Spatial Reference Information

Number

CSDGM Element Name Description Valid Values

4.1 Horizontal Coordinate System Definition

4.1.1.3 Geographic Coordinate Units Measurement units for horizontal coordinates. Must be the following value:

Valid Value:

"Degrees, minutes, and decimal seconds"

4.1.2.2.1 Grid Coordinate System, Coordinate System Name

The name of the coordinate system for data. Must be the following value:

Valid Value:

“State Plane”

4.1.2.2.2 UTM Zone Number Identifier of the UTM Zone the data set falls within. Must be the following value:

Valid Value:

See Note Below.

4.1.2.2.4.1 SPCS Zone Identifier Identifier for the State Plane Coordinate System zone. Valid Value:

See Note Below.

4.1.4.1 Horizontal Datum Name Name of the reference system used for defining horizontal coordinates. Must be the following value:

Valid Value:

“North American Datum of 1983”

Note: Four-digit numeric codes for the State Plane Coordinate Systems based on the North American Datum of 1927 are found in Department of Commerce, 1986, Representation of geographic point locations for information interchange (Federal Information Processing Standard 70-1): Washington: Department of Commerce, National Institute of Standards and Technology.

Codes for the State Plane Coordinate Systems based on the North American Datum of 1983 are found in Department of Commerce, 1989 (January), State Plane

Coordinate System of 1983 (National Oceanic and Atmospheric Administration Manual NOS NGS 5): Silver Spring, Maryland, National Oceanic and Atmospheric

Administration, National Ocean Service, Coast and Geodetic Survey.