This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2023 BAS as well.

The 2020 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. In MCD states where no MCD exists or no MCD is defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The generalized boundaries of legal MCDs are based on those as of January 1, 2020 as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This data layer is an element of the Oregon GIS Framework. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.

Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

COB_ARC: This theme shows line representation of the jurisdictional and cartographic county perimeters for Oregon and Washington.

This digital geospatial database contains four data elements as defined in the Cadastral Data Exchange Standard (CDES): tax lot, tax code, map index, and a real property table. These data are created by County Assessors to support the assessment of properties and collection of local property taxes. The CDES provides a standard format for these data to facilitate data sharing and provide consistent definitions of attributes used across the state by all 36 counties in Oregon. County data are collected, reprojected, and aggregated into statewide datasets. The source geometry and attributes are retained and published as provided. Counties may provide data to the State for publishing on a weekly, monthly, quarterly, semi-annual, or annual basis. The Import Date attribute has been added to all four data elements to indicate the date the data was submitted by the County.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.

The Map Index contains polygons that represent the map area that is the boundary of a group of taxlots. This data layer is used to produce the county assessor parcel maps.

To access the tax lot layer you will need to contact the county Assessor's office. ORMAP is a statewide digital cadastral base map that is publicly accessible, continually maintained, supports the Oregon property tax system, supports a multi-purpose land information system, strives to comply with appropriate state and national standards, and will continue to be improved over time.

This digital geospatial database contains four data elements as defined in the Cadastral Data Exchange Standard (CDES): tax lot, tax code, map index, and a real property table. These data are created by County Assessors to support the assessment of properties and collection of local property taxes. The CDES provides a standard format for these data to facilitate data sharing and provide consistent definitions of attributes used across the state by all 36 counties in Oregon. County data are collected, reprojected, and aggregated into statewide datasets. The source geometry and attributes are retained and published as provided. Counties may provide data to the State for publishing on a weekly, monthly, quarterly, semi-annual, or annual basis. The Import Date attribute has been added to all four data elements to indicate the date the data was submitted by the County.

The National Risk Index Counties Map incorporates county-level vector tile layers for the Risk Index, Expected Annual Loss, Social Vulnerability, and Community Resilience. The map is used within the National Risk Index application.The National Risk Index is a dataset and online tool that helps to illustrate the communities most at risk for 18 natural hazards across the United States and territories: Avalanche, Coastal Flooding, Cold Wave, Drought, Earthquake, Hail, Heat Wave, Hurricane, Ice Storm, Landslide, Lightning, Riverine Flooding, Strong Wind, Tornado, Tsunami, Volcanic Activity, Wildfire, and Winter Weather. The National Risk Index provides Risk Index values, scores and ratings based on data for Expected Annual Loss due to natural hazards, Social Vulnerability, and Community Resilience. Separate values, scores and ratings are also provided for Expected Annual Loss, Social Vulnerability, and Community Resilience. For the Risk Index and Expected Annual Loss, values, scores and ratings can be viewed as a composite score for all hazards or individually for each of the 18 hazard types.Sources for Expected Annual Loss data include: Alaska Department of Natural Resources, Arizona State University’s (ASU) Center for Emergency Management and Homeland Security (CEMHS), California Department of Conservation, California Office of Emergency Services California Geological Survey, Colorado Avalanche Information Center, CoreLogic’s Flood Services, Federal Emergency Management Agency (FEMA) National Flood Insurance Program, Humanitarian Data Exchange (HDX), Iowa State University's Iowa Environmental Mesonet, Multi-Resolution Land Characteristics (MLRC) Consortium, National Aeronautics and Space Administration’s (NASA) Cooperative Open Online Landslide Repository (COOLR), National Earthquake Hazards Reduction Program (NEHRP), National Oceanic and Atmospheric Administration’s National Centers for Environmental Information (NCEI), National Oceanic and Atmospheric Administration's National Hurricane Center, National Oceanic and Atmospheric Administration's National Weather Service (NWS), National Oceanic and Atmospheric Administration's Office for Coastal Management, National Oceanic and Atmospheric Administration's National Geophysical Data Center, National Oceanic and Atmospheric Administration's Storm Prediction Center, Oregon Department of Geology and Mineral Industries, Pacific Islands Ocean Observing System, Puerto Rico Seismic Network, Smithsonian Institution's Global Volcanism Program, State of Hawaii’s Office of Planning’s Statewide GIS Program, U.S. Army Corps of Engineers’ Cold Regions Research and Engineering Laboratory (CRREL), U.S. Census Bureau, U.S. Department of Agriculture's (USDA) National Agricultural Statistics Service (NASS), U.S. Forest Service's Fire Modeling Institute's Missoula Fire Sciences Lab, U.S. Forest Service's National Avalanche Center (NAC), U.S. Geological Survey (USGS), U.S. Geological Survey's Landslide Hazards Program, United Nations Office for Disaster Risk Reduction (UNDRR), University of Alaska – Fairbanks' Alaska Earthquake Center, University of Nebraska-Lincoln's National Drought Mitigation Center (NDMC), University of Southern California's Tsunami Research Center, and Washington State Department of Natural Resources.Data for Social Vulnerability are provided by the Centers for Disease Control (CDC) Agency for Toxic Substances and Disease Registry (ATSDR) Social Vulnerability Index, and data for Community Resilience are provided by University of South Carolina's Hazards and Vulnerability Research Institute’s (HVRI) 2020 Baseline Resilience Indicators for Communities.The source of the boundaries for counties and Census tracts are based on the U.S. Census Bureau’s 2021 TIGER/Line shapefiles. Building value and population exposures for communities are based on FEMA’s Hazus 6.0. Agriculture values are based on the USDA 2017 Census of Agriculture.

