Tags
Identifier for the map unit.
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Confidence that observed structure is of the type specified.
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Map unit label.
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Equivalent to DescriptionOfMapUnits symbol that references an area-fill symbol. Area-fill symbols (map-unit color, pattern, or color+pattern) must be included in accompanying .style file.
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Label (period delimited) assigned by area geologists that combines all the original map units into 7 different general geologic categories.
Oregon Department of Geology and Mineral Industries
General geologic rock type of the geologic merge unit label, expressed by the genesis of the unit.
Oregon Department of Geology and Mineral Industries
Age of geologic merge unit based on the Geologic Time Scale.
Oregon Department of Geology and Mineral Industries
Stratigraphic name (formally or informally named) for the terrane or group.
Oregon Department of Geology and Mineral Industries
Stratigraphic name (formally or informally named) for the geologic formation.
Oregon Department of Geology and Mineral Industries
Volcanic field that the unit is assigned to. In igneous provinces, a well-defined area covered with volcanic rocks with a common geologic history.
Oregon Department of Geology and Mineral Industries
Stratigraphic name (formally or informally named) for the member type.
Oregon Department of Geology and Mineral Industries
Stratigraphic name (formally or informally named) for the unit type.
Oregon Department of Geology and Mineral Industries
Characteristic lithology type name for the geologic merge unit label.
Oregon Department of Geology and Mineral Industries
Concatenation of 'DataSourceID' and 'MapUnit' fields without a space in between - for use with joins or relates of data tables in ArcGIS or other GIS software.
Oregon Department of Geology and Mineral Industries
Foreign key to DataSources table, to track provenance of each data element.
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Additional information specific to a particular feature or table entry.
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Primary key. Values MUP1, MUP2, MUP3, etc. Values must be unique to the database
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
Point Type
U.S. Geological Survey National Cooperative Geologic Mapping Program, 2020, GeMS (Geologic Map Schema)
This point feature class holds the attributes associated with the map unit polygons.
This feature class represents map unit points that house the attributes used in conjunction with the ContactsAndFaults feature class to generate the MapUnitPolys and MapUnitPolysBedrock feature classes. These vector points have no real-world physical existence and do not participate in map-unit topology. This point feature class holds the attributes associated with the map unit polygons.
The purpose of this GeMS file geodatabase is the storage and management of the geospatial data of the geologic information in the Athena 1:24,000-scale quadrangle, Umatilla County. This file geodatabase was compiled to construct a geologic map of the Athena 1:24,000-scale quadrangle, Umatilla County, Oregon, and it is this map that is a deliverable for U.S. Geological Survey STATEMAP program. This is a GeMS file geodatabase with cartographic representation and the central storage location for features and associated tables. The features and tables contain 1:24,000-scale geologic map data of Athena 7.5′ quadrangle, Umatilla County, Oregon. At the core of this product is the U.S. Geological Survey Geologic Map Schema (GeMS) file geodatabase incorporating FGDC standard schema for digital geologic map data. The storage location for features is GeologicMap dataset and with additional attributes in associated tables.
None
MAP DATA: This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information. This publication cannot substitute for site-specific investigations by qualified practitioners. Site-specific data may give results that differ from the results shown in the publication.
When contacting DOGAMI about this data set, please reference the data set title or other identifying information in your correspondence. DOGAMI publications can be downloaded from http://www.oregongeology.org
Geologic mapping was supported in part between 2021 and 2022 by grants from the STATEMAP [http://ncgmp.usgs.gov/about/statemap.html]component of the U.S. Geological Survey (USGS) National Cooperative Geologic Mapping Program under cooperative agreement G21AC00647. Additional funds were provided by the State of Oregon through the Oregon Department of Geology and Mineral Industries.
Care was taken to limit categorical attribute errors. Attribute accuracy of the database was visually inspected but despite the checks there may be some attributes that are still mislabeled.
Topology has been validated for the feature classes. Topology errors: 0. Topology exceptions: 4; MapUnitPolys must not have gaps 1 exception for project boundary of polygons; ContactsAndFaults must not have dangles 3 exceptions for faults. Duplicate point locations were found. No attempt has been made to correct the errors as they are related to multiple samples at one location, retesting of samples, and/or variance in Z values. Tests for logical consistency were performed by ArcGIS Topology software and GeMS Tools for Arc10.5 2018-03-04; Topology Check script and Validate Database script. All points, lines, and polygons were visually checked, and are labelled correctly.
Data collection does not include all possible traverses, measured sections, etc., and thereby is not complete. Not all field data were collected nor were all of the data compiled from lineage maps. Geologic concepts and definitions of map units are current. Density of observations is sufficient to support the map(s).
Data was collected and interpreted at a variety of scales. For field work, a combination of hillshade images from, DOGAMI's lidar 3 ft pixel bare earth DEM (approximately 1 point every 0.3 meters), NAIP imagery derived structure for motion (SFM) 5 m pixel bare earth DEM (approximately 1 point every 5 meters), and/or 10m pixel bare earth DEM (approximately 1 point every 10 meters) served as basemap(s). Precision mapping using, GPS, GIS, and the lidar imagery employed an application for the iPad, called iGIS. On the computer, line work was nominally drawn at a scale of 1:8,000. Also, geologic data was compiled from paper maps. Positional errors should be expected from input of digitized points and lines from paper maps and the errors that arise from georeferencing the paper maps (accuracy of content). Not all resources were tested to evaluate the degree to which these inaccuracies exist. Positional accuracy of geologic contacts, structures, and measurement points is influenced by the subjective judgment of the mappers or by interpretation of remotely sensed data (e.g., lidar). Therefore, the data user must consider the aforementioned methods of data collection and compilation in context of positional accuracy and understand that most lines and polygon boundaries are inferred based on geologic interpretations.
A combination of lidar 3 ft pixel bare earth DEM (approximately 1 point every 0.3 meters), structure for motion (SFM) derived 5 m pixel bare earth DEM (approximately 1 point every 5 meters), and/or a 10m pixel bare earth DEM (approximately 1 point every 10 meters) served as elevation model(s). Not all resources were tested to evaluate the degree to which these inaccuracies exist. Lidar-derived bare earth elevation model vertical accuracy is typically less than 1 foot.
Topology checks were performed on the GeologicMap feature dataset by, employing the Topology check script provided in the GeMS Tools for Arc10.5 version 1.6.14, and checking additional topology rules using Esri ArcGIS 10.7 for desktop. The Topology Check script in the GeMS toolkit provides additional checks for automation errors and geologic blunders. This script builds and evaluates an ArcGIS topology with these rules: no overlaps in ContactsAndFaults, no self-overlaps in ContactsAndFaults, no self intersections in ContactsAndFaults, no gaps in MapUnitPolys, no overlaps in MapUnitPolys, and all MapUnitPoly boundaries are covered by ContactsAndFaults arcs. Topology Check also evaluates node topology, summarizes the map units that bound ContactsAndFaults arcs, checks for duplicate point features, and identifies very small polygons in MapUnitPolys and very short arcs in ContactsAndFaults. Results of Topology Check should be taken with a grain of salt, as some issues flagged by this script may not be errors. In addition to the GeMS Topology Check the following are added topology rules checked for the dataset. Rule 1: ContactsAndFaults must not have dangles. Rule 2: Cartographic Lines must not self-overlap. Rule 3: Cartographic Lines must not self-intersect. Rule 4: Cartographic Lines must be single part. Lineage maps were used as base maps in the following manner: 1) to compare the mapping against previous work; 2) scribing geologic features, e.g., bedding, faults, and folds; and 3) reference materials.
When contacting DOGAMI about this data set, please reference the data set title or other identifying information in your correspondence. DOGAMI publications can be downloaded from http://www.oregongeology.org
This point feature class holds the attributes associated with the map unit polygons.
When contacting DOGAMI about this data set, please reference the data set title or other identifying information in your correspondence. DOGAMI publications can be downloaded from http://www.oregongeology.org
Although these data have been processed successfully on a computer system at the Oregon Department of Geology and Mineral Industries, no warranty expressed or implied is made by DOGAMI regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty.
When contacting DOGAMI about this data set, please reference the data set title or other identifying information in your correspondence. DOGAMI publications can be downloaded from http://www.oregongeology.org