Digitized from USGS 1:24,000-scale Digital Raster Graphics (scanned topographic maps) by the West Virginia Department of Environmental Protection. WVGISTC dissolved county boundaries to create the state boundary. Published May 2002.Coordinate System: Lat/Long NAD 1983,UTM NAD 1983

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. 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. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. 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, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The 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.

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, 2021, 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.

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

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.

Tax District Boundaries: Official tax district boundary lines adopted by the WV Legislature in 1978 as a general reference to delineate rural tax district boundaries. The boundaries were drawn from 1:24,000-scale USGS topographic maps in 1978 and coincide with county magisterial districts as of July 1, 1973. Unlike magisterial districts that are realigned every ten years following the census, the tax district boundary does not follow equal representation requirements. In 1978 the West Virginia Geologic and Economical Survey published six 1:500,000-scale maps delineating official county and tax district boundary lines for the State. In 1996 the West Virginia Department of Tax and Revenue, Property Tax Division, converted the 1978 source maps into a digital format and added descriptive attributes for each tax district. In October of 2003, the WV GIS Technical Center appended 24K DLG boundary files and lines drawn from 24K DRGs into a statewide 24K Tax District Boundary dataset. In 2017, WVGISTC has appended this file with parcel data or Census Populated Places boundaries for missing tax districts.

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, 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.

The 2023 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. 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.

Snapshot of all Interstate, US, West Virginia and County Highway Signs in West Virginia as extracted by Mutcdname from an overall Sign Dataset. Data sets include RouteID, Sign ID Number, County Code, Route Number, Sub Route Number, Sign System, Supplemental Code, Supplemental Description, Direction, Milepoint, Number of Signs, Location, Mutcdname, Mutcode, Mutcdcat, Text, County, PhotoURL, and X Y Coordinates. Data is in NAD_1983_UTM_Zone_17N coordinate system. Data is updated as part of the semiannual WVDOT Road Network release.

This layer, Blackwater Falls State Park, shows the boundary of Blackwater Falls State Park in Tucker County, West Virginia. The data associated with this layer were received from Friends of Blackwater. Source and date:The Blackwater Falls State Park boundary was received as a shapefile from Friends of Blackwater on September 29th, 2022. It reflects the boundary shown on the official Blackwater Falls State Park trail map, and was confirmed with tax parcel maps by Civil & Environmental Consultants, Inc. of Bridgeport, WV.Purpose:The Blackwater Falls State Park boundary was created to show the extent of the park and its proximity to the proposed Corridor H. Processing:ABRA imported the downloaded shapefile polygon layer into ArcGIS and symbolized it as shown to create this feature layer.Symbolization:The following symbolization is how it appears in the Parsons to Davis online map provided by ABRA.Blackwater Falls State Park: green polygon with a black dashed outline

Feature Class generated showing the physical locations of all West Virginia Division of Highways (WVDOH) Facilities including, County Headquarters, District Headquarters, Substations, Sections, Equipment Shops, Stockpiles, Bridge Departments, Storage Lots, Sign Shops, Heavy Maintenance Facilities, and Equipment Shops as illustrated in the Fuel Sites Map. Information included in this dataset is Facility Name, Facility Address, facility City, State, Zip Code, County, Facility Phone and Fax Numbers, District, Fuel Types(If available), Facility Type, Headquarters, Lat and Long Coordinates, Th This feature is in the NAD_1983_UTM_Zone_17N coordinate system. Data is updated as needed when new data becomes available or facility has changed. Data is current as of and November 2021.

An orthoimage is remotely sensed image data in which displacement of features in the image caused by terrain relief and sensor orientation has been mathematically removed. Orthoimagery combines the image characteristics of a photograph with the geometric qualities of a map. For this dataset, 2-foot pixel resolution natural color digital orthimages were obtained from the West Virginia Statewide Addressing and Mapping Board. The orthoimages were mosaicked and reprojected by the USGS from the original 2-foot pixel, West Virginia North and South State Plane (feet) Coordinate Systems to Universal Transverse Mercator (UTM) (meters), Zone 17, NAD83 datum. Each orthoimage (DOQQ) provides the equivalent to a quarter of a 7.5-minute map (3.75 minutes of latitude and longitude) with overedge. The overedge is approximately 300 meters beyond the extremes of the corners of coverage. The naming convention is based on the U.S. Geological Survey 1:24,000 Topographic Map Series with the quadrant abbreviation, i.e. athens_ne.tif, etc. This data set covers the entire state of West Virginia including into UTM zone 18 on the east edge.

The 2015 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. The records in this file allow users to map the parts of Urban Areas that overlap a particular county. After each decennial census, the Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes. 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, 2010.

Public Law (P.L.) 94-171, enacted in 1975, directs the U.S. Census Bureau to make special preparations to provide redistricting data needed by the 50 states. It specifies that within a year following Census Day (by April 1, 2011), the Census Bureau must send the governor and legislature in each state the data they need to redraw districts for the United States Congress and state legislature. The Census 2010 Redistricting Data Program was set up to afford state officials an opportunity to define the small areas for which they wish to receive census population totals for redistricting purposes. Officials then could receive data for voting districts (e.g., election precincts, wards, state house and senate districts) in addition to standard census geographic areas, such as counties, cities, census tracts, and blocks. State participation in defining areas is voluntary and nonpartisan. There are four map types that support the 2010 Census Redistricting Data (Public Law [P.L.] 94-171) program. Each of these large format map types is produced in Adobeâ s portable document format (PDF). These georeferenced PDF files were created in compliance with the OGC PDF Geo-registration Encoding Best Practice Version 2.2 (OGC project document reference number OGC 08-139r2). They will also be available through the U.S. Census Bureau Map Products web site. In addition to the maps, other geographic products include the State Redistricting Data (P.L.94-171) Shapefiles and the 2010 Census Block Assignment Files, which provide census block relationships to voting districts, state legislative districts, school districts, and congressional districts. All four map types are produced in a set for each county or statistically equivalent entity (school district maps for the District of Columbia, Florida, Hawaii, Maryland, Nevada, and West Virginia are state-based). Each map set consists of one or more numbered parent sheets which cover the entire county. If necessary, separate inset sheets show areas of dense features at a larger scale. Inset areas are identified with letters. If the set has more than one parent sheet, an index sheet is also included which depicts the arrangement of the parent sheets and inset areas in relation to the county boundary and selected major features. All of the parent sheets within a county are produced at the same scale, while maps for adjacent counties may be at different scales. The objective of each map type is to use the smallest number of sheets while preserving legibility of geographic entity names and feature identifiers. The physical size of the county and the density of features also affect the number of parent sheets and insets.

The purpose of the medication-assisted treatment (MAT) facility maps is to identify areas on a state-by-state basis that may be potentially underserved by existing treatment facilities. The maps are created with a methodology that seeks to include the highest potential need areas from individual counties so that county-level stakeholders are also informed. The maps are meant to be used as a tool for policy makers to determine potentially underserved areas—not as a definitive representation of these areas.