U.S. Census Bureau QuickFacts statistics for Oregon County, Missouri. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.

BOC/Dev Serv.Version 20091030 (October 30, 2009). The Oregon Wetlands Cover is a compilation of polygon data from numerous sources, and represents the most comprehensive dataset available for the location and composition of the state's wetlands. It uses as a base all available digital data from the National Wetland Inventory (NWI; U.S. Fish and Wildlife Service, USFWS), to which has been added draft NWI mapping (Oregon Natural Heritage Information Center and The Wetlands Conservancy, ORNHIC and TWC), mapping from Local Wetland Inventories (LWIs; Department of State Lands, DSL), wetlands along state highways (Oregon Department of Transportation, ODOT), and mapping of individual sites by a variety of federal, state, academic, and nonprofit sources. Because the Oregon Wetlands Cover is based on the NWI framework, it represents all wetland categories in the Cowardin classification (Cowardin, L.M., V. Carter, F.C. Golet & E.T. LaRoe. 1979. Classification of wetlands and deepwater habitats of the United States. USDI Fish & Wildlfe Service, Biological Services Program. FWS/OBS-79/31. 103 pp. https://www.npwrc.usgs.gov/resource/wetlands/classwet/index.htm; https://el.erdc.usace.army.mil/emrrp/emris/emrishelp2/cowardin_report.htm) that are known to be present and mappable in Oregon. It includes perennially inundated "open water" aquatic habitats such as lacustrine limnetic, riverine (all subsystems), and marine and estuarine intertidal and subtidal. Man-made water features such as industrial detention ponds, log ponds, municipal sewage treatment lagoons, and flooded gravel pits are also included because they are often habitat for wetland biota. Portions of upland riparian areas may also be included where they are intermixed with riverine or palustrine wetlands and cannot be separated at the scale used in original mapping. Despite the inclusion of wetland spatial data from many different sources, a multitude of wetlands in Oregon have yet to be identified and mapped, and are not present in this coverage. This is especially true for seasonal, small, farmed, and forested wetlands that are difficult to detect with aerial photography.

