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) System (MTS). The MTS 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. County subdivisions are the primary divisions of counties and 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 is not 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 boundaries of most legal MCDs are as of January 1, 2024, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

COB_POLY: This theme shows the jurisdictional and cartographic county areas for Oregon and Washington. The POCA layer is an integrated set of geographic- referencing data covering the state of Washington. It is derived from land surveys, DNR orthophotos, USGS 7.5' quadrangles, and DNR tract books.

Dataset

This dataset was created by Ihsan L

Released under Apache 2.0

Contents

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 Address Ranges Feature Shapefile (ADDRFEAT.dbf) contains the geospatial edge geometry and attributes of all unsuppressed address ranges for a county or county equivalent area. The term "address range" refers to the collection of all possible structure numbers from the first structure number to the last structure number and all numbers of a specified parity in between along an edge side relative to the direction in which the edge is coded. Single-address address ranges have been suppressed to maintain the confidentiality of the addresses they describe. Multiple coincident address range feature edge records are represented in the shapefile if more than one left or right address ranges are associated to the edge. The ADDRFEAT shapefile contains a record for each address range to street name combination. Address range associated to more than one street name are also represented by multiple coincident address range feature edge records. Note that the ADDRFEAT shapefile includes all unsuppressed address ranges compared to the All Lines Shapefile (EDGES.shp) which only includes the most inclusive address range associated with each side of a street edge. The TIGER/Line shapefile contain potential address ranges, not individual addresses. The address ranges in the TIGER/Line Files are potential ranges that include the full range of possible structure numbers even though the actual structures may not exist.

County boundaries in Eastern Tennessee. This layer was originally obtained from the State of Tennessee.

These files are an extract of selected geographic and cartographic information from the 1995 TIGER/Line files detailing counties and statistically equivalent entities.

Clark County Boundary as established in 1880.See Clark County Metadata Data source: ..\FGDB\dw_county.gdb\County

Washington State County Boundaries including Department of Natural Resources (DNR) county codes. This data is created from the WA Public Land Survey source data maintained by the DNR.WA County Boundaries Metadata

This data set is created using the township lines from the Snohomish County Assessor's Public Land Survey grid for the north and south boundary. The west boundary is taken from a Washington State county boundaries data set wtih a minor modification at its northerly extent to follow tide land boundries. The eastern boundary is taken from the Snohomish County basins data set.

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 All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

Clackamas, Clark, Multnomah, Washington, Polk, Columbia, Tillamook, Marion, Hood River, and Yamhill county boundaries in Oregon and Clark, Cowlitz, Skamania county boundary in Washington. Date of last data update: 2024-12-30 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/1437 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.

Washington County Maryland Interactive Parks Map

Line feature class of Washington county boundaries, obtained from US Census Bureau.

The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.

© Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project

This layer is a component of Feature classes representing locality (county, city, and town) boundaries in the Commonwealth of Virginia..

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) System (MTS). The MTS 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 All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

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) System (MTS). The MTS 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 All Roads shapefile includes all features within the MTS Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in the MTS that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

County boundaries for Washington state, with Puget Sound removed, showing coastal shoreline. Also as KINGSH for King County only.

Washington County, MN Tax Parcels. An independent manual check of the parcel data was made at the time of its initial development whereby all geo-coded parcel legal descriptions in a PLSS section were reinterpreted and examined for accuracy and completeness on the hard copy check plot. As each new plat or lot division occurs, a similar process is repeated for the new additions during the maintenance period. Multiple lines of ownership indicating ambiguity in property line location are merged into a single line if falling within 3 feet of each other. Gaps or overlaps in these situations are not shown. In some cases where two lines converge; e.g., where at one end the two lot lines are within 0.50 feet of each other and at the other end they are within 6.00 feet of each other they may be merged because the average discrepancy is 3 feet or less. Where gaps or overlaps exist in excess of approximately 3 feet in width, they are shown with text notation indicating APPARENT GAP or AREA OF DISCREPANCY.