Shoreline Management Model v.5.1 - Preferred Shoreline Best Management Practices - Virginia

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator:
Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)
Publication_Date: 20181130
Title:
Shoreline Management Model v.5.1 - Preferred Shoreline Best Management Practices - Virginia
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Center for Coastal Resources Management. 2019. Shoreline Management Model, version 5.1. Center for Coastal Resources Management, Virginia Institute of Marine Science, College of William and Mary, Gloucester Point, Virginia.
Online_Linkage: https://www.vims.edu/ccrm/ccrmp/index.php
Description:
Abstract:
In 2011, the Virginia General Assembly adopted a policy into law that specifies living shorelines as the preferred management practice for erosion control in Virginia waters. In accordance with the law, the Commonwealth defines a living shoreline as ... "... a shoreline management practice that provides erosion control and water quality benefits; protects, restores or enhances natural shoreline habitat; and maintains coastal processes through the strategic placement of plants, stone, sand fill, and other structural and organic materials".The Center for Coastal Resources Management (CCRM) at the Virginia Institute of Marine Science (VIMS) has been developing tools for several years to guide local governments in shoreline management. In particular, they have focused on the use of ecologically preferred alternatives for erosion control and have conducted research into refining the appropriate uses for a large suite of possible treatments based on existing shoreline conditions. A series of Decision Trees were developed to determine shoreline best management practices when conducting onsite inspections. These were developed to support integrated guidance at the management and regulatory level.This body of work has been expanded and re-developed as a GIS spatial model known as the Shoreline Management Model (SMM) to determine appropriate shoreline best management practices from the desk-top using available spatial data and the decision tree logic. The assessment is conducted at parcel level scale but the output represents a reach based or cumulative approach to shoreline management. The variables used in the SMM include fetch, nearshore bathymetry, bank condition, bank height, marsh presence, beach presence, tree canopy presence, and permanent structures within the riparian zone. Version 5 adds existing shoreline erosion control structures, and the presence of submerged aquatic vegetation (SAV) to enhance the models capabilities for evaluating best management practices along shorelines that have already been hardened or where erosion control practices may impact SAV.Most appropriate for desk-top reviews, regulatory compliance and comprehensive planning, the recommendations derived from the SMM may be altered due to lot size, shoreline length along a single parcel, proximity of primary buildings to the shoreline, type of existing erosion control structures, land use practices, and local biota. The output of the SMM is delivered to the end user in two ways: interactive map viewer, and digital shape file.
Purpose:
To provide a recommended preferred approach for shoreline erosion control via a geospatial Shoreline Management Model that identifies where living shorelines are suitable.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 19980101
Ending_Date: 20170831
Currentness_Reference: ground condition and currentness of associated datasets.
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Unknown
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.491055
East_Bounding_Coordinate: -75.320864
North_Bounding_Coordinate: 38.919070
South_Bounding_Coordinate: 36.529093
Keywords:
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Categories
Theme_Keyword: environment
Theme_Keyword: elevation
Theme_Keyword: planningCadastre
Theme_Keyword: geoscientificInformation
Theme_Keyword: biota
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword:
Shoreline Management Model, Preferred Shoreline Best Management Practices, Living Shorelines, Shoreline Conditions, Shoreline Structures, Riparian Land Use, Shoreline Inventory, Erosion Control, Shoreline Treatments
Place:
Place_Keyword_Thesaurus: None
Place_Keyword:
Virginia, Chesapeake Bay, Accomack, Arlington, Caroline, Charles City, Chesterfield, City of Chesapeake, City of Colonial Heights, City of Fredericksburg, City of Hampton, City of Hopewell, City of Petersburg, City of Richmond, Essex, Fairfax, Gloucester, Hanover, Henrico, Isle of Wight, James City, King George, Kiing and Queen, King William, Lancaster, Mathews, Middlesex, New Kent, Newport News, Norfolk, Northampton, Northumberland, Poquoson, Portsmouth, Prince George, Prince William, Richmond, Spotsylvania, Stafford, Suffolk, Surry, Virginia Beach, Westmoreland, Williamsburg, York
Access_Constraints: None
Use_Constraints:
These data should be used to guide the decision making process on how best to manage an erosion problem. Recommendations are made without consideration of property length, ownership, or value. Treatment recommendations are based on models that utilize best available data which may not reflect the actual conditions present on the shoreline.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Virginia Institute of Marine Science
Contact_Person: Karinna Nunez
Contact_Address:
Address_Type: mailing and physical
Address: 1375 Greate Road, P.O. Box 1346
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Country: US
Contact_Voice_Telephone: (804) 684-7273
Contact_Electronic_Mail_Address: karinna@vims.edu
Data_Set_Credit:
Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science (VIMS),
Native_Data_Set_Environment: Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9270
Data_Quality_Information:
Logical_Consistency_Report:
Topology has been checked. There are no overlapping arcs. All arcs are greater than 1m in length.
Completeness_Report:
Shoreline coded for Riparian Land Use (RiparianLU) will have a shoreline best management practice recommendation listed in the SMMv5Class field and a definition listed in the SMMv5Def field. Note that shoreline inventory data collection and publication dates vary by locality and may not reflect the actual conditon present on the shoreline.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)
Publication_Date: 20151231
Title: Tidal Marsh Inventory
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Tidal Marsh Inventory information for individual counties can be found with the Shoreline Inventory: https://www.vims.edu/ccrm/research/inventory/virginia/index.php
Online_Linkage: https://www.vims.edu/ccrm/research/inventory/virginia/index.php
Type_of_Source_Media: None
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20090601
Ending_Date: 20180816
Source_Currentness_Reference:
Marsh boundaries are digitized from high resolution aerial imagery. Field collection of marsh data is primarily performed from a small shallow-draft vessel, navigating at slow speeds parallel to the shoreline. Data was collected during the summer from 2009 to 2018.
Source_Citation_Abbreviation: Tidal Marsh Inventory
Source_Contribution:
The Tidal Marsh Inventory is produced by the Comprehensive Coastal Inventory, Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. The Shoreline Management Model obtains marsh information from this source.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)
Title: Virginia Shoreline Fetch
Geospatial_Data_Presentation_Form: vector digital data
Type_of_Source_Media: None
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20070101
Ending_Date: 20170501
Source_Currentness_Reference:
Fetch uses the shoreline developed for the shoreline inventory. Shoreline is digitized using the most recent VBMP high resolution imagery available at the time of the inventory.
Source_Citation_Abbreviation: Virginia Shoreline Fetch
Source_Contribution:
Fetch data is an unpublished data source created by the Comprehensive Coastal Inventory, Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. This dataset provides information on shoreline exposure to potential wave energy via a distance model that measures distance to nearest shoreline along compass rose. Measurements are taken at 25 meter increments along the shoreline.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Center for Coastal Resources Management, Virginia Institute of Marine Science (VIMS)
Title: Virginia Digital Shoreline Inventories
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Each county has its own shoreline inventory. Please see <http://www.vims.edu/ccrm/research/inventory/virginia/index.php> for more information pertaining to the Shoreline Inventory for individual counties.
Online_Linkage: <http://www.vims.edu/ccrm/research/inventory/virginia/index.php>
Type_of_Source_Media: None
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20080606
Ending_Date: 20180816
Source_Currentness_Reference:
Each county has its own shoreline inventory. Between 2009 - 2015 shoreline inventoriy data was field collected by 2-3 person field crews using hand-held Trimble GeoExplorers GPS Units, while navigating by boat along the shoreline. Inventories published after 2015 are generated in the lab by viewing high resoultion imagery from the Virginia Base Mapping Program (VBMP), Bing maps, and Google Earth. Temporal period extent includes field days and aerial image dates.
Source_Citation_Abbreviation: Virginia Digital Shoreline Inventories
Source_Contribution:
The Shoreline Inventory is produced by the Comprehensive Coastal Inventory, Center for Coastal Resources Management at the Virginia Institute of Marine Science, Gloucester Point, Virginia. The inventory provides information on bank height, beach presence, and forested shoreline in addition to the location of shoreline structures such as riprap and bulkhead.
Source_Information:
Source_Citation:
Citation_Information:
Title: SAV Habitat 10 Years (2007-2016)
Other_Citation_Details:
King and Queen and King William Counties SMM used SAV data from 2015-2019.
Type_of_Source_Media: None
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20070523
Ending_Date: 20161117
Source_Currentness_Reference: Time period of SAV data.
Source_Citation_Abbreviation: SAV Habitat 10 Years (2007-2016)
Source_Contribution:
The most recent 10 years of SAV merged together to show SAV presence. This layer is unpublished. SAV data can be downloaded from the VIMS website https://www.vims.edu/research/units/programs/sav/reports/index.php
Source_Information:
Source_Citation:
Citation_Information:
Title: Virginia Base Map Program Imagery 2017
Other_Citation_Details: Basemap imagery used could be VBMP 2009, 2011, 2013, or 2017
Type_of_Source_Media: None
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20090501
Ending_Date: 20170501
Source_Currentness_Reference:
Virginia Base Map Program provides high resolution aerial imagery for the Commonealth of Virginia. The best aerial coverage for Virginia's coastal plain occur in the VBMP products for 2006/2007, 2009, 2011, 2013, and 2017.
Source_Citation_Abbreviation: Virginia Base Map Program Imagery 2017
Source_Contribution:
Virginia Base Map Program Imagery from the Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN) is used to locate permanent structures, confirm road location, and identify wide beaches.
Source_Information:
Source_Citation:
Citation_Information:
Publication_Date: 20150501
Title:
TIGER/Line Shapefile, {year}, county, {County Name}, VA, All Lines County-based Shapefile
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
The year of the TIGER/Line shapefile used for each county is the same as the year the county's Shoreline Management Model was first puplished.
Online_Linkage: https://www.census.gov/geo/maps-data/data/tiger-line.html
Type_of_Source_Media: None
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20100101
Ending_Date: 20180101
Source_Currentness_Reference:
The year of the TIGER/Line shapefile used for each county is the same as the year the county's Shoreline Management Model was first puplished.
Source_Citation_Abbreviation:
TIGER/Line Shapefile, {year}, county, {County Name}, VA, All Lines County-based Shapefile
Source_Contribution:
Roads are obtained from the U.S. Department of Commerce, U.S. Census Bureau, Geography Division. The most recent TIGER/Line shapefile for the county is used. This dataset provides the location of roads and rails near the shoreline.
Source_Information:
Source_Citation:
Citation_Information:
Publication_Date: 20060101
Title: Non-Jurisdictional Beach Assessment
Type_of_Source_Media: None
Source_Citation_Abbreviation: Non-Jurisdictional Beach Assessment
Source_Contribution:
Data from the Shoreline Studies Program, Virginia Institute of Marine Science, Gloucester Point, Virginia is used to identify wide beaches.
Source_Information:
Source_Citation:
Citation_Information:
Title: Virginia Building Footprints
Online_Linkage:
https://vgin.maps.arcgis.com/home/item.html?id=994d0afa44c046498f9774613671ce9a
Type_of_Source_Media: None
Source_Citation_Abbreviation: Virginia Building Footprints
Source_Contribution:
Building Footprints are obtained from VGIN. This layer is used to locate buildings near the shoreline.
Source_Information:
Type_of_Source_Media: None
Source_Contribution:
VIMS-CCRM Coastal Management Decision Tools created by the Center for Coastal Resources Management (CCRM), Virginia Institute of Marine Science, Gloucester Point, Virginia provides the framework for the GIS Shoreline Management Model. Online Linkage: https://www.vims.edu/ccrm/ccrmp/bmp/decision_tools/index.php
Source_Information:
Source_Citation:
Citation_Information:
Publication_Date: 19980101
Title: One and Two Meter Low Water Contours of the Chesapeake Bay
Type_of_Source_Media: None
Source_Citation_Abbreviation: One and Two Meter Low Water Contours of the Chesapeake Bay
Source_Contribution:
Shoreline Management Models processed prior to July 2016 used bathymetry that originated from the Special Projects Office of the National Ocean Service, NOAA. Beginning in July 2016, the USGS Seamless Topobathymetric Elevation Model for the Chesapeake Bay (2016) is used for bathymetry. The datasets provide the 1 meter bathymetric contour to delineate shallow water.
Process_Step:
Process_Description:
The shoreline must be visually scanned to determine if there are any man-made navigable canals. If there are, the corresponding shoreline is coded canal = 'Canal'. Sand spits are noted in the shoreline inventory. If a sand spit is present, then sandspit = 'Yes'. Forestshl is coded 'Yes' if the landuse is forested or if there is a wide (>100 feet) tree fringe. Processing dates: 2012 to present.
Process_Date: 20160205
Process_Step:
Process_Description:
All processing steps occur in ArcMap, ArcGIS version 10.x. Models have been created for use with each step, however after each model run, a manual check of the results is necessary for accuracy. The SHLINV coded shoreline serves as the base shoreline and contains information on bank height, presence of beach, and forest cover. All other data layer information is added to this shoreline. Shoreline created prior to mid 2015 is delineated along the water edge. After mid-2015, the shoreline is delineated as the upland interface (the interface between the upland and water or marsh). The one meter bathymetric contour is used to determine if the nearshore is suitable for marsh planting. If the 1 meter bathymetric contour is within 10 meters of the shoreline then the bathymetry field is coded as 'deep', otherwise it is coded as 'shallow'. Processing dates: 2012 to 2022.
Process_Date: 20160205
Process_Step:
Process_Description:
Tidal marsh presence is transferred from the polygon shapefile (TMI) to the linear shoreline shapefile. Processing dates: 2012 to 2022.
Process_Date: 20160205
Process_Step:
Process_Description:
All linear shoreline structures (except dilapidated bulkhead and jetty) from the SHLINV are added to the base shoreline. Offshore structures (groin, breakwater, marsh toe revetment) are listed under the field "offshorest". All other structures are listed under "Structure". Processing dates: 2012 to 2022.
Process_Date: 20160209
Process_Step:
Process_Description:
To add roads and permanent structures (physical structures near the shoreline that would prohibit bank grading), the shoreline is buffered based on 3 times the maximum height in the bank height category plus 20 feet. Tiger roads and rails are buffered according to road/rail type. The general rule is one lane = 12 ft and shoulder = 12 ft, rail lines = 30 ft, bike paths/walkways = 8 ft, vehicular trails = 12 ft with no shoulder. Where transportation buffers and shoreline buffers intersect, shoreline should be coded for roads. Imagery along the shoreline is inspected for any permanent structures (houses, swimming pools, sheds, etc) that are within the shoreline buffer. Shoreline is coded for permanent structures when encountered. Processing dates: 2012 - 2017 Beginning with the 2018 shoreline inventory localities, a new technique was used to transfer roads and building footprints to the base shoreline. Where transportation buffer and shoreline buffer intersect, the resulting polygon vertices are converted to points. The ArcGIS NEAR tool is used to find the shortest distance from the point to the shoreline, adding x,y coordinates, distance, and direction to the point attribute table. Points that have a near distance less than or equal to the bank buffer width are retained. Near_x & near_y coordinates are converted to points (these points overlay the shoreline). The POINTS TO LINE tool converts points with the same rd_id to individual lines. The lines are buffered and the IDENTITY tool is used to place the road coding on the shoreline. Building Footprints downloaded from VITA are used to help find Permanent Structures within the shoreline bank buffer. A similar technique (describe above) is used to code the shoreline for Permanent Structure. The shoreline is also visually inspected for any permanent structures (houses, swimming pools, sheds, etc) within the shoreline buffer, that may not have been captured by using building footprints. Shoreline is coded for permanent structures when encountered. Processing dates: 2018-2019
Process_Date: 20160218
Process_Step:
Process_Description:
The Shoreline Studies Program's beach layer (where available) is used to identify potential wide beaches. If the layer is unavailable, shoreline coded as beach is manually inspected with imagery in the background to determine if the area is a wide beach. A wide beach is a sandy beach with visible beach area above the regular tide. Processing dates: 2012 to 2022.
Process_Date: 20160218
Process_Step:
Process_Description:
A tributary designation is assigned to the shoreline. Shoreline on the main stem of rivers is coded as major tributary, while small creeks are coded as tidal creek. Processing dates: 2012 to 2022.
Process_Date: 20160222
Process_Step:
Process_Description:
The most recent 10 years of SAV data was combined to create an SAV "habitat" layer. Only SAV polygons with density greater than zero were coded as "sav". The polygons were dissolved on the "sav" field to create a general sav habitat layer. The shoreline is coded for SAV presence if SAV is within 30 ft of the shoreline.
Process_Date: 20181109
Process_Step:
Process_Description:
The classification for the preferred shoreline best management practices provide recommendations across defended and undefended shorelines. There are 11 classifications: 1. Non-Structural Living Shoreline 2. Plant Marsh with Sill 3. Groin Field with Beach Nourishment 4. Maintain Beach or Offshore Breakwater with Beach Nourishment 5. Revetment 6. Revetment/Bulkhead Toe Revetment 7. Highly Modified Area 8. Ecological Conflicts 9. Special Geomorphic Feature 10. No Action Needed 11. Land Use Management
Process_Date: 20190425
Process_Step:
Process_Description:
Fetch is determined by creating 16 arcs based on the compass rose, radiating from points evenly spaced every 25 meters along the shoreline. The average arc length over water is calculated for the NE, SE, SW, and NW quadrants. The quadrant with the longest average fetch distance determines the fetch for the associated shoreline arc segment. Fetch is classified as low = 0-0.5 mile, moderate = 0.5-2 miles, and high = > 2 miles. Fetch is re-analyzed onto 100 meter segments along the shoreline by determining the most common fetch classification within each 100 meter segment. Processing dates: 2012 to 2022.
Process_Date: 20190530
Process_Step:
Process_Description:
The shoreline is given one last check for missing coding, errors, etc. Arcs less than or equal to 1m are dissolved into the larger adjacent arc. Topology is check for dangles and overlaps, and corrections made. Shoreline Management Model v.5.1 - Preferred Shoreline Best Management Practices model is run and the shoreline is coded with treatment recommendations. The SMM model queries a variety of spatial data and presents the preferred approach for erosion control. General preferred shoreline best management practices are recommended for all stretches of shoreline. Forested shoreline, bank height, marsh presence, fetch, beach presence, SAV, nearshore water depth, and existing structures feed into the resulting recommendations. Processing dates: 2012 to 2022.
Process_Date: 20191008
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 182560
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: NAD 1983 UTM Zone 18N
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 0.9996
Longitude_of_Central_Meridian: -75.0
Latitude_of_Projection_Origin: 0.0
False_Easting: 500000.0
False_Northing: 0.0
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.0001
Ordinate_Resolution: 0.0001
Planar_Distance_Units: meter
Geodetic_Model:
Horizontal_Datum_Name: D North American 1983
Ellipsoid_Name: GRS 1980
Semi-major_Axis: 6378137.0
Denominator_of_Flattening_Ratio: 298.257222101
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: SMM_v5_1_Preferred_BMPs_Virginia_Final_utm18_Feb_2_2022
Entity_Type_Definition: Shoreline Management Model version 5.1 attributes
Entity_Type_Definition_Source: Processor
Attribute:
Attribute_Label: rd_pstruc
Attribute_Definition:
road or permanent structure is present within the shoreline buffer
Attribute_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition:
road or permanent structure is present within the shoreline buffer
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain:
a road or permanent structure is present (yes) within a certain distance of the shoreline
Attribute:
Attribute_Label: Structure
Attribute_Definition:
erosion control structure: riprap, bulkhead, unconventional, etc
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Riprap
Enumerated_Domain_Value_Definition:
Generally composed of large rock to withstand wave energy, riprap revetments are constructed along shores to protect eroding fastland.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Marina < 50 slips
Enumerated_Domain_Value_Definition:
Marinas are denoted as line features in the shoreline inventory. The infrastructure associated with the marina (e.g. bulkheading, docks, wharfs, etc) are not digitized individually. The survey estimates the number of slips within the marina and classifies marinas as those with less than 50 slips and those with more than 50 slips.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Bulkhead
Enumerated_Domain_Value_Definition:
Bulkheads are traditionally treated wood or steel “walls” constructed to offer protection from wave attack. More recently, plastics are being used in the construction. Bulkheads are vertical structures built slightly seaward of the problem area and backfilled with suitable fill material. They function like a retaining wall, as they are designed to retain upland soil, and prevent erosion of the bank from impinging waves.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Debris
Enumerated_Domain_Value_Definition:
Debris represents nonconforming materials and rubble dumped along the shoreline as shoreline protection. Debris can include tires, bricks, broken concrete rubble, and railroad ties as examples.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Marina > 50 slips
Enumerated_Domain_Value_Definition:
Marinas are denoted as line features in the shoreline inventory. The infrastructure associated with the marina (e.g. bulkheading, docks, wharfs, etc) are not digitized individually. The survey estimates the number of slips within the marina and classifies marinas as those with less than 50 slips and those with more than 50 slips.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Unconventional
Enumerated_Domain_Value_Definition:
Unconventional features represent segments along the shore where unconventional material has been placed to protect a section of shore.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain:
list of shoreline protection structures that occur on the shoreline
Attribute:
Attribute_Label: invPubYr
Attribute_Definition: shoreline inventory publication year
Attribute_Definition_Source: processor
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 2009
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2009: Mathews County and Westmoreland County
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2010
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2010: Alexandria, Fairfax, and Prince William
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2011
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2011: Hampton, and Northampton
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2012
Enumerated_Domain_Value_Definition: Shoreline Inventories Published in 2012: Virginia Beach
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2013
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2013: Charles City, Poquoson, Suffolk, and York
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2014
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2014: Gloucester, James City and Williamsburg, Newport News, Norfolk, and Northumberland
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2015
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2015: Lancaster and Middlesex Counties
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2016
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2016: Accomack County, City of Chesapeake, Prince George County and the City of Hopewell
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2017
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2017: Chesterfield and the Cities of Colonial Heights, Petersburg, and Richmond, City of Fredericksburg, Hanover County, Henrico County, Isle of Wight, King George, and Surry County
Enumerated_Domain_Value_Definition_Source: processor
Enumerated_Domain:
Enumerated_Domain_Value: 2018
Enumerated_Domain_Value_Definition:
Shoreline Inventories Published in 2018: Arlington, Caroline, Essex, New Kent, Richmond Counties
Enumerated_Domain_Value_Definition_Source: processor
Attribute:
Attribute_Label: marsh_all
Attribute_Definition: marsh is present or absent
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: no
Enumerated_Domain_Value_Definition: no marsh present
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: marsh present
Enumerated_Domain_Value_Definition: marsh is present
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: values can be "marsh present" or "no".
Attribute:
Attribute_Label: HEIGHT
Attribute_Definition:
Bank height is a visual inspection of the height of the bank from the base to the top. We estimate height from imagery, field inspection, videography or a combination of all three data sources. Bank height: 0-5 feet, 5-30 feet, or >30 feet.
Attribute_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: Bank height: 0-5 feet, 5-30 feet, or >30 feet.
Attribute:
Attribute_Label: tribs
Attribute_Definition:
shoreline is classified as tidal creek, major tributary, or bay front.
Attribute_Definition_Source: Shoreline Management Model
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: major tributary
Enumerated_Domain_Value_Definition:
large stream or river that drains into an estuary like Chesapeake Bay or the Atlantic Ocean.
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: tidal creek
Enumerated_Domain_Value_Definition:
small stream or river that is tidally influenced and drains into a major tributary, an estuary like Chesapeake Bay, or the Atlantic Ocean. A tidal creek has limited shoreline exposure to fetch > 2 miles.
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain:
shoreline is classified as being part of a tidal creek or a major tributary.
Attribute:
Attribute_Label: BarrierIsl
Attribute_Definition: Barrier Islands are found in Northampton County
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: Tree_Fring
Attribute_Definition:
When the dominant riparian land use is not forested, but a line of trees is maintained along the bank edge, the land use is noted to include a tree fringe. When the tree fringe is between 100 and 500 feet, it is considered a wide tree fringe. When the tree fringe is greater than 500 feet, it would be labled "forested" in land use.
Attribute_Definition_Source:
VIMS Shoreline & Tidal Marsh Inventory Glossary, Center for Coastal Resources Management
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Yes
Enumerated_Domain_Value_Definition: Tree fringe is present
Enumerated_Domain_Value_Definition_Source:
VIMS Shoreline & Tidal Marsh Inventory Glossary, Center for Coastal Resources Management
Enumerated_Domain:
Enumerated_Domain_Value: Yes w
Enumerated_Domain_Value_Definition: Tree fringe is between 100 -500 feet
Enumerated_Domain_Value_Definition_Source:
VIMS Shoreline & Tidal Marsh Inventory Glossary, Center for Coastal Resources Management
Attribute:
Attribute_Label: ShlType
Attribute_Definition: shoreline defended or undefended based on time of survey
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Undefended
Enumerated_Domain_Value_Definition:
shoreline is not defended by a structure listed in the "Structures" or "offshorest" attributes.
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Defended
Enumerated_Domain_Value_Definition:
Shoreline is protected by a structure listed in the "Structures" or "offshorest" attributes
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: shoreline is classified as defended or undefended
Attribute:
Attribute_Label: WideBeach
Attribute_Definition:
A wide beach is a sandy beach with visible beach area above the regular tide.
Attribute_Definition_Source: Shoreline Management Model
Attribute_Domain_Values:
Unrepresentable_Domain: wide beach is present (yes) or absent
Attribute:
Attribute_Label: forestshl
Attribute_Definition:
forested shoreline is "yes" if riparian land use is coded "forested" or Tree_fring = "Yes w"
Attribute_Definition_Source: author
Attribute_Domain_Values:
Unrepresentable_Domain:
forested shoreline is "yes" if riparian land use is coded "forested" or if tree fringe is wide.
Attribute:
Attribute_Label: PubYear
Attribute_Definition: Publication year of shoreline inventory
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: canal
Attribute_Definition: man-made navigable canal
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: canal
Enumerated_Domain_Value_Definition: man-made navigable canal is present
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: canal is present (canal) or absent
Attribute:
Attribute_Label: Shape_Length
Attribute_Definition: Length of feature in internal units.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: FIPSCode
Attribute_Definition:
Federal Information Processing Standard code for Virginia cities and counties. Same as FIPS but represented as a text field.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: SURVEYED
Attribute_Definition: Year data collected and/or updated
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: Exposure
Attribute_Definition:
from the shoreline exposure model. Fetch is determined by creating 16 arcs based on the compass rose, radiating from points evenly spaced along the shoreline. The average arc length over water is calculated for the NE, SE, SW, and NW quadrants. The quadrant with the longest average fetch distance determines the fetch for the associated shoreline arc segment. Arcs were aggregated into 100 meter segments and the most common fetch classification is used.
Attribute_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: moderate
Enumerated_Domain_Value_Definition: maximum average fetch is 0.5 - 2.0 miles
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model
Enumerated_Domain:
Enumerated_Domain_Value: low
Enumerated_Domain_Value_Definition: maximum average fetch is 0 - 0.5 mile
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model
Enumerated_Domain:
Enumerated_Domain_Value: high
Enumerated_Domain_Value_Definition: maximum average fetch is > 2 miles
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model
Attribute_Domain_Values:
Unrepresentable_Domain: Fetch values are represented by low, moderate, or high.
Attribute:
Attribute_Label: HiModArea
Attribute_Definition:
Highly Modified Area includes marinas, canals, paved riparian land use with roads adjacent to shoreline, and commercial or industrial areas with hardened shoreline.
Attribute_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Highly Modified Area
Enumerated_Domain_Value_Definition:
Highly Modified Area includes marinas, canals, paved riparian land use with roads adjacent to shoreline, and commercial or industrial areas with hardened shoreline.
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: a value used when processing the model
Attribute:
Attribute_Label: RiparianLU
Attribute_Definition:
current riparian land use: agriculture, bare, commercial, forested, grass, paved, residential, scrub-shrub
Attribute_Definition_Source: Shoreline Inventory
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Paved
Enumerated_Domain_Value_Definition:
Paved areas represent roads which run along the shore and generally are located at the top of the banks. Paved also includes parking areas such as parking at boat landing, or commercial facilities.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Residential
Enumerated_Domain_Value_Definition: Residential land use includes single and multi-family dwellings
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Grass
Enumerated_Domain_Value_Definition:
Grasslands include large unmanaged fields, managed grasslands adjacent to large estates, agriculture tracts reserved for pasture, and grazing. While a general rule of thumb will classify a tract as “grass” if a home sits behind a large tract of grass, a designation of “residential” may be made if there are similar tracts adjacent to each other. This designation can be determined using best professional judgment.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Bare
Enumerated_Domain_Value_Definition:
Land use defined as bare includes areas void of any vegetation or obvious land use. Bare areas include those that have been cleared for construction.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Agriculture
Enumerated_Domain_Value_Definition:
Land use defined as agricultural includes farm tracts that are cultivated and crop producing. This designation is not applicable for pastureland.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Forested
Enumerated_Domain_Value_Definition:
Forest cover includes deciduous, evergreen, and mixed forest stands greater than 18 feet high. The riparian zone is classified as forested if the tree stand extends at least 30 feet inland of the seaward limit of the riparian zone. If the forest cover is less than 30 feet wide from the shoreline than some other primary land use designation is made.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Commercial
Enumerated_Domain_Value_Definition:
Commercial is a land use classification denoting small commercial operations such as shops, restaurants, as well as campgrounds. These operations are not necessarily water dependent businesses.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Industrial
Enumerated_Domain_Value_Definition:
Industrial operations are larger commercial businesses and can include areas where power plants, pulp mills, refineries, etc, are in operations along the coast.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Scrub-shrub
Enumerated_Domain_Value_Definition:
Scrub-shrub is a land use class that includes trees less than 18 feet high, and is usually dominated by shrubs and bushy plants.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain:
current riparian land use: agriculture, bare, commercial, forested, grass, paved, residential, scrub-shrub, timbered
Attribute:
Attribute_Label: defended
Attribute_Definition: shoreline is defended by an erosion control structure
Attribute_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition:
shoreline is defended by an erosion control structure that is listed in the attributes "Structures" and "offshorest"
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute:
Attribute_Label: shoreline
Attribute_Definition:
Shoreline is digitized while viewing high resolution imagery as the background layer. This field indicates the date of the Virginia Base Map Program (VBMP) imagery used.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: PublicRamp
Attribute_Definition: Paved Public Ramp is present
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
Federal Information Processing Standards (FIPS) are numeric codes assigned by the National Institute of Standards and Technology (NIST).
Attribute_Definition_Source: ESRI
Attribute:
Attribute_Label: bathymetry
Attribute_Definition: water depth
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: shallow
Enumerated_Domain_Value_Definition: 1 m bathymetric contour is greater than 10 m from shoreline
Enumerated_Domain_Value_Definition_Source: author
Enumerated_Domain:
Enumerated_Domain_Value: deep
Enumerated_Domain_Value_Definition: 1 meter bathymetric contour is within 10 m of shoreline
Enumerated_Domain_Value_Definition_Source: author
Attribute_Domain_Values:
Unrepresentable_Domain:
water depth is classified as either deep or shallow for use in the model.
Attribute:
Attribute_Label: SAV
Attribute_Definition:
Indicates if Submerged Aquatic Vegetation (SAV ) is present within 30 feet of the shoreline. A 10 year composite of SAV presence is used.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: SandSpit
Attribute_Definition:
A narrow coastal landform tied to the upland shoreline at one end resulting from the deposition of sand moved by tides and currents. Spit features are generally sandy and may be dominated by beach, dune, and/or marsh habitats. For inventory purposes, this definition does not include spit features that are developed or have developable upland.
Attribute_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: Sandspit is present ("yes") or absent.
Attribute:
Attribute_Label: Inventory
Attribute_Definition:
Yesr of shoreline inventory or description of imagery used to create the shoreline inventory.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: COVER
Attribute_Definition:
Bank cover is a classification based on a visual inspection of the bank. “Cover” can include either vegetative or structural cover.
Attribute_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: total
Enumerated_Domain_Value_Definition: > 75% vegetative/structural cover
Enumerated_Domain_Value_Definition_Source:
Shoreline Inventory definition, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: partial
Enumerated_Domain_Value_Definition: 25-75% vegetative/structural cover
Enumerated_Domain_Value_Definition_Source:
Shoreline Inventory definition, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: bare
Enumerated_Domain_Value_Definition: < 25% vegetative/structural cover
Enumerated_Domain_Value_Definition_Source:
Shoreline Inventory definition, Center for Coastal Resources Management, VIMS
Attribute:
Attribute_Label: BEACH
Attribute_Definition:
Beaches are persistent sandy shores that are visible during high tides. These features can be wide or thin lenses of sand. Beaches are coded as linear features at the wet/dry line to portray their location only. If a beach does not have a visible wet/dry line, then the line feature is located at the seaward edge of the beach. ‘Wide’ beaches have at least 10 feet of dry sand persistently visible above high tides. Beach features coded along tidal marsh shorelines are persistent, sandy features located on the water side of tidal marsh vegetation. Sand washed into tidal marshes is not coded as a beach if the marsh vegetation &/or marsh edge is still clearly visible. This classification of beaches along tidal marsh shorelines can include professional judgment.
Attribute_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Yes
Enumerated_Domain_Value_Definition: beach is present
Enumerated_Domain_Value_Definition_Source:
Shoreline Inventory definition, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: No
Enumerated_Domain_Value_Definition: beach is not present
Enumerated_Domain_Value_Definition_Source:
Shoreline Inventory definition, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: beach is either present (yes) or absent
Attribute:
Attribute_Label: roads
Attribute_Definition: roads are present within shoreline buffer
Attribute_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain: roads are present (roads) or absent
Attribute:
Attribute_Label: PermStruc
Attribute_Definition:
permanent structures (houses, swimming pools, etc) are within the shoreline buffer
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Permanent Structure
Enumerated_Domain_Value_Definition:
permanent structures (houses, swimming pools, etc) are within the shoreline buffer
Enumerated_Domain_Value_Definition_Source:
Shoreline Management Model, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain:
permanent structures (permanent structure) are present or absent
Attribute:
Attribute_Label: cntyName
Attribute_Definition: Virginia county or city name.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: FetchUpdat
Attribute_Definition:
Fetch calculation based on the most common fetch classification within a 100 meter arc segment. (Original fetch was calulated every 25 meters.)
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: PrevExpo
Attribute_Definition:
Fetch calculation based on one point within a 100 meter arc segment.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: bnk_height
Attribute_Definition: bank height: 0-5 feet, 5-30 feet, or >30 feet
Attribute_Definition_Source: author
Attribute_Domain_Values:
Unrepresentable_Domain: bank height: 0-5 feet, 5-30 feet, or >30 feet
Attribute:
Attribute_Label: lowBnkStrc
Attribute_Definition:
Shoreline has a low bank height (0-5 ft) and there is a road or permanent structure present that might impede bank grading.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: StrucList
Attribute_Definition: list of shoreline structures present
Attribute_Definition_Source: author
Attribute_Domain_Values:
Unrepresentable_Domain:
combines the structures listed in the "Structure" and "offshorest" attributes into one attribute list
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: County
Attribute_Definition: Virginia county or city name.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: offshorest
Attribute_Definition:
offshore erosion control structure: breakwater, groins, marsh toe revetment.
Attribute_Definition_Source: author
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Groins
Enumerated_Domain_Value_Definition:
Groins are low profile structures that sit perpendicular to the shore. They are generally positioned at, or slightly above, the mean low water line. They can be constructed of rock, timber, or concrete. They are frequently set in a series known as a groinfield, which may extend along a stretch of shoreline for some distance. Unless only a single groin can be detected, this inventory does not delineate individual groins in a groinfield. The groinfield is mapped as one linear feature parallel to the shoreline running along the length of the groin series.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Marsh Toe
Enumerated_Domain_Value_Definition:
A marsh toe revetment is a low profile revetment, typically constructed of stone, placed along the eroding edge of an existing tidal marsh.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Breakwater
Enumerated_Domain_Value_Definition:
Breakwaters are structures that sit parallel to the shore, and generally occur in a series along the shore. Their purpose is to attenuate and deflect incoming wave energy, protecting the fastland behind the structure. The Shoreline Inventory does not map individual breakwaters. A breakwater “system” is delineated and depicted as a line parallel to the series of breakwaters.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Unrepresentable_Domain:
list of shoreline protection structures that commonly extend into the water.
Attribute:
Attribute_Label: SMMv5Class
Attribute_Definition: Revised SMM v5.1 preferred shoreline BMP classifications
Attribute_Definition_Source: processor
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Non-Structural Living Shoreline
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
Remove existing shoreline structure if present; grade bank if necessary and install a non-structural living shoreline which may include riparian buffer planting along the bank, and/or marsh plants, coir logs, or oyster reefs along the shoreline. Best choice for low energy environments.
Enumerated_Domain:
Enumerated_Domain_Value: Plant Marsh with Sill
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
In moderate energy environments a sill may be required to establish a living shoreline. Remove any existing shoreline structure if present and grade the bank if possible. Stabilize bank with riparian vegetation and plant a marsh with a sill. If the bank cannot be graded, repair existing shoreline structure with a minimal footprint and consider incorporating a marsh with a sill or some other shoreline enhancement (e.g. oyster castles).
Enumerated_Domain:
Enumerated_Domain_Value: Groin Field with Beach Nourishment
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
Maintain existing wide beach between groins. Remove unnecessary structures at the backshore (e.g. bulkheads) and stabilize the bank with grading and riparian plants. Repair/replace existing groins, add beach nourishment and plant beach vegetation.
Enumerated_Domain:
Enumerated_Domain_Value: Maintain Beach or Offshore Breakwater with Beach Nourishment
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
If shoreline exceeds 200 feet in length, remove existing shoreline structure, add beach nourishment sand, consider offshore breakwaters or another type of wave attenuation device with beach nourishment; consider adding plantings to the nourished areas. When the shoreline length is less than 200 feet an offshore breakwater may not be practical. In this case, remove failed shoreline structures and repair or construct a revetment as far landward as possible. Consider shoreline enhancement such as creation of vegetated wetlands and/or riparian buffer and/or sandy beach/dune above and immediately channelward of the structure.
Enumerated_Domain:
Enumerated_Domain_Value: Revetment
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
Remove existing failing or failed shoreline structure, if present. Construct new revetment as far landward as possible; grade the bank and plant vegetation buffers where possible. If grading is not possible, construct or repair existing revetment in the same alignment. A bulkhead should be considered only if previously present and the site is limited by navigation. Consider shoreline enhancement such as creation of vegetated wetlands and/or riparian buffer and/or sandy beach/dune above and immediately channelward of the structure. In high energy settings where shoreline extends more than 200 feet see option for Offshore Breakwater with Beach Nourishment.
Enumerated_Domain:
Enumerated_Domain_Value: Revetment/Bulkhead Toe Revetment
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
If grading is possible, remove the failed bulkhead and replace with a revetment landward of the current bulkhead. When grading not possible, (re)construct bulkhead in the same alignment and/or add a toe revetment. Consider a shoreline enhancement project such as creation of vegetated wetlands and/or riparian buffer and/or sandy beach/dune above and immediately channelward of the structure.
Enumerated_Domain:
Enumerated_Domain_Value: Highly Modified Area
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
Management options for this shoreline may be limited due to the presence of highly developed upland (e.g. commercial wharfs) or infrastructure directly adjacent to the shoreline (e.g. road) and will depend on the need for and limitations posed by navigation access and erosion control. Seek expert advice on the design of your project.
Enumerated_Domain:
Enumerated_Domain_Value: Ecological Conflicts
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
Management options for this shoreline may be limited by the presence of Submerged Aquatic Vegetation (SAV) or Mangroves (Florida and Gulf coast shorelines). For Virginia shorelines, seek advice from the Virginia Marine Resources Commission Habitat Management Division <http://www.mrc.virginia.gov/>. If you live in another state, seek advice from your local marine regulatory agency.
Enumerated_Domain:
Enumerated_Domain_Value: Special Geomorphic Feature
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
Maintain the natural condition of this shoreline to allow for unimpeded sediment movement and the corresponding response of wetlands, beach and/or dune. If primary structures are present and threatened, seek expert advice on the design of your project.
Enumerated_Domain:
Enumerated_Domain_Value: No Action Needed
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Enumerated_Domain_Value_Definition:
No specific management actions are suitable for shoreline protection, e.g. boat ramps, undeveloped marsh, and barrier islands.
Enumerated_Domain:
Enumerated_Domain_Value: Land Use Management. Seek expert advice
Enumerated_Domain_Value_Definition:
Shorelines with tall banks greater than 30 feet limit possible solutions to address bank erosion. Forces other than tidal erosion, such as over-land runoff, upland development, and vegetation management are likely also having effect on bank conditions. Assessment of all factors and modifications to address causes for bank erosion are recommended. This may include changes to vegetation management, implementation of projects to address storm water, relocating buildings, utilities, and other infrastructure. All new construction should be located 100 feet or more from the top of bank. Actions may also include requesting zoning variances for relief from setback and other land use requirements or restrictions that may increase erosion risk. Seek expert advice to inform management options.
Enumerated_Domain_Value_Definition_Source: Shoreline Management Model v5.1 Glossary
Attribute:
Attribute_Label: SMMv5Def
Attribute_Definition:
Definitions for the preferred shoreline BMPs listed in the SMMv5Class field.
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: DefDate
Attribute_Definition: Date of SMMv5Def update
Attribute_Definition_Source: processor
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Metadata_Reference_Information:
Metadata_Date: 20220204
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Comprehensive Coastal Inventory Program, Center for Coastal Resources Management, Virginia Institute of Marine Science
Contact_Person: Tamia Rudnicky
Contact_Address:
Address_Type: mailing
Address: P.O. Box 1346
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Country: US
Contact_Voice_Telephone: (804) 684-7181
Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Generated by mp version 2.9.12 on Fri Feb 04 11:29:58 2022