Virginia Shoreline Inventory (2006-2019): Access Structures

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator:
Comprehensive Coastal Inventory, Virginia Institute of Marine Science
Publication_Date: 20130101
Title: Virginia Shoreline Inventory (2006-2019): Access Structures
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details:
Center for Coastal Resources Management. 2019. Virginia Shoreline Inventory Database. Center for Coastal Resources Management, Virginia Institute of Marine Science, College of William and Mary, Gloucester Point, Virginia. Retrieved from <http://www.vims.edu/ccrm/research/inventory/index.php>
Online_Linkage: <http://www.vims.edu/ccrm/research/inventory/virginia/index.php>
Description:
Abstract:
Shoreline Situation Reports (SSR) were first generated by VIMS in the 1970's to report the condition and status of the shore lands. The SSR series were published in hardcopy on a county by county basis for each Tidewater Virginia localities. The reports were intended to assist planners, managers, and regulators in decisions pertaining to management of coastal areas and natural resources therein. This Shoreline Inventory report continues a process which updates and expands the earlier reports. Data collected reports conditions surveyed in the immediate riparian zone, the bank, and along the shoreline. This dataset is the result of combining the most recent digital shoreline inventories for Virginia.
Purpose: To inventory Virginia's tidal shoreline conditions.
Supplemental_Information:
There are three shapefiles that are part of the Shoreline Inventory database: *_lubc, *_astru, *_sstru. The _lubc (land use and bank cover) is a linear shapefile containing data about land use, bank height, erosion, bank cover, Phragmites australis, tree fringe, canopy overhang, marsh, and beach status along the shoreline. The _sstru (shoreline structures) is a linear shapefile delineating hard structures at the shoreline (bulkhead, breakwater, dilapidated bulkhead, debris, jetty, marina, marsh toe revetment, unconventional, riprap, groin fields). The _astru (access structures) is a point shapefile with locations of docks, ramps, dilapidated docks, outfalls, and boathouses. The attributes of these three shapefiles are explained in the Entity and Attribute Information section below. Beginning in 2012 the method of collecting data for the shoreline inventory changed. Data for marsh and Phragmites australis is no longer recorded in the *_lubc shapefile but is found in the tidal marsh inventory shapefiles. Please visit <http://www.vims.edu/ccrm/research/inventory/virginia/index.php>. Beginning in 2016, beach is no longer included in the lubc shapefile. Beach is a stand-alone shapefile.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 19980101
Ending_Date: 20170401
Currentness_Reference: ground condition at time of survey
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.654834
East_Bounding_Coordinate: -75.328920
North_Bounding_Coordinate: 38.920399
South_Bounding_Coordinate: 36.526513
Keywords:
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: Access structures
Theme_Keyword: Shoreline structures
Theme_Keyword: Shoreline Inventory
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Categories
Theme_Keyword: environment
Theme_Keyword: structure
Place:
Place_Keyword_Thesaurus: None
Place_Keyword: Accomack County
Place_Keyword: Arlington County
Place_Keyword: Caroline County
Place_Keyword: Charles City County
Place_Keyword: Chesapeake Bay
Place_Keyword: Chesterfield County
Place_Keyword: City of Alexandria
Place_Keyword: City of Chesapeake
Place_Keyword: City of Colonial Heights
Place_Keyword: City of Fredericksburg
Place_Keyword: City of Hopewell
Place_Keyword: City of Petersburg
Place_Keyword: City of Portsmouth
Place_Keyword: City of Richmond
Place_Keyword: City of Suffolk
Place_Keyword: City of Williamsburg
Place_Keyword: Eastern Shore
Place_Keyword: Essex County
Place_Keyword: Fairfax County
Place_Keyword: Gloucester County
Place_Keyword: Hanover County
Place_Keyword: Henrico County
Place_Keyword: Isle of Wight County
Place_Keyword: James City County
Place_Keyword: King and Queen County
Place_Keyword: King George County
Place_Keyword: King William County
Place_Keyword: Lancaster County
Place_Keyword: Mathews County
Place_Keyword: Middlesex County
Place_Keyword: New Kent Countiy
Place_Keyword: Newport News
Place_Keyword: Norfolk
Place_Keyword: Northampton County
Place_Keyword: Northumberland County
Place_Keyword: Poquoson
Place_Keyword: Prince George
Place_Keyword: Prince William
Place_Keyword: Richmond County
Place_Keyword: Spotsylvania County
Place_Keyword: Stafford County
Place_Keyword: Surry County
Place_Keyword: Virginia
Place_Keyword: Virginia Beach
Place_Keyword: Westmoreland County
Place_Keyword: York County
Access_Constraints: None
Use_Constraints:
These data should not be used for jurisdictional permit determinations beyond providing general shoreline condition or status information. These data have not been surveyed to property boundaries.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Virginia Institute of Marine Science (VIMS)
Contact_Person: Marcia Berman
Contact_Position: Director of Comprehensive Coastal Inventory Program (CCI)
Contact_Address:
Address_Type: mailing and physical
Address:
Virginia Institute of Marine Science, P.O. Box 1346, 1375 Greate Rd
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Contact_Voice_Telephone: 804-684-7188
Contact_Facsimile_Telephone: 804-684-7179
Contact_Electronic_Mail_Address: marcia@vims.edu
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Virginia Institute of Marine Science (VIMS)
Contact_Person: Marcia Berman
Contact_Position: Director of Comprehensive Coastal Inventory Program (CCI)
Contact_Address:
Address_Type: mailing and physical
Address:
Virginia Institute of Marine Science, P.O. Box 1346, 1375 Greate Rd
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Contact_Voice_Telephone: 804-684-7188
Contact_Facsimile_Telephone: 804-684-7179
Contact_Electronic_Mail_Address: marcia@vims.edu
Native_Data_Set_Environment: Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9270
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
The attributes were compared to original GPS data logs for accuracy. Errors were corrected where noted. For data collected remotely, placement depends on accuracy of basemap imagery.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Explanation:
In house QAQC process involves complete checks of shoreline coding by a GIS Programmer/Analyst and a Marine Scientist.
Logical_Consistency_Report:
All points are associated with a shoreline access structure or a point of interest.
Completeness_Report:
This inventory targets tidal shoreline only. Access by boat is required for field surveys. Remote sensing techniques are used in areas where water depths are too shallow for access or where unmanaged, undeveloped shoreline persists along very long reaches. This would include headwaters of tidal creeks, and natural areas along park and conservation lands.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
Shoreline attributes recorded with a GPS unit as the boat moves along the shoreline has a horizontal accuracy of +/- 5 meters. Data was transferred from the GPS boat track to an existing digital shoreline coverage by projecting data to the shoreline at a 90 degree angle from the boat track. Rectified imagery were used as a background coverage to aid in data positioning. Land use features were placed along the shore so changes in land use were coincident with changes illustrated in the imagery. Positional accuracy for data that has been corrected with imagery which has a resolution of 2 meters or better. Accuracy limits of the field collected data, however, are set at 5 meters due to the short occupancy of GPS units. In many cases the image correction yields a final positional accuracy much closer to 2 meters or less, depending on image resolution. Time period: 1998-2013.
Using the latest VBMP (2009, 2011, 2013, 2015, or 2017 depending on locality) imagery as a background, conditions visible on shore were used to code a digital shoreline created using VBMP imagery at a scale of 1:1000. Conditions were also verified using Google Earth, and Bing imagery. Time period: 2013 to present.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Explanation:
Line position and attribution is subject to Processor interpretation and clarity of imagery used. In house QAQC process involves checks of shoreline coding by one or two different GIS Programmer/Analysts and, since 2014, a Marine Scientist.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN)
Publication_Date: 20030101
Title: Virginia Base Map Program (VBMP)
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Richmond, VA
Publisher: Virginia Geographic Information Network
Source_Scale_Denominator: 4800
Type_of_Source_Media: dvd
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 20020101
Source_Currentness_Reference: Unknown
Source_Citation_Abbreviation: VBMP 2002
Source_Contribution:
Imagery (2002) serves as a background in the map portfolio. Imagery is used to update land use and structure data as well as to remotely code areas not previously surveyed in the field. The VBMP shoreline was also used and adjusted using the imagery where needed. This shoreline was used in Westmoreland.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN)
Publication_Date: 20140101
Title: Virginia Base Mapping Program (VBMP)
Type_of_Source_Media: None
Source_Citation_Abbreviation: VBMP 2009, 2011, 2013, 2017
Source_Contribution:
Imagery (2009, 2011, 2013, 2015 and/or 2017) serves as a background in the map portfolio. Used to accurately position land use and land cover data. Provided a new digital shoreline coverage that serves as the base shoreline for shoreline conditions. Used in the following counties: City of Virginia Beach, Northampton, Charles City, City of Suffolk, City of Poquoson, City of Newport News, Northumberland, City of Norfolk, James City County, City of Williamsburg, Gloucester, York, Stafford, Middlesex, Lancaster, City of Portsmouth, Prince George, Accomack, and City of Chesapeake. Added in 2017: Hanover, Surry, King George, City of Fredericksburg, Chesterfield, Isle of Wight, Spotsylvania, and Henrico. Added in 2018: Arlington, Caroline, Essex, New Kent, and Richmond County. Added in 2019: King and Queen, and King William.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN)
Publication_Date: 20080101
Title: Virginia Base Map Program Imagery and Hydrology
Geospatial_Data_Presentation_Form: vector digital data
Type_of_Source_Media: None
Source_Citation_Abbreviation: VBMP 2006/07
Source_Contribution:
Imagery (2007) serves as a background in the map portfolio. Imagery is used to update land use and structure data as well as to remotely code areas not previously surveyed in the field. The VBMP shoreline was also used and adjusted using the imagery where needed. This shoreline was used in the following counties: Mathews.
Process_Step:
Process_Description:
The shoreline for Northampton was extracted from the VGIN LiDar derived, hydro flattened DEM for the Eastern Shore using the ArcMap contour tool. Bank height was generated from the VBMP. The 0, 5, 10 and 30 foot contours were derived from the VBMP Eastern Shore hydrologically correct DEM based on the 2010 LiDar survey, using the raster surface contour tool. It was decided that the bank would be within 10 meters of the 0 contour except on some beaches where the bank was visually further away. 10 meter buffers were created for the 5, 10 and 30 foot contours. Each of these buffers was run with the 0 contour in the intersect tool to make files showing where the contours were within 10 meters of the 0. In no case did the 30 foot contour intersect 0. The 3 files for 0, 5, and 10 were run in the identity tool to make the final file showing bank height feature attributes of 0-5, 5-10, and 10-30. This was merged with the land use data and became an attribute in the shapefile.
Process_Date: 20110101
Process_Step:
Process_Description:
Begining in 2012 marsh data is being collected separately and is no longer part of the shoreline inventory "lubc" shapefile. Marsh data (including phragmites information) will be in served in the updated Tidal Marsh Inventory (TMI): <http://www.vims.edu/ccrm/research/inventory/virginia/index.php> Dates: 2012 to 2019.
Process_Date: 20120101
Process_Step:
Process_Description:
For parts of Virginia Beach (Broad Bay and Rudy Inlet) data were logged using a geo-referenced video camera.
Process_Date: 20120101
Process_Step:
Process_Description:
In the ArcMap environment, boat-track arcs and points were manually shifted to the base shoreline. Arcs were split and moved to locations on the shoreline perpendicular to the original locations on the boat-track. Points were also moved to locations on the shoreline perpendicular to the original locations on the boat-track. Shoreline arc segments and points were coded, and the shapefiles were visually checked for attribute accuracy between coded shoreline and boat-track data. Dates: 1998-2013
Process_Date: 20121231
Process_Step:
Process_Description:
Data was collected by a three-person field crew (1989-2001) or a two-person field crew (2002 to 2012). From 2002 to 2012 a two-person crew consisted of one person collecting land use and bank condition data and one boat operator also collecting shoreline features using two hand-held Trimble GeoExplorers GPS Units, while navigating along the shoreline. A data dictionary designed for the inventory was installed on each GPS Unit. One data collector records natural features including land use, bank height, presence of marsh or beach, and shoreline stability. A second person collects data on the hardened structures: riprap, bulkheads, docks, boatramps, etc. Point features (docks, boathouses, ramps) were surveyed with a six second observation recorded at 1 reading/second. Linear features were surveyed kinematically at a rate of one observation every 3 seconds. Begining in 2012 the two-person crew consists of a boat operator and one data surveyor. The boat operator navigates the boat to follow the shoreline geometry. The data surveyor uses a geo-referenced video camera. The Red Hen System provides hardware and software to collect geo-referenced video and photo data in the field. A standard video camera (sony ACC-HDV7) is interfaced with a GPS antennae via the Red Hen hardware device - VMS 300. VMS 300 converts GPS data into audio signals, which are sent to a video camera through its microphone input connector. As the video is recorded, GPS data are transmitted once per second to the video camera by VMS 300. Each GPS location is linked with a time code on the video. Therefore, the survey is a set of videos containing geographically referenced shoreline data. Dates: 1998 to 2015
Process_Date: 20121231
Process_Step:
Process_Description:
Data from the GPS units were postprocessed using Trimble Pathfinder Office software. Postprocessing included differential correction using CORS (Continuous Operating Reference Stations) data. Corrected data are converted to shape files for further processing in the GIS environment. Dates: 1998-2013
Process_Date: 20121231
Process_Step:
Process_Description:
Land use, point structure, and linear structure locations were digitally checked and repositioned if necessary with imagery displayed in the background. Coding takes place in the ArcMap environment using coding, heads-up digitizing, and photo-interpretation techniques. Areas inaccessible by boat due to low tide were coded based on features observed on the imagery. The "remote" coded areas were given the item REMOTE = "yes" to distinquish them from GPS collected data. Background image quality depends upon imagery available the year inventory was published. Begining in 2011/2012 recent high resolution color infra-red and natural color imagery (2009, 2011, 2013, 2015, and 2017) with a resolution of 1 meter or better is used along with Bing oblique imagery to identify and code the shoreline for shoreline attributes. Dates: 1998 to 2019
Process_Date: 20151231
Process_Step:
Process_Description:
For tributaries surveyed in the field using GPS referenced videography, the proprietary software associated with the Red Hen System is used for post processing: Pixpoint and GeoVideo for GIS. The PixPoint software package is used to generate a point shapefile containing points representing locations of geo-referenced still photos taken during the survey. GeoVideo software package is an ArcGIS extension. It is a desktop mapping application that brings the geo-referenced video directly into the ArcGIS environment. This software enables users to digitally map videos using GPS coordinates. After the videos are downloaded to the computer, the GeoVideo software is used to generate a point shapefile which is geotagged to the precise track of the video survey. This shapefile is a representation of the survey track. Along with the video link, it enables GIS personnel to code the shoreline conditions in ArcMap based on what is viewed in the video. Dates: 2012 to 2015
Process_Date: 20151231
Process_Step:
Process_Description:
County inventories were merged together. Inventories completed during the year are appended to this dataset, either replacing older localities or filling in gaps.
Process_Date: 20171221
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: Entity point
Point_and_Vector_Object_Count: 33623
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: VA_astru_2006_2019
Entity_Type_Definition: Virginia Access Structures
Entity_Type_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.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: GPS_DATE
Attribute_Definition: Date of data capture
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain: Date of GPS field data.
Attribute:
Attribute_Label: REMOTE
Attribute_Definition: Remotely surveyed. This coding appears in older inventories.
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition: Data coded in the lab using background imagery
Enumerated_Domain_Value_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain: Values include Yes, No, and ' '
Attribute:
Attribute_Label: PNTSTRUC
Attribute_Definition:
Points coded for access structures: dock, dilapidated dock, boathouse, and public and private boat ramps.
Attribute_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Dock
Enumerated_Domain_Value_Definition:
Dock/Pier - In this survey, a dock or pier is a structure, generally constructed of wood, which is built perpendicular or parallel to the shore. These are typical on private property, particularly residential areas. They provide access to the water, usually for recreational purposes. Docks and piers are mapped as point features on the shore. Pier length is not surveyed.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Dilapidated Dock
Enumerated_Domain_Value_Definition:
Dilapidated Pier – A pier which has failed due to deterioration from age or storm damage is classified as a dilapidated pier. The remnants of this structure may be original pilings only.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Boathouse
Enumerated_Domain_Value_Definition:
Boathouse - A boathouse is considered any covered structure alongside a dock or pier built to cover a boat. They include true “houses” for boats with roof and siding, as well as awnings that offer only overhead protection. Since nearly all boathouses have adjoining piers, piers are not surveyed separately, but are assumed. Boathouses may be difficult to see in aerial photography.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Private Ramp
Enumerated_Domain_Value_Definition:
Boat Ramp - Boat ramps are used to launch vessels of all types. They are usually constructed of concrete, but wood and gravel ramps are also found. Point
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Public Ramp
Enumerated_Domain_Value_Definition:
Boat Ramp - Boat ramps are used to launch vessels of all types. They are usually constructed of concrete, but wood and gravel ramps are also found. Point identification of boat ramps does not discriminate based on type, size, material, or quality of the launch. This inventory attempts to distinguish, when possible, private versus public ramps. Ramps located in privately owned, commercial marinas and residential communities are classified as private.
Enumerated_Domain_Value_Definition_Source:
Glossary of Shoreline Features Defined, Center for Coastal Resources Management, VIMS
Enumerated_Domain:
Enumerated_Domain_Value: Outfall
Enumerated_Domain_Value_Definition: A visible pipe that empties into the water
Enumerated_Domain_Value_Definition_Source: processor
Attribute_Domain_Values:
Unrepresentable_Domain: Structures that allow access to tidal waters.
Attribute:
Attribute_Label: POINT_OF_I
Attribute_Definition:
Older inventories (counties inventoried between 1998 and 2002) may contain data in this Point of Interest field.
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain:
Older inventories (counties inventoried between 1998 and 2002) may contain data in this field. These points may include bridge, powerline, pilings, old boat, etc
Attribute:
Attribute_Label: COUNTY
Attribute_Definition: county or city name
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain: county or city names in Virginia along the Chesapeake Bay.
Attribute:
Attribute_Label: SURVEYED
Attribute_Definition: year data collected
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain: Year data collected and/or updated.
Attribute:
Attribute_Label: Field_Date
Attribute_Definition: Date of field survey
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain: Date of field survey, if applicable.
Attribute:
Attribute_Label: INVENTORY
Attribute_Definition:
Year of shoreline inventory or year of inventory update using imagery
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain:
Text describing the imagery used to update this inventory or the year of the shoreline inventory.
Attribute:
Attribute_Label: PubYear
Attribute_Definition: year of inventory publication
Attribute_Definition_Source: Processor
Attribute_Domain_Values:
Unrepresentable_Domain: Year published for the county inventory.
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
"Federal Information Processing Standards (FIPS) codes are a standardized set of numeric codes to ensure uniform identification of geographic entities such as cities, counties and towns." These codes are issued by the National Institute of Standards and Technology (NIST). The codes listed in this field are county and city codes for Virginia (state FIPS 51).
Attribute_Definition_Source: Virginia Department of Taxation
Attribute:
Attribute_Label: FIPSCode
Attribute_Definition:
"Federal Information Processing Standards (FIPS) codes are a standardized set of numeric codes to ensure uniform identification of geographic entities such as cities, counties and towns." These codes are issued by the National Institute of Standards and Technology (NIST). The codes listed in this field are county and city codes for Virginia (state FIPS 51). This field is the same as FIPS except it is represented as text.
Attribute_Definition_Source: Virginia Department of Taxation
Attribute:
Attribute_Label: origPntStr
Attribute_Definition: Original point structure coding.
Attribute_Definition_Source: processor
Overview_Description:
Entity_and_Attribute_Overview:
Five shape files combine to complete the Shoreline Inventory. The complete set includes va_lubc, va_astru, va_sstru, va_beach, and va_TMI. The va_lubc (land use and bank cover) file is a linear shape file containing data about land use, tree fringe, bank height, bank cover, bank stability and beach status along the shoreline. Va_astru (access structure shape file) is a point shape file with locations of docks, dilapidated docks, boathouses, and private and public boat ramps. Va_sstru (shoreline structures) is a linear shape file delineating hard structures in place at the shoreline (bulkhead, dilapidated bulkhead, riprap, wharf, unconventional, debris, marina < 50 slips, marina > 50 slips, jetty, marsh toe revetment, groinfield and breakwaters). Va_beaches is a linear shapefile showing the presence of beaches. As of 2016, beaches are digitized as a separate file and are no longer included in the _lubc shapefile. Va_TMI (tidal marshes) shows the location, size, and community type of tidal marshes.
These shape files will be modified yearly with the addition of updated locality inventories. The PubYear field denotes the publication year of the county inventory. The jurisdiction is listed in the County field. Digital shoreline inventories began in 1998. Over the years, the methodology for collecting the data, as well as what data is collected has changed. For detailed information on a particular county, please visit the GIS Data and Maps: Shoreline Inventories web site at <http://www.vims.edu/ccrm/research/inventory/virginia/index.php>
Metadata_Reference_Information:
Metadata_Date: 20200831
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Virginia Institute of Marine Science (VIMS)
Contact_Person: Tami Rudnicky
Contact_Position: GIS Programmer/Analyst
Contact_Address:
Address_Type: physical
Address: Virginia Institute of Marine Science, 1375 Greate Rd
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Contact_Voice_Telephone: 804-684-7181
Contact_Electronic_Mail_Address: tamia@vims.edu
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 Mon Aug 31 12:17:03 2020