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.

Vector polygon map data of property parcels from Kanawha County, West Virginia containing 117689 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

The WV_Parcel data is a composite dataset of individual county parcel data. Each county provides a unique dataset, with different temporal currencies, attributes and geographies.Website Link: https://www.mapwv.gov/

Vector polygon map data of property parcels from Berkeley County, West Virginia containing 54,024 features.

​

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

​

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

​

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

The original dataset was compiled by the WV Property Tax Division from WV County Assessor data, and further edited for use.

The original dataset was compiled by the WV Property Tax Division from WV County Assessor data, and further edited for use.

Will vary by map. In each map, each pixel will have a value representing the index of interest. For example, the ForDen_66ha dataset is a grid map for West Virginia at 30 meter resolution. Each pixel value represents an index of forest area density for the surrounding 65.61 ha.(27x27 pixel) analysis window.

This TNC Lands spatial dataset represents the lands and waters in which The Nature Conservancy (TNC) currently has, or historically had, an interest, legal or otherwise in West Virginia. The system of record for TNC Lands is the Legal Records Management (LRM) system, which is TNC’s database for all TNC land transactions.TNC properties should not be considered open to the public unless specifically designated as being so. TNC may change the access status at any time at its sole discretion. It's recommended to visit preserve-specific websites or contact the organization operating the preserve before any planned visit for the latest conditions, notices, and closures. TNC prohibits redistribution or display of the data in maps or online in any way that misleadingly implies such lands are universally open to the public.The types of current land interests represented in the TNC Lands data include: Fields and Attributes included in the public dataset:Field NameField DefinitionAttributesAttribute Definitions Public NameThe name of the tract that The Nature Conservancy (TNC) Business Unit (BU) uses for public audiences.Public name of tract if applicableN/A TNC Primary InterestThe primary interest held by The Nature Conservancy (TNC) on the tractFee OwnershipProperties where TNC currently holds fee-title or exclusive rights and control over real estate. Fee Ownership can include TNC Nature Preserves, managed areas, and properties that are held for future transfer. Conservation EasementProperties on which TNC holds a conservation easement, which is a legally binding agreement restricting the use of real property for conservation purposes (e.g., no development). The easement may additionally provide the holder (TNC) with affirmative rights, such as the rights to monitor species or to manage the land. It may run forever or for an expressed term of years. Deed RestrictionProperties where TNC holds a deed restriction, which is a provision placed in a deed restricting or limiting the use of the property in some manner (e.g., if a property goes up for sale, TNC gets the first option). TransferProperties where TNC historically had a legal interest (fee or easement), then subsequently transferred the interest to a conservation partner. AssistProperties where TNC assisted another agency/entity in protecting. Management Lease or AgreementAn agreement between two parties whereby one party allows the other to use their property for a certain period of time in exchange for a periodic fee. Grazing Lease or PermitA grazing lease or permit held by The Nature Conservancy Right of WayAn access easement or agreement held by The Nature Conservancy. OtherAnother real estate interest or legal agreement held by The Nature Conservancy Fee OwnerThe name of the organization serving as fee owner of the tract, or "Private Land Owner" if the owner is a private party. If The Nature Conservancy (TNC) primary interest is a "Transfer" or "Assist", then this is the fee owner at the time of the transaction.Fee Owner NameN/A Fee Org TypeThe type of organization(s) that hold(s) fee ownership. Chosen from a list of accepted values.Organization Types for Fee OwnershipFED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest HolderThe name of the organization(s) that hold(s) a different interest in the tract, besides fee ownership or TNC Primary Interest. This may include TNC if the Other Interest is held or co-held by TNC. Multiple interest holders should be separated by a semicolon (;).Other Interest Holder NameN/A Other Interest Org TypeThe type of organization(s) that hold(s) a different interest in the tract, besides fee ownership. This may include TNC if the Other Interest is held or co-held by TNC. Chosen from a list of accepted values.Organization Types for interest holders:FED:Federal, TRIB:American Indian Lands, STAT:State,DIST:Regional Agency Special District, LOC:Local Government, NGO:Non-Governmental Organization, PVT:Private, JNT:Joint, UNK:Unknown, TERR:Territorial, DESG:Designation Other Interest TypeThe other interest type held on the tract. Chosen from a list of accepted values.​Access Right of Way; Conservation Easement; Co-held Conservation Easement; Deed Restriction; Co-held Deed Restriction; Fee Ownership; Co-held Fee Ownership; Grazing Lease or Permit; Life Estate; Management Lease or Agreement; Timber Lease or Agreement; OtherN/A Preserve NameThe name of The Nature Conservancy (TNC) preserve that the tract is a part of, this may be the same name as the as the "Public Name" for the tract.Preserve Name if applicableN/APublic AccessThe level of public access allowed on the tract.Open AccessAccess is encouraged on the tract, trails are maintained, signage is abundant, and parking is available. The tract may include regular hours of availability.Open with Limited AccessThere are no special requirements for public access to the tract, the tract may include regular hours of availability with limited amenities.Restricted AccessThe tract requires a special permit from the owner for access, a registration permit on public land, or has highly variable times or conditions to use.Closed AccessNo public access is allowed on the tract.UnknownAccess information for the tract is not currently available.Gap CategoryThe Gap Analysis Project (GAP) code for the tract. Gap Analysis is the science of determining how well we are protecting common plants and animals. Developing the data and tools to support that science is the mission of the Gap Analysis Project (GAP) at the US Geological Survey. See their website for more information, linked in the field name.1 - Permanent Protection for BiodiversityPermanent Protection for Biodiversity2 - Permanent Protection to Maintain a Primarily Natural StatePermanent Protection to Maintain a Primarily Natural State3 - Permanently Secured for Multiple Uses and in natural coverPermanently Secured for Multiple Uses and in natural cover39 - Permanently Secured and in agriculture or maintained grass coverPermanently Secured and in agriculture or maintained grass cover4 - UnsecuredUnsecured (temporary easements lands and/or municipal lands that are already developed (schools, golf course, soccer fields, ball fields)9 - UnknownUnknownProtected AcresThe planar area of the tract polygon in acres, calculated by the TNC Lands geographic information system (GIS).Total geodesic area of polygon in acresProjection: WGS 1984 Web Mercator Auxiliary SphereOriginal Protection DateThe original protection date for the tract, from the Land Resource Management (LRM) system record.Original protection dateN/AStateThe state within the United States of America or the Canadian province where the tract is located.Chosen from a list of state names.N/ACountryThe name of the country where the tract is located.Chosen from a list of countries.N/ADivisionThe name of the TNC North America Region Division where the tract is located. Chosen from a list of TNC North America DivisionsN/A

Geospatial data about Wetzel County, West Virginia Parcels. Export to CAD, GIS, PDF, CSV and access via API.

This map shows high-resolution (1 meter) land cover in the EPA Region 3, covering the parts of West Virginia, Virginia, and Pennsylvania outside of the Chesapeake Bay Watershed. It contains the following classes: Water, Tree Canopy, Scrub\Shrub, Low Vegetation, Barren, Impervious Structures, Other Impervious, Impervious Roads, Tree Canopy Over Impervious Structures, Tree Canopy Over Other Impervious, and Tree Canopy Over Impervious Roads. Using object-based image analysis mapping techniques, it was mapped from a combination of remote-sensing imagery and GIS datasets, including LiDAR, multispectral imagery, and thematic layers (e.g., roads, building footprints). Draft output was then manually reviewed and edited to eliminate obvious errors of omission and commission. The classification scheme closely follows a similar mapping effort for the Chesapeake Bay Watershed; together, maps from the two projects cover the entirety of the EPA Region 3 states. One difference between the projects, however, is that tidal wetlands were mapped in the Chesapeake Bay effort, included as the class Emergent Wetlands, but not in the EPA Region 3 zones outside of the watershed. The map is considered current as of 2020 for West Virginia, 2021 for Virginia, and 2022 for Pennsylvania.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

The Map Service (WFS Group) provides the maps of the Land Development Plan Environment (2004) and Settlement (2006) of the Saarland.:Generalised presentation of waterway connections (WV) within the framework of the LEP Environment 2004.

The mapped area boundary, flood inundation extents, and depth rasters were created to provide an estimated extent of flood inundation along the Cherry River within the communities of Richwood and Fenwick, West Virginia. These geospatial data include the following items: 1. cherry_bnd; shapefile containing the polygon showing the mapped area boundary for the Cherry River flood maps, 2. cherry_hwm; shapefile containing high-water mark points, 3. polygon_cherry_hwm; shapefile containing mapped extent of flood inundation, derived from the water-surface elevation surveyed at high-water marks, 4. depth_hwm; raster file for the flood depths derived from the water-surface elevation surveyed at high-water marks, 5. polygon_cherry_dem; shapefile containing mapped extent of flood inundation, derived from the height above ground recorded at high-water marks and the digital elevation model (DEM) raster, 6. depth_dem; raster file for the flood depths derived from the height above ground recorded at high-water marks and the digital elevation model raster. The upstream and downstream mapped area extent is limited to the upstream-most and downstream-most high-water mark locations. In areas of uncertainty of flood extent, the mapped area boundary is lined up with the flood inundation polygon extent. The mapped area boundary polygon was used to extract the final flood inundation polygon and depth raster from the water-surface elevation raster file. Depth raster files were created using the "Topo to Raster" tool in ArcMap (ESRI, 2012). For this study two sets of inundation layers were generated for each reach. One raster file showing flood depths, "depth_hwm", was created by using high-water mark water-surface elevation values on the land surface and a digital elevation model. However, differences in elevation between the surveyed water-surface elevation values at HWM’s and the land-surface elevation from the digital elevation model data provided uncertainty in the inundation extent of the generated layers. Often times elevation differences of +/- 20 feet were noticed between the surveyed elevation from a HWM on the land surface and the digital elevation model land-surface elevation. Due to these elevation differences, we incorporated a second method of interpolating the water-surface layer. The recorded height above ground value from the surveyed HWM was added to the digital elevation model land-surface elevation at that point. This created a new water-surface elevation value to be used with the “Topo to Raster” interpolation method to create a second depth raster, "depth_dem". Both sets of inundation layers are provided.

This data publication contains a shapefile of points created from 1930s maps of the first land grants within the Monongahela National Forest (MNF) proclamation boundary. Corner or witness trees are those trees listed in a land survey to describe the survey corner for future re-establishment of the corner or property line. Witness trees listed in the deeds were added as attributes to the digital point locations. Deed dates range from 1752 to 1899. If no trees were listed in the deed to witness the corner, the corner was created in the point file, but no species was assigned. The deeds and surveys were created under the metes and bounds method of land survey common in the colonial era. The entire area was not surveyed in any systematic method as is found in the Western United States so there are areas of the MNF with no witness trees. Also included are the scanned images of the maps used to create the database of corner points. Each map covers a portion of the Monongahela National Forest, WV and includes latitude and longitude reference lines. On each map are the individual parcels of land drawn by draftsmen in the 1930s from the original deeds or grants. With each tract is the name of the grantee, the data of the deed or grant, the size of the tract of land (in acres), and a unique identification number that references the deed/grant from which the sketch was made. This data publication also includes two location maps (north and south) showing the location and area covered by the individual map sheets. The base map is a 1936 map of the Monongahela National Forest, WV produced by the USDA Forest Service.This database was developed to help characterize the forest at the time of European settlement.Original metadata date was 10/09/2014. Scanned images of the maps used to create the database of corner points were added on 09/15/2016 along with a few minor metadata updates.

Minor metadata updates on 12/13/2016 and 09/16/2024 (which included URL updates for related articles).

This study mapped land cover (water, bare ground, forest, grass, marsh, algal flat, building, bridge culvert, and agriculture) around Matagorda Bay, Texas. The study area was defined by a 2-km buffer around the West Matagorda Bay shoreline and extended from the western portion of the Colorado River Delta through the eastern portion of Matagorda Island, Texas. This study incorporated WorldView-2 (WV-2; acquired on 2012-11-17, 2013-05-05, and 2013-12-16) and lidar (acquired 2018-01-04 - 2018-02-23 and 2019-01-24 – 2019-01-29) to obtain a 2-m resolution habitat map for the entire study area. A novel stacked classification approach was developed to take advantage of high-resolution satellite imagery and airborne lidar point clouds. Ultimately, a rule-based classifier was stacked on a group of machine learning classifiers for multispectral images and a filter classifier for lidar point clouds. The data were created for the Texas Office of the Comptroller project titled “Matagorda Bay Ecosystem Assessment.†Maps of vegetation, sand, and water coverage for discrete dates from 1850 to 2020 are available in related dataset HI.x833.000:0020 (https://doi.org/10.7266/zs2f74bj).

no abstract provided

The mapped area boundary, flood inundation extents, and depth rasters were created to provide an estimated extent of flood inundation along the Greenbrier River within the community of Ronceverte, West Virginia. These geospatial data include the following items: 1. greenbrier_ron_bnd; shapefile containing the polygon showing the mapped area boundary for the Greenbrier River flood maps, 2. greenbrier_ron_hwm; shapefile containing high-water mark points, 3. polygon_greenbrier_ron_hwm; shapefile containing mapped extent of flood inundation, derived from the water-surface elevation surveyed at high-water marks, 4. depth_hwm; raster file for the flood depths derived from the water-surface elevation surveyed at high-water marks, 5. polygon_greenbrier_ron_dem; shapefile containing mapped extent of flood inundation, derived from the height above ground recorded at high-water marks and the digital elevation model (DEM) raster, 6. depth_dem; raster file for the flood depths derived from the height above ground recorded at high-water marks and the digital elevation model raster. The upstream and downstream mapped area extent is limited to the upstream-most and downstream-most high-water mark locations. In areas of uncertainty of flood extent, the mapped area boundary is lined up with the flood inundation polygon extent. The mapped area boundary polygon was used to extract the final flood inundation polygon and depth raster from the water-surface elevation raster file. Depth raster files were created using the "Topo to Raster" tool in ArcMap (ESRI, 2012). For this study two sets of inundation layers were generated for each reach. One raster file showing flood depths, "depth_hwm", was created by using high-water mark water-surface elevation values on the land surface and a digital elevation model. However, differences in elevation between the surveyed water-surface elevation values at HWM’s and the land-surface elevation from the digital elevation model data provided uncertainty in the inundation extent of the generated layers. Often times elevation differences of +/- 20 feet were noticed between the surveyed elevation from a HWM on the land surface and the digital elevation model land-surface elevation. Due to these elevation differences, we incorporated a second method of interpolating the water-surface layer. The recorded height above ground value from the surveyed HWM was added to the digital elevation model land-surface elevation at that point. This created a new water-surface elevation value to be used with the “Topo to Raster” interpolation method to create a second depth raster, "depth_dem". Both sets of inundation layers are provided.

Geology was researched and compiled for use in studies of ecosystem health, environmental impact, soils, groundwater, land use, tectonics, crustal genesis, sedimentary provenance, and any others that could benefit from geographically referenced geological data.

The Washington DC Area geologic map database (DCDB) provides geologic map information of areas to the NW, W, and SW of Washington, DC to various professionals and private citizens who have uses for geologic data. Digital, geographically referenced, geologic data is more versatile than traditional hard copy maps, and facilitates the examination of relationships between numerous aspects of the geology and other types of data such as: land-use data, vegetation characteristics, surface water flow and chemistry, and various types of remotely sensed images. The DCDB was created by combining Arc/Info coverages, designing a Microsoft (MS) Access database, and populating this database. Proposed improvements to the DCDB include the addition of more geochemical, structural, and hydrologic data.

Data are provided in several common GIS formats and MS Access database files. The geologic data themes included are bedrock, surficial, faults and fold axes, neat line, structural data, and sinkholes; the base themes are political boundaries, roads, elevation contours, and hydrography.

Data were originally collected in UTM coordinates, zone 18, NAD 1927, and projected to geographic coordinates (Lat/Long), NAD 1983. The data base is accompanied by large format color maps, a readme.txt file, and a explanatory PDF pamphlet.

description: The mapped area boundary, flood inundation extents, and depth rasters were created to provide an estimated extent of flood inundation along the Meadow River and Sewell Creek within the community of Rainelle, West Virginia. These geospatial data include the following items: 1. meadow_sewell_bnd; shapefile containing the polygon showing the mapped area boundary for the Meadow River and Sewell Creek flood maps, 2. meadow_sewell_hwm; shapefile containing high-water mark points, 3. polygon_meadow_sewell_hwm; shapefile containing mapped extent of flood inundation, derived from the water-surface elevation surveyed at high-water marks, 4. depth_hwm; raster file for the flood depths derived from the water-surface elevation surveyed at high-water marks, 5. polygon_meadow_sewell_dem; shapefile containing mapped extent of flood inundation, derived from the height above ground recorded at high-water marks and the digital elevation model (DEM) raster, 6. depth_dem; raster file for the flood depths derived from the height above ground recorded at high-water marks and the digital elevation model raster. The upstream and downstream mapped area extent is limited to the upstream-most and downstream-most high-water mark locations. In areas of uncertainty of flood extent, the mapped area boundary is lined up with the flood inundation polygon extent. The mapped area boundary polygon was used to extract the final flood inundation polygon and depth raster from the water-surface elevation raster file. Depth raster files were created using the "Topo to Raster" tool in ArcMap (ESRI, 2012). For this study two sets of inundation layers were generated for each reach. One raster file showing flood depths, "depth_hwm", was created by using high-water mark water-surface elevation values on the land surface and a digital elevation model. However, differences in elevation between the surveyed water-surface elevation values at HWMs and the land-surface elevation from the digital elevation model data provided uncertainty in the inundation extent of the generated layers. Often times elevation differences of +/- 20 feet were noticed between the surveyed elevation from a HWM on the land surface and the digital elevation model land-surface elevation. Due to these elevation differences, we incorporated a second method of interpolating the water-surface layer. The recorded height above ground value from the surveyed HWM was added to the digital elevation model land-surface elevation at that point. This created a new water-surface elevation value to be used with the Topo to Raster interpolation method to create a second depth raster, "depth_dem". Both sets of inundation layers are provided.; abstract: The mapped area boundary, flood inundation extents, and depth rasters were created to provide an estimated extent of flood inundation along the Meadow River and Sewell Creek within the community of Rainelle, West Virginia. These geospatial data include the following items: 1. meadow_sewell_bnd; shapefile containing the polygon showing the mapped area boundary for the Meadow River and Sewell Creek flood maps, 2. meadow_sewell_hwm; shapefile containing high-water mark points, 3. polygon_meadow_sewell_hwm; shapefile containing mapped extent of flood inundation, derived from the water-surface elevation surveyed at high-water marks, 4. depth_hwm; raster file for the flood depths derived from the water-surface elevation surveyed at high-water marks, 5. polygon_meadow_sewell_dem; shapefile containing mapped extent of flood inundation, derived from the height above ground recorded at high-water marks and the digital elevation model (DEM) raster, 6. depth_dem; raster file for the flood depths derived from the height above ground recorded at high-water marks and the digital elevation model raster. The upstream and downstream mapped area extent is limited to the upstream-most and downstream-most high-water mark locations. In areas of uncertainty of flood extent, the mapped area boundary is lined up with the flood inundation polygon extent. The mapped area boundary polygon was used to extract the final flood inundation polygon and depth raster from the water-surface elevation raster file. Depth raster files were created using the "Topo to Raster" tool in ArcMap (ESRI, 2012). For this study two sets of inundation layers were generated for each reach. One raster file showing flood depths, "depth_hwm", was created by using high-water mark water-surface elevation values on the land surface and a digital elevation model. However, differences in elevation between the surveyed water-surface elevation values at HWMs and the land-surface elevation from the digital elevation model data provided uncertainty in the inundation extent of the generated layers. Often times elevation differences of +/- 20 feet were noticed between the surveyed elevation from a HWM on the land surface and the digital elevation model land-surface elevation. Due to these elevation differences, we incorporated a second method of interpolating the water-surface layer. The recorded height above ground value from the surveyed HWM was added to the digital elevation model land-surface elevation at that point. This created a new water-surface elevation value to be used with the Topo to Raster interpolation method to create a second depth raster, "depth_dem". Both sets of inundation layers are provided.

Morgantown, WV Zoning - effective as of 08-29-2024.Data generated by City of Morgantown Development Services using Monongalia County tax parcel data and previously-established zoning maps. Data maintained by the City's GIS staff.Updates as of 08-29-2024:- Adjusted boundary as part of annexation of property at intersection of Earl Core Rd. and Brookhaven Rd. (no parcel available)- Rezoned annexed area to B-2 district.- Rezoned part of parcels 12-15-94 and 12-15-95 to R-3 district.- Rezoned parcel 15-05-18 to R-3 district.Updates as of 05-23-2023:- Rezoned parcels 15-55-92 and 15-55-93 to B-2 district.- Rezoned parcels 13-26-240, 13-26-243, and 13-26-244 to B-4 district.Updates as of 09-15-2021:- Rezoned parcels 14-45-5.2, 14-45-6, 14-45-7, and 14-45-7.4 to B-2 district.- Rezoned parcel 5-40-8.2 to B-2 district.Updated as of 08-04-2020:- Created geometry and attributes for the new Wiles Hill Gateway Overlay District (WHOD).- Attached Ordinance 2020-26 to the new Wiles Hill Gateway Overlay District (WHOD).Updates as of 07-07-2020:- Rezoned parcel 15-6-76.1 and part of parcel 15-11-258 to B-2 district.Updates as of 05-05-2020:- Rezoned parcels 12-12-1.1, 15-11-89, 15-11-90, and 15-11-91 to B-2 district.Updates as of 03-04-2020:- Ordinance 2020-06 attached to all Overlay Districts for confirmation of boundaries.Updates as of 02-04-2020:- Rezoned parcel 15-07-267 from R-1 to B-1 district.Updates as of 12-03-2019:- Adjusted zoning district boundaries to conform to existing parcel boundaries.- Added annexed parcel 08-08B-15 into R-1A district.