Attachment_4_GIS.pdf

NRHP Archaeological Determination of Eligibility of 45KL328 within the USACE Portland District, John Day Project Boundaries

Attachment 4 – GIS Data

BPA GIS Specification for FCRPS Cultural Resources Program Data – Version 4 Updated 7/22/15

1. GPS/GIS STANDARDS FOR ARCHAEOLOGICAL FIELD INVENTORY

The Agencies seek assistance to use GPS (global positioning system) to collect cultural resource Site, Survey, Documentation Methods, and Cultural Material locations within the Location of Work, as defined in the main body of the Statement of Work. The contractor will collect, edit, and differentially correct GPS files and then transmit projected ESRI geodatabase feature classes with tabular information and FGDC metadata as a deliverable. See GIS data dictionary for a list of required fields, field definitions, and values. This data dictionary is not intended to represent all of the possible information collected in the field. It is the information the agencies need for internal purposes.

1a GPS data collection The contractor will load a Data Dictionary or XML to the GPS unit. The Data Dictionary or XML file must match the BPA FCRPS Cultural Resource Program specifications1 for Feature Class Names, Field Names, Data Types/Lengths, and Field Definition and Values (Domains). If the contractor is unable to use the BPA’s XML data dictionary or geodatabase template, the contractor will create the data dictionary using the information provided in Attachment 1: GIS Data Dictionary.

1b GIS Data Formatting GIS Deliverable requirements:

Geodatabase Format: Tabular fields will be populated with information as specified in the Attachment 1: GIS Data Dictionary. All feature class names, field names, and value choices must match the naming conventions in Attachment 1: GIS Data Dictionary. The deliverable will include one geodatabase containing all deliverable feature classes. The deliverable will include one feature class for each type of feature. For example, all survey polygons will be in the Survey_Poly feature class. GIS features of the same type stored as individual features or individual shapefiles will not be accepted.

Spatial Reference: All GIS data will be correctly projected. Questions about appropriate projection should be directed to the Corps TPOC.

GIS Metadata Format:

There are twelve feature classes in Attachment 1: GIS Data Dictionary. Each feature class in the GIS deliverable will have metadata. The required metadata format is ESRI ArcCatalog Metadata using the FGDC standard: North American Profile (NAP) of ISO 19115 2003. The ESRI ArcCatalog Metadata will have these fields populated;

Tags, Summary, Description, Credits, Citation Contact(s), Resource Citation Date(s).

1 Note that BPA maintains two separate Data Dictionaries: one for the jointly managed FCRPS Cultural Resource Program, and one for cultural resource compliance in support of transmission and fish and wildlife projects.

Deliverable: Final ESRI geodatabase on two (2) compact disks shall be submitted with the final report.

1c Review GIS deliverables will be reviewed to ensure that they meet the requirements described in Task 1a and 1b. The contractor must remedy missing or incorrect requirements by the date or timeline specified in the contract.

Any questions concerning GPS or GIS should be directed to Melanie Wadsworth 503-230-5143 or mlwadsworth@bpa.gov

GIS Data Dictionary Field definitions for cultural resource geodatabase. Highlighted fields should be filled out while field work is being conducted.

Site Feature Classes; Site_Poly, Site_Pt, Site_Ln

(Used to define site boundary during initial documentation and subsequent updates associated with condition assessment monitoring and /or resurvey. “Cultural Materials” feature class to document features and artifacts.)

Field Name Alias Data

Type Field Size

Field Definition and Values

Smith_Numb Smith Number Text 30 Smithsonian Trinomial if applicable (8 digit string)

Temp_Site_No Temporary Site Number Text 40 Temporary site number used by contractor

Site_Name Site Name Text 50 Known site name

Visit_Hist Visitation History Text 10 Distinguish between newly recorded sites and revisitation associated with site condition monitoring – Values: New, Monitoring

Field_Date Field Date Date - dd/mm/yyyy

Contractor Contractor Text 50 Name of contracting company, agency, or tribe

Site_Type Site Type Text 50 General type of site- Values:

burial/grave/cemetery, camp, feature, quarry, rockshelter/cave, scatter, village/community, historic, homestead, structure, multicomponent, unknown, other

Cult_Period Cultural Period Text 100 Cultural period in which site was utilized- Values: unknown, Paleo (10,500 BP or earlier), Archaic (Specific period not established), Early Archaic (10,500 BP- 7,000 BP), Middle Archaic (7,000 BP-2,000 BP), Late Archaic (2,000 BP-Contact), Contact period, Historic, 19th Century, Early 20th Century (1900-1930), Depression/WWII (1929-1950), Recent (post1950), Multicomponent (Historic & Prehistoric), Multicomponent (Prehistoric Only), Multicomponent (Historic Only), Prehistoric (undetermined pre-contact)

Nreg_Status National Register Status Text 35

Status of National Register of Historic Places- Values: Eligible, Evaluation Testing Recommended, Not Eligible, Listed, Nominated, Recommend Eligible, Recommend Not Eligible, Unevaluated, Unknown

Site_Condition Site Condition Text 30 Site condition observed during this visit- Values: Unknown [no data or condition unknown], Excellent [<5% damage], Good [between 5% and 40% damage], Fair

[between 40% and 60% damage], Poor [between 60% and 95% damage], Destroyed [>95% damage]

Site_Impact Site Impact Text 40 Impact to site- Values: bioturbation, erosion (wind, sheet wash), grazing, recreation, reservoir erosion, undisturbed, vandalized

Min_Elevation Minimum Elevation Text 15 Elevation of site in meters at lowest point

Max_Elevation Maximum Elevation Text 15 Elevation of site in meters at highest point

Data_Der Data Derived Text 25 How was data derived? Values: GPS, digitized, report narrative, personal communication

Lnd_Man Land Manager Text 30 Responsible land management party- Values:

United States Army Corps of Engineers, Bureau of Reclamation, National Park Service, Forest Service, Tribal, Private, and Unknown

Comment Comment Text 255 Open field for additional information

Survey Feature Classes; Survey_Poly, Survey_Pt, Survey_Ln

(Used to document new survey and resurvey.)

Field Name Alias Data Type

Field Size

Field Definition and Values

Field_Date Field Date Date - dd/mm/yyyy

Survey_Tp Survey Type Text 20 Type of survey conducted – Values: New [area not previously surveyed using systematic transect intervals], Re-survey [area previously surveyed using any methods], Reconnaissance [area surveyed, but not using systematic transect intervals]

Contractor Contractor Text 50 Name of contracting company

Title Report Title Text 255 Full title of report

Dt_Report Date of Report Text 4 Date report was completed; Stored as year

Data_Der Data Derived Text 30 How was GIS data derived? Values: GPS, digitized, report narrative, personal communication

Interval Transect Interval Text 20 Interval of survey in meters (use “N/A” for reconnaissance survey)

Documentation Methods and Control Points Feature Classes; Doc_Poly, Doc_Pt, Doc_Ln

(Used to document methods employed to document and evaluate cultural resources, including excavation and condition monitoring.)

Field Name Alias Data

Type Field Size

Field Definition and Values

Cont_Pt_Tp Control Point Type Text 50 Type of control point(s) used for NR determination and/or condition monitoring- Values: Site Datum(s), Erosion Control Point, Photo Point, Shovel Test Probe, Excavation Unit/Trench, Surface Collection Unit (no excavation), Disturbed Area, Waterline, Cutbank, Other

Cont_Pt_Nm Control Point Name Text 30 Name of control point (examples: “Datum- 1”, “STP-3”, “Disturbance Area-2”). A corresponding description of each control point must be included in field notes (Example: “Disturbance Area-3 measures 8m N-S by 6m E-W and ranges from 3cm to 20cm deep. Artifact context has been altered by ATV use in area, which has churned sediments).

Cultural Materials Feature Classes; CulturalMaterial_Poly, CulturalMaterial_Pt, CulturalMaterial_Ln

(Used to record cultural materials within or outside a site boundary during initial documentation, or subsequent monitoring - artifacts collected, diagnostic artifacts, features, site datum, photo points, erosion station points, etc.)

Field Name Alias Data Type

Field Size

Field Definition and Values

Smith_Numb Smith Number Text 30 Smithsonian Trinomial if applicable (8 digit string)

Temp_Site_No Temporary Site Number Text 40 Temporary site number used by contractor

Field_Date Field Date Date - dd/mm/yyyy

Contractor Contractor Text 50 Name of contracting company

Obj_Type Object Type Text 25 What is being recorded? – Values: Artifact, Feature, Loci (artifact concentration), Isolate (use only if object is outside site boundary)

Obj_Type_Nm Object Type Name Text 100 Name of data being collected (example:

Feature-1, Projectile Point-3, Ground Stone- 13, Locus-2, etc.) Object Type Name and description must be included in the field notes/monitoring form (Example: Ground Stone-13 is a basalt hammerstone 13cm x 6cm x 8cm with use wear on one end)

Art_Collect Artifact Collected Text 5 If Object is an artifact, was it collected?

Values: Yes, No

Art_TCM Artifact Temporary Catalog Number

Text 20 If Object is a collected artifact, what is the temporary field catalog number?