ArcGIS REST Services Directory Login | Get Token
Home > services > MarineSpatialPlanning > MSP (MapServer) > Combined Shoreline API Reference
JSON

Layer: Combined Shoreline (ID: 0)

Name: Combined Shoreline

Display Field: SOURCE_ID

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: This dataset was primarily made by combining two shoreline datasets from NOAA: Electronic Navigational Charts (ENC) from the Office of Coast Survey, and the Continually Updated Shoreline Product (CUSP) from the National Geodetic Survey. A third dataset, (a MHHW shoreline developed by the University of Washington Olympic Natural Resources Center) was also used for Willapa Bay.Typically the CUSP data was used where available, and the ENC data was used otherwise. The ONRC MHHW shoreline was used for Willapa Bay. Where line segments were missing, or where two shorelines did not connect, artificial line segments were added.-----CUSP-----Data was downloaded as a shapefile."The shoreline is a representation based on an office interpretation of imagery or derived from Lidar. Shoreline vectors were verified with contemporary imagery. Sources of non-NOAA vector shoreline included U.S. Fish and Wildlife Service, North Carolina Department of Environment and Natural Resources, and U.S. Geological Survey. Non-NOAA imagery sources for interpreting shoreline included USDA-FSA Aerial Photography Field Office, ESRI Imagery World 2D (USGS, U.S. Geological Survey, and U.S. Department of Agriculture), Bing Maps Imagery Service, and Google Earth (TerraMetrics and DigitalGlobe)."-----ENC-----Data was downloaded in the International Hydrographic Organization S-57 Standard format. Data exists at multiple resolutions. All data used to create this feature class were one of the following resolutions:3 is for coastal charts with scales ranging from 1:150,001 - 1:600,0004 is for approach charts with scales ranging from 1:50,001 - 1:150,0005 is for harbour charts with scales ranging from 1:50,000 or larger.Where level 5 data was available, it was used. If level 5 data was not available, level 4 data was used where available. And where level 5 and level 4 data were not available, level 3 data was used.The "LNDARE Polygon" features were used to determine the shoreline.FURTHER INFORMATIONFrom: http://www.nauticalcharts.noaa.gov/mcd/learnnc_shoreline.html"The shoreline shown on nautical charts represents the line of contact between the land and water at a selected vertical datum. In areas affected by tidal fluctuations, this is usually the mean high-water line. In confined coastal waters of diminished tidal influence, a mean water level line may be used. The shoreline of interior waters (rivers, lakes) is usually a line representing a specified elevation above a selected datum.""NOAA’s National Geodetic Survey (NGS) conducts high accuracy photogrammetric surveys that are used as a basis to update NOAA charts. NGS may also identify shoreline changes from satellite imagery. Some shoreline updates are received through the U.S. Army Corps of Engineers when construction permits have been issued. The shoreline on any particular NOAA nautical may be based on a patchwork of surveys that have been conducted over many years. "-----ONRC-----Though new and old features were removed, added, or modified, the currentness should still be considered as 2008. This is because many such features, natural or manmade, may still exist in this dataset. Ground truthing has not been done nor has checking for the possible presence of these features by other means due to time constraints.In areas of the intertidal zone that hosted Spartina, elevations will be lower now than they were when the dataset was originally produced. This is due to the success of the Spartina Eradication and Control Project which succeded in removing the Spartina epiflora (I'm specific here because other epiflora were *not* removed. Thus, these areas are now exposed to erosional forces not experienced previously.This dataset does *not* extend beyond saltwater influence as this dataset is intended to represent a marine shoreline. Saltwater influence is not the same as tidal influence, as freshwater influx may "back up" during rising tides and this affect is felt farther upstream than tidal mixing of salt and fresh water.Tides become more extreme, and undergo greater delays relative to the distance from the mouths of restricted waterways. These effects attenuate as tidal influence wanes at the upstream end of estuarine reaches.Placement accuracy of MHHW is more problematic near the mouth of Willapa Bay, though strand lines continue to be a good guide there.

Copyright Text: Electronic Navigational Chart source data obtained from the NOAA Office of Coast Survey: http://www.nauticalcharts.noaa.gov/mcd/enc/, http://www.charts.noaa.gov/ENCs/ENCs.shtml Continually Updated Shoreline Product source data obtained from the NOAA Shoreline Data Explorer: http://www.ngs.noaa.gov/NSDE/ ONRC MHHW shoreline data was provided by Keven Bennett at ONRC. Data processed by the University of Washington School of Environmental and Forest Sciences.

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata