This service provides the point dataset representing bridges and other structures, extracted and attributed by the NCDOT Bridge Maintenance Unit's bridge database. The bridge layer is a compilation of data originally found in the Bridge Inventory maps produced by the Mapping group of the State Road Maintenance Unit which has been supplemented with updates from the bridge database of the NCDOT's Bridge Maintenance Unit. This service includes points representing locations of the following structure types:BridgeFederal BridgeLarge PipeCulvertRailroad BridgeTunnelPedestrian WalkwayPedestrian UnderpassPedestrian BridgeCantilever SignOverhead SignT-Pole SignFerry RampPrivate StructureVehicular UnderpassMetadataThe metadata for the contained layer of the NCDOT Structures Service is available through the following link:NCDOT StructuresPoint 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 Structures 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-11-11 00:00:00

NCDOT 2024-2033 Transportation Improvement Program (STIP) Projects for Chatham CountyThis data is pulled from a NCDOT rest service (https://gis11.services.ncdot.gov/arcgis/rest/services/NCDOT_STIP/MapServer) This data was created as part of the Manager's Office Chatham County Performance Hub.

With more than 44,000 Portable Traffic Count (PTC) Stations located throughout North Carolina, Traffic Survey has adopted a collection schedule. Please see our website: https://www.ncdot.gov/projects/trafficsurvey/for further details. The data in this file was digitized referencing the available NCDOT Linear Referencing System (LRS) and is not the result of using GPS equipment in the field, nor latitude and longitude coordinates. The referencing provided is based on the 2015 Quarter 1 publication 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: CVRG_VLM_I: Traffic Survey's seven digit unique station identifier COUNTY: County NameROUTE: Numbered route identifier, or local name if not State maintainedLOCATION: Description of the Annual Average Daily Traffic station location AADT_2015: Estimated Annual Average Daily Traffic in vehicles per day for 2015AADT_2014: Estimated Annual Average Daily Traffic in vehicles per day for 2014AADT_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. With the exception of 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 814-5116. Disclaimer related to the spatial accuracy of this file: Data in this file was digitized referencing the available NCDOT GIS Data Layer, LRS Arcs Shapefile Format from Quarter 1 release and is not the result of using GPS equipment in the field.North Carolina Department of Transportation shall not be held liable for any errors in this data. This includes errors of omission, commission, errors concerning the content of data, and relative positional accuracy of the data. This data cannot be construed to be a legal document.

This map viewer identifies stormwater post-construction permitting authorities and requirements for development projects in NC. The contact is Bethany Georgoulias at bethany.georgoulias@ncdenr.gov or (919) 807-6372.

View what City-and-state planned roadway project(s) may be taking place near a specific property.

This feature layer spatially represents DriveNC//NCDOT’s TIMS incident data feed by Road Condition. The TIMS Incidents data contains the general location of and details about incidents that affect or will affect travel on roads maintained by the North Carolina Department of Transportation.This hosted feature layer view is intended for public viewing.NCDOT TIMS Incidents Points - Contains a point reference for all incidents, point and line.NCDOT TIMS Incidents Lines - Lines representing linear incidents. Generally, only select incidents types and road closed conditions will be represented as lines. A point feature will represent the same incident.This data includes all incidents including those recorded on concurrent routes. To remove these from the data, filter where "CreatedFromConcurrent = False".The data is provided through an automated routine that pulls data from the TIMS geojson feed every 5 minutes. Note that the data may disappear for a few moments while being refreshed.The feature layer contains all incidents; current and future. To only view current incidents in your web map, create a filter using the "StartDate" field. For example, filter by Start Date "in the last" 6 years. Note: DateTime fields are in UTC (as indicated in the field name). Text fields contain data/time values in Eastern Time.

Attributes/Fields:

Attribute/Field 


Description/Comments

Id

Unique Id of the Incident

Location

General description of the incident location.

Road

The road on which the incident occurred.

CommonName

Common name of the road on which the incident occurred or will occur

Direction

Direction of traffic impacted. Values include: North South East West All Inner Out

RouteType

Type of Route. Values include: Interstate US Route NC Route Secondary Road

RouteSuffix

Route Suffix. Values include: Alternate Business Bypass Connector Express Truck Toll

RouteId

NCDOT route id

City

Name of the nearest city to the incident.

CountyId

County number in which the incident occurred. Values from 1 to 100, where Alamance is 1 and Yancey is 100.

CountyName

Name of the county in which the incident occurred.

Division

Division number

EventId

Id of the Event designation. If the field is blank, the incident is not associated with an event.

EventName

Name of the Event designation. If the field is blank, the incident is not associated with an event.

Reason

Additional information about the incident.

IncidentType

Type of incident. Values include: Emergency Road Work Construction Night Time Construction Weekend Construction Maintenance Night Time Maintenance Road Obstruction Vehicle Crash Disabled Vehicle Congestion Signal Problem Weather Event Fog Fire Special Event Other Reported Incident

Severity

Severity of the incident. Values include: 1 = Low Impact 2 = Medium Impact 3 – High Impact

Condition

Road condition caused by the incident. Congestion Lane Closed Lane Shift Lanes Closed Lanes Narrowed Moving Closure Permanent Road Closure Ramp Closed Rest Area Closed Road Closed Road Impassable Shoulder Closed Lane Narrowed Ramp Lane Closed Ramp Lane Narrowed Road Closed with Detour

Detour

The detour or alternate route instructions

LanesClosed

The total number of lanes closed due to the incident

LanesTotal

The total number of lanes affected by the incident

DriveNCLink

Link to the DriveNC web page for the incident

StartDateUTC

Incident start date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate EST subtract 5 hours. To calculate EDT subtract 4 hours.

EndDateUTC

Incident end date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate subtract 5 hours. To calculate EDT subtract 4 hours.

LastUpdateDateUTC

Last update date/time in UTC. AGOL automatically adjust date/time to the local time zone. Calculate the time when used outside of AGOL. To calculate subtract 5 hours. To calculate EDT subtract 4 hours

TIMCCreationDateUTC

TIMS Creation date/time in UTC. Calculate the time when used outside of AGOL. To calculate EST subtract 5 hours.To calculate EDT subtract 4 hours

StartDateET

Incident Start Date in ET (EDT or EST).This is a text field suitable for display. Use the UTC fields for filtering on time.

StartTimeET

Incident Start Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

EndDateET

Incident End Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

EndTimeET

Incident End Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

LastUpdateDateET

Last Update Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

LastUpdateTimeET

Last Update Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

TIMSCreationDateET

TIMS Creation Date in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

TIMSCreationTimeET

TIMS Creation Time in ET (EDT or EST). This is a text field suitable for display. Use the UTC fields for filtering on time.

Latitude

Latitude

Longitude

Longitude

Note: Details about the incident are available through the NCDOT TIMS site. You can link directly to the incident details by combining https://tims.ncdot.gov/TIMS/IncidentDetail.aspx?id= and the TimsId/Incident ID. Note: The Last Modified and Created dates apply to this item entry in GO!NC/ArcGIS Online and may not reflect the actual dates of the data or map service itself.

The Developmentfeature service is a graphical depiction of development locations within Apex's jurisdiction that are proposed, approved, or under construction. A hyperlink is included for access to submitted plans. New developments are added at the beginning of each month. The status of each development is updated as the following benchmarks are met: Town of Apex Technical Review Committee approval, Town Council approval, and construction permit issuance. Developments are removed once certificates of occupancy are issued. Hyperlinked PDFs are updated with either the latest preliminary plans, approved plans, or signed construction drawings. The Apex Development Reportmay be referenced as a complementary resource.

This dataset is the 5 foot contour intervals for all of Buncombe County, NC. This data was created using a 20ft Digital Elevation Model (DEM). The DEMs were developed from Light Detection and Ranging (LIDAR) data acquired January though February through April 2003, with partial re-flights for gap data in December 2003. Cell values in the DEMs were derived from a Triangulated Irregular Network (TIN) produced from the bare earth mass points and breaklines. The dataset was provided to the Buncombe County by the NC Floodplain Mapping Project as pre-release data in July and Sept 2006 .Specific information about individual data tiles can be obtained at www.ncfloodmaps.comTo download the 5 foot contours go to https://www.buncombecounty.org/governing/depts/gis/download-digital-data.aspx

This feature service is for viewing Brownfields projects content and is updated continuously. This data set shows boundaries of Brownfields Projects that have entered into the program to receive a Brownfields Agreement. The boundaries and areas shown reflect the current status of the project in its progression towards having a recorded Notice of Brownfields Property with a finalized Brownfields Agreement. Additional web links are also provided to view corresponding online project documentation and to download compliance forms.

These data depict Road Segment Centerlines and attributes for roads that are managed and maintained by the National Park Service. Road data are used for many purposes including planning and management, mapping and condition assessment, routing and navigation, public information, emergency response, and research. A current, accurate representation of park roads is needed for national reporting and a variety of mapping requirements at all levels of the National Park Service and the general public. A National-level dataset allows the NPS to communicate a consistent and high-quality roads database to NPS staff, partners, visitors, and entities that produce maps and location-based services of park units. The collection, storage, and management of road-related data are important components of everyday business activities in many Federal and State land-managing agencies, road organizations, and businesses. From a management perspective, road data must often mesh closely with other types of infrastructure, resource, and facility enterprise data. For the public using paper maps, the internet, GPS or other instrumentation, standard data formats enable users to consistently and predictably identify specific trails and a core set of corresponding information. Today, digital road data are a necessity throughout a road data management life-cycle, from road planning through design, construction, operation, and maintenance. Automating, sharing, and leveraging road data through this widely accepted standard can provide a variety of important benefits: Efficiency – creating and gathering road data that are standardized and readily usable. Compatibility – compiling data from one project or discipline that can be compatible with other applications; Consistency – using the same standards, meshing data produced by one organization with that developed by another; Speed – hastening the availability of data through a reduction in duplicative efforts and lowered production costs (Applications can be developed more quickly and with more interoperability by using existing standards-compliant data); Conflict resolution – resolving conflicting road data more easily if compliant to the same standards; Reliability – improving the quality of shared road data by increasing the number of individuals who find and correct errors; and Reusability – allow maximum reuse across agencies and support objectives of EGovernment (E-Gov) initiatives and enterprise architecture.

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.

This dataset is the 20ft Digital Elevation Model (DEM) for all of Buncombe County, NC. The DEMs were developed from Light Detection and Ranging (LIDAR) data acquired January though February through April 2003, with partial re-flights for gap data in December 2003. Cell values in the DEMs were derived from a Triangulated Irregular Network (TIN) produced from the bare earth mass points and breaklines. The dataset was provided to the Buncombe County by the NC Floodplain Mapping Project as pre-release data in July and Sept 2006 .Specific information about individual data tiles can be obtained at www.ncfloodmaps.com

Data available for use in making maps and products related to Hurricane Florence.Esri is supporting organizations that are responding to hurricane/cyclone disasters with software, data, imagery, project services, and technical support. If you are in need of software or support, complete the Request Assistance form. All requests should be justified in the message section of the form and are subject to approval.

These data were automated to provide an accurate high-resolution historical shoreline of Onslow Bay, NC suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attributio...

Summary:

With funding from the Albemarle-Pamlico National Estuary Partnership (APNEP) and field and technical support from the NC Division of Marine Fisheries (NCDMF), digital data of coastal submerged aquatic vegetation (SAV) was mapped by APNEP for imagery years 2019-2020. In addition to its role as critical habitat for many aquatic fauna species, SAV is an important bio-indicator of environmental health because of its sensitivity to aquatic stressors. The ability to detect SAV is critical in understanding ecosystem health and effects of restoration and protection activities. Because SAV distribution, abundance, and density varies seasonally and annually in response to climatic variability, large-scale SAV changes may occur; thus, due to its dynamic nature, these data need to be continually updated as monitoring continues in the APNEP region.This is the third mapping effort led by APNEP to map the distribution, abundance, and change of SAV in North Carolina; the first and second efforts were mapped for imagery years 2006-2008 and 2012-2014, respectively (those data are also publicly available). Additional SAV mapping for NC coastal waters outside of the APNEP region were led by NCDMF for 2015 and 2021 (those data are also publicly available).

Purpose:

These data were created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS) and are intended for research or planning projects that will contribute to better protection for the ecological features involved. APNEP should be contacted prior to use of this dataset to ensure it is the most recent available.

Mapping Extent:

Visible SAV was mapped along the coast of North Carolina. This extent encompasses the high-salinity coastal zone that lies within the APNEP regional boundary (Hwy. 64 Bridge of Roanoke Sound south to Bogue Inlet).

Completeness Report:

These data represent the locations of visible SAV, as could be digitized from remotely-sensed imagery. A substantial portion of SAV beds remain invisible from remote sensing due to environmental factors above (e.g., haze and clouds), on (e.g., white caps), and below (e.g., turbidity) the water's surface.Imagery Acquisition:All imagery was collected with a Vexcel Ultracam Eagle (Mark 3). Aircraft height was 11,300 feet for a final imagery product with a 0.45-foot pixel size.Bogue Sound and Back Sound were collected on June 25, 2019 and May 16, 2020.Core Sound was collected on June 2, 2019 and May 16, 2020.Pamlico Sound from the Hwy. 64 bridge at Roanoke Sound south to Ocracoke Inlet was collected on June 14 and 15, 2019 and June 1, 2020.Onslow Bay, which is outside of the APNEP region and lies between Bogue Inlet and Mason Inlet, was collected on June 21, 2019.Map Digitization:The imagery was loaded into ArcGIS for manual on-screen digitizing using procedures described in Rohman and Monaco (2005). Digitizing scale was set between 1:1,500 and 1:3,000. Habitat boundaries were delineated around benthic habitat features (e.g., areas with visually discernible differences in color and texture patterns). The imagery was occasionally manipulated in terms of brightness, contrast, and color balance to enhance interpretability of subtle features and boundaries. The minimum mapping unit (MMU) is generally defined as the smallest feature (e.g., an individual SAV bed) or aggregate of features (e.g., SAV patches) that is delineated using a given source of imagery. For this study the MMU was approximately 0.2 ha, or in general patches that were at least 15 m across on their longest axis.IMPORTANT – Environmental conditions, including turbidity and cloud cover were determined to be insufficient for accurate delineation of 2019 imagery. Environmental conditions were also insufficient for accurate delineation of some imagery collected in 2020, specifically the mainland side of Core Sound from Marshallberg north to and including Cedar Island and the following areas of Pamlico Sound: Hatteras Island in the vicinity of Rollinson Channel (604 acres of uninterpretable imagery) and Old Rollinson Channel and Kings Channel (151 acres of uninterpretable imagery); Pea Island National Wildlife Refuge (multiple areas totaling 1,156 acres of uninterpretable imagery); spoil islands in the vicinity of Old House Channel (83 acres of uninterpretable imagery); and Roanoke Sound in the vicinity of Bodie Island Lighthouse (2,063 acres of uninterpretable imagery) and just north of Duck Island (140 acres of uninterpretable imagery). Thus, these areas are not included in this mapping project.

Attributes/Values:

CLASS: Type of classification for SAV polygonCONTINUOUS: A polygon with 70-100% SAV coveragePATCHY: A polygon with 5-70% SAV coverageACRES: SAV polygon area in acresHECTARES: SAV polygon area in hectares

Credits:

APNEP / NCDEQ / NCDMF / NCDOT

For more information, please view the metadata and visit the APNEP SAV Monitoring website.

These features represent Capital Improve Projects for Transportation that have been recently completed, currently funded, proposed by NCDOT, or planned for the future (both short and long term projects). These line features in this layer are only meant to represent location in a very basic sense, and are not necessarily tied to an official design extent. For more information please visit the Fuquay-Varina Transportation Projects web page; you will also find a web map linked there that shows this layer symbolized based on the categories mentioned above (recently completed, funded, etc).

The Transportation Improvement Program (TIP) is typically a seven-year funding document for highway, public transportation, bicycle, pedestrian, and rail projects. In this current TIP cycle, the North Carolina Department of Transportation (NCDOT) has developed the seven-year State TIP within a ten-year work program. Projects must be in the TIP in order to receive state or federal funding. Every two years, the Durham-Chapel Hill-Carrboro (DCHC) Metropolitan Planning Organization (MPO) works with local citizens, government officials, elected officials, and the North Carolina Department of Transportation to develop a TIP that is eventually adopted as part of the State TIP.

