§ 153.047 SITE DEVELOPMENT STANDARDS.

   (A)   Intent. The intent of the Mixed Use Regional (MUR) Districts is to enable the development pattern and form envisioned by the Dublin Corporate Area Plan and the MUR Design Guidelines, emphasizing the creation of a walkable, mixed use environment.

   (B)   Applicability. The standards set forth in this chapter establish the regulations for the arrangement and development of land and structures within the MUR Districts.

   (C)   General development standards. Table 2 outlines the general development regulations for land and structures within the Mixed Use Regional (MUR) Districts. Map 1 outlines the subareas within MUR-4.

Table 2: Mixed Use Regional (MUR) Districts - General Development Standards
Development Standard	Metro/Blazer (MUR-1)	Tuttle/Rings (MUR-2)	Emerald (MUR-3)	Llewellyn Farms (MUR-4)
Minimum Lot Size				20,000 sq. ft.
Minimum Lot Width				100'
Maximum Lot Coverage				75%
Maximum Building Height				Subarea A: 2 stories, not to exceed 32 feet
				Subarea B: 3 stories, not to exceed 40 feet
				Subarea C: 1-story, not to exceed 22 feet with 75' minimum setback up to maximum of 2-story, not to exceed 32 feet with 95' minimum setback Height can be increased at 1':2' height to setback ratio between 75' to 95'
				Subarea D: 1 story, not to exceed 20 feet; pitched roof required
Maximum Building Footprint				N/A
Minimum Front Yard Building Setback				15'
Maximum Front Yard Building Setback				N/A
Minimum Side Yard Building Setback				Subarea A: 10 feet
				Subarea B: 10 feet
				Subarea C: Abutting non-residential use - 10' Abutting residential use - 75' minimum for 1-story not exceed a 22-foot tall building, and 95' minimum for 2-story at 32-foot tall building, increasing setback at 1':2' height to setback ratio between 75' and 95'
				Subarea D: Abutting non-residential use - 10 feet Abutting residential use - 25 feet
Minimum Rear Yard Building Setback				Subarea A: 25 feet
				Subarea B: 25 feet
				Subarea C: Abutting non-residential use - 10' Abutting residential use - 75' minimum for 1-story at 22-foot tall building, and 95' minimum for 2-story at 32-foot tall building, increasing setback at 1':2' height to setback ratio between 75' and 95'
				Subarea D: Abutting non-residential use - 10 feet Abutting residential use - 25 feet
Minimum Front Yard Pavement Setbacks				15'
Side and Rear Yard Pavement Setbacks				Subarea A: 10 feet
				Subarea B: 10 feet
				Subarea C: Abutting non-residential use - 10 feet Abutting residential use - 25 feet
				Subarea D: Abutting non-residential use - 10 feet Abutting residential use - 25 feet
Parking Location				Parking lots are recommended to be located between the building and the property line to provide additional separation from existing residential.

 

Map 1: MUR-4 Subarea Map

   (D)   Additional development standards.

      (1)   Outdoor storage. Exterior storage shall not be permitted in the MUR Zoning Districts, unless it is determined that the proposed outdoor storage is harmonious to the surrounding area and is adequately screened and approved by the required reviewing body.

      (2)   Service areas and structures.

         (a)   Overhead doors shall be located to the side or rear of structures to minimize visibility from public streets. Open service areas and loading docks shall be screened by walls a minimum of six feet in height, but not greater than 12 feet. Walls, fences, or landscape screening shall have 100% opacity to effectively conceal service and loading operations from an adjoining public right-of-way and from any residential zoning district or residential use. This does not apply to overhead doors used for aesthetic purposes such as overhead doors that lead to patios or gathering areas.

         (b)   Service structures shall be screened consistent with the regulations set forth in § 153.077.

      (3)   Mechanical screening.

         (a)   Roof-mounted equipment. All roof-mounted mechanical equipment and penetrations (including but not limited to HVAC equipment, exhaust fans, vents, fans, cooling towers, and related guard rails or safety equipment) shall be fully screened from view at ground level on all sides of the structure, to the extent practicable, from adjacent buildings of similar height. The location of roof top mechanicals shall be placed so as to minimize the visual impacts from adjacent residential uses, as required by the required reviewing body.

         (b)   Ground-mounted equipment. All ground-mounted mechanical equipment shall be incorporated within the footprint of a principal or accessory structure or shall be fully screened from view on all sides.

         (c)   Exemptions. The requirement to screen roof-mounted or ground-mounted equipment shall not apply if the only feasible location for screening would impede the functioning of solar, wind, or geothermal energy equipment or systems.

   (E)   Architectural requirements.

      (1)   Applicability. Architectural requirements as specified in this section shall apply to new construction. New construction is also subject to the MUR Design Guidelines as applicable. Design of additions to structures existing as of the date of this amendment may coordinate with the architecture of the existing structure, but to the extent possible shall meet the requirements of this section.

      (2)   Windows. Building walls shall incorporate windows or glass openings to effectively avoid blank and undifferentiated elevations, while balancing the needs of internal spaces and operations. Windows and glass openings on second stories or above that abut and face towards a residential zoning district or use are subject to the review and approval of the Planning and Zoning Commission. Applicants shall strategically locate second story and higher windows that face a residential use to avoid direct lines of sight to such uses. Landscaping may be used to buffer direct lines of sight.

      (3)   Roofs.

         (a)   Pitched and flat roof types are permitted, unless specified.

         (b)   Pitched roof shall not be sloped less than a 6:12 (rise:run) or more than 12:12, unless otherwise approved by the required reviewing body.

         (c)   Downspouts and scuppers shall be carefully integrated into the facade design.

      (4)   Exterior materials. At least 80% of the exterior walls shall be constructed out of one or more of the primary materials listed below:

         (a)   Primary materials.

            1.   Brick. Brick shall be uniform in color within any one specific color range but using more than one color range to create patterns is acceptable. Bricks that have been flashed to change color in the individual unit, distressed bricks, and wood mold bricks are not acceptable.

            2.   Glass. Transparent, tinted, reflective, coated, opaque, translucent, and textured glass, is permitted.

            3.   Stone. Stone such as limestone, granite, and marble are acceptable. Synthetic stone of a high quality that is indistinguishable from natural stone is also acceptable.

            4.   Pre-cast concrete. Pre-cast concrete panels developed with shadow lines, reveals, textural changes, color variations, and/or exposed aggregate are acceptable.

            5.   Architectural metal. Smooth face, textured face, and corrugated type insulated, or un-insulated metal panels are acceptable. Careful attention to how the panels are adjoined, detailed at corners, and attached is required. Long span, high profile fluted, or ribbed metal panels are prohibited.

            6.   Synthetics. Synthetic siding materials such as fiber cement siding and EIFS may be acceptable if carefully integrated into the building’s design and detailed with a high level of shadow lines and reveals. EIFS is not permitted on the ground story.

            7.   Other primary building materials may be approved by the Planning and Zoning Commission if demonstrated to be of similar quality to the permitted primary materials.

         (b)   Secondary materials.

            1.   Any primary material listed above may be considered as a secondary material.

            2.   Gypsum fiber reinforced concrete (GFRC), wood siding, fiber cement siding and Exterior Insulation and Finishing Systems (EIFS) may be used for trim, detailing, and architectural features.

            3.   Other secondary building materials may be approved if demonstrated to be of similar quality to the permitted secondary materials.

      (5)   Accessory structures. Attached or detached accessory structures shall be constructed similar in design, style, quality, and appearance with identical materials as the principal structure.

   (F)   Landscaping and tree preservation.

      (1)   General.

         (a)   The provisions of §§ 153.130 through 153.149 shall apply to the MUR Zoning Districts, unless specifically exempted, modified, or waived by the Planning and Zoning Commission.

         (b)   Site landscaping shall comply with the general character and design components as prescribed in the Dublin Corporate Area Plan and the MUR Design Guidelines.

      (2)   Perimeter landscape buffer. The following landscape regulations apply to properties contained within the MUR Zoning Districts:

         (a)   Perimeter landscape buffer is required when a non-residential land use is adjacent to a residential zoning district or use (regardless of whether there is an intervening street, alley, driveway, or easement). The intent of the buffer is to provide multiple levels of screening. The buffer shall be a minimum of 25 feet wide and be planted with one tree per 20 lineal feet or fraction thereof as a combination of evergreen and deciduous planted in a staggered line. The tree requirement should include a combination of small, medium and large trees to ensure a variety of heights within the buffer. The buffer shall also include a continuous six-foot high opaque screen constructed out of plantings, a hedge, wall, fence, earth mound, or combination thereof.

         (b)   Existing healthy and non-invasive trees and underlying plant material located within the required buffer area shall be preserved and counted toward the perimeter landscape buffer. Protective measure should be taken to ensure the drip line and root system of the existing trees are preserved.

         (c)   These requirements apply when a site that is subject to these requirements is developed or redeveloped. No existing development shall be required to install perimeter landscape buffering because of a change in the nature, character, or zoning classification of an adjacent parcel.

         (d)   The required perimeter landscape buffer area may be located within a utility or other easement with the prior approval of the City Engineer provided all of the landscape requirements are met.

         (e)   Required buffer materials must be placed on the parcel where development or redevelopment is occurring, unless both the parcel providing the buffering and the parcel being buffered are in common ownership, in which case the buffer may be provided on either or portions of both properties.

         (f)   Vehicles or other objects shall not overhang or otherwise intrude upon the required perimeter landscape buffer. Refer to division (G)(7) of this section for curb and wheel stop requirements.

         (g)   Existing landscape material in good or fair condition may be used to satisfy these requirements with the prior approval of the Director.

      (3)   Surface parking and circulation area landscaping. All surface parking lots located within the MUR Zoning Districts that contain ten or more parking spaces and other vehicular use areas shall provide landscaping as required by this section.

         (a)   Street frontage screening. Surface parking lots and other vehicular use areas located within 40 feet of a public street shall be landscaped along the parking lot boundary facing the street to create a visual edge along the public right-of-way.

         (b)   Perimeter buffering. Where a surface parking lot is located within 50 feet of a side, or rear lot line, and the adjacent property contains a residential zoning district or use, the property owner shall install perimeter buffering meeting the requirements of division (F)(2) of this section.

         (c)   Interior landscaping. Parking lot islands shall be strategically distributed throughout paved parking areas and shall be consistent with section 3.4 of the MUR Design Guidelines. Interior landscaping is not required in the interior of service courts and loading docks.

      (4)   Foundation planting. Building foundation landscaping is required along all sides of a building facing a public street or private drive, a residential zoning district or use, open space, or facing a surface parking area located on the same lot.

      (5)   Use of mounding. The general design of sites shall avoid the use of uniform mounding to meet screening and buffering requirements. Integration of mounding as one of the forms of screening should focus on landforms of varying width and height that will achieve a more natural and less “engineered” appearance.

      (6)   Street trees. Street trees are required along all public streets per the regulations set forth in § 153.134.

      (7)   Tree preservation. All sites within the MUR Districts are expected to retain and protect natural features to the greatest extent practicable as part of the development process. Sites shall also comply with the procedures for §§ 153.140 to 153.149.

   (G)   Parking requirements.

      (1)   Parking shall comply with §§ 153.200 through 153.212, unless specifically provided herein. In the case of conflicts, regulations for the MUR Districts will prevail.

      (2)   Parking shall not be located within a setback, as outlined in Table 2, except that parking areas may extend across contiguous lots in developments with coordinated site design, shared access points and/or shared parking arrangements.

      (3)   Applicability. Any existing structure which does not have the minimum number of parking spaces or loading areas as required by this section, and which thereafter provides additional parking and/or loading spaces in conjunction with an improvement, shall be required to meet the minimum number of parking spaces as provided by Table 3 unless an adjustment is granted per § 153.048 (parking adjustments).

      (4)   Parking requirements.

         (a)   Minimum amount required.

            1.   Each use shall provide the minimum amount of parking required for that use listed on Table 3, except as may be modified by the Planning and Zoning Commission.

            2.   When calculating minimum parking requirements, fractional numbers shall be increased to the next whole number.

            3.   Unless otherwise noted, all square footage requirements are based on indoor gross floor area.

            4.   Except as noted in Table 3, no additional parking is required for accessory or temporary uses when the square footage of the uses is included in the parking calculation for the gross floor area of the principal use.

            5.   Parking and loading spaces for uses not addressed in Table 3 shall be determined by the Planning Director based on the anticipated parking impacts of the proposed use, its similarity to characteristics of other listed uses, and supporting documentation that may be provided by the applicant.

Table 3: Parking Space Requirements
Use	Minimum Required
Bank	2.5 per 1,000 sq. ft
Day Care, Adult and Child	1 space per 10 clients at licensed capacity
Government Services, Safety	2 per 1,000 sq. ft.
Office, General	4 per 1,000 sq. ft.
Office, Medical	5 per 1,000 sq. ft.
Park or Open Space	Per approved parking plan
Professional/Technical Training Facility	2 per classroom plus 1 for every 20 students for which the facility is designed
Research & Development	2 per 1,000 sq. ft.
Tutoring Services	2 per classroom plus 1 for every 20 students for which the facility is designed

 

      (5)   Parking plan.

         (a)   A parking plan demonstrating compliance with the provisions of § 153.048(G) is required for the following conditions and may be submitted as a minor project:

            1.   Applications for a Final Development Plan;

            2.   Applications that include a request for off-site parking;

            3.   In cases where a modified parking agreement necessitates a new or modified parking plan;

            4.   Applications involving a use listed in Table 3 for which the parking requirement is specifically noted as being determined by an approved parking plan;

            5.   Applications that include a request for an adjustment to required vehicle parking;

            6.   Applications that include a request for an adjustment to the number or location of required loading spaces;

            7.   Applications for a minor project for a change of use that requires 25% or more parking spaces than the previous use;

            8.   Applications requesting shared or phased parking arrangements; or

            9.   Other circumstances determined by the Director to require a parking plan, which shall be reviewed with the minor project application.

         (b)   A parking plan shall include, at a minimum, the following, as applicable:

            1.   Required parking and loading computations in accordance with Table 3 and Table 4 and the numbers of parking spaces and loading spaces to be provided.

            2.   Information regarding any requested parking adjustments.

            3.   Signed and executed easements, agreements, or other documentation required to ensure that spaces counted toward the parking requirements are properly secured.

            4.   Plan(s) for planned parking areas covered by the parking plan indicating locations of planned parking, names of property owners for properties not under direct control of the applicant, and any other related site details relevant to the parking plan application.

            5.   Any other information required by the Director to ensure an adequate review of the parking plan information.

         (c)   Demonstration of parking need. The Planning and Zoning Commission shall be permitted to approve a parking plan for fewer than the minimum required parking spaces based on a demonstration of parking need by the applicant. The required reviewing body shall consider:

            1.   The land use and development character of the area to be served by the parking facility;

            2.   The availability of other publicly available parking in the area;

            3.   The timing of parking use relative to other uses in the area;

            4.   The parking requirement for similar uses as may be determined by the Director;

            5.   Whether the provided parking meets the location requirements;

            6.   Whether compliance with Table 3 is made to the maximum extent practicable;

            7.   Whether other adjustments as described in this section should apply in conjunction with or in lieu of the requested need-based adjustment; and

            8.   Whether supporting documentation, if provided, adequately demonstrates that sufficient parking is available to meet projected typical demand.

            9.   Off-street parking requirements may be met in a shared parking lot located within 600 feet of building/structure served.

      (6)   Alternative parking space dimensions.

         (a)   A property owner may request an adjustment to parking space dimensions for no more than 5% of required parking spaces, based on documentation of a formal policy or program to encourage the use of compact vehicles by employees or visitors, as approved by the PZC.

         (b)   Where alternative dimensions are approved, which would have the effect of reducing the number of required spaces meeting the standard dimension requirements, the remaining standard spaces shall be subject to the deferred parking requirements.

      (7)   Curbs and wheel stops.

         (a)   Raised or rolled concrete curbs or wheel stops at least five inches high shall be installed to prevent vehicle conflicts with abutting landscape areas, sidewalks, streets, buildings, or lot lines. There shall be a minimum of four feet of clear walkway area and at least two and one-half feet between a curb or wheel stop and any property line, planting area, street, or building.

         (b)   Planted areas shall be installed at a lower grade than the parking lot pavement, include curbing at the edge of a landscaped area and have openings or gaps allowing drainage from the pavement to enter and percolate through the landscaped areas when used for stormwater management purposes, or if required by the City Engineer.

         (c)   Wheel stops may be used in conjunction with accessible parking spaces where an adjacent walkway is installed at the same grade as the parking space. Wheel stops may be used in addition to raised curbs where necessary to prevent vehicle overhang onto adjacent walkways or near buildings, or in conjunction with curb breaks used for stormwater drainage. Curbs shall be required in all other circumstances.

      (8)   Bicycle parking.

         (a)   One bicycle parking space shall be required for every 20 parking spaces required, or fraction thereof. A minimum of four spaces shall be provided whenever bicycle parking is required. Parking lots containing less than 20 spaces are not required to provide bicycle parking.

         (b)   Every effort should be made to provide clear pedestrian connectivity from the public street to the main entrance of buildings. Clear path of travel through parking areas should be designed in a manner to effectively minimize conflict with vehicles.

         (c)   Bicycle parking shall be located within 100 feet of the entrance to a principal structure. Parking may be located within the principal structure and should be located where conflicts with pedestrian or vehicular travel can be avoided.

         (d)   Bicycle parking racks, docks, or posts shall be designed and installed to provide two points of contact to an individual bicycle frame when used as intended. Enclosed locker-type facilities may be provided in lieu of open racks. Racks and lockers must be designed to allow a bicycle to be locked to a structure attached to the pavement, building, or other permanent structure.

         (e)   Bicycle racks shall be installed according to the dimensional requirements set forth by the bike rack manufacturer and the latest edition of the APBP Bicycle Parking Guidelines, or similarly acceptable industry publication.

         (f)   A minimum five-foot access aisle or maneuvering zone shall be provided for each bicycle parking facility.

      (9)   Vehicle charging stations. Parking lots shall provide at least one vehicle charging station for every 50 parking spaces, unless waived by the PZC. Plug-in points shall be associated with an individual parking space and shall be installed according to appropriate design standards, as approved by the Director. Plug-in points are exempt from the service structure screening requirements of division (D)(3) of this section.

      (10)   Loading areas.

         (a)   Number. The minimum number of loading spaces shall be provided in accordance with the loading space requirements table below. Requirements may be modified upon approval of a parking plan and upon making the determination that another measure would be more appropriate because of the number or type of deliveries experienced by a particular business or use.

 

Table 4: Minimum Loading Spaces Required Per Principal Structure
25,001 - 50,000 sq. ft. GFA	1 space
50,001 - 100,000 sq. ft. GFA	2 spaces
100,001 sq. ft. and above GFA	3 spaces

 

         (b)   Location. Loading/unloading areas and docks shall be prohibited in the front yard. Loading or unloading spaces or docks are prohibited within 50 feet of any residential zoning district or use unless completely enclosed or screened from view in accordance with the Zoning Code.

         (c)   Design requirements.

            1.   An alley or front service drive may be used where a single loading space is required. In all cases, service vehicles must be able to maneuver on-site without interfering with travel on a public street, with off-street parking or the normal movement of vehicles and pedestrians on-site.

            2.   Loading spaces separate from docks shall be at least 12 feet wide, 30 feet long and 14 feet high for adequate clearance.

            3.   Loading docks shall be permitted on front elevations facing a public street. Loading docks shall not be permitted to face abutting residential uses.

         (d)   All service vehicles and/or fleet parking must be maintained within appropriately screened areas and shall not be placed forward of the structure.

   (H)   Circulation and access.

      (1)   Rights-of-way dedication. Private development shall include the dedication of rights-of-way for the future expansion and widening of public roads to serve properties in accordance with the city’s Thoroughfare Plan.

      (2)   Site access. All access from public rights-of-way shall be provided at locations approved by the city for the purposes of access management and safety. Cross access easements shall be provided for all shared driveways, and all sites shall comply with the city’s Administrative Policy for Intersection Visibility Triangles at proposed access points. Cross access easements shall extend all the way to the property line.

      (3)   Construction durability. All private drives, parking areas, pedestrian paths, and sidewalks shall meet at least the minimum requirements established by the city.

      (4)   Paths and connections.

         (a)   Public access easements shall be provided in all cases where shared-use paths are provided through a site and not along a public street.

         (b)   Installation of sidewalks and shared-use paths on site shall be made in compliance with the Dublin Corporate Area Plan and other city plans and policies.

         (c)   Pedestrian access shall be provided from all building entrances to public sidewalks along the street right-of-way. Continual maintenance of all access on a site shall be the responsibility of the property owner.

         (d)   A minimum four-foot sidewalk shall be required along the edge of all parking lots on sides adjacent to buildings to adequately facilitate pedestrian access into the building.

   (I)   Signs. Signs shall comply with §§ 153.150 through 153.164 unless specifically provided for in the following section or by the approval of a Master Sign Plan per § 153.048 (Master Sign Plan). In the case of conflicts, regulations for the MUR Zoning Districts will prevail.

      (1)   Table of height, area, & setbacks. Table 5 shall provide for the implementation of sign requirements for the MUR Zoning Districts:

 

Table 5: Sign Regulations
District	Wall Signs		Monument Signs			Window Signs	Projecting Signs (Wall or Post Mounted)
	Maximum Area (sq. ft.)	Maximum Height (ft.)	Maximum Area (sq. ft.)	Maximum Height (ft.)	Minimum Setback (ft.)	Maximum Area (sq. ft.)	Maximum Area (sq. ft.)	Maximum Height (ft.)	Minimum Setback (ft.)
MUR-4 (day cares, tutoring services, government services, safety)	30	15	30	8	8	N/A	6	6	6
MUR-4 (office, general and medical, professional/technical training, research and development	50	15	50	8	8	6	N/A	N/A	N/A
MUR-4 (other uses not listed)	30	15	30	8	8	6	N/A	N/A	N/A
MUR-4 (joint identification)	N/A	N/A	50	8	8	6	N/A	N/A	N/A

 

      (2)   Table of numbers. The following summarizes the number of signs permitted within the MUR Zoning Districts. The intent of the Districts is that each site is permitted one monument and wall or projecting sign as its primary identification. For designated uses an additional window sign can be used to identify main entrances. An additional sign may be permitted in instances where support services available to the public area integrated within the first floor of a primary structure such as a large office complex. In no case shall more than one sign identifying a particular business be oriented toward the same property line.

 

Table 6: Sign Type and Number
Sign Type	Number Permitted
Wall Sign	•   1 sign per building or use. •   For multiple street frontages, 1 sign per frontage, not to exceed a total of 2 (provided a minimum of 100 feet of frontage on each street). •   For multi-user buildings where tenants have individual entrances, 1 wall sign per tenant space is permitted to a size as defined by the Sign Code. •   In larger office/research complexes with multiple building wings connected by a shared atrium, 1 wall sign may be permitted for each wing.
Monument Sign	•   1 sign per lot or multiple lots if devoted to one specific use or user. •   For multiple street frontages, 1 sign per frontage, not to exceed a total of 2 (provided a minimum 100 feet of frontage on each street).
Window Signs	•   1 sign per business or use when the use has an individual entrance (in addition to any monument, wall, or projecting sign).
Projecting Signs	•   Generally limited to 1 per building or use.

 

      (3)   Joint identification signs. No more than four tenant panels may be provided on one monument sign. Tenant panels must include a frame to visually separate the individual panels.

      (4)   Wall signs. Based upon the specific architecture of buildings, wall signs may be administratively approved by the PZC at a greater building height, not to exceed the primary roof line.

      (5)   Secondary image. Secondary images for signs within the MUR Zoning Districts may be designed up to 30% of the maximum permitted area of the sign face.

      (6)   Sign types. To better accommodate contemporary architecture, sites permitted multiple signs may utilize a combination of sign types.

      (7)   Sign lighting. Signs may be illuminated per the requirements in § 153.159(E) except that no internally illuminated signs shall be located on a building wall that faces a residential zoning district or use.

   (J)   Site lighting. The lighting standards within this section are intended to allow adequate nighttime lighting to protect public safety while also protecting adjacent residential uses, where applicable, from excessive nighttime light and glare, protecting motorists from glare among public rights-of-way, reducing consumption of electricity for lighting purposes, and prohibiting excessive light trespass beyond property lines.

      (1)   Exemptions.

         (a)   Pedestrian walkway ground lighting; and

         (b)   Street lighting.

      (2)   Fixture power and efficiency. All light fixtures shall meet the standards in Table 7.

 

Table 7: Fixture Power and Efficiency
Maximum permitted initial lamp lumens per sq. ft.	9.7 lumens/sq. ft.
Maximum lamp allowance	44,000 lumens
Minimum lumens per watt or energy consumed (as documented by manufacturers specifications or results of an independent testing laboratory)	80 lumens/watt

 

      (3)   Shielding.

         (a)   All exterior light sources and lamps that emit more than 900 lumens shall be concealed or shielded with an Illuminations Engineering Society of North America (IESNA) full cut-off style fixture with an angle not exceeding 90 degrees to minimize the potential glare and unnecessary diffusion on surrounding property. No portion of the lamp, reflector, lens, or refracting system may extend beyond the housing or shield, with the exception of pedestrian lighting.

         (b)   All light sources shall be designed, located, and installed so that the light source is not directly visible from any surrounding property in a residential district.

      (4)   Lighting uniformity. Lighting across a horizontal surface shall have an average range from one to three footcandles.

      (5)   Light trespass. Light generated on site shall not add more than one footcandle to illumination levels at any point at grade level ten feet beyond the property line.

      (6)   Lighting plans. Lighting plans submitted as part of applicable minor projects or final development plans shall include existing lighting from streets and surrounding buildings developed under these standards, and proposed lighting generated from light poles and building lighting.

      (7)   Light poles.

         (a)   The base of light poles in parking areas and non-parking areas shall be either flush with grade or mounted on a concrete foundation projecting no more than six inches above grade.

         (b)   Light poles should be a maximum of 20 feet in height.

      (8)   Wall lighting.

         (a)   Decorative wall lighting may be used to provide up-lighting, downlighting, or other types of lighting accents for buildings within the MUR Districts.

         (b)   Decorative lighting shall not exceed 900 lumens unless installed and shielded in accordance with this section.

         (c)   Ground or pole-mounted floodlights are not permitted for facade lighting.

   (K)   Utility undergrounding and screening.

      (1)   In the MUR Zoning Districts, all utility lines including but not limited to water supply, sanitary sewer service, electricity, telephone and gas, and their connections or feeder lines shall be placed underground.

      (2)   All utility connections shall be kept to the rear or the side of the building, out of view or screened. Applicants shall coordinate with utility providers to site transformers and other similar utility structures to the rear or sides of buildings, or otherwise out of view or screened.

      (3)   Existing above-ground utility lines shall be required to be buried with the provision of new streets, or as otherwise required by the City Engineer.

(Ord. 86-21, passed 12-6-21)

§ 153.048 REVIEW AND APPROVAL PROCEDURES AND CRITERIA.

   (A)   Process purpose and intent. The purpose of this section is to provide adequate review of applications for rezoning and/or development with the Mixed Use Regional (MUR) Zoning Districts. These procedures are intended to create an efficient and predictable review process for projects within these districts.

   (B)   Process summary.

      (1)   The following table summarizes the review and approval processes for the various application types that are applicable to development within a MUR Zoning District. Specifics for each of these processes can be found in the respective section identified in the column titled “Zoning Code Reference”.

Table 8: Process Summary Table
R=Recommendation D=Decision A=Administrative Appeal RF=Review & Feedback
Review/ Approval Body:	Planning Director	Administrative Review Team	Board of Zoning Appeals	Planning and Zoning Commission	City Council	Zoning Code Reference
Zoning Code Approvals
Zoning Map or Text Amendment	R			R	D	§ 153.234
Conditiona l Use	R			D		§ 153.236
Special Permit	R		D			§ 153.231(G)
Zoning Code Approvals
Use Variance	R		R		D	§ 153.231(H)(3)
Non-Use (Area) Variance	R		D			§ 153.231(H)(2)
MUR District Applications
Pre-Applic ation Staff Meeting	RF					§ 153.048(C)
Informal Plan	R			RF		§ 153.048(D)
Concept Plan	R			D		§ 153.048(E)
Concept Plan with a Develop- ment Agreement	R			R	D	§ 153.048(E)(1)(e)
Final Develop- ment Plan	R		A	D		§ 153.048(F)
Minor Project	R	D		A		§ 153.048(G)
Waivers	R			D		§ 153.048(H)
Administra tive Departure	D		A			§ 153.048(I)
Master Sign Plan	R			D		§ 153.048(J)
Administra tive Approvals	D					§ 153.048(K)
Certificat e of Zoning Plan Approval	D					§ 153.048/ § 153.048(M)(3)

 

      (2)   Process flow chart. The following flow chart identifies the primary process applicable to development applications within the MUR Zoning Districts. This is an illustrative representation of the process and does not reflect all possible scenarios and situations.

   (C)   Pre-application staff meeting.

      (1)    Purpose and applicability.

         (a)    The purpose of the pre-application staff meeting submittal is to provide a potential applicant with a non-binding review of a development proposal and to provide information on the procedures and policies of the city, including application review procedures.

         (b)   Pre-application reviews do not result in a development decision or permit and shall not obligate the city or the applicant to take any action on the proposal.

      (2)   Review procedures.

         (a)   A request for a pre-application review shall be made in accordance with the provision of division (M)(1) of this section.

         (b)   Requests shall be submitted to the Director, who shall be responsible for circulating any submittal material to the applicable departments for input.

         (c)   The Director and staff shall use reasonable efforts to conduct an expeditious review of the submitted materials and provide non-binding input and recommendations.

         (d)   The Director may schedule a meeting with the potential applicant to discuss the request or may provide a written summary of the staff review.

         (e)   Additional staff reviews of the pre-application submittal may be requested by the applicant prior to filing a formal application.

         (f)   Any and all written summaries of the pre-application review shall be forwarded to the required reviewing body with a formal application.

   (D)   Informal Plan. Prior to submittal of an application for a Concept Plan, an applicant may submit an informal application for review of a development concept with the PZC. Such submittal shall include a completed application form and supporting material sufficient to describe the development concept. The review of the informal submittal shall be non-binding upon the PZC and the applicant, however, it is intended to provide feedback by the PZC that should inform the preparation and subsequent review of the Concept Plan. The Planning Director shall prepare a brief analysis and comments that will be submitted to the PZC with the application.

   (E)   Concept Plan.

      (1)   Purpose and applicability.

         (a)   The purpose of the Concept Plan is to provide a general outline of the scope, character, and nature of the proposed development to determine if it is consistent with the policy direction and recommendations set forth in the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, the requirements of the MUR Zoning Districts, and applicable Zoning Code requirements.

         (b)   The Concept Plan review provides an opportunity for public input at an early stage of the development process.

         (c)   The Concept Plan review is intended to provide clear direction to the applicant by the required reviewing body resulting from its review and approval of the application.

         (d)   If the Concept Plan is approved by the reviewing body, it shall serve as a basis for preparation by the applicant of the FDP for the proposed development.

         (e)   For projects that will propose a development agreement due to the need for development timeframe, public infrastructure, public and private contributions, development restrictions, or other related items, City Council shall serve as the required reviewing body for the Concept Plan. In those cases, the Director and the Planning and Zoning Commission shall each review the Concept Plan and provide a recommendation to Council to approve, approve with conditions, or disapprove the Concept Plan.

      (2)   Review procedures.

         (a)   The Concept Plan is a mandatory step in the development review and approval process.

         (b)   An application for a Concept Plan shall be made in accordance with the provisions of division (M)(1) of this section.

         (c)   The Planning and Zoning Commission shall be required reviewing body for the Concept Plan in the MUR Zoning Districts, unless a development agreement is proposed in conjunction with a proposed project, then City Council shall be required reviewing body for the Concept Plan.

         (d)   The Concept Plan shall be forwarded to the PZC for approval, approval with conditions, or denial of the application under the criteria of division (E)(4) of this section.

         (e)   The PZC shall review the Concept Plan application, the Director’s recommendation, and render its decision based on the criteria of division (E)(4) of this section. In the instance the PZC is the required reviewing body, the Commission will render a decision for approval, approval with conditions, or denial and written record of the Commission’s decision shall be provided.

         (f)   In the instance of a Concept Plan associated with a proposed development agreement, the Commission will make a recommendation of approval, approval with conditions, or denial to City Council.

         (g)   City Council shall review the Concept Plan application and the recommendations of PZC and the Director, and render its decision based on the criteria of division (D)(3) of this section of approval, approval with conditions, or denial.

      (3)   Submittal requirements. It is the intent of these regulations that the Concept Plan shall indicate overall design of the proposed project. Information submitted should be comprehensive enough to enable the required reviewing body to understand the existing site and concept for the proposed development, and to evaluate consistency with the review criteria in division (E)(4) of this section. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (4)   Review criteria. The required reviewing body shall make its decision on an application for a Concept Plan based on each of the following criteria and may consider the recommendation of the Director and, if City Council is the required reviewing body, the recommendation of the PZC. For applications associated with a development agreement, the PZC shall apply these criteria in the formulation of its recommendation to City Council.

         (a)   The Concept Plan is consistent with the applicable policy guidance of the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, the requirements of the MUR Zoning Districts, other applicable Zoning Code requirements, and other applicable city plans, and citywide administrative and financial policies;

         (b)   The Concept Plan conforms to the applicable requirements of the Code;

         (c)   The illustrative lots, supporting street and pedestrian network, and internal circulation provide a coherent development pattern and the conceptual locations of access points to surrounding streets will avoid adverse impacts on surrounding neighborhoods and traffic infrastructure;

         (d)   The proposed land uses allow for appropriate integration into the community, consistent with adopted plans, and align with the requirements of § 153.046, Uses;

         (e)   The conceptual buildings are appropriately sited and scaled to create a cohesive development character that complements the surrounding environment, and conforms to the requirements of § 153.047, Site Development Standards and the MUR Design Guidelines;

         (f)   The conceptual design of open spaces, including location and relationship to surrounding buildings, provides for meaningful public gathering spaces that benefit the community both within and outside the proposed development; and

         (g)   The Concept Plan allows for the connection and or expansion of public or private infrastructure and the continued provision of services required by the city or other public agency.

   (F)   Final Development Plan.

      (1)   Purpose and applicability.

         (a)   The purpose of the Final Development Plan (FDP) is to confirm compliance with the Concept Plan, all applicable requirements of the Code, Community Plan, Dublin Corporate Area Plan, MUR Design Guidelines, and other adopted plans, policies, and regulations, and the review criteria.

         (b)   The FDP allows the PZC to ensure that the proposed development is compliant with the following:

            1.   That the street network provides a coherent and rational development pattern, and the site provides for clearly identified pedestrian accessible routes and connections;

            2.   That the proposed building(s) is appropriate to the location and neighborhood, including assuring that the dimensions of a parcel meet the lot size requirements for the applicable zoning district;

            3.   That the architecture, building materials and colors, landscaping and buffering, and site layout create a functional, aesthetically appealing place;

            4.   That planned open spaces and building are integrated in order to complement each other;

            5.   That the proposed development is consistent with the general development requirements of the city with respect to such elements as infrastructure, transportation, and environmental considerations; and

            6.   That the proposed development will contribute to the creation of signature places in the city.

         (c)   The FDP is intended to verify the proposed development, or phases of development, is in compliance with all applicable code requirements and design guidelines and is consistent with the Concept Plan.

         (d)   All development within the MUR Districts shall require an approved FDP prior to applying for site disturbance approval, Certificate of Zoning Plan Approval (CZPA), and/or building permits. In addition, the following development activities shall also require an approved FDP:

            1.   When a project involves the design or construction of new streets, or a proposed realignment or relocation of any street that is required or permitted by the city;

            2.   When a project requires land subdivision in accordance with Chapter 152; or

            3.   When a project does not meet the criteria for a Minor Project (MP).

         (e)   Applications for an FDP shall be reviewed by the PZC, whose approval shall be binding and shall serve as the regulatory and administrative document for zoning compliance.

      (2)   Review procedures.

         (a)   An application for an FDP shall be submitted in accordance with the provisions of divisions (F)(4) and (M)(1) of this section.

         (b)   The PZC shall be the required reviewing body for the FDP within the MUR Zoning Districts.

         (c)   The Director shall make a recommendation to the PZC for approval, approval with conditions, or denial of the FDP application under the criteria of division (F)(4) of this section.

         (d)   The PZC shall review the FDP application and the recommendation of the Director and render its decision based on the criteria of division (F)(4) of this section for approval, approval with conditions, or denial. A written record of the Commission’s decision shall be provided.

      (3)   Submittal requirements. It is the intent of these regulations that an FDP shall provide final project information that is sufficient to ensure general conformity to an approved Concept Plan. Information should be sufficiently detailed to enable the PZC to understand the existing site and the FDP for the proposed project or a portion thereof, and to evaluate consistency with the review criteria in division (F)(4) of this section. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (4)   Review criteria. The PZC shall make its decision on an application for an FDP based on each of the following criteria:

         (a)   The FDP shall be substantially similar to the approved Concept Plan, and consistent with the record established by the required reviewing body, the associated staff report, and the Director’s recommendation;

         (b)   The proposed development is consistent with the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, other adopted city plans, and citywide administrative and financial policies;

         (c)   The proposed land uses conform to all applicable requirements and use specific standards of § 153.046, Uses;

         (d)   The proposed buildings are appropriately sited and conform to the requirements of § 153.047, Site Development Standards;

         (e)   The proposed street layout and lots conform to the requirements;

         (f)   The proposed design of the internal circulation system, driveways, and any connections to the public realm provide for safe and efficient access for pedestrians, bicyclists, vehicles, and emergency services;

         (g)   The proposed building design, site design, landscaping and buffering plan, and open spaces are consistent with the MUR Design Guidelines;

         (h)   The scale and design of the proposed development allows for the adequate provision of services currently furnished by or that may be required by the city or other public agency including, but not limited to, fire and police protection, public water and sanitary sewage services, recreational activities, traffic control, waste management, and administrative services;

         (i)   The proposed development provides adequate stormwater management systems and facilities that comply with the applicable regulations of this Code and any other applicable design criteria or regulations as adopted by the city or required by other government entities;

         (j)   The proposed development can be adequately serviced by existing and/or planned public or private infrastructure consistent with the city's most recently adopted capital improvements program;

         (k)   If the development is proposed to be implemented in phases, each phase has adequate infrastructure to serve the development independently without the need for further phased improvements; and

         (l)   The proposed development demonstrates consistency with the recommendations, principles, and intent of all applicable design standards and guidelines, including but not limited to buildings, open spaces, and streetscapes.

   (G)   Minor Project.

      (1)   Purpose and applicability. The purpose of the Minor Project (MP) is to provide an efficient review process for smaller projects that do not have significant community effects.

      (2)   Minor Projects defined. The following projects shall be considered eligible for review and approval as a Minor Project:

         (a)   Development of mixed use and nonresidential principal structures of 3,500 square feet or less gross floor area and associated site development requirements for sites zoned MUR-4.

         (b)   Additions or modifications to principal structures that increase the gross floor area by not more than 25%, or not more than 2,500 square feet gross floor area, whichever is less, existing as of the effective date of this amendment, or when first constructed, and associated site development requirements for sites zoned MUR-4.

         (c)   Exterior modifications to principal structures involving not more than 25% of any individual facade elevation of the structure. The repainting of a facade, either partially or fully, shall be considered a Minor Project.

         (d)   Signs, landscaping, parking, and other site related improvements that do not involve construction of a new principal building.

         (e)   Accessory structures and uses.

         (f)   Parking plans when not associated with an FDP.

      (3)   Review procedure.

         (a)   An application for a Minor Project (MP) shall be made in accordance with the provisions of divisions (G)(5) and (M)(1) of this section.

         (b)   The ART shall be the required reviewing body for the MP.

         (c)   The Director shall make a recommendation to the ART for approval, approval with conditions, or denial of the MP under the criteria of division (G)(5) of this section.

         (d)   The ART shall review the MP application and the Director’s recommendation, and render its decision based on the criteria of division (G)(5) of this section for approval, approval with conditions, or denial. A written record of the PZC’s decision shall be provided.

         (e)   If the application is not approved by the ART, the applicant shall be given the opportunity to revise the application in response to the ART comments and resubmit for reconsideration.

         (f)   Decisions of the ART are appealable to the PZC.

      (4)   Submittal requirements. It is the intent of these regulations that an application for a MP provides sufficient information to ensure general conformity to the applicable provisions of this Code. The information should be sufficiently detailed to enable the required reviewing body to understand the existing site and the MP request for the proposed project or a portion thereof. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (5)   Review criteria. The Planning and Zoning Commission shall make its decision on an application for a MP based on each of the following criteria and the recommendation of the Director:

         (a)   The MP shall be consistent with the Community Plan, the Dublin Corporate Area Plan, applicable Zoning Code requirements, MUR Design Guidelines, and adopted plans, policies, and regulations;

         (b)   In cases where a MP is proposed within or as part of an approved FDP, the MP shall be consistent with such approved FDP;

         (c)   The MP shall be consistent with the record established by the required reviewing body, the associated staff report, and the Director’s recommendation;

         (d)   The proposed land uses meet all applicable requirements and use specific standards of § 153.046, Uses; and

         (e)   The proposed site improvements, landscaping, screening, and buffering shall meet all applicable requirements of the Code and respond to the standards of the MUR Design Guidelines.

   (H)   Waivers.

      (1)   Purpose and applicability. Under the provisions of this section, waivers are a process to allow deviations from specific Code requirements that may only be granted by the PZC.

      (2)   Waivers defined. A waiver is defined as a request for a deviation from the requirements of § 153.047 (site development standards) which do not otherwise qualify for an AD under the provisions of division (I) of this section.

      (3)   Review procedure.

         (a)   An application for a waiver shall be made in accordance with the provisions of divisions (H)(2) and (M)(1) of this section.

         (b)   A waiver may be submitted with any application for an FDP or a MP.

         (c)   The Director shall make a recommendation to the PZC for approval, approval with conditions, or denial of the waiver under the criteria of division (H)(5) of this section. Additional waivers determined by the Director during his/her review, may be included for review by the PZC.

         (d)   The PZC shall review the requested waiver using the criteria of division (H)(5) of this section. Should other waivers be necessary to resolve conflicts with other requirements of this chapter resulting from the requested waiver, those waivers shall also be reviewed by PZC.

         (e)   The PZC shall approve, approve with conditions, or deny the waiver request. A written record of the ARB decision will be provided.

      (4)   Submittal requirements. It is the intent of these regulations that an application for a waiver provides sufficient information to evaluate whether the waiver should be granted under divisions (H)(2) and (H)(5) of this section. The information should be sufficiently detailed to enable the PZC to understand the existing site, proposed FDP or MP, and the related waiver request for the proposed project or a portion thereof. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (5)   Review criteria. The ARB shall make its decision on an application for a proposed waiver based on all of the following criteria:

         (a)   The need for the waiver is caused by unique site conditions, the use of or conditions on the property or surrounding properties, or other circumstance outside the control of the owner/lessee, including easements and rights-of-way;

         (b)   The waiver, if approved, will generally meet the spirit and intent of the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, applicable Zoning Code requirements, other adopted city plans and policies, and all applicable requirements in §§ 153.045 through 153.048;

         (c)   The waiver is not being requested solely to reduce cost or as a matter of general convenience;

         (d)   The waiver, if approved, will ensure that the development is of equal or greater development quality with respect to design, material, and other similar development features than without the waiver;

         (e)   The requested waiver is better addressed through the waiver rather than an amendment to the requirements of this chapter; and

         (f)   The waiver does not have the effect of authorizing any use that is not otherwise permitted in the applicable zoning district.

   (I)   Administrative Departures.

      (1)   Purpose and applicability.

         (a)   The intent of the Administrative Departure (AD) is to provide an efficient process to allow minor deviations from the strict application of the Code requirements caused by unusual site or development conditions or conditions unique to a particular use or other similar conditions that require reasonable adjustments, while remaining consistent with the intent of this chapter.

         (b)   The AD shall not convey special rights or other approvals that would not otherwise result from a decision under this Code.

      (2)   Administrative Departure defined. An AD shall be limited to any modification of no greater than 10% to a numeric zoning standard related to building dimensions, lot dimensions or coverage, open space, landscaping, parking, fencing, walls, screening, or exterior lighting.

      (3)   Review procedure.

         (a)   An application for an AD shall be made in accordance with the provisions of divisions (I)(5) and (M)(1) of this section.

         (b)   The PZC shall be the required reviewing body for administrative departures.

         (c)   A request for an AD may be submitted with an application for an FDP, MP, or at any other time as may be necessary.

         (d)   A request for an AD may be processed simultaneously with an FDP or MP to which it relates.

         (e)   The Director shall make a recommendation to the PZC for approval, approval with conditions, or denial of the AD under the criteria of division (I)(5) of this section.

         (f)   The PZC shall determine whether each requested AD is approved, approved with conditions, or denied. A written record of the PZC’s decision will be provided.

         (g)   Should the PZC find that the request does not meet the criteria for an AD, the applicant may request a waiver under the provisions of division (H) of this section or submit a new application for an FDP or MP, as applicable.

      (4)   Submittal requirements. It is the intent of these regulations that an application for an AD provides sufficient information to evaluate whether the request should be granted under divisions (I)(2) and (I)(5) of this section. The information should be sufficiently detailed to enable the required reviewing body to understand the existing site, proposed AD, and the related FDP or MP for the proposed project or a portion thereof. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (5)   Review criteria. The PZC shall make its decision on the requested AD based on the following criteria:

         (a)   The need for the AD is caused by unique site conditions, conditions on surrounding properties, and/or otherwise complies with the spirit and intent of the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, applicable Zoning Code requirements, other adopted city plans and policies, and all applicable requirements within §§ 153.045 through 153.048;

         (b)   The AD is not being requested simply to reduce cost or as a matter of general convenience;

         (c)   The AD does not have the effect of authorizing any use, sign, building type, or open space type that is not otherwise permitted in the applicable zoning district;

         (d)   The AD, if approved, does not adversely impact the pedestrian experience; and

         (e)   The AD, if approved, will ensure that the development is of equal or greater development quality with respect to design, material, and other development features than without the AD.

   (J)   Master Sign Plan.

      (1)   Purpose and applicability.

         (a)   The purpose of the Master Sign Plan (MSP) is to define the scope, character, and aesthetic quality of signs and sign regulations for an individual tenant, multi-tenant building, or multi-building development; while allowing an additional degree of flexibility and creativity in sign design and display.

         (b)   The MSP review is intended to confirm the proposed sign design or comprehensive sign plan is consistent with the development context, architectural character, the Dublin Corporate Area Plan, and the MUR Design Guidelines. MSPs are not intended to permit larger or more visible signs and are not intended to permit a greater number of signs without consideration of the MUR Design Guidelines.

         (c)   The MSP allows the PZC the means to evaluate the proposal for its consistency with §§ 153.045 through 153.048; the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, and other adopted city plans, and the review criteria, and to consider the proposal within the context of existing and planned development within the vicinity of the project boundary.

      (2)   Review procedure.

         (a)   An application for an MSP shall be submitted in accordance with the provisions of divisions (J)(4) and (M)(1) of this section.

         (b)   The PZC shall be the required reviewing body for MSPs in the MUR Zoning Districts.

         (c)   The Director shall make a recommendation to the PZC for approval, approval with conditions, or denial of the MSP application under the criteria of division (J)(4) of this section. The Director’s recommendation shall be provided prior to the respective public hearing.

         (d)   The PZC shall review the MSP application and the recommendation of the Director, and render its decision based on the criteria of division (J)(4) of this section for approval, approval with conditions, or denial. A written record of the Commission’s decision shall be provided.

         (e)   The applicant may request additional review meetings with the PZC.

      (3)   Submittal requirements. It is the intent of these regulations that the MSP shall indicate general information, sign design standards, and the area of applicability. Information submitted should be comprehensive enough to enable the PZC to understand the existing site and design concept for the proposed MSP. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (4)   Review criteria. The PZC shall render its feedback on an application for an MSP based on each of the following criteria and the recommendation of the Director.

         (a)   The MSP is consistent with the Community Plan, the Dublin Corporate Area Plan, the MUR Design Guidelines, applicable Zoning Code requirements, and other adopted city plans and policies;

         (b)   The proposed signs are appropriately sited and scaled to create a cohesive character that complements the surrounding environment and meets the intent of the requirements of § 153.047, Site Development Standards and the MUR Design Guidelines; and

         (c)   The proposed signs are not in conflict with public streets, open spaces, utilities, or rights-of-way, and do not impede the continued provision of services required by the city or other public agency.

   (K)   Administrative Approvals.

      (1)   Purpose and applicability.

         (a)   The Director may authorize an Administrative Approval (AA) to an approved FDP or MP that is required to correct any undetected errors or omissions, address conditions discovered during the permitting process or construction, or that is necessary to ensure orderly and efficient development.

         (b)   Any approved AA must be consistent with the intent of the related approved FDP or MP.

         (c)   The Director may also authorize an AA to existing structures and associated site improvements that are necessary to complete ordinary maintenance, refurbishment, or Zoning Code compliance.

      (2)   Administrative Approval defined. The following are considered AA’s:

         (a)   Adjustments to lot lines;

         (b)   Adjustments to the location and layout of parking lots;

         (c)   Adjustments of up to 10% in total building floor area or floor plan;

         (d)   Adjustments to building height up to 10% for no more than 10% of the floorplate of the highest occupied floor when necessary, to accommodate building equipment or features required to comply with building code;

         (e)   Substitution of landscaping materials specified in the landscape plan;

         (f)   Redesigning and/or relocating stormwater management facilities;

         (g)   Relocating fencing, walls, or screening (not including screening walls);

         (h)   Modifications to sign location, sign face, landscaping, and lighting;

         (i)   Changes in building material or color;

         (j)   Changes required by outside agencies such as the county, state, or federal departments; and/or

         (k)   Other modifications deemed appropriate by the Director that do not alter the basic design or any specific conditions imposed as part of the original approval.

      (3)   Review procedure.

         (a)   An application for an AA shall be made in accordance with the provisions of divisions (K)(4) and (M)(1) of this section.

         (b)   The Director shall be the required reviewing body for applications for an AA.

         (c)   The Director shall review the request after receiving a complete application and make a decision to approve, approve with conditions, or deny an AA application under the criteria of division (K)(5) of this section. The Director’s decision shall be provided to the applicant in writing.

         (d)   The Director may forward any AA application to the PZC for consideration. In making such a determination, the Director shall conclude that the application raises complex issues, including that the proposal is of such magnitude that it has a detrimental effect on the approved development or there are neighborhood or community-wide effects that may result if the proposal is approved, that would benefit from a public review and decision by the PZC.

         (e)   If denied, or approved with conditions, the applicant shall be given the opportunity to revise the request in response to the Director's comments and resubmit for further consideration.

         (f)   Requests not meeting the requirements for an AA shall require the filing and approval of a new application for an FDP, MP, or other application as applicable, in accordance with this section.

         (g)   Decisions by the Director may be appealed to PZC.

      (4)   Submittal requirements. It is the intent of these regulations that an application for an AA provides sufficient information to ensure general conformity to the applicable provisions of this Code and the approved FDP or MP, and to evaluate whether the AA should be granted under division (K)(2) and (K)(5) of this section. The information should be sufficiently detailed to enable the Director to understand the existing site and the AA request for the proposed project or a portion thereof. The applicant shall submit an application and supplemental materials as outlined in division (M)(1) of this section and determined by the Director.

      (5)   Review criteria. The Director shall make his or her decision on an application for a proposed AA based on all of the following criteria:

         (a)   Adjustments to lot lines do not create additional lots and required setbacks are maintained, and the boundaries to any approved FDP or MP are not altered;

         (b)   Adjustments to the location and layout of parking lots maintain the perimeter setbacks, yards, buffers, and required parking;

         (c)   Adjustments for buildings do not alter the character or the use of the originally approved building, building height(s), or floor plans except as provided for in division (K)(2) of this section;

         (d)   Substitution of landscaping materials shall be of an equal or greater size and quality as the approved materials;

         (e)   Redesigned and/or relocated stormwater management facilities shall maintain the approved general character of said facilities and the approved stormwater capacities;

         (f)   Relocating fencing, walls, or screening (not including screening walls) shall maintain the same level and quality of materials and screening;

         (g)   Modifications to sign location, sign face, and related landscaping and lighting, shall maintain the approved general sign design, number of signs, and dimensional requirements;

         (h)   Changes in building material shall be similar to and have the same general appearance comparable to previously approved material; such changes shall be of equal or higher quality than the previously approved material;

         (i)   Changes in color shall be complementary to the architectural design and character of the building;

         (j)   The modification is not being requested solely to reduce cost or as a matter of general convenience; and

         (k)   The requested modification would be better addressed through the modification rather than an amendment to the requirements of this chapter or to the approved FDP or MP.

   (L)   Other applicable approvals.

      (1)   Conditional uses. The conditional use approval procedures in § 153.236 shall apply in the MUR Zoning Districts. The PZC is the required reviewing body for conditional use applications.

      (2)   Zoning map or text amendment. The amendment procedures of § 153.234 shall apply in the MUR Zoning Districts. In addition, a recommendation from the Director shall be submitted for consideration by the PZC and City Council.

      (3)   Preliminary and final plats. Reviews of preliminary and final plats shall be governed by Chapter 152 of the Dublin Code of Ordinances.

      (4)   Special permit. The special permit procedures in § 153.231(G) shall apply in the MUR Zoning Districts.

      (5)   Zoning variance. The zoning variance procedures in § 153.231(H) shall apply in the MUR Zoning Districts. In addition, a recommendation from the Director shall be submitted for consideration by the Board of Zoning Appeals, and for City Council in the instance of a use variance.

      (6)   Public tree permit. The tree permit requirements of § 153.134(G) shall apply in the MUR Zoning Districts.

   (M)   General provisions.

      (1)   Applications.

         (a)   Each application required by this section shall be made in writing on a form provided by the city and shall be accompanied by the fee as established by City Council.

         (b)   Applications shall include all information required by the city, unless deemed unnecessary by the Director based on the nature and scale of the proposed development. No application shall be accepted and processed by the city until it is deemed complete by the Director. If found to be incomplete, the Director shall inform the applicant of any additional materials required to certify that the application is complete.

         (c)   After acceptance of a complete application, the Director and/or required reviewing body may request additional materials if deemed necessary to evaluate the proposal.

         (d)   No application for an FDP that has been denied by the PZC shall be resubmitted for a period of one year from the date of the decision, unless permitted by the Director after a demonstration by the applicant of a change of circumstances from the previous application that may reasonably result in a different decision.

         (e)   The Director may approve the simultaneous review of applications required by this chapter and/or a subdivision plat required by the Code if the Director determines that simultaneous review will not adversely impact the achievement of the purpose and intent of this chapter.

         (f)   Where public reviews are required by this chapter, a written notice of the public meeting shall be sent, not less than ten days prior to the meeting, to the applicant, property owner, and owners of parcels of land within 300 feet of the subject parcel(s), as listed on the County Auditor's current tax list. The notice shall, at a minimum, indicate the property that is the subject of the request, describe the nature of the request, the time, date and location of the meeting at which the application will be considered, and indicate when and where written comments will be received concerning the request.

      (2)   Decisions.

         (a)   Any application required to be reviewed under this section shall be approved, approved with conditions, or denied by the required reviewing body based on the applicable review criteria as provided in this section and other applicable provisions of this chapter. The recommending body and required reviewing body shall state the reasons for their decisions in the minutes and provide a written record of the decision.

         (b)   Prior to reaching a decision, if the required reviewing body determines that an application does not meet the applicable review criteria as provided in this section and other applicable provisions of this chapter, but determines that the application could meet those criteria with modifications that could not be reasonably conditioned, the applicant may request that the decision on the application be postponed to provide the opportunity to make those modifications.

         (c)   Following the approval of an FDP or MP, the applicant may proceed with the process for obtaining a Certificate of Zoning Plan Approval (CZPA) and Building Permit (BP), consistent with the approval as granted. All construction and development under any BP shall comply with the approved FDP and MP, and any other approval, as applicable.

      (3)   Certificate of Zoning Plan Approval. A CZPA issued by the Director verifying compliance with all applicable zoning requirements is required prior to modification, extension, or alteration of sites and structures, and/or change of use in MUR Zoning Districts.

      (4)   Duration of approvals.

         (a)   An approved Concept Plan shall be valid for a period of no more than one year. If an application has not been filed for an FDP for at least a portion of the site within that two-year period, then the Concept Plan shall no longer be valid. A new Concept Plan application shall be required in accordance with the requirements of this chapter.

         (b)   An approved FDP shall be valid for a period of no more than two years. If a Building Permit and/or CZPA has not been filed for at least a portion of the project within the two-year period, the FDP shall no longer be valid. A new FDP application shall be required in accordance with this chapter.

         (c)   An approved MP shall be valid for a period of no more than two years. If a Building Permit and/or CZPA for at least one portion of the site has not been filed within that two-year period, then the MP shall no longer be valid. A new MP application shall be required in accordance with this chapter.

         (d)   Abandonment.

            1.   Once a final approval is granted by the required reviewing body, if the Director of Building Standards determines that work has been abandoned for a continuous period of six months, the approval shall lapse and cease to be in effect.

            2.   The Director of Building Standards shall make the determination of abandonment based on the presence of one or more of the following conditions:

               A.   Removal of construction equipment or supplies;

               B.   Expiration of an active building permit issued by the city;

               C.   Evidence of a failure to maintain the property, such as overgrown weeds, failure to secure buildings, broken windows, or other evidence of lack of maintenance;

               D.   Other actions documented by the Director of Building Standards and/or Director evidencing an intent to abandon the construction of the project.

            3.   Once the Director of Building Standards makes a determination of abandonment, if a new application is not submitted within 90 days from the date of the determination, the owner shall restore the site to its previous condition, and/or remove any structures or other evidence of work on the site, within 180 days from the date of the determinat ion of abandonmen t. If the owner fails to restore the site to its previous condition within 180 days, the city may take any and all actions necessary to restore the site to its previous condition, including removing any structures or other evidence of work, and the costs of removal shall be assessed against the property.

(Ord. 86-21, passed 12-6-21)

PLANNED DEVELOPMENT DISTRICTS

§ 153.050 PURPOSE AND APPLICATION.

   (A)    Purpose. The Planned Developmen t District (PD) regulation s are based on the premise that the ultimate quality of a built environmen t or developmen t proposal is determined not only by the type, character and allocation of land uses but also by the way in which such land uses are executed. In many cases, the subdivision regulations and standard zoning district regulations and procedures do not adequately regulate the design of buildings or enable the range of uses in a single zoning district that are appropriate in the city. The Neighborhood Design Guidelines shall be considered with new residential development to ensure the design details meet the desired neighborhood quality.

      (1)   The purposes of the Planned Development District regulations are to:

         (a)   Provide an opportunity for a mix of land uses otherwise not permitted within the standard municipal zoning district classifications.

         (b)   Allow the creation of development standards that respect the unique characteristics, natural quality and beauty of the site and the immediate vicinity and protect the community's natural resources by avoiding development on, and destruction of, sensitive environmental areas.

         (c)   Enable greater review of design characteristics to ensure that the development project is properly integrated into its surroundings and is compatible with adjacent development.

         (d)   Assure compatibility between proposed land uses within and around the Planned Development District through appropriate development controls.

         (e)   Pursue the housing and economic development goals of the city.

         (f)   Promote economical and efficient use of land and reduce infrastructure costs through unified development.

         (g)   Provide for supporting community facilities.

         (h)   Establish objective criteria for development plan review that ensure conformity to community and district standards and allow for consistent treatment throughout.

      (2)   The procedures established for Planned Development Districts are designed to encourage:

         (a)   Unified development projects that exhibit creative planning and design in ways that cannot be achieved through a standard zoning district or subdivision regulation, yet are consistent with all applicable plans, including but not limited to, the Community Plan, Thoroughfare Plan, infrastructure system, contiguous land uses, and the intent of the Zoning and Subdivision Code.

         (b)   Imaginative architectural design.

         (c)   Flexibility in building styles and types.

         (d)   Proper relationships between buildings, between developments and between structures and the land.

         (e)   The development of the land in an orderly, coordinated and comprehensive manner consistent with accepted land planning, landscape architecture practices and engineering principles according to approved development plans.

   (B)   Application. The Planned Development District regulations assist in accomplishing these purposes by establishing review steps that combine the request for a zoning with the development plan review process, and when applicable, the subdivision process. Subsequent plan review following the zoning amendment also requires simultaneous review of subdivision plats.

      (1)   Each Planned Development District shall be considered a separate and unique zoning district wherein a preliminary development plan, including associated text depicting the specific development standards, is adopted simultaneously with the amendment of the zoning map to apply the PD designation. The preliminary development plan shall apply only to the property within that particular Planned Development District.

      (2)   Planned Development Districts adopted and established in accordance with the provisions of this chapter and the requirements contained herein shall take precedence over any conflicting regulations contained in the Zoning Code and Subdivision Regulations.

   (C)   Ownership. The Planned Development District shall be an integrated, unified development project wherein the entire project area shall be in joint ownership or control at the time the application is made for the PD designation so that all property owners are applicants. Any transfer of land within the development resulting in ownership within the development by two or more parties after an application has been filed shall not alter the applicability of the regulations contained herein. A preliminary development plan approved in accordance with these or previous regulations for a Planned Development District shall be binding upon the owners, their successors and assigns and shall limit and control the issuance and validity of all certificates of zoning compliance.

(Ord. 75-03, passed 5-3-04; Am. Ord. 05-23, passed 3-27-23)

§ 153.051 STATUS OF PREVIOUSLY APPROVED PLANNED DEVELOPMENT DISTRICTS.

   (A)   Existing Planned Development Districts. Planned Development Districts and all associated development plans and supporting documentation adopted prior to the effective date of these Planned Development District regulations shall continue in effect and be considered legally conforming under this code. The procedures for the implementation of those developments must conform to the regulations indicated in this code. Such planned developments include:

      (1)   Planned Low-Density Residential Districts (PLR) and their development plans and all supporting documentation adopted pursuant to the Planned Low-Density Residential District regulations.

      (2)   Planned Commerce Districts (PCD) and their composite plans and all supporting documentation adopted pursuant to the Planned Commerce District regulations.

      (3)   Planned Industrial Park Districts (PIP) and their development plans and all supporting documentation adopted pursuant to the Planned Industrial Park District regulations.

      (4)   Planned Unit Development Districts (PUD) and their preliminary development plans and all supporting documentation adopted pursuant to the Planned Unit Development District regulations.

   (B)   Consistency of terms. For the purposes of this code, plans including all supporting documentation adopted at the time of rezoning shall be referred to as preliminary development plans, and plans including all supporting documentation approved subsequent to such rezoning shall be referred to as final development plans.

   (C)   Changes to preliminary development plans. A change to an adopted preliminary development plan shall be considered to be a zoning amendment and shall be reviewed according to the procedures set forth in § 153.053 and the plan approval criteria set forth in § 153.055.

   (D)   Final development plans.

      (1)   A final development plan shall be required for each phase of development in a Planned Development District, including the Planned Low-Density Residential Districts. If the construction drawings for a particular phase have already been approved as of the effective date of this subchapter, the completion and submission of a final plat in accordance with Chapter 152, Subdivision Regulations shall complete that portion of the project.

      (2)   An application for review of a final development plan for a Planned Development District established prior to the effective date of these Planned Development District regulations shall follow the procedural steps set forth in § 153.053, shall include the submission requirements set forth in § 153.054, and shall be evaluated according to the plan approval criteria set forth in § 153.055.

   (E)   Final subdivision plats. Applications for final subdivision plats for phases of Planned Development Districts that are yet to be approved or for changes to previously approved plats shall be reviewed according to the subdivision review procedures in Chapter 152, Subdivision Regulations.

(Ord. 75-03, passed 5-3-04)

§ 153.052 ESTABLISHMENT OF PLANNED DEVELOPMENT DISTRICT.

   (A)   Planned Development Districts adopted after the effective date of these regulations. A Planned Development District that is adopted after the effective date of these regulations shall be established according to the following:

      (1)   All rezonings to a Planned Development District shall be designated as Planned Unit Development Districts (PUD).

      (2)   A request for rezoning land to a Planned Unit Development District designation shall be made according to § 153.234.

      (3)   A preliminary development plan shall be reviewed by the Planning and Zoning Commission and City Council according to § 153.053 and a preliminary development plan and supporting documentation shall be adopted at the time of rezoning.

      (4)   Detailed final development plans shall be reviewed and acted upon by the Planning and Zoning Commission according to § 153.162.

      (5)   A preliminary subdivision plat may be reviewed simultaneously with a preliminary development plan. A final subdivision plat shall be reviewed simultaneously with a final development plan, unless a final plat has already been approved or is not required for completion of the project. All subdivision plats shall be reviewed and approved by the Planning and Zoning Commission according to Chapter 152, Subdivision Regulations, except as otherwise addressed in §§ 153.050 through §§ 153.056.

   (B)   General development criteria. A PUD shall be designed and depicted on the preliminary development plan and final development plan in accordance with the following general development criteria:

      (1)   Plan design. The proposed PUD shall be designed in accordance with accepted planning principles, including the planning and development principles included in this section, to ensure that the use of land, buildings and other structures; the building location, bulk, layout, arrangement, design, and height; the percentages of lot areas that may be occupied; the setback of buildings; the sizes of yards and other spaces; and the density of population are in compliance with the purposes and objectives of the PD regulations as set forth in § 153.050(A).

      (2)   Permitted and conditional uses. A PUD may include any combination of uses when such use(s) are found to be compatible with one another and in keeping with the intent of these general development criteria, provided the proposed location of the uses will not adversely affect adjacent property and/or the public health, safety and general welfare.

         (a)   The list of specific uses to be included in the proposed PUD shall be clearly delineated in the preliminary development plan and its supporting documentation.

         (b)   Uses shall be identified as either permitted uses or conditional uses.

         (c)   Listed uses shall be defined by their customary name or identification, except where they are specifically defined or limited in this Zoning Code.

         (d)   Any listed use may be limited to areas delineated in the preliminary development plan.

      (3)   Planning and development principles. The proposed PUD shall be designed in accordance with the following planning and development principles:

         (a)   Arrangement of use areas.

            1.   Buildings and uses within the proposed development shall be located to reduce any adverse influences and to protect and enhance the character of areas adjacent to the development;

            2.   Whenever a proposed development includes areas of a higher intensity than that permitted in adjacent areas, the location and arrangement of use areas shall include appropriate buffers, open spaces, setbacks, or other transitional areas to ensure compatibility with the lower intensity areas.

            3.   Buildings, structures and parking areas shall be designed and located within the PUD in ways that conserve environmentally sensitive or unique natural, historic, or cultural features, and minimize environmental impacts.

         (b)   Arrangement of buildings and yards.

            1.   The physical relationship of buildings and other site improvements to one another and the surrounding open space, as created by building size, mass, height, shape, and setback, shall result in a harmonious development within the PUD and adjacent to it.

            2.   The bulk and height of buildings within the proposed development shall be compatible with the surrounding development and sufficiently buffered from the surrounding development to mitigate any potential adverse impact(s).

         (c)   Landscaping, screening and buffering.

            1.   The pattern of landscaping shall be coordinated in design and type of materials, mounding and fencing used. Landscaping may vary in density, spacing and other treatments to reflect variations of topography, existing landscape or land uses.

            2.   Privacy for residential buildings shall be maintained through the use of landscaping, screening and buffering.

            3.   Appropriate buffer zones with adequate landscaping shall be provided between the proposed development and adjacent areas.

            4.   Alternative design approaches to meet the intent of the landscape regulations may be incorporated.

         (d)   Open space. Adequate open spaces shall be integrated throughout the development to meet the objectives of the Community Plan and shall comply with the open space requirements set forth in Chapter 152, Subdivision Regulations. PUDs that include residential uses shall include open space that is located and designed as follows:

            1.   Open space shall be sufficiently aggregated to create large useable areas of planned open space.

            2.   Open space shall conserve significant natural features within the PUD to the extent practicable.

            3.   Open space shall provide a scenic natural environment along existing public streets characterized by large building setbacks that enable the preservation of natural features.

            4.   All open space shall be easily accessible to residents of the PUD.

            5.   Where possible, open space areas shall be connected with open space areas on abutting parcels, and wherever possible, by open space corridors.

            6.   Stormwater features shall not count as open space, unless they achieve a superior, interactive design as outlined in the Neighborhood Design Guidelines.

            7.   Easements and required perimeter setbacks shall not count toward open space unless they are integrated into the overall open space framework pursuant to the Neighborhood Design Guidelines.

         (e)   Protection of natural features.

            1.   Trees shall be preserved, protected, and replaced in compliance with the requirements set forth in §§ 153.140 through 153.148.

            2.   A riparian buffer shall be provided along the entire length and on both sides of a river or perennial stream channel. Walkways may be permitted to be located within riparian buffers when the Planning and Zoning Commission determines that such will create minimal change to the riparian buffer.

            3.   Floodplains shall be protected in compliance with § 153.111 and Chapter 151, Flood Control.

            4.   Wetlands that are to be retained in their natural state within the PUD shall be protected. A buffer area not less than 20 feet in width measured from the edge of the delineated wetland shall be provided along the entire perimeter of the designated wetland. The buffer area shall not be disturbed and shall be retained in its natural state. Minimum building and pavement setbacks to protect such wetlands and buffer areas shall be established and shall be measured from the edge of such wetlands.

         (f)   Pedestrian circulation systems. A pedestrian circulation system shall be included and designed to provide convenient and safe pedestrian access throughout the PUD, and to connect to neighboring developments and community facilities. The pedestrian circulation system may include sidewalks and other walkways not located along streets. Trails with public right of passage should be incorporated in the pedestrian circulation system.

         (g)   Bike paths and other trail systems. Trail systems for bikes and other purposes shall be included and designed in accordance with the city's plan for bike paths. Such trail system shall have a minimum width of eight feet and be properly buffered from any adjacent residential areas.

         (h)   Street design and vehicular circulation.

            1.   The proposed vehicular circulation system shall provide adequate connections to the existing street network.

            2.   The area of the project devoted to streets and related pavement should be the minimum necessary to provide adequate and safe movement and access.

            3.   Street alignments should be designed to conserve natural features and minimize the need for cut and fill practices.

            4.   The function of adjacent thoroughfares shall be maintained by limiting access points to the minimum needed, relating them to existing access points, the street patterns on surrounding development, the Thoroughfare Plan and the intensity of proposed uses.

            5.   Private streets as a common easement may be used to provide access to clustered lots and/or structures.

            6.   Street lighting and street signs shall be adequate for safety and security.

            7.   The applicant shall provide and construct on-site and off-site street improvements for the PUD in accordance with the requirements of Chapter 152, Subdivision Regulations and consistent with recommendations included in traffic studies and with any agreements submitted as supporting documentation for the PUD.

            8.   The design and locations of streets and parking areas shall comply with the requirements set forth in Chapter 53, Storm Water Management.

         (i)   Off-street parking. The layout of parking areas, service areas, and related entrances, exits, signs, lighting, noise sources or other potentially adverse influences shall be designed and located to protect the character of the area and as well as those areas adjacent to the development.

         (j)   Signs. All signs and graphics within the PUD shall be compatible in size, location, height, material, shape, color and illumination.

            1.   A sign plan for the entire PUD shall set forth the design parameters for the entire project to ensure a consistent and comprehensive character throughout the project. The sign plan shall include the design, layout, and dimensions of all ground, window and wall signs as well as distances from rights-of-way and the type and intensity of illumination.

            2.   Signs should contribute to an overall cohesive design, reflect simplicity, and avoid visual clutter.

            3.   The overall design and placement of buildings should take into account the general placement of signs so that all permanent signs and their associated lighting fixtures complement the appearance and architecture of the buildings and the PUD.

            4.   Ground signs should be designed to relate to and share common design elements with the building.

            5.   The materials and colors of the sign, sign background and sign frame should be compatible with the building's materials and colors.

         (k)   Utilities. The applicant shall provide and construct on-site and offsite water, sewer and other infrastructure improvements for the PUD in accordance with the requirements of Chapter 152, Subdivision Regulations and consistent with any agreements submitted as supporting documentation for the PUD.

      (4)   Project phasing. If the PUD is to be implemented in phases, each phase shall have adequate provision for access, parking, storm water management, utilities, and other public improvements to serve the development in accordance with the applicable criteria set forth above. Each phase shall be provided with temporary and/or permanent transitional features, buffers, or protective areas in order to prevent any adverse impact on completed phases, future phases, and adjoining property. Open space areas shall be reasonably proportioned in each phase of the project, and the proposed construction of any recreation facilities shall be clearly identified on a phasing plan.

      (5)   Common facilities. Common facilities and park areas, regardless of ownership, may be required to be maintained. Adequate access shall be provided at all times to vehicular traffic so that fire, police, health, sanitation, and public utility vehicles can serve the properties contiguous or adjacent thereto. All streets and roadways not dedicated to the public shall be operated and maintained at no expense to any governmental unit.

   (C)   Compliance with existing development standards. Unless otherwise stated and varied in the development standards text, the standards contained in the Dublin Zoning Code that pertain to the specific uses or land development in the PUD shall be applicable. Such standards include, but are not limited to:

      (1)   Floodplain protection set forth in § 153.111 and Chapter 151, Flood Control.

      (2)   Landscaping requirements set forth in §§ 153.130 through 153.139.

      (3)   Tree preservation, protection and replacement requirements set forth in §§ 153.140 through 153.148.

      (4)   Sign regulations set forth in §§ 153.150 through 153.164.

      (5)   Off-street parking and loading requirements set forth in §§ 153.200 through 153.212.

      (6)   Subdivision requirements set forth in Chapter 152, Subdivision Regulations.

      (7)   Provisions of the Residential Appearance Code, § 153.190.

      (8)   Requirements for storm water management set forth in Chapter 53, Storm Water Management.

   (D)   Unique requirements and guidelines for PUD. Requirements and guidelines that are necessary to ensure that the proposed PUD complies with the intent of these Planned Development District regulations shall be clearly delineated in the development standards text submitted as part of the preliminary development plan. Elements of the development standards text shall include:

      (1)   All requirements that are necessary to ensure the PUD is consistent with the Community Plan and compatible with the surrounding development, including, but not limited to:

         (a)   The list of permitted and conditional uses;

         (b)   The maximum density for each use area;

         (c)   Standards for the protection of natural features;

         (d)   The major vehicular, pedestrian and bike circulation system;

         (e)   Setbacks and buffer standards for the perimeter of the PUD district and between subareas and differing land uses; and

         (f)   Any unique development standards or other standards that are determined essential for the project.

      (2)   All other provisions that set forth the methods for complying with the general development criteria set forth in § 153.052(B).

(Ord. 75-03, passed 5-3-04; Am. Ord. 05-23, passed 3-27-23)