Loading...
(a) Ownership. In order to submit an application for RPD review, the tract or tracts of land included within the proposed RPD shall be in one ownership or control, or shall be subject to a joint application by the owners of all properties included within the proposal.
(b) Review procedure options.
(1) All applications shall be preceded by a pre-application conference pursuant to this chapter.
(2) All applications shall be subject to relevant sections of the common review requirements in § 1214.01: Common Review Requirements.
(3) All applications that are not already within an RPD District shall include a separate application for a zoning map amendment to an RPD District. Such amendment shall be reviewed as part of the RPD development plan.
(c) RPD submission and review procedure.
(1) Step 1 - Pre-application meeting (required). An applicant shall be required to have a pre-application meeting with the Development Review Committee to informally discuss the application and any concept plans. Such meeting shall be subject to § 1214.01(f).
(2) Step 2 - Application. The applicant shall submit an application in accordance with § 1214.01: Common Review Requirements, and with the provisions of this section.
(3) Step 3 - RPD development plan and zoning map amendment.
A. The RPD development plan approval procedure involves a zoning map amendment to rezone the subject property to an RPD with an approved RPD development plan.
B. The procedure for this stage shall comply with the requirements of § 1214.02: Code Text and Map Amendments, including review by the Development Review Committee.
C. In accordance with the zoning map amendment review procedure, the Planning Commission shall hold a public hearing to review the RPD development plan and make a recommendation to City Council to approve, approve with modifications, or deny the application. The recommendation shall be made based on review of the application using the criteria contained in § 1222.04: Review Criteria.
D. In accordance with the zoning map amendment review process, City Council shall hold a public hearing on the RPD development plan and zoning map amendment and decide to approve, approve with modifications, or deny the application using the criteria contained in § 1222.04: Review Criteria, of this chapter. If the application is approved, the area of land involved in the application shall be rezoned as an RPD with a related, approved RPD development plan.
E. Such action of City Council shall only require concurring vote of a simple majority of City Council unless the City Council votes to approve, in any form, an application where the Planning Commission recommended denial, in which case the approval shall require a three-fourths majority vote of City Council.
F. In making its recommendations or decisions, the Planning Commission and/or City Council may impose such conditions of approval as are in its judgment necessary to ensure conformity to the applicable criteria and standards of this zoning code and with the Comprehensive land use plan. In so doing, the Planning Commission and/or City Council may permit the applicant to revise the plan and resubmit it as an RPD development plan within 60 days of such action.
G. Preliminary subdivision plat approval may occur concurrently with the RPD development plan approval if permitted by the Code Administrator. If submitting plats for subdivision review simultaneously with the RPD development plan, the plats shall be subject to all applicable subdivision standards and requirements including the applicable review process.
(4) Step 4 - Site plan review and/or zoning permit issuance.
A. Zoning permits shall not be issued until the lot or applicable subdivision has been fully recorded in the office of the Lorain County Recorder’s office and public improvements have been installed in accordance with the applicable subdivision regulations.
B. For development activities where site plan review is required, the applicant shall be required to received site plan review prior to issuance of a zoning permit.
(d) Time limit.
(1) Any RPD development plan shall be valid for a period of two years after the date of approval by City Council. If no development has begun (development being defined as the start of construction of the required public/private improvements as shown on the approved RPD development plan for one or more phases of the project) within two years from the date of approval, such approval shall lapse and be of no force and effect.
(2) Two one-year extensions of the time limit set forth in division (d)(1) of this section, may be granted by the Planning Commission if such extension is not in conflict with the most current comprehensive land use plan and that such extension is in the best interests of the entire community. The developer/owner shall apply for an extension and shall state the reason for the extension.
(3) If an approved RPD development plan lapses as provided in this section, the RPD development plan shall be considered void. Notice of such lapse shall be filed by the Planning Commission and forwarded to the City Council.
(4) Voiding of the RPD development plan shall not rezone the property. After such plans are voided, the Planning Commission, City Council, or property owners may initiate a rezoning to a base zoning district in accordance with § 1214.02: Code Text and Map Amendments, or the property owner, or their agent, may resubmit an RPD development plan in accordance with the procedures of this chapter.
(e) Changes to approved RPDs.
(1) An RPD shall be constructed and completed in accordance with the approved RPD development plan including all supporting data and conditions. The RPD development plan and supporting data, together with all recorded amendments, shall be binding on the applicants, their successors, grantees and assignees, and shall limit and control the use of premises (including the internal use of buildings and structures) and the location of structures in the RPD as set forth therein.
(2) Where a property owner on a lot in an RPD seeks a variance from the applicable standards for an individual property that will not apply to any other property in the RPD, the property owner shall request such variance in accordance with § 1214.09: Variances.
(3) Any request to change or otherwise modify the approved RPD development plan as it applies to more than one property owner, shall be reviewed based on whether the change is considered major or minor, in accordance with this division.
A. Major changes reviewed by Planning Commission and City Council. Where an applicant proposes any of the following, the applicant shall submit a revised RPD development plan that will be subject to the same review as a new RPD, in accordance with § 1222.03: RPD Submission and Review Procedure:
1. Expansion of an existing RPD beyond the limits of the RPD Development plan approval; or
2. Proposed changes to the uses or density that will result in an increase in residential dwelling units of more than 5% of the total dwelling units approved as part of the original RPD development plan.
B. Major changes reviewed by Planning Commission only. The following changes shall require approval by the Planning Commission following a public hearing unless the Code Administrator determines that changes are not significant enough to substantially alter the originally approved plan:
1. Changes in the development plan relative to the arrangement of lots, the layout of streets or circulation patterns, the size, configuration and location of common open space, and changes in any approved elements of the RPD; and
2. Amendments to the conditions that were attached to the RPD development plan or RPD development plan approval.
C. Minor changes reviewed by the Code Administrator.
1. Minor changes are those proposed by the developer/owner which do not disturb or affect the basic design and approved RPD development plan, and which are essentially technical in nature, as determined by the Code Administrator, shall be reviewed administratively by the Development Review Committee. The Development Review Committee shall make a recommendation to approve or deny the change to the Code Administrator who shall have the authority to make a final decision.
2. The Code Administrator shall have the authority to forward the action to the Planning Commission in the case that the recommendation is to deny the change.
3. Examples of minor changes include, but are not limited to, changes in the intensity of lighting, changes to individual floor plans, changes to the siting of an individual building on a lot within approved setbacks, changes in the size and location of water and sewer lines within approved easements, engineering changes that do not alter street or lot layouts, and changes in the location and number of fire hydrants.
4. The Code Administrator shall notify the Planning Commission of all such approved minor changes.
(f) Revocation.
(1) In the event of a failure to comply with the approved plan or any prescribed condition or approval, including failure to comply with the stage development schedule, the Planning Commission may, after notice and hearing, revoke the approval of the RPD development plan. The Planning Commission shall at the same time recommend whether to maintain the RPD zoning district or the rezoning of the properties to another zoning district.
(2) The revocation shall become final 30 days after City Council passes an ordinance to rezone the property to a non-RPD zoning category or a decision by the Planning Commission to revoke the approved plans but retain the RPD zoning.
(3) Where the RPD zoning remains without an approved RPD development plan, the property owner or agent shall be required to submit a new RPD development plan in accordance with the review procedures of this chapter.
(g) Recording. The recording of the subdivision related to the RPD approval shall be done in the same manner as outlined in § 1214.05: Major Subdivisions.
(Ord. 21-161, passed 12-13-2021)
All RPD applications shall be reviewed based on the following general criteria and the applicable review body shall consider such criteria in the creation of their specific findings when making recommendations and decisions regarding RPD applications:
(a) The proposed development is in conformity with the goals, policies and any applicable recommendations of the Avon Lake comprehensive land use plan;
(b) The proposed development meets the intent and spirit of this code and all other applicable city ordinances or adopted plans;
(c) The development provides an environment of stable character that promotes a harmonious relationship between land uses within the site and a harmonious relationship with surrounding development, utilizing adequate buffers where necessary;
(d) The proposed development provides a development pattern which preserves and utilizes the natural topography, geologic features, scenic vistas, natural vegetation and natural drainage patterns of the site;
(e) The proposed development maximizes the opportunity for privacy within residential areas and minimizes nuisances between residential areas and other land uses;
(f) The proposed development, while compatible with its surroundings, provides a more diverse environment for living, shopping and/or working than would be possible under strict application of the standard minimum design requirements of other districts provided within this code;
(g) The proposed development promotes greater efficiency in the use of land and does not impose an undue burden on public services and facilities such as fire and police protection, public works, schools, water supply and wastewater disposal due to excessive population densities;
(h) The proposed development is not likely to result in significant adverse impacts upon the natural environment, including air, water, noise, stormwater management, wildlife, and vegetation, or such impacts will be substantially mitigated;
(i) The proposed development is accessible from public thoroughfares adequate to accommodate the traffic which will be imposed on them by the proposed development, and the proposed streets and parking areas within the site are adequate to serve the proposed arrangement and densities of land uses;
(j) The proposed development minimizes pedestrian, bicycle and vehicle conflicts;
(k) The proposed development provides a higher quality and more useful design of landscaping and open space and amenities than would normally be required under the strict application of existing zoning and subdivision requirements;
(l) The proposed development contains such proposed covenants, easements, association by-laws and other such provisions as may reasonably be required for the public health, safety, and welfare;
(m) The proposed development is designed in such a way that each individual section of the development as well as the total development, can exist as an independent section capable of creating an environment of sustained desirability and stability or that adequate assurance has been provided that such an objective shall be attained;
(n) Where common open space is required, appropriate arrangements with the applicant have been made which will ensure the reservation of common open space as identified on the RPD development. If deemed necessary by City Council during the RPD development plan review process, City Council may require the applicant to hold bond to ensure the successful and proper reservation of open space. Furthermore, the RPD development plan shall demonstrate how the open spaces shall be duly transferred to a legally established homeowners’ association or has been dedicated to the city or another public or quasi-public agency for preservation and maintenance;
(o) Appropriate agreements with the applicant have been made to ensure the proper completion of public improvements in compliance with Title Four, Platting and Subdivisions, of the code of ordinances of Avon Lake, Ohio;
(p) The proposed development can be substantially completed within the time specified in the schedule of development submitted by the developer; and
(q) The RPD plans have been transmitted to all other agencies and departments charged with responsibility of review and any identified issues have been considered and reasonably addressed by the applicant.
(Ord. 21-161, passed 12-13-2021)
(a) Principal uses.
(1) Only those uses listed as a permitted residential use or public, institutional, and recreational use in this code (see § 1216.05: Allowed Principal Uses) may be considered in the application of an RPD. A use shall be considered permitted use in an RPD if is permitted as-of-right, permitted with standards, or permitted as a conditional use in § 1216.05: Allowed Principal Uses.
(2) The permitted uses within the RPD shall be established for the subject property in the comprehensive land use plan. Any request for alternative land uses shall require the approval of the Planning Commission and City Council as part of the RPD review process.
(3) In general, any standards that applies to a specific use in this code shall also apply to those same uses in an RPD. However, the Planning Commission and City Council may adjust or waive any of those use-specific standards based on unique circumstances.
(4) As part of any approval, the Planning Commission and/or City Council may restrict the uses permitted within an individual RPD by adopting a list of uses permitted within the RPD.
(5) All uses shall be subject to the performance standards of § 1226.02: Performance Standards.
(b) Accessory uses.
(1) Unless otherwise allowed for in the approved plans, accessory uses associated with development in an RPD shall be allowed in accordance with the following.
A. Accessory uses permitted in the R-1, R-1A, R-1B and R-1C Districts shall be allowed for any single-family dwelling.
B. Accessory uses allowed in the R-2 and R-3 Districts shall be allowed for any two-family, three-family or multi-family dwelling.
(2) Any allowed accessory uses shall still comply with the applicable accessory use-specific standards established in this code in § 1224.01: Accessory Uses and Structures.
(3) As part of any approval, the Planning Commission and/or City Council may restrict the accessory uses permitted within an individual RPD.
(4) For residential uses, the maximum gross floor area of accessory buildings shall be as established in Table 1222-1. The table also establishes the maximum lot coverage, of the rear yard, by all accessory structures, including accessory buildings. The accessory structures that count toward lot coverage are identified in Table 1224-2. The maximum rear yard lot coverage requirements shall not be waived as part of the RPD process.
Table 1222-1: Maximum Floor Area and Rear Yard Coverage for Accessory Structures | |||
Lot Area (Square Feet) | Maximum Sq. Ft. of Any One Accessory Building | Maximum Sq. Ft. of All Accessory Buildings | Maximum Coverage of Rear Yard by All Accessory Structures |
15,000 or more | 500 | 1,000 | 40% |
12,000 to 14,999 | 500 | 1,000 | 45% |
6,500 to 11,999 | 250 | 500 | 65% |
Under 6,500 | 250 | 500 | 65% |
(Ord. 21-161, passed 12-13-2021)
(a) Lot and density regulations.
(1) Table 1222-2 sets out the density, total lot coverage and building height requirements for the different areas of Avon Lake based on the future land use categories of the comprehensive land use plan. See § 1226.01: Lot and Principal Building Regulations for methods of calculation.
Table 1222-2: RPD Density, Lot Coverage and Building Height Standards | ||||
Future Land Use Plan Category | Maximum Density | Maximum Lot Coverage | Maximum Front Yard Setback | Maximum Building Height |
Low-density residential | 2 units per acre | 40% | 30 feet | 35 feet |
Medium-density residential | 15 units per acre | 50% | 20 feet | 45 feet |
High-density residential | Up to 25 units per acre | 50% | 15 feet | 50 feet |
(2) The Planning Commission and City Council shall have the authority to restrict densities based on the compatibility of the development with surrounding development, the scale of the overall project, traffic impacts, and recommendations from the comprehensive land use plan.
(3) The Planning Commission and City Council may waive requirements to lessen the density or intensity of uses but an increase in density or intensity shall require an amendment to the comprehensive land use plan.
(4) Each principal building shall have its own private yard.
(5) The RPD development plan shall illustrate lot areas and setbacks (e.g., building area for each lot) for each lot.
(6) Every building in an RPD shall have access either to a street, walkway or other area dedicated to common use.
(7) In RPDs with residential dwelling units, the privacy of future residents shall be assured by yards, creative building arrangements, screening and other design elements. At a minimum, residential dwellings shall meet the following standards in an RPD.
A. The minimum distance between principal buildings shall not be less than ten feet.
B. For multi-family dwellings, principal buildings should be oriented in a manner that will provide the most privacy to individual dwellings through creative placement and increased separation.
C. Driveways may be located along a lot line but on lots where there is a side-loading garage or access to a garage where a vehicle backs out of the garage toward an adjacent lot line instead of a street and where a zero-foot setback is proposed, a curb shall be installed along the entire driveway to prevent the overhang of any vehicles across lot lines and to direct drainage to approved drainage systems.
(b) Open space. All RPD applications shall incorporate open space as required in Chapter 1230: Open Space and Recreation Impact Fee Requirements based on the density of residential development.
(c) Design and development standards. Where this code provides for design and development standards not specifically addressed in this chapter, development within an RPD shall comply with the applicable standard.
(1) Illumination. All development shall comply with the outdoor lighting standards of § 1226.04: Outdoor Lighting unless waived by the Planning Commission and City Council.
(2) Off-street parking and loading. All development shall comply with the requirements of Chapter 1234: Parking, Access, and Mobility Standards unless waived by the Planning Commission and City Council where shared parking, on-street parking or other arrangements will not necessitate as much parking.
(3) Landscaping and buffering.
A. All RPDs shall comply with the applicable landscaping and buffering requirements of Chapter 1232: Landscaping and Screening Standards, which shall be established as the minimum landscaping and buffering requirements. To the maximum extent possible, applicants should make efforts to preserve large areas of mature tree stands in areas that will provide natural landscaping and buffering between uses, in which case, the opacity requirements of § 1232.05(b) may be waived.
B. All development and common open space shall be landscaped according to all overall coordinated plan, utilizing a variety of trees, including evergreen type whenever possible to maximize screening potential year-round. Plantings, walls, fencing and screens shall be so designed and located as to optimize privacy and aesthetic quality without encroaching upon required automobile sight distances.
C. The percentage of retained and proposed landscaped areas to the total area shall not be less than 20% of the entire lot.
D. In general, all unpaved areas of a lot shall be landscaped, or a bond or irrevocable letter of credit submitted to guarantee the installation of landscaping prior to occupancy of a principal building.
E. The amount of landscaping shall be comparable to the intensity of the development proposed to soften the developed areas. Particular care shall be taken to introduce trees and other landscaping into parking and other paved areas that are sustainable given the proximity to large expanses of pavement.
F. Outdoor areas or containers holding or storing trash, garbage, recycled or reused materials shall be screened on three sides from adjoining properties, streets and other public areas. Such areas or containers shall be screened in accordance with this code and shall include a decorative gate for access.
G. Project buffer.
1. RPDs that contain residential uses of a higher density than of adjacent residential uses shall be required to provide a permanent open space buffer consisting of mounding and vegetative plantings sufficient to protect the privacy and amenity of such adjoining areas. The buffer area shall be a minimum of:
a. Twenty feet in width if the gross density of the RPD is more than one unit per acre higher than adjacent residential development;
b. Fifty feet in width if the gross density of the RPD is more than five units per acre higher than adjacent residential development; or
c. Planning Commission and City Council may reduce the required buffer based on the presence of adjacent open space or landscaping areas that provides a pre-existing buffer or the presence of other design elements that will help mitigate the need for such buffer.
2. The buffer area shall be maintained by the land owner or owner association in such a manner as to ensure its effectiveness.
3. The project buffer area shall not be included in the calculation for the lot area of any private lot.
(4) Signs.
A. Signs shall be integrated into the building and landscaping plans to enhance the overall appearance while providing adequate identification of the development.
B. The requirements of Chapter 1236: Sign Standards, may only be waived as part of the approval of the preliminary RPD plan when the applicant submits a master sign plan for the entire RPD. In such cases, the master sign plan shall not allow for more than a 10% increase in the total sign area allowed in Chapter 1236: Sign Standards.
(5) Development layout. Dwelling units shall be grouped or clustered to provide interest and diversity in the arrangement, maximize privacy, collect and maximize the common open space and promote the individual character and coordinated layout of each lot, cluster and grouping. Streets and cul-de-sacs shall be laid out so as to discourage through and high-speed traffic unless such through street is needed to be in compliance with the approved city plans.
(6) Vehicular access points.
A. Adequate and properly arranged facilities for internal pedestrian and traffic circulations shall be provided.
B. Topography, landscaping and existing vegetative clusters shall be utilized as necessary to make the project attractive and provide buffers between areas of substantially different character.
C. The street and thoroughfare network shall be designed to minimize truck and through traffic passing through residential areas of the development, especially where dwelling units with two or more bedrooms are common.
D. A minimum of two ingress and egress points shall be provided for any RPD. If an RPD is phased, each phase shall have a minimum of two ingress and egress points at the time of construction. Planning Commission and City Council may approve one ingress and egress point for the RPD or individual phase if the establishment of two access points is determined not to be feasible.
E. Where an RPD is located adjacent to a vacant lot, connections shall be planned for the future connection to the future development of the vacant lot unless waived by the Planning Commission and City Council. Where such connections are made, a temporary turnaround may be established and the future connection shall be noted on the RPD development plan and the final subdivision plat. An easement shall be provided on the final plat of the subdivision to keep the land open in perpetuity for the connection.
(7) Vehicular circulation. The circulation system and parking facilities shall be designed to fully accommodate the automobile with safety and efficiency. Any driveway to arterial and collector streets shall be placed at locations where the traffic can be controlled and operated effectively with the minimum interference with the capacity and flow of the existing streets.
(8) Pedestrian circulation. An interconnecting walkway system shall be designed to promote easy and direct barrier free access, using accepted criteria, to all areas of the development in a carefully conceived total service plan while also considering the security of the residents in the design. Wherever possible, the vehicular and pedestrian circulation patterns shall be completely separate and independent of one another.
(9) Bicycle plan. A planned unit development shall consider bicycle plans adopted by the city and/or a regional agency, where applicable, on or adjacent to the site. A component of the bike plan which is proposed within a planned unit development shall be assured for public access by easements, agreements or covenants as may be appropriate after review by appropriate departments, acceptance by the Law Director and approval by Council.
(10) Solid waste storage and disposal. All solid waste rubbish, garbage and receptacles shall be stored in enclosed areas acceptable to and regulated by the city.
(d) Improvement standards.
(1) Subdivision compliance. Unless alternative standards are approved as part of a subdivision modification, all RPDs shall comply with the applicable subdivision improvement and design standards established in Chapter 1238: Subdivision Design Standards.
(2) Streets. All streets proposed within an RPD shall be public streets, dedicated to the city in accordance with the applicable subdivision regulations, unless otherwise approved by Planning Commission and City Council as part of the RPD development plan approval. In considering the approval of any application that proposes the use of private streets, the Planning Commission and City Council shall consider the following.
A. All private streets shall be designed in accordance with the standards of § 1238.12(f).
B. Adequate provision shall be made for storm drainage, guest parking and for access by emergency vehicles and trash collection trucks.
C. Private streets are discouraged for use with developments of over 20 dwelling units and shall not be used solely to avoid the construction of public streets. Planning Commission and City Council may approve the use of private streets for more than 20 dwelling units if the design of such streets can sufficiently accommodate emergency service vehicles.
D. Any development proposed containing private streets shall also contain a description of the method by which such streets are to be maintained, such as the by-laws of a homeowners’ association.
(3) Pedestrian walkways. In addition to any sidewalk requirements required by the applicable subdivision standards, any RPD that contains residential uses shall provide for adequate pedestrian walkways connecting residences to existing and proposed recreational facilities, schools, neighborhood shopping, other residential areas and adjoining sidewalk systems.
(Ord. 21-161, passed 12-13-2021)