Layer: OPA Specific Plan Area (ID:2)

View In: Map Viewer

Name: OPA Specific Plan Area

Display Field: Plan_Area

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Is View: true

Is Updatable View: true

Source Schema Changes Allowed: true

Sources

Description: Combined four layers below and cleaned up fields to create one layer with SPs, PUDs, PCs, and Neighborhood Plans/Character Areas:civ-sql-cluster/CommunityDevelopment_Planning/DBO.Cypress_St_Barriociv-sql-cluster/CommunityDevelopment_Planning/DBO.El_Modena_Barriociv-sql-cluster/CommunityDevelopment_Planning/DBO.PlanningLandbaseciv-sql-cluster/CommunityDevelopment_Planning/DBO.OPA_Specific_Plan_AreaOriginal layer (PlanningLandbase) was a copy of parcels. Dissolve tool used to consolidate boundaries of each plan area type.Removed following layers from database as they have been combined into this new layer, "PlanAreas"DBO.Chapman_University_Specific_PlanDBO.Cypress_St_BarrioDBO.Depot_Specific_ZoneDBO.El_Modena_BarrioDBO.OPA_Specific_Plan_AreaDBO.OPA_Specific_Plan_Area_in_Orange_JurisdictionDBO.PlanAreas (previously was just SPs. layer was removed and name was used for this new layer)DBO.PlanningLandbaseSpecific Plans and Neighborhood Plans in OrangeA specific plan is a detailed plan for the development of a particular area. Specific plans are intended to provide finite specification of the types of uses to be permitted, development standards (setbacks, heights, landscape, architecture, etc.), and circulation and infrastructure improvements that are only broadly defined by the General Plan. Specific plans are often used to ensure that multiple property owners and developers adhere to a single common development plan. Specific plans are also used as a means of achieving superior design by providing flexibility in development standards beyond those contained in the Zoning Ordinance.

Copyright Text:

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

{"renderer":{"type":"simple","symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[130,130,130,0],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[255,0,0,255],"width":4}}},"scaleSymbols":true,"transparency":0,"labelingInfo":null}
HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:

OBJECTID (type: esriFieldTypeOID, alias: OBJECTID_1, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
Plan_Area (type: esriFieldTypeString, alias: Plan_Area, SQL Type: sqlTypeOther, length: 40, nullable: true, editable: true)
PA_Num (type: esriFieldTypeString, alias: PA_Num, SQL Type: sqlTypeOther, length: 5, nullable: true, editable: true)
PA_Minor (type: esriFieldTypeString, alias: PA_Minor, SQL Type: sqlTypeOther, length: 50, nullable: true, editable: true)
PA_Note (type: esriFieldTypeString, alias: PA_Note, SQL Type: sqlTypeOther, length: 120, nullable: true, editable: true)
Type (type: esriFieldTypeString, alias: Type, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
Shape__Area (type: esriFieldTypeDouble, alias: Shape__Area, SQL Type: sqlTypeDouble, nullable: true, editable: true)

Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 9/29/2025 5:44:23 PM

Schema Last Edit Date: 9/29/2025 5:44:23 PM

Data Last Edit Date: 9/29/2025 4:56:22 PM

Supported Operations: Query Query Pivot Query Top Features Query Analytic Query Bins Generate Renderer Validate SQL Get Estimates ConvertFormat