This service provides vector polygon dataset defining the official boundaries of the 100 counties within North Carolina as well as the boundaries between North Carolina and the states which border North Carolina.The North Carolina county polygon boundary service provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. Some boundaries cannot be surveyed in cases where boundaries are coincident with river centers. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.This data is updated annually, first quarter (usually in February).MetadataThe metadata for the contained layer of the NCDOT County Boundaries Service is available through the following link:County Boundaries PolygonPoint of Contact North Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the County Boundaries data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product Team

The NC OneMap Direct Data Downloads allows for the download of pre-packaged popular data sets imagery, parcels, contour lines, elevation data (DEMs) and address points, by county.

For more information related to these data, please see:

 Imagery
 Parcels
 Contours/Elevation
 Addresses

The North Carolina State and County Boundary vector polygon data provides location information for North Carolina State and County Boundary lines derived from the best available survey and/or Geographic Information System (GIS) data. Sources for information are the North Carolina Geodetic Survey (NCGS), NC Department of Transportation (NCDOT), United States Geological Survey (USGS), and field surveys conducted by licensed surveyors in North Carolina and neighboring states that have been approved and recorded in their respective counties. North Carolina Geodetic Survey assists counties on a cooperative basis (NC General Statute 153A-18) in defining and monumenting the location of uncertain or disputed boundaries as established by law. Some counties have completed boundary surveys for at least a portion of their county boundary. However, the majority of county boundaries have not been surveyed and are represented by the best currently available data from GIS sources, including NCDOT county maps (which originally came from the USGS) and updated county parcel maps.

This service provides the polygon representing the North Carolina state boundary. It allows the entire state to be viewed as one polygon. The boundary is selected from the outermost county boundaries bordering other states and the Atlantic Ocean.MetadataThe metadata for the contained layer of the NCDOT State Boundary Service is available through the following link:NC State BoundaryPoint of Contact North Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the State Boundary data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product Team

NOTE: To download parcels by county DO NOT use the map. Instead:click the Download buttonclick Download parcels by county or all counties at oncescroll to the Direct Data Downloads section and download your dataThis digital geospatial dataset represents parcel boundaries with standard core attributes for a collection of parcel data from North Carolina county data producers and the Eastern Band of Cherokee Indians. The Integrated Cadastral Data Exchange project transformed source datasets from county data producers to create a standardized dataset with consistent attributes (fields). The individual standardized county datasets were aggregated into a single dataset. The aggregated parcel dataset includes all 100 counties in North Carolina plus lands of the Eastern Band of Cherokee Indians. The source geometry is retained as published by individual county data producers. This dataset includes attributes such as ownership, area in acres, assessed value, and other core cadastral attributes. Web services have both polygons (parcel boundaries) and points representing each property, placed at or near the geometric center, with the same set of attributes.See the NC OneMap parcels page for more information.

A 60" x 32" general reference wall map containing roads, boundaries (state, county, and municipal), and major water bodies.

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

911 Public Safety Answering Point (PSAP) service area boundaries in North Carolina According to the National Emergency Number Association (NENA), a Public Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1 calls. The service area is the geographic area within which a 911 call placed using a landline is answered at the associated PSAP. This dataset only includes primary PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive calls that have been transferred by a primary PSAP. Backup PSAPs provide service in cases where another PSAP is inoperable. Most military bases have their own emergency telephone systems. To connect to such system from within a military base it may be necessary to dial a number other than 9 1 1. Due to the sensitive nature of military installations, TGS did not actively research these systems. If civilian authorities in surrounding areas volunteered information about these systems or if adding a military PSAP was necessary to fill a hole in civilian provided data, TGS included it in this dataset. Otherwise military installations are depicted as being covered by one or more adjoining civilian emergency telephone systems. In some cases areas are covered by more than one PSAP boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where a specific call is routed may depend on how busy the applicable PSAPS are (i.e. load balancing), operational status (i.e. redundancy), or time of date / day of week. If an area does not have 911 service, TGS included that area in the dataset along with the address and phone number of their dispatch center. These are areas where someone must dial a 7 or 10 digit number to get emergency services. These records can be identified by a "Y" in the [NON911EMNO] field. This indicates that dialing 911 inside one of these areas does not connect one with emergency services. This dataset was constructed by gathering information about PSAPs from state level officials. In some cases this was geospatial information, in others it was tabular. This information was supplemented with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was researched to verify its tabular information. In cases where the source data was not geospatial, each PSAP was researched to determine its service area in terms of existing boundaries (e.g. city and county boundaries). In some cases existing boundaries had to be modified to reflect coverage areas (e.g. entire county north of Country Road 30). However, there may be cases where minor deviations from existing boundaries are not reflected in this dataset, such as the case where a particular PSAPs coverage area includes an entire county, and the homes and businesses along a road which is partly in another county. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.

The 2022 cartographic boundary KMLs 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 cartographic boundary files 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 generalized boundaries of most incorporated places in this file are based on those as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

The 2020 TIGER/Line Shapefiles contain current geographic extent and boundaries of both legal and statistical entities (which have no governmental standing) for the United States, the District of Columbia, Puerto Rico, and the Island areas. This vintage includes boundaries of governmental units that match the data from the surveys that use 2020 geography (e.g., 2020 Population Estimates and the 2020 American Community Survey). In addition to geographic boundaries, the 2020 TIGER/Line Shapefiles also include geographic feature shapefiles and relationship files. Feature shapefiles represent the point, line and polygon features in the MTDB (e.g., roads and rivers). Relationship files contain additional attribute information users can join to the shapefiles. Both the feature shapefiles and relationship files reflect updates made in the database through September 2020. To see how the geographic entities, relate to one another, please see our geographic hierarchy diagrams here. Census Urbanized Areashttps://www2.census.gov/geo/tiger/TIGER2020/UAC Census Urban/Rural Census Block Shapefileshttps://www.census.gov/cgi-bin/geo/shapefiles/index.php 2020 TIGER/Line and Redistricting shapefiles:https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.2020.html Technical documentation:https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2020/TGRSHP2020_TechDoc.pdf TIGERweb REST Services:https://tigerweb.geo.census.gov/tigerwebmain/TIGERweb_restmapservice.html TIGERweb WMS Services:https://tigerweb.geo.census.gov/tigerwebmain/TIGERweb_wms.html The legal entities included in these shapefiles are:American Indian Off-Reservation Trust LandsAmerican Indian Reservations – FederalAmerican Indian Reservations – StateAmerican Indian Tribal Subdivisions (within legal American Indian areas)Alaska Native Regional CorporationsCongressional Districts – 116th CongressConsolidated CitiesCounties and Equivalent Entities (except census areas in Alaska)Estates (US Virgin Islands only)Hawaiian Home LandsIncorporated PlacesMinor Civil DivisionsSchool Districts – ElementarySchool Districts – SecondarySchool Districts – UnifiedStates and Equivalent EntitiesState Legislative Districts – UpperState Legislative Districts – LowerSubminor Civil Divisions (Subbarrios in Puerto Rico) The statistical entities included in these shapefiles are:Alaska Native Village Statistical AreasAmerican Indian/Alaska Native Statistical AreasAmerican Indian Tribal Subdivisions (within Oklahoma Tribal Statistical Areas)Block Groups3-5Census AreasCensus BlocksCensus County Divisions (Census Subareas in Alaska)Unorganized Territories (statistical county subdivisions)Census Designated Places (CDPs)Census TractsCombined New England City and Town AreasCombined Statistical AreasMetropolitan and Micropolitan Statistical Areas and related statistical areasMetropolitan DivisionsNew England City and Town AreasNew England City and Town Area DivisionsOklahoma Tribal Statistical AreasPublic Use Microdata Areas (PUMAs)State Designated Tribal Statistical AreasTribal Designated Statistical AreasUrban AreasZIP Code Tabulation Areas (ZCTAs)Shapefiles - Features:Address Range-FeatureAll Lines (called Edges)All RoadsArea HydrographyArea LandmarkCoastlineLinear HydrographyMilitary InstallationPoint LandmarkPrimary RoadsPrimary and Secondary RoadsTopological Faces (polygons with all geocodes)Relationship Files:Address Range-Feature NameAddress RangesFeature NamesTopological Faces – Area LandmarkTopological Faces – Area HydrographyTopological Faces – Military Installations

A 49" x 23" general reference river basin wall map containing river basin boundaries, county boundaries, roads, major water bodies, and cities.

The NC Center for Geographic Information and Analysis, using US Department of Commerce, Bureau of the Census data, developed the GIS data set versions of the 1990 Census TIGER/Line files for each of the 100 counties in North Carolina. This data is stored in a county library under the layer name tiger90. Associated attribute tables also reside in each tile workspace.

Broadband Serviceable Locations (BSLs) that are eligible for funding through the NC Completing Access to Broadband (CAB) Program. Eligible locations are determined by analyzing the availability of broadband as reported by internet providers to the Federal Communications Commission (FCC) through their Broadband Data Collection (BDC). Locations are categorized into service levels in the data as:No Service – Locations with no reported service from Fiber, Cable, DSL, Licensed Fixed Wireless, or Licensed-by-Rule Fixed Wireless providers at any speed.Unserved Locations – Locations without access to internet service of at least 25mb/s download and 3mb/s upload speeds (25/3) and with low latency. Locations which are only served by DSL, Licensed-by-Rule Terrestrial Fixed Wireless, Unlicensed Fixed Wireless, or Licensed Fixed Wireless over mobile networks at any speed are also considered unserved.Underserved Locations – Locations with access to internet service of at least 25mb/s download and 3mb/s upload speeds, but less than 100mb/s Download and 20mb/s Upload speeds (100/20). Locations with service greater than 25/3 but are served with technology other than Cable and Fiber are also considered underserved.Participating counties may choose to prioritize certain geographic areas, within its county geographic boundaries, as areas to receive priority for CAB project deployments. Those counties that have prioritized certain locations for CAB applications will have those rankings listed in the "county_priority_rank" field in the data table with values of 1 being the highest priority locations, 2 being the next highest priority locations, and so on. Locations with a value of NULL have not been prioritized by the county. A county with all locations containing a value of NULL have either not become active projects or have not prioritized any areas in the respective county.

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File 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 2010 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 TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File 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 2010 Census blocks nest within every other 2010 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 Files are shapefiles and related database files (.dbf) that 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 File 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 2010 Census blocks nest within every other 2010 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.

Historical population as enumerated and corrected from 1790 through 2020. North Carolina was one of the 13 original States and by the time of the 1790 census had essentially its current boundaries. The Census is mandated by the United States Constitution and was first completed for 1790. The population has been counted every ten years hence, with some limitations. In 1790 census coverage included most of the State, except for areas in the west, parts of which were not enumerated until 1840. The population for 1810 includes Walton County, enumerated as part of Georgia although actually within North Carolina. Historical populations shown here reflect the population of the respective named county and not necessarily the population of the area of the county as it was defined for a particular census. County boundaries shown in maps reflect boundaries as defined in 2020. Historic boundaries for some counties may include additional geographic areas or may be smaller than the current geographic boundaries. Notes below list the county or counties with which the population of a currently defined county were enumerated historically (Current County: Population counted in). The current 100 counties have been in place since the 1920 Census, although some modifications to the county boundaries have occurred since that time. For historical county boundaries see: Atlas of Historical County Boundaries Project (newberry.org)County Notes: Note 1: Total for 1810 includes population (1,026) of Walton County, reported as a Georgia county but later determined to be situated in western North Carolina. Total for 1890 includes 2 Indians in prison, not reported by county. Note 2: Alexander: *Iredell, Burke, Wilkes. Note 3: Avery: *Caldwell, Mitchell, Watauga. Note 4: Buncombe: *Burke, Rutherford; see also note 22. Note 5: Caldwell: *Burke, Wilkes, Yancey. Note 6: Cleveland: *Rutherford, Lincoln. Note 7: Columbus: *Bladen, Brunswick. Note 8: Dare: *Tyrrell, Currituck, Hyde. Note 9: Hoke: *Cumberland, Robeson. Note 10: Jackson: *Macon, Haywood. Note 11: Lee: *Moore, Chatham. Note 12: Lenoir: *Dobbs (Greene); Craven. Note 13: McDowell: *Burke, Rutherford. Note 14: Madison: *Buncombe, Yancey. Note 15: Mitchell: *Yancey, Watauga. Note 16: Pamlico: *Craven, Beaufort. Note 17: Polk: *Rutherford, Henderson. Note 18: Swain: *Jackson, Macon. Note 19: Transylvania: *Henderson, Jackson. Note 20: Union: *Mecklenburg, Anson. Note 21: Vance: *Granville, Warren, Franklin. Note 22: Walton: Created in 1803 as a Georgia county and reported in 1810 as part of Georgia; abolished after a review of the State boundary determined that its area was located in North Carolina. By 1820 it was part of Buncombe County. Note 23: Watauga: *Ashe, Yancey, Wilkes; Burke. Note 24: Wilson: *Edgecombe, Nash, Wayne, Johnston. Note 25: Yancey: *Burke, Buncombe. Note 26: Alleghany: *Ashe. Note 27: Haywood: *Buncombe. Note 28: Henderson: *Buncombe. Note 29: Person: Caswell. Note 30: Clay: Cherokee. Note 31: Graham: Cherokee. Note 32: Harnett: Cumberland. Note 33: Macon: Haywood.

