Name: Monterey Bay Proposed Receiver Site

Display Field: Name

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Given the location of the critical areas of erosion and the need to avoid adverse impacts to local sensitive habitat, the Southern Monterey Bay Coastal RSM Plan recommends that the coastal area between Wharf II in Monterey to Marina be considered as potential receiver site locations for both subaerial beach and nearshore sand placement. For the latter, the area between the Monterey Beach Resort and the Ocean Harbor House condominiums is considered suitable for three main reasons: The net alongshore sediment transport rate is low and to the north, but the gross transport rate is high in both northerly and southerly directions. This location is fairly central to the southern bight and would allow the sand to be transported most effectively along the whole shoreline. Sand placed at a location further to the north would be unlikely to disperse sufficiently to cover critical areas of erosion towards Monterey Harbor given the overall net transport to the north, and placement further to the south would be too close to the sensitive habitat located offshore. This location is far enough away from the sensitive kelp, eelgrass and rocky reef habitat so as not to cause disturbance through sedimentation or turbidity during construction and post-construction phases of the project. The location is relatively close to a potential stockpile area proposed at Fort Ord where inland sediments, if they become available, could be placed temporarily until a beach nourishment maintenance-style project could be developed. Road access to the location is available. Beach nourishment would occur within the Cities of Sand City, Seaside, and Monterey. The shapefile showing this location was compiled by PWA as a recommendation in the Southern Monterey Bay Coastal Regional Sediment Management Plan (AMBAG, 2008).

Copyright Text: Philip Williams & Associates, Ltd. (PWA), Association of Monterey Bay Area Governments (AMBAG), Coastal Sediment Management Workgroup

Default Visibility: true

MaxRecordCount: 2000

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: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.35686904849E7
YMin: 4383655.472599998
XMax: -1.35626488829E7
YMax: 4388817.3521
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [207, 121, 22, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Id ( type: esriFieldTypeInteger, alias: Id )
• Name ( type: esriFieldTypeString, alias: Name, length: 50 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape_Length ( type: esriFieldTypeDouble, alias: Shape_Length )

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

  Iteminfo   Thumbnail   Metadata