ID07180034_Supporting_Documents_Part_5.pdf

Page 1 of 6 Digital Data Request Document version 1.3 20181004

Air Force Civil Engineer Center Environmental GIS

Digital Data Request Form

AFCEC Environmental Functional Data Sets Air Quality

Cultural Resources

Hazardous Materials

Hazardous Waste

Integrated Solid Waste

Restoration

Tanks

Water Quality

Habitat Disturbance Area

Air Emission Source

Archaeological Site SENSITIVE Cemetery or Burial Site SENSITIVE Cultural Resources Potential Area Cultural Restricted Access Cultural Survey Area Historic Building Historic District Historic Landscape Historic Object Native Affiliation Sacred Site SENSITIVE Traditional Cultural Resource SENSITIVE

Hazardous Material Site

Hazardous Waste Site

Solid Waste Landfill Solid Waste Management

Environmental Operable Unit Environmental Restoration Site Environmental Restoration Sample Location Land Use Control

Restoration Treatment System Restoration Treatment System Complex Pipes Restoration Treatment System Complex Wells

Environmental Water Quality Permit Environmental Water Quality Sample Location Spill Incident Area

Potential Environmental Site

Storage Tank

Natural Resources Agricultural Tract Coastal Zone Management Area Dispersed Recreation Area Essential Fish Habitat Fauna Incident Point Fire Area Fire Break Line Flood Plain Area Forest Compartment Forest Management Area Forest Product Harvest Forest Stand Fuel Break Line Fuel Management Area

Habitat Protective Zone Hazardous Suppression Area Historic River Alignment Land Cover Natural Resource Recreation Feature NR Restoration Reclamation Project Natural Resource Survey Noxious or Invasive Species Prescribed Burn Unit Recreation Nature Trail Soil Survey Area Special Management Area Special Status Species Species Area Species Specific Habitat Surface Riparian Area Vegetation Water Body Watercourse Line Water Feature Watershed Wetland Wildland Urban Interface Area Wildlife Management Area

Environmental Constraints Environmental Constraints

Page 2 of 6 Digital Data Request Document version 1.3 20181004

Air Force Civil Engineer Center Environmental GIS

Digital Data Request Form

Installation Specific Air Force Environmental Mission Data Layers

AF Installation*

AF Authorizer ** Position Title Affiliation/Org.

Email and Phone

Signature

GIS Data Requestor Position Title Affiliation/Org.

Email and Phone Task Order # **

GIS Data Fulfiller Position Title Affiliation/Org.

Email and Phone Date Request Fulfilled

*Additional installations can be added on page 3.

**See instructions on page 5 for additional information on data request procedures

SENSITIVE data layers may not be accessed by unauthorized individuals or used in cartographic representations without explicit consent of the Air Force Authorizer or the respective data steward. When authorization to display Sensitive data layers is granted they must be represented using an irregular buffer to obscure precise locations of sensitive information. These restrictions are IAW the Archaeological Resources Protection Act, 16 USC § 470hh and National Historic Preservation Act, 54 USC § 307103.

Requestor or Authorizer initial consenting to sensitive data layer restrictions

Page 3 of 6 Digital Data Request Document version 1.3 20181004

Air Force Installations

01. 02. 03.

04. 05. 06.

07. 08. 09.

10. 11. 12.

13. 14. 15.

16. 17. 18.

19. 20. 21.

22. 23. 24.

25. 26. 27.

28. 29. 30.

31. 32. 33.

34. 35. 36.

37. 38. 39.

40. 41. 42.

43. 44. 45.

46. 47. 48.

49. 50. 51.

52. 53. 54

55. 56. 57.

58. 59. 60.

61. 62. 63.

64. 65. 66.

67. 68. 69.

70. 71. 72.

73. 74. 75.

76. 77. 78.

79. 80. 81.

82. 83. 84.

85. 86. 87.

88. 89. 90.

91. 92. 93.

94. 95. 96.

97. 98. 99.

100.

Air Force Authorizer Position Title Affiliation/Org.

Email and Phone

Signature

Page 4 of 6 Digital Data Request Document version 1.3 20181004

Air Force Authorizer Position Title Affiliation/Org.

Email and Phone

Signature

Air Force Authorizer Position Title Affiliation/Org.

Email and Phone

Signature

Air Force Authorizer Position Title Affiliation/Org.

Email and Phone

Signature

Air Force Authorizer Position Title Affiliation/Org.

Email and phone

Signature

Air Force Authorizer Position Title Affiliation/Org.

Email and Phone

Signature

Page 5 of 6 Digital Data Request Document version 1.3 20181004

Single Base Data Request

Single Program Area – Use the below steps to complete pages 1 & 2 when requesting data for a single installation and a single program area.

1. Select all requested feature classes on page 1

