Schoolhouse Point Mound Data: Strata
Part of the Roosevelt Platform Mound Study: Pinto Creek Complex, Schoolhouse Point Mound (DRAFT) project
Creator(s): Archaeological Research Institute, Arizona State University
Year: 1996
Summary
The strata represent major natural or cultural depositional events such as erosional fill, roof fall, floor contexts, and sterile substrate. Strata are depicted as horizontal rows of interconnected boxes on a Harris Matrix. Within a feature, each stratum is designated by the feature number (e.g., 10, 11, 12, etc.) and a letter that designates a particular stratum (e.g., A, B, C). The letters are assigned in descending order. Mixed levels and artifacts collected out of context are designated by a "?". Artifacts from each feature (or mixed context) are tallied according to strata. Please see column metadata for further detail.
Cite this Record
Schoolhouse Point Mound Data: Strata. Archaeological Research Institute, Arizona State University. Tempe, Arizona: Office of Cultural Resource Management, Arizona State University. 1996 ( tDAR id: 394231) ; doi:10.6067/XCV88C9Z84
This Resource is Part of the Following Collections
Data Set Structure
Table Information: SHMound_Strata_U.8.24-13a1
Column Name | Data Type | Type | Category | Coding Sheet | Ontology | Search |
---|---|---|---|---|---|---|
Screened Volume (cu. M) | Measurement of the volume (in cubic meters) of fill that was screened from a designated stratum. The measure is 0.00 if no fill was screened from a stratum (i.e., The context or feature fill was not screened.). | |||||
VARCHAR | Uncoded Value | Provenience and Context : Volume | none | none | true | |
Total Volume (cu. M) | Measurement of the volume (in cubic meters) of total fill in a designated stratum. | |||||
VARCHAR | Uncoded Value | Provenience and Context : Volume | none | none | true | |
Associated Subfeatures | Identifies the subfeatures associated with each feature -- often each feature stratum. A subfeature is designated by the associated feature number and an assigned subfeature decimal number (e.g., 10.01, 10.02, 10.03). Subfeature numbers begin with .01 for each associated feature and increase sequentially. Also identifies the subfeature type. Each subfeature is labeled with the assigned subfeature type, to the right of the subfeature number. Examples: 10.04 Timber = a timber subfeature associated with Feature 10 10.05 In-Place Vessel = an in-situ vessel associated with Feature 10 10.06 Roof Fall = well-defined roof fall in association with Feature 10 Note that subfeatures are frequently associated with a particular stratum within a feature. For example, subfeatures 10.04, 10.05, and 10.06 may be associated with Stratum 10C. Other subfeatures may be associated with Stratum 10D, etc. | |||||
VARCHAR | Uncoded Value | Provenience and Context : Feature Type | none | none | true | |
Associated Subfeatures | Identifies the subfeatures associated with each feature -- often each feature stratum. A subfeature is designated by the associated feature number and an assigned subfeature decimal number (e.g., 10.01, 10.02, 10.03). Subfeature numbers begin with .01 for each associated feature and increase sequentially. Also identifies the subfeature type. Each subfeature is labeled with the assigned subfeature type, to the right of the subfeature number. Examples: 10.04 Timber = a timber subfeature associated with Feature 10 10.05 In-Place Vessel = an in-situ vessel associated with Feature 10 10.06 Roof Fall = well-defined roof fall in association with Feature 10 Note that subfeatures are frequently associated with a particular stratum within a feature. For example, subfeatures 10.04, 10.05, and 10.06 may be associated with Stratum 10C. Other subfeatures may be associated with Stratum 10D, etc. | |||||
VARCHAR | Uncoded Value | Provenience and Context : Feature Type | none | none | true | |
Type | Identifies the feature type for each feature. In addition, identifies the stratum type for each stratum in and/or associated with a feature. Examples: Feature 10 = Cobble Masonry Room (feature type) Stratum 10? = unassigned contexts in Cobble Masonry Room, Feature 10 Stratum 10B = roof fall in Cobble Masonry Room, Feature 10 | |||||
VARCHAR | Uncoded Value | Provenience and Context : Feature Type | none | none | true | |
Feature | Identifies the assigned feature number for each identified feature.Feature numbers begin with 1 at each site and increase sequentially (e.g., 10, 11, 12). | |||||
VARCHAR | Uncoded Value | Provenience and Context : Feature ID/Number | none | none | true | |
Stratum | Identifies a major natural or cultural depositional event such as erosional fill, roof fall, floor contexts, and sterile substrate (i.e., a single archaeological context in both horizontal and vertical space). Strata are depicted as horizontal rows of interconnected boxes on a Harris Matrix. A stratum is a combination of an individual feature and a context in or associated with that feature. For example, Feature 10 might be a structure with an erosonial fill stratum, a roof fall stratum, a floor stratum, and a sterile substrate stratum. Within each feature, each stratum is designated by the feature number (e.g., 10, 11, 12, etc.) and a letter that designates a particular stratum (e.g., A, B, C). The levels excavated in a feature were aggregated into individual feature strata (e.g., Levels 1 - 3 = Stratum A). A feature's stratum letters are assigned in descending order. A context letter of "?" designates a mixed level or context or artifacts collected out of context. Examples: 0? = General Cultural Fill/No Feature and Indeterminate context 10A = Feature 10 and Context A 10B = Feature 10 and Context B 10C = Feature 10 and Context C 22? = Feature 22 and Mixed and/or Undefined context 22A - Feature 22 and Context A Each stratum (e.g., 10C) is assigned to a stratum type. Examples: 10A = Feature 10 and Context A = Feature 10, erosional fill 10B = Feature 10 and Context B = Feature 10, roof fall 10C = Feature 10 and Context C = Feature 10, floor Some strata are associated with one or more subfeatures. Please see the Associated Subfeatures columns. | |||||
VARCHAR | Uncoded Value | Provenience and Context : Stratum | none | none | true |
Keywords
Site Name
AR-03-12-06-13a(USFS)
•
AZ U:8:101(ASU)
•
AZ U:8:24(ASM)
•
Schoolhouse Point Mound
Site Type
Artifact Scatter
•
Funerary and Burial Structures or Features
•
Hamlet / Village
•
Hearth
•
Midden
•
Mound / Earthwork
•
Platform Mound
•
Post Hole / Post Mold
•
Refuse Pit
•
Roasting Pit / Oven / Horno
•
Rock Alignment
•
Rock Art
•
Room Block / Compound / Pueblo
•
Storage Pit
Investigation Types
Architectural Documentation
•
Data Recovery / Excavation
•
Heritage Management
•
Methodology, Theory, or Synthesis
Geographic Keywords
Pinto Creek
•
Salt River
•
Theodore Roosevelt Lake
•
Tonto Basin
•
Tonto National Forest
Temporal Keywords
Classic Period
Temporal Coverage
Calendar Date: 690 to 1630
Spatial Coverage
min long: -111.026; min lat: 33.628 ; max long: -110.984; max lat: 33.672 ;
Individual & Institutional Roles
Contact(s): USDI Bureau of Reclamation, Phoenix Area Office
Contributor(s): Peter H. McCartney; Arleyn W. Simon; Ronna J. Bradley; Judi L. Cameron; J. Phil Dering; Suzanne K. Fish; Joel D. Irish; Chris Loendorf; Marcia H. Regan; Christy G. Turner II; Lisa Ipock
Principal Investigator(s): Glen E. Rice; Charles Redman
Sponsor(s): USDI Bureau of Reclamation, Phoenix Area Office
Repository(s): Center for Archaeology and Society, Arizona State University
Prepared By(s): Office of Cultural Resource Management, Arizona State University
Submitted To(s): USDI Bureau of Reclamation, Phoenix Area Office
Record Identifiers
Roosevelt Monograph Series(s): 6
Anthropological Field Studies(s): 35
Roosevelt Platform Mound Study, Complex(s): Pinto Creek
Bureau of Reclamation Contract No.(s): 9-CS-32-06230
Roosevelt Platform Mound Study, Management Group(s): Schoolhouse
File Information
Name | Size | Creation Date | Date Uploaded | Access | |
---|---|---|---|---|---|
SHMound_strata_U.8.24-13a.xls | 157.00kb | Dec 9, 2014 1:59:52 PM | Public | ||
Translated version
SHMound_strata_U.8.24-13a_translated.xls
(177.50kb)
Data column(s) in this dataset have been associated with coding sheet(s) and translated:
|