Use the app to find the downloadable area within Jackson County - 2 Foot Contour MapThe 2-foot Contour Map shows contours that were derived from several different LiDAR projects in the Rogue Valley over the last 10 years. The map can be used to both download and view the contour data. To use the map, search or zoom in to an address. When zoomed in to a specific scale, the map will change from the downloadable areas layer to 2-foot interval contour lines. The LiDAR Project Dates layer can be used to identify the date when the elevation was collected in an area. Please note that data is available only for the valley floor areas at this time.The 2ft contours were created from 1-meter pixel DEM and then cleaned to remove very small elevation changes and to create a smooth contour line. This information should not be used to create topographic surveys or other applications where the precise elevation of a location is required. For additional information on LiDAR in Oregon or to download the source data, please visit the DOGAMI Lidar Viewer.The downloadable data is a zipped ESRI Shapefile and is projected to Oregon State Plane South (Intl Feet) with NAD 1983 datum.

Scoggins Dam in northwest Oregon lies within the Gales Creek fault zone (GCF), a northwest-striking system of active faults forming the boundary between the Coast Range and the Tualatin Valley about 25 km east of Portland, Oregon. Geologic mapping published in 2020 shows the dam to lie within a block-faulted releasing stepover between the right-lateral, NW-striking Scoggins Creek and Parsons Creek strands of the GCF. The Scoggins Creek strand is presently mapped beneath the existing dam about 200 m north of the south abutment. Preliminary results from paleoseismic trenching by the U.S. Bureau of Reclamation, Portland State University, and the U.S. Geological Survey indicate that these two major fault strands have had multiple surface rupturing earthquakes in the Holocene. To confirm the accuracy of the 2020 geologic map and the geometry of the GCF in the releasing stepover region, we completed additional geologic mapping of the dam, reservoir, and an alternative dam site downstream between July 2018 and May 2020. Using high-resolution lidar topographic data and satellite imagery on handheld digital tablets, we collected data at ~500 field sites in the heavily forested terrain. We used these detailed field observations to locate and digitally map the main Scoggins Creek and Parsons Creek fault strands, as well as the cross faults linking the two main strands, to produce an improved and more detailed geologic map and cross sections of Scoggins Valley and its existing and proposed dam sites.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk Information And supporting data used to develop the risk data. The primary risk; classificatons used are the 1-percent-annual-chance flood event, the 0.2-percent- annual-chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12,000.

U.S. Census Bureau QuickFacts statistics for Columbia County, Oregon. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.

Extreme temperatures can vary greatly across communities due to differences in land use, shade availability, proximity to water, and elevation. Spatially detailed estimates of temperature are difficult to find - often they are stations that are not regularly spaced or are from satellite observations, which estimate only the surface temperature, which can be quite different from air temperature. The PRISM Climate Group at the Oregon State University have developed an 800-meter resolution climatology of temperature for the United States that provides enough detail for intra-city temperature comparisons. It is created by a downscaling model, Parameter-elevation Regressions on Independent Slopes Model (PRISM).The 1991-2020 climate normal for maximum temperature for the month of July was downloaded and analyzed in ArcGIS Pro. Zonal Statistics provide min, max, and mean summaries for county and census tracts (2020 version) geometries. All temperatures were converted from degrees Celsius to Fahrenheit. Additionally, in each layer the mean of the maximum temperature analysis for the next order of geometry is provided (e.g., county data in the tracts layer), which allows comparison of the observed temperature to a larger geographic average. Data Source: https://www.prism.oregonstate.edu/normals/Citation: PRISM Climate Group, Oregon State University, https://prism.oregonstate.edu, data created 10 June 2022, accessed 10 June 2022

U.S. Census Bureau QuickFacts statistics for Bethany CDP, Oregon. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.

County tax assessors tax lots, including rights of way, with associated property data, excluding ownership information. Selected items from each county assessor's file are included and standardized for all three counties. The tax lot spatial features and data associated with the tax lot are compiled by Metro from existing records created and maintained by the local county assessment and taxation offices. This is a downloadable zip file that includes the taxlots shapefile and layer files for visualizing taxlots with or without right of ways. Use the original feature layers if viewing the layers in ArcGIS Online: "Taxlots (Public)" or "Taxlots with Right of Way (Public)." Date of last data update: 2025-01-17 This is official RLIS data. Contact Person: Christine Rutan christine.rutan@oregonmetro.gov 503-797-1669 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3733 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use