Laserfiche WebLink
than the minimum project size; and <br />d. Allow off-site or satellite affordable and/or workforce housing units on a different project site but must have <br />a timing component (must be completed prior to 30% or 40% of market rate units). <br />Recommendation: Staff recommends that the BCC and the PZC consider providing policy direction or actual <br />changes to the current PD ordinance to specify what types of affordable and/or workforce housing incentives <br />are acceptable or preferred. <br />4. Minimum Project Size: <br />Most nearby jurisdictions require a minimum (gross) project size for PD projects; however, the project size <br />requirements can vary considerably (see Attachment 2). Based on cursory research, the minimum PD project <br />size ranges from 5 acres to 200 acres, with the average being 35.6 acres across 9 nearby jurisdictions. It should <br />also be noted that the County's PD regulations currently require a minimum project size of 40 acres for a TND <br />project, a maximum of 40 acres for a mixed use PD project. <br />As discussed in item #3 above, the BCC and the PZC may want to consider allowing PD projects below a <br />minimum required size if it includes a minimum percentage of affordable and/or workforce housing units. <br />Recommendation: Staff recommends that the BCC and the PZC consider providing policy direction or actual <br />changes to the current PD ordinance to specify if all new project PD project's should require a minimum (gross) <br />project size, and if that project size may be reduced (or waived entirely) for projects that include a minimum <br />percentage of affordable and/or workforce housing units. <br />5. Compatibility with Neighboring Properties and Uses: <br />The current PD ordinance contains compatibility standards in Section 915.16 (see Attachment 1). However, <br />these compatibility standards are generally limited to the project's proposed use(s) (e.g. residential, <br />commercial, etc.) and the adjacent property's future land use designation (e.g. L-1, M-1, or C/I). While the <br />current compatibility standards have generally worked well in establishing a baseline, they are not specific <br />enough to account for unique or unusual scenarios. For example, a group of neighboring properties may have <br />an L-2 land use designation (which generally equates to an RS -6 zoning with a 70 -foot minimum lot width; <br />however, those properties are already developed as 1 -to -2 -acre estate -style properties with a ±250 -foot lot <br />width versus a new PD project that is proposing 60 -foot -wide perimeter lots. Therefore, the compatibility <br />standards may need to be revised to provide more specificity based on the existing development patterns of <br />neighboring properties. <br />As discussed in item #2 above, a percentage or specified/defined approach may be helpful to consider. For <br />example, an additional 1 foot of buffer width may be required for each 2 feet of perimeter lot width reduction. <br />Therefore, if a project proposes reducing the perimeter lot width by 10 feet, then the perimeter buffer width <br />should be increased by 5 feet which would typically result in a total perimeter buffer width increase from 25 <br />feet to 30 feet. <br />Recommendation: Staff recommends that the BCC and the PZC consider providing policy direction or actual <br />changes to the current PD ordinance to specify what types of compatibility standards are acceptable or <br />preferred. <br />6. Other Procedural Items: <br />Lastly, there are some minor procedural items that the BCC and the PZC might want to consider for all new PD <br />projects moving forward: <br />Indian River County, Florida Page 4 of 5 Printed on 10/17/2025 <br />powered 4 Legistar' <br />