This data is maintained by and obtained from Metro GIS. Click the link above to view the Metro GIS metadata for this dataset.

This data is maintained by and obtained from Metro Data Resource Center. Please go to https://gis.oregonmetro.gov/rlis-metadata/#/details/155 for the complete metadata.-- Additional Information: Category: Boundary Purpose: For use as a "base" layer on map products to shade county areas and in analysis to capture areas within each county. Update Frequency: None planned-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=155

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.

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.

Map showing public lands in Jackson County. The map document is 34 inches by 44 inches.

This map show the zip code areas in Jackson County. The map is 34 inches by 44 inches.

Crook County's boundary

FEMA Framework Basemap datasets comprise six of the seven FGDC themes of geospatial data that are used by most GIS applications (Note: the seventh framework theme, orthographic imagery, is packaged in a separate NFIP Metadata Profile): cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water areas & lines. These data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13)

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 primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

Geospatial data about Marion County, Oregon Fire District Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

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.

This digital map database, compiled from previously published and unpublished data, and new mapping by the authors, represents the general distribution of bedrock and surficial deposits of the Salem East and Turner 7.5 minute quadrangles. A previously published adjacent geologic map and database by Tolan, Beeson, and Wheeler (1999) contains a text file (geol.txt or geol.ps), it provides current information on the geologic structure and stratigraphy of the area covered. The database delineates map units that are identified by general age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution (scale) of the database to 1:24,000 or smaller.

This map layer includes cities and towns in Oregon. These cities were clipped from a larger dataset of cities collected from the 1970 National Atlas of the United States. Where applicable, U.S. Census Bureau codes for named populated places were associated with each name to allow additional information to be attached. The Geographic Names Information System (GNIS) was also used as a source for additional information. This is a revised version of the December 2003 map layer.

This data release for the reconnaissance geologic map of the Hells Canyon Study Area, Wallowa County, Oregon, and Idaho and Adams Counties, Idaho, is a Geologic Map Schema (GeMS, 2020)-compliant version of the geologic map published in U.S. Geological Survey (USGS) Scientific Investigations Report Map SIR 2007-5046 (Simmons, et al, 2007). The database represents the geology for the 625,177-acre (2,530 square kilometers), geologically complex Hells Canyon Study Area in two plates, at a publication scale of 1:48,000. The study area includes (1) the Hells Canyon Wilderness; (2) parts of the Snake River, Rapid River, and West Fork Rapid River Wild and Scenic Rivers; (3) lands included in the second Roadless Area Review and Evaluation (RARE II); and (4) part of the Hells Canyon National Recreation Area. References: Simmons, G.C., Gualtieri, J.L., Close, T.J., Federspiel, F.E., and Leszcykowski, A.M., 2007, Mineral resources of the Hells Canyon study area, Wallowa County, Oregon, and Id ...

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 Floodplain Mapping study deliverables depict and quantify the flood risks for the study area. 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 Floodplain Mapping flood risk boundaries are derived from the engineering information 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. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).

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.

This map shows the Housing and Urban Development Areas in Jackson County and was Map 12 in the Jackson County Community Fire Plan. The page size is 11 inches by 17 inches.

Clackamas, Clark, Multnomah, Washington, Polk, Columbia, Tillamook, Marion and Yamhill county boundaries in Oregon and Clark, Cowlitz, Skamania county boundaries in Washington. Date of last data update: 2024-12-23 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/155 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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