This map displays the highway capacity projects that are included in the Draft FY 2013-2023 TIP/work plan released by the MPO in October 2012. Bicycle, pedestrian, transit, and highway maintenance projects are not shown. Projects are classified by which phases are funded in the draft TIP: feasibility study only, right-of-way acquisition, and construction. The final TIP and State TIP are expected to be adopted in 2015.

This feature service is for viewing Brownfields projects content and is updated continuously. This data set shows Areas of Environmental Concern ("AEC") locations within Brownfields Project boundaries that have a recorded Notice of Brownfields Property or "NBP". The areas and locations shown in this feature set reflect those areas and locations identified on an NBP's associated recorded Plat map attached as Exhibit B to the Notice. However, please note that not all Brownfields Properties with a recorded NBP and Plat have an identified AEC within the Brownfields Property boundary.

EP21 SA4 Orthoimagery in Wilson, Wayne, Johnston, Sampson, and Bladen Counties, North Carolina captured during leaf-off conditions in early 2021, 6-inch ground resolution, is a public resource provided by North Carolina's Statewide Orthoimagery Program, supported by the NC 911 Board. The state program includes orthoimagery acquired between 2012 and 2020. The NC 911 Board funded the 2012 and 2013 acquisition as well as the statewide collection in 2010. The 2021 project is consistent with the Business Plan for Orthoimagery in North Carolina (https://ncgicc.net/Portals/3/documents/OrthoImageryBusinessPlan_NC_20101029.pdf) that recommends acquisition of one-fourth of the state (or 27 counties) per year in a four-year cycle. The products are orthoimagery in true color, 6-inch ground resolution in 5,000 by 5,000-foot tiles, in uncompressed and compressed formats, packaged by county for distribution and accessible through the NC OneMap Geospatial Portal. The project was managed by the NC Center for Geographic Information and Analysis (CGIA) in the NC OneMap framework of data access. CGIA collaborated with the NC Geodetic Survey, the NC Department of Transportation's Photogrammetry Unit, and the Land Records Management office in the Office of the Secretary of State to form a state team with expertise and experience in orthoimagery. Acquisition contractors were selected by a Qualifications-Based Selection process. In addition the Statewide Mapping Advisory Committee's Working Group for Orthophotography Planning provided technical advice. Images were collected with digital cameras in early 2021, image processing and quality control occurred through 2021, and products became available by mid-year 2021. Image services are accessible and data are downloadable through NC OneMap. The digital imagery for The EP21 SA4 area was acquired from January 29 to March 05, 2021. The orthophoto tile naming convention utilizes the NC statewide index and uses the following parameters:OF is the 2 digit product code, O=orthoimagery, F=Four Band (RGBIR)6io is the 3 digit pixel size for 6-inch imagery37 is the 2 digit NC ANSI (FIPS) code000 is the 3 digit alpha numeric custodian code, Code "000" represents state maintained data"00959502" is the map index number. It is an 8 digit SOS LRM numbering of the basic modular unit with millionth place digit.20190208 is the 8 digit date (YYYYMMDD) representing the starting flight date for the county0307R0 is the 4 digit data (MMDD) representing the ending flight date for the county followed by the revision number for that tile.Seamline polygons are also available in Shapefile format for the county. Each Shapefile contains the following fields: Study Area ID, Strip ID (flight line), Exposure ID, Date Flown.Technical reports were created across the project study area and include the following:Attachment C: Flight & Control Plan (shows maps, layouts & details for planned flight lines & survey control per study area)Attachment C-1: Control Surveys Rerport (shows final locations, descriptions & diagrams for survey ground control across the study area)Attachment D: Imagery Acquisition Compliance Report (provides flight acquisition maps, specifications & supporting documentation by AT block across the study area)Attachment E: Airborne GPS-IMU Post Processing & Aerotriangulation Report (provides flight details, state specification compliance table, software used, GPS-IMU summary tables, AT statistics and multiple supporting tables/files per AT block)In addition supporting documentation was created for each county and includes the following:Attachment F Report: Signed and Sealed Orthoimagery Delivery ReportAttachment G Report: Quality Review Issues and Resolutions ReportThis dataset was generated to provide a consistent reference map for base mapping and display in emergency 911 operations and GIS applications.The State of North Carolina and Wilson County shall not be held liable for any errors in this dataset, including visual content and positional accuracy of this imagery or image capture dates associated with the filename.

