This is the parcel level detail of existing and proposed zoning and land use policy. Parcels were extracted on 9/6/22. Initial layers from Dudek were used as a basis for coding proposed zoning and land use policy after a couple rounds of quality control in August and September, 2022. DRP SDE layers for existing zoning and land use policy, along with an updated zoning layer from the DRP zoning conflation project were also used to code the parcels. This layer also shows Assessor taxroll information, along with this additional information:

• SPLIT_STATUS - This is the result of an analysis of Dudek's zoning and land use policy datasets and coding the parcels to with the existing / proposed zoning and land use categories. The ones identified as 'SPLIT' means that an existing zoning or land use policy line cuts through a parcel and is legitimate (ie. NOT a sliver). Those that say "OK - Spatial Join' means that there is only one zoning / land use policy category per parcel - included in this category are the following:

  • Those slight misalignments with the zoning or land use policy compared to the parcel (sliver polygons - where the area / perimeter creates a ratio of less than one)

  • Those cases where whole blocks of parcels were shifted by the Assessor. These are cases where existing zoning or land use cuts through a parcel are not technically sliver polygons, but since there is a systematic shift, the parcels were all coded with only one zoning or land use policy category.

  • All of these were found doing several overlay analyses and QC.

• In Specific Plan? - (YES/NO) if a parcel is within a Specific Plan (all of Florence-Firestone was coded as such, even though it's not yet been adopted)

• HEU Change? - (YES/NO) if a parcel is a Housing Element Update Rezoning change

• GZ Change? - (YES/NO) if a parcel is an existing industrial zone and within 500' of a sensitive use - the zoning suffix will be "-GZ"

• MULT_AIN - Whether a parcel is split by an existing or proposed category; this displays the number of parcel parts per APN where applicable

• Duplicate Parcels - Identifies a parcel is spatially duplicated - in the case of a condo, or a DWP right-of-way.

• Zone Change? - (YES/NO) if a parcel's zoning is being changed (in whole, or in part). Note that just adding a '-GZ' is not considered a zone change.

• LUP Change? - (YES/NO) if a parcel's land use policy is being changed (in whole, or in part).

• Change Type - These are three tiers that are categorized below - this is to assist in notification mailings:

  • Tier 1 - Any Housing Element update or Industrial Downzoning (LSP, or M-0.5)

  • Tier 2 - Any other zone change or LUP change that affects density that was found during DRP's quality control process

  • Tier 3 - Any administrative change to zoning or LUP. This is predominantly the changing of Area / Community Plan categories to match the General Plan legend.

• Industrial Rezone Change? - YES if a parcel is affected by an Industrial rezoning (those being downzoned to LSP or M-0.5).

• SP Change? - (YES/NO) if a parcel is within a Specific Plan area which is updating the Specific Plan zoning (only applicable to Florence-Firestone TOD)

• FFTOD - Specific Plan (existing and proposed) - These are the categories for the Florence-Firestone TOD Specific Plan that are existing (as it was adopted in February, 2023), and proposed changes from the Metro Area Plan.

Additional Notes for Florence Firestone: Due to the Florence-Firestone TOD going before the Metro Area Plan, the following is important to know.

• All existing and proposed zoning is shown as 'SP', therefore, no zone changes are flagged here.

• Several Housing Element update parcels are listed as 'YES'. These are reflected in the Specific Plan.

• Several parcels are flagged with a 'YES' for Industrial Rezoning, and the TOD Specific Plan zoning will need to be updated.

From this layer, the proposed zoning, proposed land use policy, and proposed zone change area layers were extracted with a model.

UPDATE HISTORY:

• 10/16/22 - final QC completed.

• 12/21/22 - Additional parcels flagged for removal for zone changes based on staff recommendations.

• 3/16/23 - Exported proposed M-0.5 and LSP zones to a separate layer (Parcels_Proposed_Zoning_M05_and_LSP). Reverted these proposed zones back to their existing category.

• 3/20/23 - Made the following changes:

  • Updated Land Use Policy for those formerly proposed M-0.5 and LSP zones to be reflective of M-1, M-1.5, and M-2.

  • Added FFTOD fields so that the Florence-Firestone TOD Specific Plan gets reflected (adopted by BOS on 2/7/23).

  • Discovered that 3 parcels had a zone change from Green Zones Ordinance that weren't reflected in FFTOD - hence, they were over-written back to heavy industrial, and will need to be corrected later.

  • Coded Proposed FFTOD Specific Plan category changes (mostly GZ), and noted the details of the change.

  • Flagged all the formerly proposed M-0.5 and LSP parcels.

• 3/30/23 - Brought over the FFTOD Specific Plan categories to reflect the existing LUP and Specific Plan categories as of BOS adoption - added proposed changes (GZ-related changes and clean-up parcels). Updated the '3 Green Zones Parcels' to what their proper SP Category and Proposed LUP should be.

• 4/17/23 - for FFTOD - coded Zone Change to 'No' for those that were only Green Zone changes.

• 5/10/23 - Updated some parcels for a zone change / plan amendment in Willowbrook; coded a few additional parcels as HEU as they were adjacent to HEU changes and changing to MU/MXD (request from Dudek); removed 'GZ' designation from a couple proposed commercial zones. All these changes were noted in the "MAP Update Notes" field.

• 5/31/23 - Coded all GZ parcels with Zone Change = YES - they were 'NO' previously and that was erroneous.

• 6/29/23 - Coded all GZ parcels in FFTOD with SPChange = YES. They were 'NO' previously (except for the three that had gotten overwritten with the FFTOD adoption).