2. Provide data layer name for any installation specific Air Force environmental data layers (pg 2)

3. Enter the AF Installation name for requested data (pg 2)

4. AF Authorizer for single program area requests will be the installation program manager for the feature classes requested. To sign with certificates in Adobe Acrobat Pro follow the below instructions (pg 2)

i. Select the Tools icon from the menu bar

ii. Click the certificates icon with “Add” selected in the dropdown menu

iii. Select “Digitally Sign” from the Certificates menu

iv. Drag a box in the signature block where the digital signature will appear and select “Sign” in the pop-up that appears

v. Save the signed pdf as prompted

5. GIS Data Requestor section should have all fields populated with current information. All requests fulfilled for work associated with a contract or cooperative agreement should populate the Task Order (TO) Number section, all others may leave this line blank. (pg 2)

6. Persons requesting feature classes marked as sensitive must initial following the statement on page 2 acknowledging the restrictions placed on those layers.

7. Submit completed requests to the CSU ISS Analyst

8. GIS Data Fulfiller section to be completed by the CSU ISS Analyst fulfilling the data request (pg 2)

Multiple Program Areas – Follow the same steps as detailed above in the Single Program Area request, however, instead of having the program manager sign as the AF Authorizer have the Environmental Chief sign for authorization and complete pages 1 & 2. If individual Program Manager authorization is preferred, have each individual program manager for the respective feature class requested sign as authorizers on pages 3 & 4.

Page 6 of 6 Digital Data Request Document version 1.3 20181004

Multiple Base Data Request

Use the below steps to complete pages 1-4 when requesting data for a single or multi program areas for multiple installations.

1. Select all requested feature classes on page 1

2. Provide data layer name for any installation specific Air Force environmental data layers and include the AF Installation beside the data layer name (pg 2)

3. Enter the AF Installation name for requested data, additional installations can be added on

4. AF Authorizer for multiple base data requests should include the signature of the AFCEC SME overseeing the contract for which data is being requested. Enterprise requests submitted through the GIO office require GIO authorization. To sign with certificates in Adobe Acrobat Pro follow the below instructions (pg 2)

i. Select the Tools icon from the menu bar

ii. Click the certificates icon with “Add” selected in the dropdown menu

iii. Select “Digitally Sign” from the Certificates menu

iv. Drag a box in the signature block where the digital signature will appear and select “Sign” in the pop-up that appears

v. Save the signed pdf as prompted

5. GIS Data Requestor section should have all fields populated with current information. All requests fulfilled for work associated with a contract or cooperative agreement should populate the Task Order (TO) Number section, all others may leave this line blank. (pg 2)

6. Persons requesting feature classes marked as sensitive must initial following the statement on page 2 acknowledging the restrictions placed on those layers

7. Submit completed requests to the CSU Program Analyst

8. GIS Data Fulfiller section to be completed by the CSU analyst fulfilling the data request (pg 2)

March 01, 2018

Data Layer Specifications for:

Cultural Restricted Access

United States Air Force

Environmental GIS Program

Data Layer Specification – Cultural Restricted Access

2 | P a g e

Revision History Date: Version: Description of Revision:

12/12/2016 CulturalRestrictedAccess _20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

10/4/2016 CulturalRestrictedAccess _20161004

Updated feature class code used for creating Resource ID when MCRAD data is not present.

6/23/2016 CulturalRestrictedAccess _20160623

Updated “Positional Accuracy” section.

3/10/2017 CulturalRestrictedAccess _20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 CulturalRestrictedAccess _20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

03/01/2018 CulturalRestrictedAccess _20180301

Updated the “Definition”, “Geometry/Topology”, “Positional Accuracy”, “Attributes”, “Business Tables,” and “Appendix 1: SDSFIE 3.1.1 AF AFCEC/CZ Adaptation Attribute Domain Tables” sections.

3 | P a g e

This Data Layer Specification (DLS) defines geospatial data specifications for the

CulRestrictedAccess_A data layer implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition An area that has restricted access due to cultural concerns.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

CulRestrictedAccess_A

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalCulturalResources

Previous Layer Names:

cultural_restricted_area CulturalRestrictedAccess

Geometry Type: Polygon

Data Steward Organization (Program Area):

Program Area: Cultural Resources

Data Steward POC: AFCEC/CZTQ Air Force Cultural Resources Program SME

Representation:

Cultural restricted access areas are represented as closed polygons depicting the outermost extent of the area.

Each individual cultural restricted access area is represented by a single area feature.

Implementing Authorities and Regulations Implementing Program(s):

Driver(s):

HQ AF/A7CAN

36 CFR 60.4, Criteria for evaluation, 1 July 2012

36 CFR 63.2, Determination of eligibility process, 1 July 2012

36 CFR 800, Protection of Historic Properties, 1 July 2012

Historic Sites Act of 1935