Summary:With funding from the Albemarle-Pamlico National Estuary Partnership (APNEP) and field and technical support from the NC Division of Marine Fisheries (NC-DMF) and the National Oceanic and Atmospheric Administration (NOAA) Beaufort Laboratory, digital data of coastal submerged aquatic vegetation (SAV) was mapped by APNEP and NOAA-Beaufort for imagery years 2012-2014. In addition to its role as critical habitat for many aquatic fauna species, SAV is an important bio-indicator of environmental health because of its sensitivity to aquatic stressors. The ability to detect SAV is critical in understanding ecosystem health and effects of restoration and protection activities. Because SAV distribution, abundance, and density varies seasonally and annually in response to climatic variability, large-scale SAV changes may occur; thus, due to its dynamic nature, these data need to be continually updated as monitoring continues in the APNEP region.This is the second mapping effort led by APNEP to map the distribution, abundance, and change of SAV in North Carolina; the first effort was mapped for imagery years 2006-2008 (those data are also publicly available).Purpose:These data were created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS) and are intended for research or planning projects that will contribute to better protection for the ecological features involved. APNEP should be contacted prior to use of this dataset to ensure and confirm its currency.Mapping Extent:Visible SAV was mapped along the coast of North Carolina. This extent encompasses the high-salinity coastal zone that lies within the APNEP regional boundary (Hwy. 64 Bridge of Roanoke Sound south to Bogue Inlet).Completeness Report:These data represent the locations of visible SAV, as could be digitized from remotely-sensed imagery. A substantial portion of SAV beds remain invisible from remote sensing due to environmental factors above (e.g., haze and clouds), on (e.g., white caps), and below (e.g., turbidity) the water's surface.Imagery Acquisition:All imagery was collected with Intergraphs Z/I Digital Mapping Camera (DMC). Aircraft height was 3,048 m for a final imagery product with a 0.3 m pixel size.Currituck Sound, North Carolina, and Back Bay, Virginia, were collected on October 12, 2012.Bogue Sound and Back Sound were collected on May 27, 2013.Pamlico Sound from the Hwy. 64 bridge at Roanoke Sound south to Ocracoke Inlet was collected on May 30, 2013.Core Sound was collected on July 1, 2014. Map Digitization:The imagery was loaded into ArcGIS for manual on-screen digitizing using procedures described in Rohman and Monaco (2005). Digitizing scale was set between 1:2,000 and 1:3,000. Habitat boundaries were delineated around benthic habitat features (e.g., areas with visually discernible differences in color and texture patterns). The scanned images were occasionally manipulated in terms of brightness, contrast and color balance to enhance interpretability of subtle features and boundaries. The minimum mapping unit (MMU) is generally defined as the smallest feature (e.g., an individual SAV bed) or aggregate of features (e.g., SAV patches) that is delineated using a given source of imagery. For this study the MMU was approximately 0.2 ha, or in general patches that were at least 15 m across on their longest axis.Environmental conditions, including turbidity and cloud cover were determined to be insufficient for accurate delineation of 2012 imagery from Currituck Sound and Back Bay and 2014 imagery of Core Sound; thus, these areas are not included in this mapping project.Attributes/Values:CLASS: Type of classification for SAV polygonCONTINUOUS: A polygon with 70-100% SAV coveragePATCHY: A polygon with 5-70% SAV coverageACRES: SAV polygon area in acresHECTARES: SAV polygon area in hectaresCredits:NCDEQ / APNEP / NCDMF / NCDOT / NOAAFor more information, please view the metadata and visit the APNEP SAV Monitoring website.