Note 34: Catawba: Lincoln. Note 35: Gaston: Lincoln. Note 36: Cabarrus: Mecklenburg.
Note 37: Stanly: Montgomery. Note 38: Pender: New Hanover. Note 39: Alamance: Orange.
Note 40: Durham: Orange, Wake. Note 41: Scotland: Richmond. Note 42: Davidson: Rowan. Note 43: Davie: Rowan.Note 44: Forsyth: Stokes. Note 45: Yadkin: Surry.
Note 46: Washington: Tyrrell.Note 47: Ashe: Wilkes. Part III. Population of Counties, Earliest Census to 1990The 1840 population of Person County, NC should be 9,790. The 1840 population of Perquimans County, NC should be 7,346.

The NC Center for Geographic Information and Analysis developed the GIS data set, Type A Future Public Water Systems, as mapped by contractors to the NC Rural Center (engineering firms McGill & Associates and Hobbs, Upchurch & Associates) during 2004, 2005, and 2006 to facilitate planning, siting and impact analysis in the 100 individual counties of North Carolina. This file enables the user to make various county-level determinations when used in conjunction with other data layers. "Future" in the title Type A Future Public Water Systems refers to system boundary the water system owner expects in 2010. The tabular data will be the same as it was for the current data.

The NC Center for Geographic Information and Analysis developed the GIS data set, Type A Future Public Sewer Systems, as mapped by contractors to the NC Rural Center (engineering firms McGill & Associates and Hobbs, Upchurch & Associates) during 2004, 2005, and 2006 to facilitate planning, siting and impact analysis in the 100 individual counties of North Carolina. This file enables the user to make various county-level determinations when used in conjunction with other data layers. "Future" in the title Type A Future Public Sewer Systems refers to system boundary the water system owner expects in 2010. The tabular data will be the same as it was for the current data.

The North Carolina Department of Environment, Health, and Natural Resources, Division of Environmental Management, in cooperation with the NC Center for Geographic Information and Analysis, developed the digital Water Supply Watersheds data to enhance planning, siting and impact analysis in areas directly affecting water supply intakes. This file outlines the extent of protected and critical areas and stream classifications for areas around water supply watersheds in which development directly affects a water supply intake. This file enables users to identify the areas which have special restrictions for building and development based on water supply intakes. This file is updated as changes occur.

This data was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS).

system filename: wsw Revisions and updates to this layer include:

18.) filename: wsw496 The April 1, 1996 update: A) The Upper Frech Broad River (Asheville) water supply watershed was moved from the proposed coverage to the adopted coverage. B) The Mills River (Asheville) water supply watershed was moved from the proposed coverage to the adopted coverage. C) The French Broad River water supply watershed was moved from the adopted coverage into the proposed coverage. These edits affect Buncombe and Henderson Counties. 17.) filename: wsw396 The March 6, 1996 update: A) The Reedy Fork critical area was changed to 'WS-III NSW' to match the protected area. This affected the Greensboro 100k tile area. B) The Belews Creek protected area was changed to 'WS-IV' to match the critical area. This affected the Winston-Salem 100k tile area. 16.) filename: wsw196 The January 25, 1996 update: A) Protected boundary was altered in the Long Creek (Little Tennessee) watershed. The watershed name was renamed to be Rock Creek (Little Tennessee). This affected the Robbinsville 24k quad. B) Protected boundary was altered in the South Fork Catawba River watershed. This affected the Banoke 24k quad. C) Addition of protected boundary for the Belews Creek watershed. This affected the Belews Creek 24k quad. D) Watersheds were deleted by request of DEM-Tranters Creek which was on the Rocky Mount & Plymouth 100k quads and Stokely Hollow which was on the Asheville 100k quad. E) Extensive changes to the actual boundaries of the watersheds throughout the state in an effort to have them coincident with the Hydrologic Units adopted earlier by EHNR-DEM and USDA-NRCS. Boundaries coincident in both coverages were deleted from the watershed file and copied back from the hydrologic units file. PREVIOUS TO THE 1/25/96 FILE, THIS FILE WAS NAMED: NC.WSW 15.) filname: nc.wsw695 The June 30, 1995 update: A) Protected and critical boundaries were altered in the Hiawassee River watershed. This affected the Mocksville, Peachtree, Marble, and Andrews 24k quads. B) The protected boundary was altered in the South Fork Catawba River watershed in Catawbaw and Lincoln Counties. The Banoak, Reepsville, and Maiden 24k quads were affected. C) The entire WSW area in Bear Creek was deleted in Davie County, affecting the Mocksville and Calahan 24k quads. D) Protected and critical boundaries were altered in the North Toe watershed in Avery and Mitchell counties. This affects the Carvers Gap, Newland, Spruce Pine, and Linville Falls 24k quads. 14.) filename: nc.wsw595 The May 4, 1995 update: an arc was deleted which divided the South Yadkin River-Cooleemee protected area. The change affects the area within the Cool Springs, Cooleemee, Calahan, and Mocksville 24k quads. 13.) filename: nc.wsw195 The January 13, 1995 update: A) A new boundary was added to the Hiawassee River (Murphy) in the Hiawassee River Basin. This addition split the existing watershed, and the western half was deleted. The change affects the Hayesville, Peachtree, and Murphy 24k quads. 12.) filename: nc.wsw1194 The November 4, 1994 update: A) The Smith River WSW, in the Roanoke river basin, had one of its boundaries altered. The change affects the Northeastern Eden 24k quad. 11.) filename: nc.wsw994 The September 13, 1994 update: A) The Lands Creek in the Little Tennessee River Basin in Swain County on the Fontana Lake 100k quad had the PAT attributes added. 10.) filename: nc.wsw894 The August 26, 1994 update consisted of the following watershed adoptions (additions). A) The Deep River in Lee County, in the Cape Fear River Basin. B) The Deep Creek in Swain County, in the Little Tennessee River Basin. C) The Yadkin River in Davie County, in the Yadkin River Basin. D.) The Yadkin River in King County, in the Yadkin River Basin, E) The South Yadkin River in Cooleemee City, in the Yadkin River Basin. 9.) filename: nc.wsw594 The May 18, 1994 update: A) The Tar River WSW within the Tar-Pamlico river basin was deleted. 8.) filename: nc.wsw494 The April 28, 1994 update: A) All proposed areas were removed from the data and are managed separately. Only amended areas are now reflected in this data. 7.) filename: nc.wsw194 The January 12, 1994 update: A) The Campbell Creek watershed in the French Broad river basin had the northern boundary moved. The edits affected the Dellwood 24k quad. B) The South Fork Catawba in the Catawba Watershed had its classification modified from WS-IV CA to WS-IV. C)The South Fork Catawba in the Catawba Watershed had its protected area reduced in size. The change affects the Banoak and Reepsville 24k quads. 6.) filename: nc.wsw102893 The October 28, 1993 update: A) The South Fork Catawba had previously had the protected area deleted. An additional portion of the boundary had been deleted, which was supposed to remain. The boundary was added back into the coverage. The affected maps were the 24k Maiden, Reepsville, Lincolnton West, Hickory, and Banoak, 100k quads were Hickory and Gastonia. 5.) filename: nc.wsw101593 The October 15, 1993 update: A) The northern protected area boundary for Clark Creek was deleted and the east and west critical area buffers were redigitized. Affected maps are the 24k Reepsville and Maiden and the Hickory 100k quad. 4.) filename: The September 8, 1993 update: A) The Little Tennessee River (Fontana Lake) protected area had the southeastern radius line removed, and had a northern ridgeline added. Affected maps are the 24k Fontana Dam and Tuskeegee quads, and the Fontana Lake 100k quad. 3.) filename: wsw193 The January 22, 1993 update: A) Cold Water Creek (Lake Fisher) in the Yadkin River Basin was changed from WS-III to WS-IV. 2.) filename: The November 17, 1992 update: A) Stokely Hollow, 100k Asheboro quad changed from WS-I to WS-II. B) Corrected location of Reddies River intake for the Yadkin river basin, Wilkesboro 24k, Boone 100k. C) Changed location of watershed boundary, intake, and critical area for the South Fork New River, New River Basin, Jefferson 24k, West Jefferson 24k Boone 100k. 1.) filename: nc.pcarv.old (protected/critical area with the same state lake as the .coe coverage, but this version was interpreted from USGS maps) filename: nc.pcarv.coe (protected/critical area with the Army Corp of Engineers version of a state lake) filename: nc.pcarv Previous to August 1992, this file was called Public Water Supply watersheds and only included WS-I, WS-II, WS-III classifications. filename: nc.pca filename: nc.pca2