National Historic Preservation Act of 1966

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 18 November 2014

4 | P a g e

Implementing Program(s):

Driver(s):

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Geometry/Topology Polygon Features:

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Military Cultural Resources Analysis Database (MCRAD) is a relational data model that uses the functionality of Microsoft Access. It was created by Dr. Paul Green in collaboration with Dr. Brian

Crane to resolve the issues that arise due to idiosyncratic formats of cultural resource data. MCRAD has been refined to support cultural resource business practices with DoD-wide input and has been adopted by the Deputy Under Secretary of Defense for Installations and Environment as a cultural resources geodata standard. MCRAD, if being used, should only be used to populate the business tables.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

5 | P a g e

Positional Accuracy Horizontal Accuracy: Data developed within this layer is meant to hide the true location of culturally sensitive areas, thus horizontal positional accuracy is not applicable.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System

The bounding coordinates to capture the north, south, east, and west most spatial extents of the

CulRestrictedAccess_A layer will be based on the Universal Transverse Mercator (UTM) Zone, meters. Datasets within the database should have a spatial reference with a precision of 1000. The horizontal datum to be utilized for all data is World Geodetic System 1984 (WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the CulRestrictedAccess_A data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate culRestrictedAccessIDP

K

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7 digit unique number starting with 0000001.

String (20)

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

6 | P a g e

Domain (D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate sdsFeatureName The common name of the feature.

Any common name used to describe the Cultural Restricted

Access area.

String (80)

SDSFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the

Cultural Restricted Access area that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID The foreign key to a metadata record.

(80)

SDSFIE

areaSize The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

D areaSizeUOM The unit of measure for the area of the calculated area.

acre

String (20)

AF

perimeterSize The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF

D perimeterSizeUOM The perimeter unit of measure.

foot

String (25)

AF

latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

Latitude and Longitude values.

AF

7 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate manAreID

Represents the Primary Key

(ManAreID) for the feature in the MCRAD database. If the Man_Are_ID does not currently exist in MCRAD, use a concatenation of the installation siteID, the FDS code (CR), and the feature class code (YYYY) followed by a unique sequential six digit number (example:

XXXX0001CRYYYY0000

01) to develop a unique identifier. This value is used to link to the feature class business table. See feature class Data

Layer Specifications for applicable feature class code.

Feature Class Code for Cultural Restricted Access is “CRAA”.

String (50)

AF

gisDataSource The data source of the feature.

(255)

AF

gisDataReliability The reliability of the

GIS data.

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

AF

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (100)

8 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business rules of the feature class.

AF

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

https://www.extranet.nga.mil/ https://www.extranet.nga.mil/ http://www.nationsonline.org/oneworld/country_code_list.htm http://www.nationsonline.org/oneworld/country_code_list.htm

9 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

Smith would be attributed as "SmithJ."

(30)

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created or generated the

10 | P a g e

Attribute Name Definition Allowed Values Data Type

(Length) Advocate editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, Jane Smith would be attributed as SmithJ.

AF

dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was created or edited and why.

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, and other digital media.

AF

narrative Any additional comments or notes.

AF

GEOLOC

JOPES geolocator code.

(4)

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business table will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. The business table for CulRestrictedAccess_A is:

Table Name Identifier Source cr_CulRestrictedAccess_A ManAreID MCRAD database

11 | P a g e

Business Table Attributes for cr_CulRestrictedAccess_A

(D)

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

ManAreID

Primary Key in MCRAD Management_Area table.

Relates back to CulRestrictedAccess_A data layer attribute table.

MCRAD

Management_Area table

String (50)

Area_Name Name of the management area. MCRAD Management_Area table.

MCRAD

Management_Area table

String (250)

Area_Stt_D The status of the area.

MCRAD

Management_Area table.

MCRAD

Management_Area table

String (16)

Reason

The reason for the restriction or particular procedure. MCRAD Management_Area table.

MCRAD

Management_Area table

String (240)

Mgt_Area_Description Description of the management area. MCRAD Management_Area table.

MCRAD

Management_Area table

String (255)

Mgt_Area_Start_Date

Beginning date of the management area designation. Format for date is YYYYMMDD (i.e., September 15, 1994 =

19940915). MCRAD

Management_Area table.

MCRAD

Management_Area table

Integer (Long)

Mgt_Area_End_Date

End date of the management area designation. Format for date is YYYYMMDD (i.e., September 15, 1994 =

19940915). MCRAD

Management_Area table.

MCRAD

Management_Area table

Integer (Long)

Mgt_Area_Notes Notes. MCRAD

Management_Area table.

MCRAD

Management_Area table String (255)

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

12 | P a g e

For Empty Text Values TBD (To Be Determined) – A value is required but the value has yet to be determined.

unknown The value cannot be reasonably determined.

NA (Not Applicable) No value exists.

For Empty Integer Values 99999 (To Be Determined) – A value is required but the value has yet to be determined.

88888 The value cannot be reasonably determined.

77777 (Not Applicable) No value exists.

For Empty Date Values

9/9/9999 (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete Federal Geographic Data Committee (FGDC) compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are made or as necessary.

Theme Keywords: Cultural Resources, Cultural Restricted Access

Cultural Survey Area

Data Layer Specification – Cultural Survey Area

12/12/2016 CulturalSurveyArea _20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

10/4/2016 CulturalSurveyArea _20161004

Updated feature class code used for creating Resource ID when MCRAD data is not present.

6/23/2016 CulturalSurveyArea _20160623

Updated “Positional Accuracy” section.

3/10/2017 CulturalSurveyArea _20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

6/8/2017 CulturalSurveyArea _20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

03/01/2018 CulturalSurveyArea _20180301

Updated the “Definition”, “Geometry/Topology”, “Positional Accuracy”, “Attributes”, “Business Tables,” and “Appendix 1:

SDSFIE 3.1.1 AF AFCEC/CZ Adaptation Attribute Domain Tables” sections.

This Data Layer Specification (DLS) defines geospatial data specifications for the CulSurveyArea_A and CulSurveyArea_P data layers implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition The area in which a cultural resource inventory has been conducted.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

CulSurveyArea_A CulSurveyArea_P

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalCulturalResources

Previous Layer Names:

cultural_cleared_area cultural_survey_area CulturalSurveyArea

Geometry Type: Polygon, Point

Data Steward Organization (Program Area):

Program Area: Cultural Resources

Data Steward POC: AFCEC/CZTQ Air Force Cultural Resources Program SME

Representation:

A cultural survey area will represent the outermost limit of a known cultural survey.

Each individual survey area is represented by a single area feature.

All points developed from an area shall represent the centroid of the cultural survey area.

Implementing Authorities and Regulations Implementing Program(s):

Driver(s):

HQ AF/A7CAN

AFI32-7064, Integrated Natural Resources Management, 17 September 2004

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7001, Environmental Management, 4 November 2011

AFI32-7045, Environmental Compliance Assessment and Management Program (ECAMP), 1 July 1998

AFI32-7062, Comprehensive Planning, 27 June 2013

Driver(s):

AFI32-7064, Integrated Natural Resources Management, 18 November 2014

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Executive Order (EO) 13287, Preserve America

Geometry/Topology

Polygon Features:

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Point Features:

If a point represents a polygon feature, then the point must fall properly inside of the coinciding polygon.

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Military Cultural Resources Analysis Database (MCRAD) is a relational data model that uses the functionality of Microsoft Access. It was created by Dr. Paul Green in collaboration with Dr. Brian

Crane to resolve the issues that arise due to idiosyncratic formats of cultural resource data. MCRAD has been refined to support cultural resource business practices with DoD-wide input and has been adopted by the Deputy Under Secretary of Defense for Installations and Environment as a cultural resources geodata standard. MCRAD, if being used, should only be used to populate the business tables.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, (CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 3 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated accuracy threshold value.

Vertical Accuracy: Not applicable.

Note: Horizontal accuracy should be recorded within the “Quality” element of the metadata. Where positional accuracy cannot be determined, this section should be populated with “Not Recorded” and a brief statement explaining why it cannot be determined should be provided.

Coordinate System The bounding coordinates to capture the north, south, east, and west most spatial extents of the

CulSurveyArea_A and CulSurveyArea_P layers will be based on the Universal Transverse Mercator

(UTM) Zone, meters. Datasets within the database should have a spatial reference with a precision of 1000. The horizontal datum to be utilized for all data is World Geodetic System 1984 (WGS84), and the projection is the Universal Transverse Mercator (UTM) zone for the installation.

Attributes The following table lists the attributes for the CulSurveyArea_A and CulSurveyArea_P data layer.

SDSFIE 3.1.1 Air Force AFCEC/CZ Adaptation Attributes

(D)

Attribute Name Definition Allowed Values Data Type

(Length) Advocate culSurveyAreaIDPK

The unique identifier for each feature in the feature class. The value should be calculated as follows:

INST_SITE0001000000

1, where INST is the 4 character installation ID, SITE0001 is the 4 character 4 digit site ID, followed by a 7

AF

sdsID A unique identifier for all features and objects in the SDSFIE.

GUID SDSFIE

sdsFeatureName The common name of the feature.

Any common name used to describe the Cultural Survey Area.

String (80)

SDSFIE

sdsFeatureDescription A narrative describing the feature.

Any descriptive information about the Cultural Survey Area that is not already included in the attribute table.

String (255)

SDSFIE

sdsMetadataID

SDSFIE

areaSize

(Polygon geometry) The value of the measured area.

Recorded to the 1/1000 of an acre.

Double AF

D areaSizeUOM

(Polygon geometry)

The unit of measure for the area of the calculated area.

acre

String perimeterSize

The value of the measured perimeter.

Recorded to the 1/1000 of a foot.

Double AF

D perimeterSizeUOM (Polygon geometry)

The perimeter unit of measure.

foot String (25)

Attribute Name Definition Allowed Values Data Type latitude

The latitude coordinate of the "centroid" of the polygon in decimal degrees.

decimal degrees Double AF longitude

The longitude coordinate of the "centroid" of the polygon in decimal

MGRScentroid

Military Grid Reference System for the centerpoint of the

(area) critical infrastructure. MGRS is calculated from the

Latitude and Longitude values.

(Point geometry)

The latitude coordinate in decimal degrees to sub foot precision.

The longitude coordinate in decimal degrees to sub foot

MGRS

Military Grid Reference System for the coordinate point.

MGRS is calculated from the Latitude and

Longitude values.

elevation

The elevation of the subject item in relation to a datum.

Double AF

D elevationUOM

(Point geometry)

The unit of measure for elevation dimension.

foot String

Attribute Name Definition Allowed Values Data Type

(Length) Advocate eventID

Represents the Primary Key (EventID) for the feature in the MCRAD database. If the Event_ID does not currently exist in

MCRAD, use a concatenation of the installation siteID, the FDS code (CR), and the feature class code (YYYY) followed by a unique sequential six digit number (example:

XXXX0001CRYYYY0000

01) to develop a unique identifier. This value is used to link to the feature class business table. See feature class Data

Layer Specifications for applicable feature class code.

Feature Class Codes for Cultural Survey

Area:

Area – “CSAA” Point – “CSAP”.

String (50)

AF

gisDataSource

AF

gisDataReliability

AF

D installationID

Installation identifier assigned to the

Installation by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (16)

AF

D installationName

The actual name of the installation that is associated with the installation ID defined by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D siteID Installation identifier assigned to the Site by real property.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (36)

AF

D majorCommand Service Major

Command of the installation.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

D realPropertySiteUniqu eID

The unique identifier (UID) used to permanently identify a Site. This UID will be a

Real Property Site Unique Identifier (RPSUID). Source:

RPIM, v3.0, extracted 4/2009.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

wacInnrCode The NGA World

Airfield Identifier.

The NGA World Airfield Identifier

Code: List of codes can be accessed at the following site:

https://www.extranet.

nga.mil/

String (10)

AF

dataSteward

The data steward is the entity that oversees the data content, context, and associated business

AF

D country

The country code is an abbreviation for the country that owns the specific feature class.

For the list of domain values see ISO ALPHA-

2 Code / FIPS 10-4 standard.

String (5)

AF

https://www.extranet.nga.mil/ https://www.extranet.nga.mil/ http://www.nationsonline.org/oneworld/country_code_list.htm

Attribute Name Definition Allowed Values Data Type

(Length) Advocate

D owner

The military service, country, government that owns that specific feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (10)

AF

createDate

Date the feature was originally acquired, created or generated.

If the day is unknown, default to the first day of the month. If only the year is known, default to the first day of the year.

Date AF creator

Person who created the feature. Last name of the person and first initial. Example: Jane

AF

D dataCollection

Coded domain value which identifies the collection methodology used to calculate, create or record the feature.

For the list of domain values see the Air

Force GeoBase Data Working Group AF

Adaptation 3.1.1 Data Dictionary.

String (20)

AF

dataSource

Identifies the installation office, government agency, contractor or vendor that acquired, created

Attribute Name Definition Allowed Values Data Type

(Length) Advocate editor

Contractor or person that edited the feature attribution or geometry from its original or previous value. Last Name of the person and first initial. For example, AF dateEdited

Date that the feature was edited from its original or previous value.

Date AF metaNotes

Describes other details about what was

AF

mediaLink

Used to link the record to associated multimedia records that reference data such as imagery, video, audio, scanned documents, drawings, AF narrative

AF

GEOLOC

AF

SHAPE_Length ESRI-generated field. ESRI

SHAPE_Area ESRI-generated field. ESRI

Business Tables The business tables will contain information that goes beyond the attribute table information, which will be related to the data layer using a Feature Key or other Identifier found in both the attribute table and business table. The business tables for CulSurveyArea_A and CulSurvyArea_P are:

cr_CulSurveyArea_A EventID MCRAD Events table cr_CulturalSurveyMethods EventID MCRAD Surv_Meth_Areas table cr_CulturalSurveyTests EventID MCRAD Survey_Tests table

Business Table Attributes for cr_CulSurveyArea_A and cr_CulSurveyArea_P

Domain (D)

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

EventID

Primary Key in MCRAD Events table. Used to link this business table to the appropriate feature class.

MCRAD Events table String (50)

Event_Type

Describes the type of event: Literature Search, Eval, Data Recovery, Accidental Discovery, Vandalism, Unanticipated Effect, etc. MCRAD Events table.

MCRAD Events table / Literature Search, Eval, Data Recovery, Accidental Discovery, Vandalism, Unanticipated Effect, etc.

String (50)

Event_Desc Description of event.

MCRAD Events table.

MCRAD Events table String (255)

Law Preservation law followed or violated. MCRAD Events table.

MCRAD Events table

String (50)

Agency_Num Agency assigned project identifier. MCRAD Events table.

MCRAD Events table

String (20)

Project_Name The name of the project.

MRCRAD Events table.

MCRAD Events table

String (255)

Recorder Individual/Group recording event. MCRAD Events table.

MCRAD Events table String (100)

Lead_Agency Lead agency for Section 106 purposes. MCRAD

Events table.

MCRAD Events table

String (50)

Hours Personnel/Hours spent on site. MCRAD Events table.

MCRAD Events table Double

Permit_Agency Agency that gave ARPA Permit. MCRAD Events table.

MCRAD Events table

(50)

13 | P a g e

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

Permit_No Number of permit. MCRAD

Events table.

MCRAD Events table

String (50)

App_Date

Date of permit application.

Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915). MCRAD Events table.

MCRAD Events table Integer (Long)

Appr_Date

Date of permit approval.

Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915). MCRAD Events table.

MCRAD Events table Integer (Long)

Exp_Date

Date of permit expires.

Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915). MCRAD Events table.

MCRAD Events table Integer (Long)

Permit_Stat

The status of the permit:

Approved, Pending, Terminated. MCRAD

Events table.

MCRAD Events table / Approved, Pending, Terminated

String (50)

Tribes Tribes notified per 32 CFR

229.7 or ARPA. MCRAD Events table.

MCRAD Events table String (250)

Value_Rec Value received in awards, property/artifacts siezed.

MCRAD Events table.

MCRAD Events table Double

Value_Note

Source of value received (Grant, Confiscation of stolen material, etc.).

MCRAD Events table.

MCRAD Events table / Grant, Confiscation of stolen material, etc.

String (50)

Survey_Cost Cost of event. MCRAD

Events table.

MCRAD Events table Double

Cost_Note

Source of cost (Contractor for consultant, Damage lost, Cost for law enforcement). MCRAD

Events table.

MCRAD Events table / Contractor for consultant, Damage lost, Cost for law enforcement

14 | P a g e

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

Begin_Date_Survey

Beginning date of event.

Format for date is YYYYMMDD (i.e., September 15, 1994 = 19940915). MCRAD Events table.

MCRAD Events table Integer (Long)

End_Date_Survey

End date of event. Format for date is YYYYMMDD

(i.e., September 15, 1994 = 19940915). MCRAD Events table.

MCRAD Events table Integer (Long)

Business Table Attributes for cr_CulturalSurveyMethods_A and cr_CulturalSurveyMethods_P

Domain (D)

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

EventIDFK Used to link this business table to the appropriate feature class.

MCRAD Surv_Meth_Areas table

String (50)

Meth_Area_ID Primary Key in

Surv_Meth_Areas table in

MCRAD.

MCRAD Surv_Meth_Areas table

String (50)

D Method Survey method used in survey subarea. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

For a list of domain values, see SurveyMethod in

Appendix 1.

String (20)

Begin_Date_Methods

Beginning date of survey in subarea. Format for date is

YYYYMMDD (i.e., September 15, 1994 =

19940915). MCRAD

Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

Integer (Long)

End_Date_Methods

End date of survey in subarea. Format for date is

YYYYMMDD (i.e., September 15, 1994 =

19940915). MCRAD

Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

Integer (Long)

15 | P a g e

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

Survey_Int

Survey intensity: Records search, Prelim field, Intens field, % Surveyed. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Survey_Config Survey configuration:

Block, Transect. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table / Block, Transect

String (50)

Bias

Particular survey bias: i.e.

Only looking for particular resource types. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Pedestrian Type of pedestrian survey.

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Ped_Coll

Surface collection methods (All, Diagnostic only, etc).

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Shovel_Tests Shovel tests used. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

Double

Excav_Units Excavation units. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

Double

Pedest_Int Pedestrian interval.

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Trans_Num Number of transects.

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

STP_Interval STP Interval. MCRAD

Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table String (50)

Unit_Size Size of excavation units.

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Unit_Interval Excavation unit interval.

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Unit_Number Number of excavation units. MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Field_Cond Description of field conditions. MCRAD

Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

16 | P a g e

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

Perc_Grnd_Visib % Ground Visibility.

MCRAD Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table

String (50)

Method_Notes Notes. MCRAD

Surv_Meth_Areas table.

MCRAD Surv_Meth_Areas table String (255)

Business Table Attributes for cr_CulturalSurveyTests_A and cr_CulturalSurveyTests_P

Domain (D)

Attribute Name Definition Data Source / Allowed

Values

Data Type

(Length)

EventIDFK Used to link this business table to the appropriate feature class.

MCRAD Survey_Tests table

String (50)

Test_ID Primary Key in

Survey_Tests table in

MCRAD.

MCRAD Survey_Tests table String (50)

Test_Name Test field ID. MCRAD Survey_Tests table.

MCRAD Survey_Tests table String (50)

Excavator Excavator's name. MCRAD

Survey_Tests table.

MCRAD Survey_Tests table

String (30)

StratSum Stratigraphy summary.

MCRAD Survey_Tests table.

MCRAD Survey_Tests table

String (60)

ArtSum Artifact summary. MCRAD

Survey_Tests table.

MCRAD Survey_Tests table

String (240)

Ext_Typ_D Test type (STP, Unit, etc).

MCRAD Survey_Tests table.

MCRAD Survey_Tests table String (16)

Depth Depth of excavatoin.

MCRAD Survey_Tests table.

MCRAD Survey_Tests table Double

Depth_U_D Depth units. MCRAD Survey_Tests table.

MCRAD Survey_Tests table String (16)

Test_Notes Notes. MCRAD

Survey_Tests table.

MCRAD Survey_Tests table

17 | P a g e

“No Data” Value in Attributes Directions for populating required attributes for which no data/information is available. Use the appropriate values below:

For Empty Text Values TBD (To Be Determined) – A value is required but the value has yet to be determined.

8/8/8888 The value cannot be reasonably determined.

7/7/7777 (Not Applicable) No value exists.

Extent The data layer’s extent will be to the installation boundary, unless otherwise noted by the program area manager.

Metadata Complete Federal Geographic Data Committee (FGDC) compliant metadata for the data layer using the Procedures for Creating Metadata document. Update the metadata Lineage section as edits are

Theme Keywords: Cultural Resources, Cultural Survey Area

18 | P a g e

Appendix 1: SDSFIE 3.1.1 AF AFCEC/CZ Adaptation

Attribute Domain Tables DOMAIN TABLE NAME: SurveyMethod

ATTRIBUTE NAME: Method

CODED DOMAIN DEFINITION

aerial100 Aerial Survey - 100% aerialJudg Aerial Survey - Judgmental aerialSample Aerial Survey - Sample aerialUnk Aerial Survey - Methodology Unknown amateurReport Amateur Report auger100 Auger Test Survey - 100% augerJudg Auger Test Survey - Judgmental augerSample Auger Test Survey - Sample augerUnk Auger Test Survey - Methodology Unknown automobile Automobile Survey bankline100 Bankline Survey - 100% banklineJudg Bankline Survey - Judgmental banklineSample Bankline Survey - Sample banklineUnk Bankline Survey - Methodology Unknown collected Collected/Collections eqpExcavation Heavy Equipment Excavation excavated Excavated informAmateur Informed Amateur lit100 Literature Survey - 100% litJudg Literature Survey - Judgmental litSample Literature Survey - Sample litUnk Literature Survey - Methodology Unknown

NA Not Applicable: No value exists.

other Other. Must be described in the sdsFeatureDescription attribute.

remote100 Remote Sensing Survey - 100% remoteJudg Remote Sensing Survey - Judgmental remoteSample Remote Sensing Survey - Sample remoteUnk Remote Sensing Survey - Methodology Unknown serendipity Serendipity shovel100 Shovel Test Survey - 100% shovelJudg Shovel Test Survey - Judgmental shovelSample Shovel Test Survey - Sample shovelUnk Shovel Test Survey - Methodology Unknown surface100 Surface Survey - 100% surfaceJudg Surface Survey - Judgmental surfaceSample Surface Survey - Sample surfaceUnk Surface Survey - Methodology Unknown

TBD To Be Determined: A value is required but the value has yet to be determined.

tested Tested underwtr100 Underwater Survey - 100% underwtrJudg Underwater Survey - Judgmental underwtrSample Underwater Survey - Sample underwtrUnk Underwater Survey - Methodology Unknown undisturbed Undisturbed (Surveyed, No Collections) unknown The survey methodology is unknown.

19 | P a g e

Historic Building

Data Layer Specification – Historic Building

12/12/2016 HistoricBuilding _20161212

Removed “the vertical datum shall be Mean Sea Level (MSL_Height),” from the Coordinate System section.

10/4/2016 HistoricBuilding _20161004

Updated feature class codes used for creating Resource ID when MCRAD data is not present.

6/23/2016 HistoricBuilding _20160623

Updated HistoricBuilding_P representation under “Data Layer Details” section.

Updated “Positional Accuracy” section.

3/10/2017 HistoricBuilding _20170310

Updated all Air Force Standard attribute fields to match August 6, 2015 GeoBase Data Dictionary.

Updated “Positional Accuracy” section.

Updated “For Empty Text Values” subsection.

Updated the “Representation” subsection of the “Data Layer Details” section.

Updated the “Point Features” subsection of the “Geometry/Topology” section.

6/8/2017 HistoricBuilding _20170608

Updated the data layer update frequency in the “Sources and Source Selection” section.

Updated “Data Steward POC”

03/01/2018 HistoricBuilding _20180301

Updated the “Definition”, “Geometry/Topology”, “Positional Accuracy”, “Attributes”, “Business Tables,” and “Appendix 1:

SDSFIE 3.1.1 AF AFCEC/CZ Adaptation Attribute Domain Tables” sections.

This Data Layer Specification (DLS) defines geospatial data specifications for the HistoricBuilding_A and HistoricBuilding_P data layers implemented under the United States Air Force Civil Engineer

Center (AFCEC) Environmental GIS Program.

Definition A building or structure that has cultural significance due to its historic background, association with a famous person, or its architectural features.

Data Layer Details

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Class Name:

HistoricBuilding_A HistoricBuilding_P

SDSFIE 3.1.1 AF AFCEC/CZ

Adaptation Feature Dataset:

environmentalCulturalResources

Previous Layer Names:

historic_structure_area historic_structure_point HistoricObject HistoricObject_P

Geometry Type: Polygon, Point

Data Steward Organization (Program Area):

Program Area: Cultural Resources

Data Steward POC: AFCEC/CZTQ Air Force Cultural Resources Program SME

Representation:

Historic building areas are represented as closed polygons depicting the outermost footprint of the building.

Each individual historic building is represented by a single area feature.

All points developed from areas shall represent the centroid of the historic building area.

Implementing Authorities and Regulations

Implementing Program(s):

Driver(s):

HQ AF/A7CAN

36 CFR 60.4, Criteria for evaluation, 1 July 2012

36 CFR 63.2, Determination of eligibility process, 1 July 2012

36 CFR 800, Protection of Historic Properties, 1 July 2012

Historic Sites Act of 1935

National Historic Preservation Act of 1966

Driver(s):

AFI32-10112, Installation Geospatial Information and Services (IGI&S), 19 October 2007

AFI32-7062, Comprehensive Planning, 27 June 2013

AFI32-7064, Integrated Natural Resources Management, 18 November 2014

AFI32-7065, Cultural Resources Management Program, 19 November

AFH32-9007, Managing Air Force Real Property, 1 May 1999

AFI32-1084, Facility Requirements; Chapter 11-16, 1 September 1996

Garrison Mapping Concept of Operations (CONOPS) Version 2.0, 12 June 2003

USAF Installation Geospatial Information and Services (IGI&S) Data Model, 15 December 2009

Real Property Inventory Management (RPIM), v2.0

RPIM 3.0, extracted 4/2009

Geometry/Topology Polygon Features:

Polygons must not overlap.

Polygons must be single part features.

Polygons must be larger than cluster tolerance (.001 meter).

Point Features:

Points must be disjoint.

If a point represents a polygon feature, then the point must fall properly inside of the coinciding polygon.

Sources and Source Selection Information for this geospatial data layer must be obtained and/or validated at the installation level. The Data Steward will have overall responsibility for completing and updating the spatial, attribute and metadata features of this geospatial data layer in accordance with this DLS. The data layer will be updated on an annual (yearly) basis at a minimum. More frequent updates may be performed if new data has been developed prior to the annual update. Additionally a bi-annual

(every 6 months) Quality Control (QC) check will be performed on all data housed in GeoBase.

Updates and QC will be performed on any new data prior to uploading it to GeoBase.

Military Cultural Resources Analysis Database (MCRAD) is a relational data model that uses the functionality of Microsoft Access. It was created by Dr. Paul Green in collaboration with Dr. Brian

Crane to resolve the issues that arise due to idiosyncratic formats of cultural resource data. MCRAD has been refined to support cultural resource business practices with DoD-wide input and has been adopted by the Deputy Under Secretary of Defense for Installations and Environment as a cultural tables.

Possible sources for the data layer are: planimetric data extracted from stereo or ortho-imagery, differential GPS survey, conventional surveys using a survey grade GPS, computer aided design

(CAD), imagery, hardcopy documents, attribute or tabular data.

Positional Accuracy Horizontal Accuracy: Data developed within this layer should be within 3 meters of the actual location at the 95% confidence level. Accuracy reported at the 95% confidence level means that

95% of the positions in the dataset would have an error with respect to true ground position that is equal to or smaller than the stated…