Layers:

Layer: SpecificPlan_boundary_scag (0)

Name: SpecificPlan_boundary_scag

Display Field: SP_NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: SCAG has developed its regional geospatial dataset of land use information at the parcel-level (approximately five million parcels) for 197 local jurisdictions in its region. The regional land use dataset is developed (1) to aid in SCAG’s regional transportation planning, scenario planning and growth forecasting, (2) facilitate policy discussion on various planning issues, and (3) enhance information database to better serve SCAG member jurisdictions, research institutes, universities, developers, general public, etc. It is the most frequently and widely utilized SCAG geospatial data. In 2024, SCAG successfully released the final 2019 regional land use dataset, developed for the Final Connect SoCal 2024, the 2024-2050 Regional Transportation Plan/Sustainable Communities Strategy (RTP/SCS), which includes general plan land use, specific plan land use, zoning code and existing land use information. The 2019 regional land use dataset was reviewed by local jurisdiction, and SCAG staff made every effort to ensure the data reflect local jurisdiction’s input received during the Connect SoCal 2024 Local Data Exchange process. Following the successful adoption of Connect SoCal 2024, SCAG launched the 2024 regional land use data development process to update parcel-level land use information in preparation for Connect SoCal 2050, the 2028-2050 Regional Transportation Plan/Sustainable Communities Strategy (RTP/SCS). Between summer and fall of 2024, SCAG staff collected 2024 parcel boundary GIS files and tax roll property data from county assessor’s offices. After several months of data standardization and cleanup, SCAG released the 2024 parcel boundary GIS files in March 2025, followed by the 2024 Annual Land Use dataset in June 2025. In June 2025, SCAG staff successfully developed the preliminary dataset of the 2024 Specific Plan Land Use dataset. These datasets will serve as key inputs for the development of Connect SoCal 2050, supporting growth forecasting, scenario planning, policy discussions, and analysis of regional growth strategies.This dataset is intended for planning purposes only, and SCAG shall incur no responsibility or liability as to the completeness, currentness, or accuracy of this information. SCAG assumes no responsibility arising from use of this information by individuals, businesses, or other public entities. The information is provided with no warranty of any kind, expressed or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Users should consult with each local jurisdiction directly to obtain the official land use information.Data Field/Value DescriptionField NameData TypeLengthDescription SourceField DescriptionOBJECTIDObject IDESRIInternal feature numberShapeGeometryESRIType of geometryCOUNTYText50SCAGCounty nameCITYText50SCAGCity nameSP_NAMEText100SCAG, Local JurisdictionsSpecific plan nameNOTESText200SCAGAdditional informationCITY_ADOPTEDText255SCAGCity adopted the planYEAR_SPDateLocal JurisdictionsYear when jurisdiction adopted/last updated current specific plan land use elementYEARShortSCAGDataset YearShape_LengthDoubleESRILength of feature in internal unitsShape_AreaDoubleESRIArea of feature in internal units squared

Copyright Text: SCAG

Default Visibility: true

MaxRecordCount: 2000

MaxSelectionCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.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: 287627.65359999985
YMin: 3615347.8384000007
XMax: 731056.1640999997
YMax: 3862025.5054
Spatial Reference: 26911  (26911)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [252, 238, 204, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Feature Draw Order:
N/A
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
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• COUNTY ( type: esriFieldTypeString, alias: COUNTY, length: 15 )
• CITY ( type: esriFieldTypeString, alias: CITY, length: 22 )
• CITY_ADOPTED ( type: esriFieldTypeString, alias: CITY_ADOPTED, length: 22 )
• SP_NAME ( type: esriFieldTypeString, alias: SP_NAME, length: 95 )
• YEAR_SP ( type: esriFieldTypeDate, alias: YEAR_SP, length: 8 )
• NOTES ( type: esriFieldTypeString, alias: NOTES, length: 190 )
• YEAR ( type: esriFieldTypeInteger, alias: YEAR )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )