My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
10/14/1999
CBCC
>
Meetings
>
1990's
>
1999
>
10/14/1999
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/23/2015 12:11:58 PM
Creation date
6/17/2015 10:16:25 AM
Metadata
Fields
Template:
Meetings
Meeting Type
Special Call Meeting
Document Type
Minutes
Meeting Date
10/14/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
28
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
• <br />more county control and requires more project improvements than the conventional <br />development process. <br />PD Compatibility Requirements <br />The existing PD ordinance requires all PD projects to meet or exceed the following <br />compatibility requirements: <br />Twenty-five foot (2S) perimeter setback.' all residential PD projects require <br />a minimum 25' setback. No building or roadway pavement is allowed within <br />the 25' setback, although pool and patio improvements are allowed within the <br />setback. <br />Required buffers and transition areas: based upon a buffer/transition area <br />table in the PD ordinance, buffers are required along perimeters of PD <br />projects. The type of required buffer is based upon the land use designation <br />of the PD site and the designation of the adjacent site. Buffer requirements <br />are greater where PD projects abut sites with a less intense designation. <br />Transition areas are alternatives to buffers where the perimeter of a PD <br />Proles is designed to match the conventional lot size/dimension standards of <br />an adjacent site's designation or zoning. The PD buffer/transition area table <br />is shown in attachment #3. <br />These compatibility requirements are designed to ensure that a PD project fits in with <br />the existing development patterns in the area where it is proposed. That fit is assured <br />by making the PD project's edge compatible with adjacent property. <br />Reasons Developers Choose the PD Process <br />Uses defined in the zoning ordinance as "permitted" on a site and standard layouts <br />can be approved through the conventional site plan or subdivision development <br />process. Such a process approves development "by right", with no special <br />requirements applied. By contrast, the PD process is an option for the developer. <br />Generally, developers choose the PD process over the conventional process for one <br />or more of the following reasons: <br />• To transfer development rights (TDR) from environmentally sensitive land to <br />preserve such lands while retaining development potential. <br />• To preserve natural upland areas by clustering the total site's allowable number of <br />units in other area of the project site. <br />• To obtain a density bonus in return for providing affordable housing. <br />• To develop agriculturally designated lands with residential units. <br />• To allow a specific commercialYindustrial use or mix of uses not allowed under any <br />single conventional district or under a site's current zoning. <br />• To allow multi -family units to be sold -off with small or oddly shaped fee simple lots <br />with reduced setbacks. <br />• To allow a single-family product on smaller lots with smaller setbacks and reduced <br />right-of-way widths (trading conventional private lot area for common open space). <br />Each type of project referenced above proposes a trade-off between the developer and <br />the county. The developer obtains desired design or use flexibility and/or the <br />benefits of a particular incentive, while the county obtains extra design and use <br />control, public benefits (e.g. preserved natural open spaces), and creation of <br />innovative development products that meet market demands. <br />OCTOBER 14, 1999 <br />-5- <br />BOOK Ill PAGE <br />• <br />
The URL can be used to link to this page
Your browser does not support the video tag.