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.
Geospatial data about Lane County, Oregon Census Tracts. Export to CAD, GIS, PDF, CSV and access via API.
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.
Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas.
The BG boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.
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
2010 Deschutes County, Oregon Census Blocks. Census blocks are geographic areas within a census block group. U.S. Census blocks are the smallest geographic entities within a county for which the Census Bureau tabulates population.
Notes: These 7 fields are mutually exclusive. Use them if you need the sum of the race categories to equal total population. NH_WHITE_O Not Hispanic or Latino: Population of one race: White alone NH_BLACK_O Not Hispanic or Latino: Population of one race: Black or African American alone NH_AIAN_ON Not Hispanic or Latino: Population of one race: American Indian and Alaska Native alone NH_ASIAN_O Not Hispanic or Latino: Population of one race: Asian alone NH_NHOPI_O Not Hispanic or Latino: Population of one race: Native Hawaiian and Other Pacific Islander alone NH_OTHER Not Hispanic or Latino: Population of one race: Some Other Race alone NH_TWO_OR_ Not Hispanic or Latino: Population of two or more races
Use these fields to include all people who chose the specific race. For example, 30% of Oregonians who chose ""Black or African American"" also chose another race and some also chose Hispanic, so the NH_BLACK_O field under reports the African American population. The sum of these fields may exceed total population.WH_AOIC White alone or in combination with one or more other races BL_AOIC Black or African American alone or in combination with one or more other races AIAN_AOIC American Indian and Alaska Native alone or in combination with one or more other races ASN_AOIC Asian alone or in combination with one or more other races NHOPI_AOIC Native Hawaiian and Other Pacific Islander alone or in combination with one or more other races OTH_AOIC Some Other Race alone or in combination with one or more other races.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Urban Growth AreasThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau, displays Urban Growth Areas (UGA) in the United States. Per the USCB, “UGAs are legally defined entities in Oregon and Washington and are used to regulate urban growth. UGA boundaries, which need not follow visible features, are delineated cooperatively by state and local officials in Oregon and Washington and then confirmed in state law.”Metro Urban Growth AreaData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Urban Growth Areas) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 62 (Series Information for 2020 Census Urban Growth Area (UGA) State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Urban Growth Areas - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit:Urban Growth AreasUrban Growth Area Maps (Washington)Urban Growth Boundaries (Oregon)For feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets
Click here for research on the effects of land use planning and gentrification on Portland’s communities of color and other vulnerable populations. Economic Vulnerability Assessment:This map identifies census tracts in Portland where residents are more vulnerable to changing economic conditions, making resisting displacement more difficult. These areas have residents who are more likely to:Be "housing cost-burdened", meaning they pay 30% or more of their income on housing costs.Belong to communities of color, particularly Black and Indigenous communities.Lack college degrees, andHave Lower Incomes.This dataset provides an update to the vulnerability risk analysis that Dr. Lisa Bates prepared for the Bureau of Planning and Sustainability in 2012.This latest dataset includes the following changes in methodology:Low income households were replaced with a size-adjusted median household income. This helps account for how different household sizes experience living with different incomes.Renter households were replaced with households that are housing cost-burdened (pay 30%+ on housing costs). This acknowledges that homeowners who pay a high percentage of their income on housing can be vulnerable to displacement as well.A new variable, Black and Indigenous population, was added to better incorporate past harms to these communities.The vulnerability score was rescaled from 0 to 100. A score of 60 or greater is considered a vulnerable tract.Data sources: U.S. Census Bureau, 2022 ACS 5-year estimates, Tables B25106, B25010, B03002, B19013, B15002. Prepared Summer 2024 by the Portland Bureau of Planning and Sustainability.Download dataset from City of Portland Open Data siteAbout the Bureau of Planning and SustainabilityThe Portland Bureau of Planning and Sustainability (BPS) develops creative and practical solutions to enhance Portland’s livability, preserve distinctive places and plan for a resilient future.Need more information about this data? Email bpsgis@portlandoregon.gov-- Additional Information: Category: Planning Purpose: Map the areas susceptible to gentrification pressure. Update Frequency: Yearly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54141
Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
License information was derived automatically
This map shows the life expectancy at birth by census tract in the 3-county region. Life expectancy data originates from Oregon Health Authority, 2018 report.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
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.