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 was published in hardcopy on a county by county basis for each Tidewater Virginia locality. 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.
To inventory Virginia's tidal shoreline condition.
There are three shapefiles that are part of the City of Portsmouth Shoreline Inventory database: port_lubc, port_astru, port_sstru. Port_lubc (land use and bank cover for the City of Portsmouth) is an linear shapefile containing data about land use, bank height, bank cover, erosion, and marsh,and beach status along the shoreline. Port_sstru ( City of Portsmouth shoreline structures) is a linear shapefile delineating hard structures in place for shoreline protection (breakwater, bulkhead, dilapidated bulkhead, groinfield, jetty, marina, miscellaneous, military wharf, seawall, shipyard, wharf, and riprap). Port_astru (City of Portsmouth structures) is a point shapefile with locations of docks, dilapidated docks, outfall, private and public ramps, and boathouses. The attributes of these three shapefiles are explained in the Entity and Attribute Information section below.
Ground condition at time of survey
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.
The attributes were compared to original GPS data logs for accuracy. Errors were corrected where noted.
Chain-node topology present. Linear coverages were built for lines and point coverages were built for points.
All shoreline of the City of Portsmouth that has a minimum depth of 2 feet at mean low water was surveyed. Some shorelines are coded remotely if access was restricted due to depth.
Shoreline conditions were recorded with a GPS unit as the boat moved along the shoreline. Data were 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. High resolution orthophotography was used as background imagery to aid in data positioning. Dock and boathouse point data were aligned with docks on the images. 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 is .3 meters (equivalent to image resolution). Data not visable on the imagery (bulkheads, riprap, etc.) has a positional accuracy of 11 meters. Accuracy was determined by comparing digitally processed data locations to onsite GPS ground surveys collected at random.
Imagery serves as a background in the map portfolios. Imagery is used to update land use and structure data as well as to remotely code areas not surveyed in the field. The VBMP shoreline was also used and adjusted using the imagery where needed.
Data were collected by a two-person field crew using hand-held GPS units and navigating along the shoreline in a shoal draft boat. Features collected include land use, bank height, bank cover, presence of marsh or beach, shoreline stability, riprap, marinas, breakwaters, dilapidated bulkheads, bulkheads, groinfields, miscellaneous,jetties, docks, dilapidated docks, boat ramps, boathouses, military wharfs, wharfs, shipyards, seawalls, and outfalls. Point features 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.
Data from the GPS units were postprocessed on a PC with Trimble Pathfinder Office software. Postprocessing includes differential correction using base station data collected at the VIMS laboratory. Corrected data is converted to shapefiles for further processing.
Data processing of the new shape files occurs in the ArcMap environment. Boat-track "arcs" were manually corrected to the base shoreline (VBMP). Arcs were split and moved to locations on the shoreline perpendicular to the original locations on the boat-track. Shoreline arc segments were coded, and the shapefiles were visually checked for attribute accuracy between coded shoreline and boat-track data. VBMP imagery was used to validate arc locations that could be seen on the imagery (e.g. riparian land use).
Data processing of the new shapefiles occurs in the ArcMap environment. Boat-track "points" were manually corrected to the base shoreline (VBMP). Points were moved to locations on the shoreline perpendicular to the original locations on the boat-track. Points were coded and the access structures (astru) were visually checked for attribute accuracy between coded shoreline and boat-track data. VBMP imagery was used to validate point locations that could be seen on the imagery (e.g. docks and boathouses).
Using ArcMap, the VBMP imagery was used as a data source to code shoreline in areas inaccessible by boat due to water depth. Imagery was suitable for coding not all, but certain features such as land use, docks, boathouses and some erosion control. These "remote" coded areas were given the item REMOTE = 'yes' to distinguish them from data collected in the field using GPS.
Areas surveyed prior to image collection could be updated using the high resolution 2006 VBMP imagery in the background. Certain features and attributes such as land use and structures could be detected and therefore digitally checked and updated as a quality control measure. Using ArcMap 9.2, docks, boathouses, boat ramps, some erosion control, and new development constructed after the original survey were digitized and coded as item REMOTE = 'yes' to distinguish them from data collected in the field using GPS.
A portfolio containing ten 1:12,000 scale plates was created for the City of Portsmouth. Each plate shows four maps: riparian land use, bank conditions, shoreline features, and natural buffers. VBMP 2006 imagery is displayed in the background to provide users with additional information.
Metadata imported.
Internal feature number.
ESRI
Feature geometry.
ESRI
coded in the lab using field data and VBMP
Point features that include structures for accessing and observing the water as well as miscellaneous features (e.g. outfalls).
Two other shapefiles combine with _astru to complete the City of Portsmouth Shoreline Inventory. The complete set includes _lubc, _astru, and _sstru. Attributes in the _lubc file include: FEATURE or land use which contains the following values: agriculture, commercial, forest, grass, paved, residential, scrub-shrub, industrial, timbered, unknown and bare; HEIGHT is the bank height with 0 - 5 feet, 5 - 10 feet, and 10 - 30 feet, and >30; EROSION or bank erosion can have the values: low or high or undercut; MARSH values are Yes(Erosion), Yes(No_Erosion), No, or a blank field; BEACH defines the presence and condition of the beach: Yes(Eroding), Yes(No_Erosion), No, or blank field; COVER is bank cover and defined as bare, partial, and total coverage; and REMOTE refers to data gathered remotely: a blank value indicates the data was collected with the GPS unit, a "y" indicates that the shoreline attributes where determined from the 2006 VBMP imagery. Attributes in the _astru (access structure shapefile) are: PNTSTRUC contains access structures boathouse, dock, dilapidated dock, outfall, and public or private ramp; and REMOTE. Attributes found in the _sstru shapefile are: STRUCTURE (erosion control)with values such as breakwater, bulkhead, dilapidated bulkhead,groin, jetty, marina, miscellaneous and riprap; and REMOTE.
The Comprehensive Coastal Inventory Program (CCI) at VIMS performs a service by distributing data generated by either CCI or public agencies which offer data without restriction or charge. CCI assumes no responsibility for data accuracy or precision, metadata completeness or correctness for digital information. CCI assumes no liability for misuse of any data which may arise as a result of any alteration, conversion, or combination with other data sources. As well, the timeliness and scale of these products must be considered when evaluating appropriate use.
Greate Road