5 datasets found
  1. d

    USGS NED 1/3 arc-second Contours for Winston-Salem E, North Carolina...

    • datadiscoverystudio.org
    shapefile
    Updated May 1, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Geological Survey, National Geospatial Program (2015). USGS NED 1/3 arc-second Contours for Winston-Salem E, North Carolina 20150501 1 x 1 degree Shapefile [Dataset]. http://datadiscoverystudio.org/geoportal/rest/metadata/item/95dcc39263c64e49bc98c7ef9089f041/html
    Explore at:
    shapefile(135.789503)Available download formats
    Dataset updated
    May 1, 2015
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Area covered
    Description

    These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.

  2. n

    North Carolina Water Supply Watersheds

    • cmr.earthdata.nasa.gov
    Updated Apr 21, 2017
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2017). North Carolina Water Supply Watersheds [Dataset]. https://cmr.earthdata.nasa.gov/search/concepts/C1214613212-SCIOPS
    Explore at:
    Dataset updated
    Apr 21, 2017
    Time period covered
    Aug 1, 1992 - Apr 1, 1996
    Area covered
    Description

    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

  3. n

    North Carolina Effective Flood Zones

    • nconemap.gov
    • hub.arcgis.com
    • +1more
    Updated May 6, 2019
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    State of North Carolina - Emergency Management (2019). North Carolina Effective Flood Zones [Dataset]. https://www.nconemap.gov/maps/a178aae74ee347d786e853e5a442eea2
    Explore at:
    Dataset updated
    May 6, 2019
    Dataset authored and provided by
    State of North Carolina - Emergency Management
    Area covered
    Description

    North Carolina Effective Flood zones: In 2000, the Federal Emergency Management Agency (FEMA) designated North Carolina a Cooperating Technical Partner State, formalizing an agreement between FEMA and the State to modernize flood maps. This partnership resulted in creation of the North Carolina Floodplain Mapping Program (NCFMP). As a CTS, the State assumed primary ownership and responsibility of the Flood Insurance Rate Maps (FIRMs) for all North Carolina communities as part of the National Flood Insurance Program (NFIP). This project includes conducting flood hazard analyses and producing updated, Digital Flood Insurance Rate Maps (DFIRMs). Floodplain management is a process that aims to achieve reduced losses due to flooding. It takes on many forms, but is realized through a series of federal, state, and local programs and regulations, in concert with industry practice, to identify flood risk, implement methods to protect man-made development from flooding, and protect the natural and beneficial functions of floodplains. FIRMs are the primary tool for state and local governments to mitigate areas of flooding. Individual county databases can be downloaded from https://fris.nc.gov Updated Jan 17th, 2025.

  4. n

    NCDOT State Maintained Roads

    • nconemap.gov
    • hub.arcgis.com
    Updated Dec 6, 2013
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    North Carolina Department of Transportation (2013). NCDOT State Maintained Roads [Dataset]. https://www.nconemap.gov/maps/157dbc4ef33f4db4aa1ecc1a3182a375
    Explore at:
    Dataset updated
    Dec 6, 2013
    Dataset authored and provided by
    North Carolina Department of Transportation
    Area covered
    Description

    This service provides a quarterly snapshot of the North Carolina state-maintained road network centerlines. Here, the route network is divided into three layers with symbolized Route Classifications listed below.State Maintained RoadsInterstateUS RouteNC RouteSecondary RouteRampsRest AreasOther State Agency RouteState Maintained Roads - Primary RoadsInterstateUS RouteNC RouteState Maintained Roads - InterstatesInterstateNorth Carolina’s route network is comprised of Interstate, US, NC, Secondary Roads, Ramps, and non-state maintained and projected roads required for federal reporting purposes. Route attributes include Route Class, Route Qualifier, Route Inventory, Route Number, Route Name, and County name. The Route ID attribute is an 11-digit composite route number, the identifier for the Dominant Route. It uniquely identifies routes statewide and should be used as the route identifier when performing LRS analysis using route/milepost referencing.NCDOT adopted the road centerline based Linear Reference System (LRS) Network as it’s official Enterprise LRS, to which multiple road inventory attributes are referenced along measured routes throughout North Carolina. These routes are classified as either System or Non-System routes. System routes are routes within the state-maintained road network, and are comprised of Interstates, US Routes, NC Routes, Secondary Routes, Ramps, and Non-System Routes. Non-System routes are routes that are typically not maintained by NCDOT, but instead by a local agency (county, city or MPO/RPO). The local agency is the source for updating these Non-System routes in NCDOT’s LRS. The collection of routes, System and Non-System, is the NCDOT LRS Network referred to as MilePoint.MetadataThe metadata for the contained layers of the NCDOT State Maintained Roads service is available through the following links:NCDOT Route ArcsPoint 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 Maintained Roads data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product TeamLastUpdated: 2024-01-01 00:00:00

  5. a

    NCDOT AADT Stations

    • hub-onslow.opendata.arcgis.com
    • hub.arcgis.com
    Updated Jan 14, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Onslow County GIS (2021). NCDOT AADT Stations [Dataset]. https://hub-onslow.opendata.arcgis.com/maps/onslow::ncdot-aadt-stations
    Explore at:
    Dataset updated
    Jan 14, 2021
    Dataset authored and provided by
    Onslow County GIS
    Area covered
    Description

    The AADT file is a station point location of Annual Average Daily Traffic (AADT) estimates. This includes the data submitted to FHWA for Highway Performance Monitoring System (HPMS) AADT reporting for 2021. Data are reported for AADT on all highways with a Functional Classification (FC) above Local. A full coverage is provided for these routes where AADT segmentation is based on network configuration, travel patterns, and land use. The extent of highway this AADT represents has not been determined. An AADT is an Annual Average Daily Traffic volume for all lanes in both directions passing a point on the highway system. It represents the average of all days during the year with typical traffic conditions. An AADT estimate is generated using procedures that comply with the standards specified in the Traffic Monitoring Guide published by the Federal Highway Administration. There are over 44,000 AADT stations that provide traffic data history from 2002 to the current year. With these collection locations, Traffic Survey has adopted the following data collection schedule: Interstate route volumes are collected on an annual basis; US and NC route volumes are also collected on an annual basis except for stations that fall within the off-cycle urban areas. (See urban area cycle below.) Secondary Road (SR) volumes are collected on a biennial cycle with approximately half being counted each year. If a particular secondary road is not available for the most current year, it may be available for the prior year. North Carolina's eighteen largest urban areas are counted on a biennial cycle with 10 urban areas counted during the even years, and 8 urban areas counted during the odd years. The following urban areas are collected during the even year cycle: Asheville, Charlotte, Concord-Kannapolis, Fayetteville, Gastonia, Goldsboro, Greenville, and Jacksonville. The following urban areas are collected during the odd year cycle: Burlington, Chapel Hill, Durham, Greensboro, Hickory, High Point, Raleigh, Rocky Mount, Wilmington, and Winston-Salem. Data in this file derives from NCDOT Roads & Highways, Quarter 1 publication of the current calendar year. The referencing provided is based on the 2022 Quarter1publication of the NCDOT Linear Referencing System (LRS). Some differences will be found when using different quarterly publications with this data set. The data provided is seasonally factored to an estimate of an annual average of daily traffic. The statistics provided are Location_ID - 10-digit unique count location identifier, ROUTE: Numbered route identifier, or local name if not State maintained, LOCATION: Description of the Annual Average Daily Traffic station location. AADT 2021: Estimated Annual Average Daily Traffic in vehicles per day for 2021 AADT_2018: Estimated Annual Average Daily Traffic in vehicles per day for 2018 AADT_2017: Estimated Annual Average Daily Traffic in vehicles per day for 2017 AADT_2016: Estimated Annual Average Daily Traffic in vehicles per day for 2016 AADT_2015: Estimated Annual Average Daily Traffic in vehicles per day for 2015 AADT_2014: Estimated Annual Average Daily Traffic in vehicles per day for 2014 AADT_2013: Estimated Annual Average Daily Traffic in vehicles per day for 2013 AADT_2012: Estimated Annual Average Daily Traffic in vehicles per day for 2012 AADT_2011: Estimated Annual Average Daily Traffic in vehicles per day for 2011 AADT_2010: Estimated Annual Average Daily Traffic in vehicles per day for 2010 AADT_2009: Estimated Annual Average Daily Traffic in vehicles per day for 2009 AADT_2008: Estimated Annual Average Daily Traffic in vehicles per day for 2008 AADT_2007: Estimated Annual Average Daily Traffic in vehicles per day for 2007 AADT_2006: Estimated Annual Average Daily Traffic in vehicles per day for 2006 AADT_2005: Estimated Annual Average Daily Traffic in vehicles per day for 2005 AADT_2004: Estimated Annual Average Daily Traffic in vehicles per day for 2004 AADT_2003: Estimated Annual Average Daily Traffic in vehicles per day for 2003 AADT_2002: Estimated Annual Average Daily Traffic in vehicles per day for 2002 Note: A value of zero in the AADT field indicates no available AADT data for that year. Please note the following: Not ALL roads have PTC stations located on them. Except for Interstate, NC and US routes, NCDOT County Maps refer to roads using a four-digit Secondary Road Number, not a road’s local name. If additional information is needed, or an issue with the data is identified, please contact the Traffic Survey Group at (919) 707-0936. Disclaimer related to the spatial accuracy of this file: This data cannot be construed to be a legal document.

  6. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
U.S. Geological Survey, National Geospatial Program (2015). USGS NED 1/3 arc-second Contours for Winston-Salem E, North Carolina 20150501 1 x 1 degree Shapefile [Dataset]. http://datadiscoverystudio.org/geoportal/rest/metadata/item/95dcc39263c64e49bc98c7ef9089f041/html

USGS NED 1/3 arc-second Contours for Winston-Salem E, North Carolina 20150501 1 x 1 degree Shapefile

Explore at:
shapefile(135.789503)Available download formats
Dataset updated
May 1, 2015
Dataset provided by
United States Geological Surveyhttp://www.usgs.gov/
Area covered
Description

These vector contour lines are derived from the 3D Elevation Program using automated and semi-automated processes. They were created to support 1:24,000-scale topographic map products, but are also published in this GIS vector format. Contour intervals are assigned by 7.5-minute quadrangle, so this vector dataset is not visually seamless across quadrangle boundaries. The vector lines have elevation attributes (in feet above mean sea level on NAVD88), but this dataset does not carry line symbols or annotation.

Search
Clear search
Close search
Google apps
Main menu