Laserfiche WebLink
a node to determine whether the entire parcel should be <br />included in or'excluded from the node. <br />o The staff report has been revised to indicate that the <br />clustering provisions incorporated into the county's <br />comprehensive plan were prompted by amendments to resolve <br />plan intervenors' issues as well as to. meet DCA's <br />stipulated settlement agreement requirements. <br />o The staff revised the Capital Improvements Element to <br />correct the mis-labeling of Table 13.17. <br />It is staff's position that the referenced changes satisfy DCA's <br />concerns and adequately address the issues identified in the ORC <br />report. <br />Future Land Use Element <br />Policy 1.23 <br />As identified in the Description and Conditions section of this <br />staff report, several problems have been identified with respect to <br />policy 1.23. Mostly, these problems relate to a lack of <br />specificity with the policy, particularly a lack of any defined <br />methodology to estimate node size, node development percentage, and <br />other components of the policy. Also, the policy fails to identify <br />circumstances that would make a node expansion "otherwise <br />warranted." <br />In analyzing Policy 1.23, staff has found that the Policy's <br />substantive criteria appear to be adequate to accomplish the <br />objective of allowing node expansion only when a need for that <br />expansion has been justified. The lack of specified methodology, <br />however, detracts from implementation of this policy by changing <br />the focus of node expansion requests from substantive to procedural <br />issues. <br />In node expansion amendment requests addressed by staff since plan <br />adoption, considerable time, effort, and expense have been expended <br />to estimate node size and developed acreage. This has occurred <br />because different sources of information and different assumptions <br />have been useck by applicants and staff. The result has been an <br />emphasis on methodology disagreements, instead of an analysis of <br />substantive criteria based on accepted data, information and <br />calculations. <br />To rectify this problem, staff has revised policy 1.23 to <br />incorporate a methodology to be used to assess node expansion <br />requests. As reflected in the revised policy, the changes involve <br />specification of information sources (current node boundary map, <br />and property appraiser's map) and identification of a development <br />area determination methodology. With these changes, policy 1.23 <br />will be more easily understood and applied by the planning and <br />zoning commission, board of county commissioners, staff, and <br />applicants. <br />While policy 1.23 has a specific 70 percent node expansion <br />criterion, the policy also has the "otherwise warranted" catch-all <br />phrase. Although that phrase had been included to provide <br />flexibility, it has not served that purpose. Instead, DCA has <br />reviewed node expansion requests strictly - using the 70 percent <br />factor and generally discounting the unless "otherwise warranted" <br />phrase because of its lack of specificity. Consequently, DCA had <br />suggested that the policy be revised to delete the phrase or to <br />more specifically define it. <br />Since staff has addressed several node expansion requests, various <br />circumstances warranting expansion without a 70 percent or more <br />buildout have been identified. These include: a need to <br />accommodate a use where no suitable sites for expansion exist in <br />123 <br />