The URL can be used to link to this page

Ordinance 014-15RECORD OF ORDINANCES Wvton L.cgal Blank. Inc 14 -15 Passed Farm No 30043 Ordinance No. DETERMINING THE SUFFICIENCY OF THE PETITION TO ESTABLISH THE BRIDGE PARK NEW COMMUNITY AUTHORITY, AUTHORIZING THE EXECUTION OF SUCH PETITION BY THE CITY AS A PROXIMATE CITY, SETTING A DATE FOR A PUBLIC HEARING UNDER CHAPTER 349 OF THE OHIO REVISED CODE, AND DECLARING AN EMERGENCY 20 WHEREAS, pursuant to Chapter 349 of the Ohio Revised Code, a petition (the "Petition's for the establishment of the Bridge Park New Community Authority (the "Authority') was filed with this Council and the Clerk of the Franklin County Board of County Commissioners by Crawford Hoying Development Partners, Ltd. ("Crawford Hoying'j on February 17, 2015; and WHEREAS, the City of Dublin (the "City's is the "proximate city" for the Authority, as that term is defined in Section 349.01(M) of the Ohio Revised Code; and WHEREAS, the "organizational board of commissioners," as that term is defined in Section 349.01(F) of the Ohio Revised Code, for the proposed Authority is comprised solely of this City Council (the "Council's of the City; and WHEREAS, pursuant to Section 349.03(A) of the Ohio Revised Code, this Council, as the organizational board of commissioners, upon the filing of the Petition must determine whether the Petition is sufficient and complies with the requirements of Section 349.03 of the Ohio Revised Code; and WHEREAS, pursuant to Section 349.03(A) of the Ohio Revised Code, this Council, as the organizational board of commissioners, upon the determination that a sufficient petition has been filed, must fix a time and place of a hearing on the Petition not less than thirty (30) days or more than forty-five (45) days from the date of the filing of the Petition; NOW, THEREFO , BE IT ORDAINED by the Council of the City of Dublin, State of Ohio, of the elected members concurring that: Section 1 . This Council hereby deems the Petition executed on behalf of the City, and authorizes and ratifies the execution of the Petition by the City Manager on behalf of the City, as the proximate city for the establishment of the Authority. S ection 2. This Council has examined the Petition and finds and determines that the Petition is sufficient and complies as to form and substance with the requirements as set forth Section 349.03(A) of the Revised Code and has been executed by all proximate cities. Section 3. A public hearing on the Petition shall be held on Thursday, March 19, 2015 at 6:30 p.m. at the offices of the City, 5200 Emerald Parkway, Dublin, Ohio 43017. The Clerk of Council shall inform the Clerk of the Franklin County Board of Commissioners of the time and place of that public hearing and shall arrange for notice of that public hearing by publication once each week for three consecutive weeks in a newspaper of general circulation in Franklin County pursuant to Section 349.03(A) of the Revised Code. RECORD OF ORDINANCES 17'dp�oR Up- 131-k, Inc Fomi No 30043 14 -15 Page 2 of 2 Ordinance No. Ptasved 'U Section 4 . This Council finds and determines that all formal actions of the Council concerning and relating to the adoption of this Ordinance were taken in an open meeting of this Council and that all deliberations of this Council and of any committees that resulted in those formal actions were in meetings open to the public in compliance with the law. Section 5. This Ordinance is declared to be an emergency measure necessary for the immediate preservation of the public peace, health, safety or welfare, and for the further reason that approving the establishment of the Authority is necessary for the advancement of the redevelopment of the Bridge Street corridor. Therefore, this Ordinance shall take effect immediately upon passage. Passed this 17111 day of Y U 2015. J Mayor — Presiding bfficer ATTEST: Clerk of Council BEFORE THE CITY COUNCIL OF THE CITY OF DUBLIN, OHIO PETITION FOR ESTABLISHMENT OF THE BRIDGE PARK NEW COMMUNITY AUTHORITY AS A NEW COMMUNITY AUTHORITY UNDER OHIO REVISED CODE CHAPTER 349 Submitted By: CRAWFORD HOYING DEVELOPMENT PARTNERS, LTD. As the Developer 8178133v8 TABLE OF CONTENTS PETITION ........................................................................................ ............................... APPROVAL OF THE CITY OF DUBLIN .................................... ............................... MAP OF DISTRICT ........................................................................ ............................... LEGAL DESCRIPTIONS OF REAL PROPERTY COMPRISING DISTRICT .......... ZONING FOR DISTRICT .............................................................. ............................... PROPOSED COMMUNITY FACILITIES ..................................... ............................... PRELIMINARY ECONOMIC FEASIBILITY ANALYSIS .......... ............................... FINANCIAL PLAN ......................................................................... ............................... DEVELOPER'S MANAGEMENT CAPABILITY ........................ ............................... ......... TAB 1 ......... TAB 2 EXHIBIT A EXHIBIT B EXHIBIT C EXHIBIT D EXHIBIT E .EXHIBIT F EXHIBIT G 8178133v8 BEFORE THE CITY COUNCIL OF THE CITY OF DUBLIN, OHIO PETITION FOR ESTABLISHMENT OF THE BRIDGE PARK NEW COMMUNITY AUTHORITY AS A NEW COMMUNITY AUTHORITY UNDER OHIO REVISED CODE CHAPTER 349 Pursuant to Ohio Revised Code Chapter 349 (the "Act "), Crawford Hoying Development Partners, Ltd. (the "Developer "), in its capacity as a "developer" as defined in Section 349.01(E) of the Ohio Revised Code, hereby makes and files this petition (the "Petition ") with the Clerk of the Board of County Commissioners of Franklin County, Ohio (as required by Section 349.03(A) of the Ohio Revised Code) and with the City Council of the City of Dublin, Ohio (the "City "), as the organizational board of commissioners under Section 349.01(F) of the Ohio Revised Code (the "City Council "), in order to initiate proceedings for the establishment of a new community authority (the "Authority ") and for the new community district described in Section 3 below (the "District "). The Developer further states as follows: Section 1 Name of the Proposed Authoritv The Authority shall be named the "Bridge Park New Community Authority." Section 2 Principal Office of the Proposed Authoritv The principal office of the Authority shall be located at 555 Metro Place North, Suite 600, Dublin, Ohio 43017 until such time as the Developer no longer owns property in the District or the board of trustees of the Authority determines another location for the principal office of the Authority. Section 3 Map; Full and Accurate Description of the Proposed District A full and accurate description of the boundaries of the District is attached hereto in the form of a map as Exhibit A , and the legal descriptions for the parcels comprising the District are attached hereto as Exhibit B . As indicated in the map, all of the real property comprising the District is developable as one functionally interrelated community and is owned or controlled, through leases of at least seventy -five years' duration, options, or contracts to purchase by the Developer. Section 4 Zoning for the Proposed District The current plans for the development of the proposed District comply with the applicable zoning regulations, including Sections 153.057 through 153.066 of the Bridge Street Corridor Development Code, a certified copy of which is attached hereto as Exhibit C . 8178133v8 -1- Section 5 Current Plans for the Development of the Proposed District The current plans for the development of the proposed District, indicating the proposed "new community development program," as defined in the Act, are provided below and in certain Exhibits attached to this Petition (collectively, the "Development Program "). The Development Program outlines the general program for the development of the District, and includes (a) the land acquisition and land development activities to be undertaken within the area including the District, (b) the acquisition, construction, operation, and maintenance of community facilities and other public infrastructure improvements for the District (the "Community Facilities "), (c) the provision of District services to be undertaken by the Authority, (d) the proposed method of financing such Community Facilities and District services, (e) the projected total employment within the District, and (f) the projected total population of the District. The development of the area included in the proposed District is being described as the "Bridge Park Development" and will include the construction of retail, commercial, residential and recreational facilities. Additional information about the plans for the Bridge Park Development are available at the City's office of Land Use & Long Range Planning, 5800 Shier Rings Road, Dublin, Ohio 43016. a. Development Program, Including Land Acquisition and Land Development The Development Program does not contemplate that the Authority would undertake any plans for the acquisition of real property and interests in real property other than the acquisition of fee interests, easements, rights -of -way, licenses, leases and similar property interests necessary to complete the Community Facilities. b. Plan for Communitv Facilities The Community Facilities shall include all real property, buildings, structures, or other facilities, including related fixtures, equipment, and furnishings, to be owned, operated, financed, constructed, and maintained under the Act. As provided in the Act, the Community Facilities consist generally of (i) any real property, buildings, structures, or other facilities, including related fixtures, equipment, and furnishings, to be owned, operated, financed, constructed, and maintained, including public, community, village, neighborhood, or town buildings, centers and plazas, auditoriums, recreation halls, educational facilities, recreational facilities, natural resource facilities, including parks and other open space land, lakes and streams, cultural facilities, community streets, pathway and bikeway systems, pedestrian underpasses and overpasses, lighting facilities, design amenities, or other community facilities, and buildings needed in connection with water supply or sewage disposal installations or steam, gas, or electric lines or installation; and (ii) any community facilities that are owned, operated, financed, constructed, or maintained for, relating to, or in furtherance of community activities, including, but not limited to, town buildings or other facilities, and off - street parking facilities. 8178133v8 -2- Specifically, it is presently anticipated that the Community Facilities will include the facilities described in Exhibit D attached hereto. c. Provision of District Services The Authority is authorized to provide services within the District, including, but not limited to, landscaping, street and sidewalk cleaning and maintenance, maintenance of parking facilities, and any other community improvement services. d. Method of Financing The Developer proposes to finance the construction of certain of the Community Facilities through the issuance of one or more series of bonds, notes issued in anticipation of the issuance of bonds, or bonds issued to refund such bonds or notes (the "Bonds "), either by the Authority or another entity, including the Columbus - Franklin County Finance Authority (the "Finance Authority "). The Bonds will be secured (i) through the levy and collection by the Authority of a "community development charge," as defined in the Act (the "Community Development Charge "), that the Authority expects to levy on certain parcels within the District, and (ii) through service payments in lieu of taxes (the "TIF Service Payments ") generated through a tax increment financing program that is expected to be implemented by the City with respect to certain parcels within the District. The development plan for the property to be located in the District includes the proposed creation of a community reinvestment area overlaying the District and additional property, as determined by the City, which would provide for a 15- year, 100% real property tax exemption pursuant to Section 3735.65, et seq., of the Ohio Revised Code (the "Tax Abatement") for certain property within the District. While the Tax Abatement is in place, the Community Development Charge will serve as the primary source of security for the payment of (a) the annual debt service charges on the Bonds ( "Bond Debt Service "), (b) operating, maintenance and administrative expenses of the Authority ( "O &M "), and (c) a payment to the City as a contribution toward the cost of infrastructure improvements that the City is expected to undertake in connection with the development of the District and for other lawful purposes (the "City Contribution" and, together with the Bond Debt Service and O &M, the "Annual Amount "). Upon the expiration of the Tax Abatement, the TIF Service Payments will serve as the primary source of funds to pay the amounts described in the preceding sentence, and the Community Development Charge will serve as the secondary source of payment to the extent that the TIF Service Payments are insufficient to cover the Annual Amount. There may also be a component of the Community Development Charge that is determined on the basis of gross receipts of restaurants and other retail, excluding any use that is predominantly grocery, operating in the District, in an amount not greater than ' / %, and a Community Development Charge that is determined on the basis of gross receipts of hotels operating in the District, in an amount not 8178133v8 -3- greater than 1 %. These amounts would be collected by an independent collection agent engaged by the Authority and would be used to pay the Annual Amount. e. Projected Total Employment within the District All of the above - described Community Facilities will benefit the businesses in the District and will result in a projected total employment of approximately 1,600 individuals within the District. f Projected Total Population of the District All of the above- described Community Facilities will benefit a projected total population of approximately 1,650 residents within the District. Section 6 Board of Trustees of the Proposed Authoritv The Developer recommends that the number of members of the board of trustees of the Authority (the `Board ") be comprised of 7 members selected as provided in Section 349.04 of the Ohio Revised Code. a. Appointment of Members of the Board The City Council, as the organizational board of commissioners under Section 349.01(F) of the Ohio Revised Code, shall appoint 3 citizen members of the Board to represent the interests of present and future employers, within the District and any present and future residents of the District and 1 member to serve as a representative of local government. The Developer shall appoint 3 members to serve on the Board as representatives of the Developer. b. Replacement of Members of the Board The Developer recommends that, pursuant to Section 349.04(C), members of the Board be selected as follows: 1. While any Bonds are outstanding, the methodology for replacement of members of the Board be as follows: A. City Council, as the organizational board of commissioners under Section 349.01(F) of the Ohio Revised Code, shall continue to appoint replacement citizen members of the Board and the representative of local government upon the expiration of that member's term or resignation by that member unless the City determines, by resolution of City Council, that such citizen members of the Board and the representative of local government shall be elected in the manner prescribed by Sections 349.04(A) and (C) of the Ohio Revised Code; B. The Developer shall continue to appoint replacement representatives of the Developer to the Board upon the expiration of that member's term or resignation by that member unless the Developer determines, by delivering notice to the City, that such members of the Board 8178133v8 -4- shall be elected in the manner prescribed by Section 349.04(B) of the Ohio Revised Code; and 2. After the Bonds are no longer outstanding, members of the Board shall be elected in accordance with the provisions of Section 349.04 of the Ohio Revised Code. Section 7 Preliminary Economic Feasibility Analysis for the Proposed Authority The preliminary economic feasibility analysis is provided below and in certain Exhibits attached to this Petition. The preliminary economic feasibility analysis examines (a) development patterns and demand factors of the area including the District, (b) the location and size for the proposed District, (c) the present and future socio- economic conditions of the area including the District, (d) a description of the public services to be provided with respect to the area including the District, (e) a financial plan with respect to the area including the District, and (f) a description of the Developer's management capability. a. Development Patterns and Demand Factors of District The current land use of the area within and without the District is vacant land, primarily vacant commercial buildings, and service uses. The proposed future land use of the District will be a multi -use development consisting of new business, commercial, retail and residential facilities. Demographic and development information related to certain areas within and without the District are attached hereto as Exhibit E b. Location and Size of Proposed District The District is located in the City as more fully shown in Exhibit A and described in Exhibit B . The size of the proposed District is approximately 28.89 acres. c. Public Services Provision All law enforcement services within the District shall be provided by the City of Dublin. All fire and emergency medical services shall be provided by Washington Township. Roadways and utilities will be provided by the applicable public or utility entities. All public education services shall be provided by the Dublin City School District and the Tolles Career and Technical Center. d. Preliminary Economic Feasibilitv Analysis A preliminary economic feasibility analysis for development of the District, including the area development pattern and demand, and present and future socio- economic conditions of the area including the District is attached hereto as Exhibit E . e. Financial Plan A preliminary financial plan for the development and the District is attached hereto as Exhibit F . f Developer's Management Capability A description of the management capability of the Developer is attached hereto as Exhibit G . 8178133v8 -5- Section 8 Environmental Statement The Authority and the Developer shall comply with all applicable environmental laws and regulations with respect to the District. The Developer has previously undertaken Phase I Environmental Property Assessments related to a majority of the parcels to be located within the District. Section 9 Provisions Regarding This Petition For the purposes of the establishment of the Authority, the City is the only city that can be defined as a "proximate city" as that term is defined in Section 349.01(M) of the Ohio Revised Code. Exhibits A B C D E F and G attached hereto, are hereby incorporated as part of this Petition. Words and terms not defined herein shall have the meanings given in Section 349.01 unless the context requires a different meaning. The Developer hereby requests the City Council, as the organizational board of commissioners under Section 349.01(F) of the Ohio Revised Code, to determine that this Petition complies as to form and substance with the requirements of Section 349.03 of the Ohio Revised Code and further requests that the members of the City Council fix the time and place of a hearing on this Petition for the establishment of the Authority. Pursuant to Section 349.03(A) of the Ohio Revised Code, such hearing must be held not less than thirty nor more than forty -five days after the filing of this Petition with the Clerk of the Board of County Commissioners of Franklin County, Ohio. If the City Council approves the establishment of the Authority, the Developer further requests that the City Council make such determination effective upon the Developer filing a declaration of covenants and restrictions ( "Declaration ") against the real property comprising the District. [Signature Page Follows on Next Page] 8178133v8 -6- This Petition is filed with the Clerk of the Board of County Commissioners of Franklin County, Ohio and the City Council of the City of Dublin, Ohio on this 17 day of February, 2015. Respectfully submitted, CRAWFORD HOYING DEVELOPMENT PARTNERS, LTD. By: Name: �e,,ON YQt76r, Title: Ty'tr-AunL 8178133v8 SIGNATURE OF THE CITY OF DUBLIN AS PROXIMATE CITY The City of Dublin, Ohio, by Ordinance number 14 -15, adopted by the City Council of the City of Dublin, Ohio on February 17, 2015, attached hereto and incorporated herein by this reference, as a "proximate city" as that term is defined in Section 349.01(M) of the Ohio Revised Code, has approved the filing by Crawford Hoying Development Partners, Ltd., as the developer for purposes of Section 349.01(E), Ohio Revised Code, of the foregoing Petition for the establishment of the Bridge Park New Community Authority as a new community authority under Ohio Revised Code Chapter 349, and has authorized the execution of the Petition as the "proximate city." CITY OF DUBLIN, OHIO By: S , z� Printed Name: �Gl�� ,�. Title: �/ / n At Vez State of Ohio ) ) ss: County of Franklin ) On this 1 day of February, 2015, before me, a Nota Public in and for said County and State, personally appeared �d�.lA L. M4 x&- the CXN rAP -AWL of the City of Dublin, Ohio, who acknowledged that, with due authorization and as such officer on behalf of the City, that person did sign the foregoing instrument and the signing of that instrument is that person's voluntary act and deed individually as such officer and the voluntary and corporate act and deed of the City. In witness whereof, I have hereunto subscribed my name and affixed my official seal on the day and year aforesaid. '�W C CHRISTOPHER J. FRANZMANN Attorney at Law Notary Public, State of Ohio N EXHIBIT A MAP OF DISTRICT A -1 [This Page Intentionally Left Blank] f � I L 1 n o [Ell F F �T� o � v G f'1 f'1 [s7 0 eneineen • Nrveyors • Pbnnen • S<lentisb 5500 New Alba N Raab, Cdumb e, OH 13054 Ptwne:614.I15A500 DMI Flex e9 P5. emhtcom �S nor TU( IER Rn6 r _ u - Il d su m l i CITY OF DUBLIN, FIC NIadN COUNTY,OHIO EXHIBIT FOR BRIDGE PARK NEW COMMUNITY AUTHORITY DATE: Febroa" 17,2015 SCALE: AsNoted JOB NO.: 2013 -1481 b YY ssn��yns�nss� 2 ro d k�mmm'= Neugga CITY OF DUBLIN, FIC NIadN COUNTY,OHIO EXHIBIT FOR BRIDGE PARK NEW COMMUNITY AUTHORITY DATE: Febroa" 17,2015 SCALE: AsNoted JOB NO.: 2013 -1481 [This Page Intentionally Left Blank] EXHIBIT B LEGAL DESCRIPTIONS OF REAL PROPERTY COMPRISING DISTRICT C [This Page Intentionally Left Blank] LEGAL DESCRIPTION OF: PARCEL NO. 1 15.073 ACRES TAX PARCEL I.D: 273 - 012471 PER DESCRIPTIONS ON FOLLOWING PAGES: 15.097 ACRE TRACT EXEMPTING THEREFROM A 0.024 ACRE TRACT AS CONVEYED TO THE CITY OF DUBLIN 15.097 ACRES Situated in the State of Ohio, County of Franklin, City of Dublin, lying in Quarter Township 2, Township 2, Range 19, United States Military District, being 15,097 acres of the remainder of the 30.539 acre tract conveyed to Invictus Land Holding, LLC by deed of record in Instrument Number 200007070134979, being part of Lot No. 3 as shown on the plat entitled "Lands of Chauncey McGurer" of record in Plat Book 12, Page 27, (all references are to the records of the Recorder's Office, Franklin County, Ohio) and being more particularly described as follows: BEGINNING, FoR REFERENCE, at a magnetic nail previously set as shown in Plat Book 115, Pages 79 and 80 at the centerline intersection of John Shields Parkway (76 foot width) with Mooney Street (60 foot width) as dedicated in Plat Book 115, Pages 79 and 80; thence South 68° 26' 48" West, with the centerline of John Shields Parkway, a distance of 5 8. 10 feet, to a point; thence South 21° 33' 12" East, a distance of 38.00 feet, to an iron pin set in the southerly right -of -way line of John Shields Parkway, being the TRUE POINT of BEGINNING; thence North 68° 26' 48" East, with said southerly right -Gf - -way line, a distance of 115.12 feet, to an iron pin set; thence across said 30.539 acre tract, the following courses: South 24° 37' 39" West, a distance of 34.62 feet, to an iron pin set to a point on a curve; with the are of said curve to the right, having a central angle of 05° 05' 22 ", a radius of 532.50 feet, an arc length of 47.30 feet, and a chord bearing of South 16° 38' 50" East, a chord distance of 47.28 feet, to an iron pin set at a point on a non - tangent line; North 68° 26' 48" East, a distance of 34.54 feet, to an iron pin set to a point of curvature; with the arc of said curve to the right, having a central angle of 23 00' 57 ", a radius of 690.42 feet, an arc length of 277.34 feet, and a chord bearing of North 79° 57' 17" East, a chord distance of 275.48 feet, to an iron pin set on the westerly right -of -way line of Tuller Ridge Road (60 foot width) as dedicated in Plat Book 71, Page 60; thence with said westerly right -of -way line, the following courses: South 03' 26' 58" West, a distance of 46.79 feet, to a 3/4 inch iron pipe found at a point of curvature; with the arc of said curve to the left having a central angle of 28° 46' 59 ", a radius of 655.00 feet, an are length of 329.04 feet, and a chord bearing of South 10 56' 32" East, a chord distance of 325.60 feet, to an iron pin set at the northernmost comer of the 0.821 acre tract conveyed to The City of Dublin, Ohio by deed of record in [ nstrument Number 201212310201439 and at a point of reverse curvature, thence continuing with the westerly line of said 0.821 acre tract, the following courses: with the arc of said curve to the right, having a central angle of 28 58' 08 ", a radius of 370.00 feet, an arc length of 187.07, and a chord bearing of South 10 50' 57" East, a chord distance of 185.09 feet to an iron pin set at a point of tangency; South 03 38' 07" West, a distance of 374.03 feet, to an iron pin set at a point of curvature; with the arc of said curve to the left, having a central angle of 17 06' 36 ", a radius of 530.00 feet, an are length of 158.27 feet, and a chord bearing of South 04' 55' 11" East, a chord distance of 157.68 feet, to an iron pin set at a southwesterly comer thereof and in the northerly line of the remainder of the 6.202 acre tract conveyed to Dale Holding Co. of Columbus, LLG by deed of record in Instrument Number 200504120068206; thence North 86° 21' 53" West, with the southerly line of said 30.539 acre tract, said northerly line, the northerly line of the 1.200 acre tract conveyed to the Central Ohio Transit Authority by deed of record in Official Record 29294B09, the northerly line of FHIT, LLC by deed of record in Instrument Number 200707270131599, and the northerly line of the 1.318 acre tract conveyed to Peace Hanson, LLC by deed of record in Instrument Number 15.097 ACRES -2- 201006220077436 (passing a 3/4 inch iron pipe with an "RDZANDE" cap found at 22.64 feet and passing a 3/4 inch iron pipe found at 310.34 feet, being 0.37 feet southerly), a total distance of 707.03 feet, to an iron pin set at a southeasterly corner of the 12.884 acre tract conveyed to The City of Dublin, Ohio by deed of record in Instrument Number 201212310201439; thence with the easterly line of said 12.884 acre tract, the following courses: North 07° 18' 56" East, a distance of 195.56 feet, to an iron pin set at a point of curvature; with the arc of said curve to the left, having a central angle of 21° 18' 56 ", a radius of 1755.00 feet, an arc length of 652.91 feet, and a chord bearing of North 03° 20' 32" West, a chord distance of 649.15 feet, to an iron pin set; thence across said 30.539 acre tract, the following courses: North 68° 26' 48" East, a distance of 290.83 feet, to an iron pin set at a point on a curve; with the arc of a curve to the left having a central angle of 05 31' 06 ", a radius of 467.50 feet, an are length of 45.03 feet, and a chord bearing of North 15° 49' 06" West, a chord distance of 45.01 feet, to an iron pin set at a point of non - tangency; North 65 03' 55" West, a distance of 36.26 feet, to the TRUE POINT OF BEGINNING, containing 15.097 acres, more or Iess. Of the above described parcel, 0.003 acre lies within the I foot wide sidewalk easement as shown on Plat Book 115, Pages 79 and 80. Subject, however, to all legal rights -of -way and/or easements, if any, of previous record. Iron pins set} where indicated, are iron pipes, thirteen sixteenths (13/16) inch inside diameter, thirty (30) inches long with a plastic plug placed in the top bearing the initials EMHT INC. The bearings shown hereon are based on the Ohio State Plane Coordinate System South Zone as per NAD83 (1986 Adjustment). Control for bearings was from coordinates of monuments FRANK 73 and FRANK 74, having a bearing of South 73° 57' 18" East, established by the Franklin County Engineering Department. This description is based on an actual field survey performed by EMH &T in 2005 and 20013 and retraced under the direct supervision of Joshua M. Meyer, Registered Surveyor Number 8485 in April 2013, ..t11 EVANS, MECHWART, HAMBLETON & TILTON. INC. = / /lid ran / .� MEYFR a _ s-e4W o z a `- J Joshua M. Meyer 0 ,- �� -L� �- 15•o�l1 o 0��01 DESCIM10N vERME:D DRiNGI.E. P.Ei. P.s DA I NOW ed ,ty of Dublin S 1 .t a/3 Garg F Gundenllan, Planning Man ger Date PR•ELIl4il JARY �1PtR VAL N r FR NITY ENG N R G DATE:/ 6Y: 0.024 ACRE Situated in the State of Ohio, County of Franklin, City of Dublin, lying in Lot 16, Quarter Township 2, Township 2, Range 19, United States Military District, being a part of the 15.097 acre tract conveyed to Scioto Tuller Acquisition, LLC by deed of record in Instrument plumber 201308160140286, (all references are to the records of the Recorder's Office, Franklin County, Ohio) and being more particularly described as follows: BEGINNING, FoR REFERENCE, at a magnetic nail set marking the centerline intersection of John Shields Parkway (76 foot width), as dedicated in Plat Book 115, Pages 79 and 80, with Tuller Ridge Drive (60 foot width), as dedicated in Plat Book 71, Page 60; thence with the centerline of Taller Ridge Drive, the following courses: South 03° 26' 58" West, a distance of 156.26 feet to a point of curvature; with the arc of a curve to the left, having a central angle of 28 46' 59 ", a radius of 625.00 feet, an arc length of 313.97 feet, a chord bearing of South 10° 56' 32" East and chord distance of 310.68 feet to a point; thence South 64° 39' 59" West, across the right -of -way of Tuller Ridge Drive, a distance of 30.00 feet to a point on a curve in the westerly right -of -way line of Tuller Ridge Drive, at the northernmost comer of the 0.821 acre tract conveyed to The City of Dublin, Ohio by deed of record in Instrument Number 201212310201439, and in the easterly line of said 15.097 acre tract; thence with the common perimeter of said 15.097 acre tract and said 0.821 acre tract, the following courses: with the are of a curve to the right, having a central angle of 28° 58' 08 ", a radius of 370.00 feet, an arc length of 187.07 feet, a chord bearing of South 10° 50' 57" East and chord distance of 185.09 feet to a point of tangency; South 03° 38' 07" West, a distance of 374.03 feet to an iron pin set at a point of curvature, being the TRUE POINT OF BEGINNING; with the arc of a curve to the left, having a central angle of 17° 06' 36 ", a radius of 530.00 feet, an arc length of 158.27 feet, a chord bearing of South 04 55' 11" East and chord distance of 157.68 feet to an iron pin set at the common corner thereof and in the northerly line of the 4.567 acre tract conveyed to Dale Drive Properties LLC by deed of record in Instrument Number 201405020064216; North 86 2 P 53" West, with the line common to 0.821 acre and said 4.567 acre tracts, a distance of 17.15 feet to an iron pin set on a curve; thence across said 15.197 acre tract, the following courses: with the arc of a curve to the right, having a central angle of 08° 50' 50 ", a radius of 530.00 feet, an are length of 81.84 feet, a chord bearing of North 00 47' 18" West and chord distance of 81.76 feet to an iron pin set at a point of tangency; North 03 38' 07" East, a distance of 74.42 feet to the TRUE POINT OF BEGINNING, containing 0.024 acre, more or less, from Auditor's Parcel Number 273 - 012471. Subject, however, to all legal rights -of -way and/or easements, if any, of previous record. 0.024 ACRE -2- Iron pins set, where indicated, are iron pipes, thirteen sixteenths (13/16) inch inside diameter, thirty (30) inches long with a plastic plug placed in the top bearing the initials EMHT INC. The Bearings shown hereon are based on the Ohio State Plane Coordinate System South Zone as per NAD83 (1986 Adjustment). Control for bearings was from coordinates of monuments FRANK 73 and FRANK 74, having a bearing of South 73' 57' 18" East, established by the Franklin County Engineering Department, using Global Positioning System procedures and equipment. This description is based on an actual field survey performed by or under the direct supervision of Joshua M. Meyer, Registered Surveyor Number 8485 in April 2013 and April 2014. EVANS, MECHWART, HAMBLETON & TILTON, INC. I JOSHUA a i, MP ¢ OHAL 9•' tills JMM:sg , 0 024 ac20f4050- VS- Bi1'BY- 05.doc /---1 ""', f,-' 8_2-0-261'! Joshua M. Meyer Date Professional Surveyor No. 8485 p •'31-1D 0- A DESCR[mioN VERIFIED DM- RINGL , P.O., M. BY• DA TE:2 \_!M LEGAL DESCRIPTION OF: PARCEL NO.2 1.68 ACRES TAX PARCEL I.D: 273 - 008998 EXHIBIT "A" LEGAL DESCRIPTION File No.: 01032 -12686 Situated In the State of Ohio, County of Franklin, City of Dublin, Quarter Township 3, Township 2, Flange 19, United States Military Lands, being part of the original 9.356 acre tract of land as described In a deed to Village Square center, Ltd., or record in Deed Book 3719, Page 818 (all references herein being to the records located in the recorder's Office, Franklin County, Ohio) and being more particularly described as follows: Beginning at an iron pin set in the northerly right of way line of Dale Drive, 60 feet In width, as shown and delineated upon the plat "DALE CENTER ", of record in Plat Book 50, Pages 81 and 82 and in the easterly line of said original 9.356 acre tract; Thence North 84 degrees 06 minutes 43 seconds West, along said right of way line, a distance of 321.86 feet to an iron pin set at a point of curvature; Thence continuing along said right of way line with the are of a curve to the left, having a radius of 430.00 feet, a central angle of 9 degrees 54 minutes 08 seconds, the chord of which bears North 89 degrees 03 minutes 47 seconds West, a chord distance of 74.22 feet to a point; Thence North 6 degrees 05 minutes 23 seconds East, through said original 9.356 acre tract, a distance of 207,48 feet to a point in the northerly line of same and in the southerly line of same and in the southerly line of that 51.77 acre tract of land as described in a deed to City National Bank Trust Company, Trustee, of record in Deed Book 3774, Page 868; Thence South 83 degrees 54 minutes 37 seconds East, along said northerly and southerly lines, a distance of 332.00 feet to an iron pin found at the northeasterly corner of said original 9.356 acre tract; Thence South 11 degrees 37 minutes 28 minutes East along the easterly line of said original 9.356 acre tract, a distance of 209,62 feet to the place of beginning and containing 1.678 acres of land. Bearings herein conform to those of the referenced plat of "DALE CENTER" of record in Plat Book 58 Pages 81 and 82. Iron pins set consist of a 1" O.D. iron pipe, 30" long with a plastic cap stamped "M -E BLDG CONSULTANTS ". This description was prepared by M -E Building Consultants, Inc., Civil Engineering Division, from information obtained by an actual field survey in January, 1986. Parcel No.: 273 - 008998 -00 DsAr C. n rGt..[ p.t?., P,s. AY:_� DATE• 0 p,dr,Q -A A -Of LEGAL DESCRIPTION OF: PARCEL NO.3 2.03 ACRES TAX PARCEL I.D: 273 - 008867 EXHIBIT A THEpROPERTY Situated in the State of Ohio, County of Franklin, and in the City of Dublin: Being Lot Number One (1), in "DALE CFNTFR" ns the same is numbered and delineated upon the recorded plat thereof, of rccord in Plat Book 58, Pages 81 and 82, Recorder's Office, Franklin County, Ohio. LEGAL DESCRIPTION OF: PARCEL NO's. 4,5 6,7,8,9, 10, 11 7.182 ACRES TAX PARCEL I.D's: 4: 273 - 008994 5: 273 - 008838 6:273- 008858 7: 273 - 008857 8: 273 - 008831 9: 273 - 008834 10: 273 - 008832 11: 273 - 008856 7.182 ACRES Situated in the State of Ohio, County of Franklin, City of Dublin, lying in Quarter Township 3, Township 2, Range 19, United States Military L2rtds, and being part of that 12,363 acre tract conveyed to 6490 Riverside Drive, LLC by deed of record in Instrument Number 201203120033906 (all references are to the records of the [recorder's Office, Franklin County, Ohio) and being more particularly described as follows: Beginning at a 314 inch iron pipe found at the northwesterly corner of Lot 1 of that subdivision entitled "Dale Center" of record in Plat Book 58, Pages 81 and 82, the northeasterly corner of said 12.363 acre tract in the southerly right -of -way line of Dale Drive (60 feet wide) as dedicated in said Plat Book 58, Pages 8l and 82; Thence South 14 °01'13" East, with the line common to said 12.363 acre tract, said Lot 1, and Lot 2 of said "Dale Center', a distance of 838.21 feet (passing a 3l4 inch iron pipe capped "EM`H &T" found at a distance of 321.39 feet and a 314 inch iron pipe found at a distance of 596.24 feet) to an iron pin set; Thence across said 12.363 acre tract, the following courses and distances: North 80°49 West, a distance of 133.00 feet to an iron pin set; North 88 °33'55" West, a distance of 70.00 feet to an iron pin set; North 70 °47'35" West, a distance of 28.00 feet to a mag nail set; North 57 °10'46" West, a distance of 40.00 feet to a snag nail set; North 51 °51'31" West, a distance of 25.00 feet to an iron pin set; North 51'20'08" West, a distance of 35.00 feet to a mag nail set; North 54 °4418" West, a distance of 40 00 feet to a mag nail set; North 47 °43'47" West, a distance of 36.00 feet to a mag nail set; North 42 °37'38" West, a distance of 42.00 feet to a mag nail set; North 38 °36'19" West, a distance of 37.00 feet to a mag nail set; North 34 °21'58" West, a distance of 37.00 feet to a mag nail set; North 29 1 3347" West, a distance of 49.00 feet to a mag nail set; North 26 °29'52" West, a distance of 60.00 feet to a mag nail set; North 18'1515" l5" West, a distance of 184.00 feet to a mag nail set; North 15 "02'28" West, a distance of 78.00 feet to a mag nail set; North 10'1813" West, a distance of 142.00 feet to a mag nail set; and North 07 °31'16" West, a distance of 118,20 feet to an iron pin set in the southerly right -of -way line of said Dale Drive; Thence with said southerly right -of -way line and with the northerly line of said 12363 acre tract. with the arc of a curve to the right, having a central angle of 10 °19'32 ", a radius of 370.00 feet, an are length of 66.68 feet, and a chord that bears North 88 °20'11" East, a chord distance of 66.59 feet to an iron pin set at a point of tangency; Thence South 86 East, continuing with said southerly right -of -way line and said northerly line, a distance of 340.75 feet to the point of beginning and containing 7.182 acres, more or less of which 3.291 acres are located within parcel number 273. 008994, 1.532 acres arc located within parcel number 273 -008834, 0.056 acre is located within parcel number 273. 008857, 0.283 acre is located within parcel number 273 - 008838, 0.840 acre is located within parcel number 273- 008832, 0.084 acre is located within 7.182 ACRES -2- parcel number 273 -008831, 0.208 acre is located within parcel number 273 -008858, and 0.888 acre is located within parcel number 273 - 008856. Subject, however, to all legal rights -of -way and/or easements, if any, of previous record. Iron pins set, where indicated, are iron pipes, thirteen sixteenths (13/16) inch inside diameter, thirty (30) inches long with a plastic plug placed in the top bearing the initials EMI rNC, The bearings herein are based on the Ohio State Plane Coordinate System South - Lone as per NAD83 (1986 Adjustment). Control for hearings was from coordinates of monuments FRANK 73 and FRANK 74, having a bearing of South 73° 57' 18" East, established by the Franklin County Engineering Department, using Global Positioning System procedures and equipment. This description is based on an actual field survey performed by or under the direct supervision of Joshua M. Meyer, Registered Surveyor Number 8485 in April 2013. - .ut1Uur.. EVANS, MI?CHWART, EIAMBLETON & TILTON, INC. JOSH � r.' �t�R p S -ft�8� O Joshua M. Meyer Date Professional Surveyor No. 8485 ONAL 7� , rMM:mw 7 Wu- 26130753- VS- ALTA.doc �tl *tA, A r �f 'rMl��. C,�UIJIV [ EMI. $ASS �0A ok E - >Y DESCRnynoN VERIFIED �Ys6 DEAN C. RtNGt.P. P.E.. P.S. (% �tl *tA, A r �f 'rMl��. C,�UIJIV [ EMI. I r G DEPT. 56%'3, E - >Y DESCRnynoN VERIFIED DEAN C. RtNGt.P. P.E.. P.S. (% d� PR LIM ARY A r �f 'rMl��. C,�UIJIV [ EMI. I r G DEPT. 56%'3, E - >Y DATE: LEGAL DESCRIPTION OF: PARCEL NO's. 12 & 13 2.93 ACRES TAX PARCEL I.D's: 12: 273 - 000108 13:273- 000004 PER DESCRIPTIONS ON FOLLOWING PAGES: 7.253 ACRE TRACT AND A 3.225 ACRE TRACT EXEMPTING THEREFROM: A 6.780 ACRE TRACT CONVEYED TO THE CITY OF DUBLIN AND A 0.768 ACRE TRACT CONVEYED TO THE CITY OF DUBLIN EXHIBIT "A" October 21, 1999 DESCRIP'T'ION OF 7,270 ACRES NORTH OF NORTH HIGH STREET EAST OF HIGH STREET DUBLIN, OHIO Situated in the State of Ohio, County of Franklin, City of Dublin, being a part of Virginia Military Survey Number 2542, being 7.270 acres of land consisting of part of that tract of land as described in Official Records Volume 6494, Page G -09, all of those tracts of land as described in Official Records Volume 10325, Page 105, all as conveyed by deed to River's Edge Two, and portions of two alleys vacated by the Council of the City of Dublin, Ohio, by Ordinance No. 92- 86 (all deed references herein being to lire records located in the Recorder's Office, Franklin County, Ohio), said 7.270 acre tract being more particularly described as follows; Beginning, FOR REFERENCE, at the centerline intersection of North Street (formerly Darby Street). 66 feet in width, and High Street, 60 feet In width, as delineated upon the plat of Dublin, of record in Plat Book 3, Page 199; them= North 7° 00' 00" West, along the centerline of High Street, a distance of 214.50 feet to a railroad spike set; thence North l I ° 38'00" West, along the old centerline of S.R. 745, a distance of 1.00 foot to the'1 "RUB POINT OF BEGiNNING� Thence North 11 ° 38 West, continuing along said centerline, a distance of 362.96 feet to a point; Thence through said River's Edge'l'wo tract of record in Official Records Volume 6494, Page G -09 the following five courses and distance; 1. North 86 38'00" East, a distance of 144.16 feet to a point; 2. North 11 ° 47' 18" West, a distance of 109.18 feet to a point; 3. North 86 Fast, a distance of 220,56 feet to a point; 4. South 17" 37'00" East, a distance of 111.43 feet to a point; 5. North 86° 38'01Y East, a distance of 282.69 feet to a point in the easterly line of said River's Edge Two tract on the west bank of the Scioto River; Thence South 11° 30'40" East, along said west bank a distance of 447.19 feet to the northeasterly corner ofthat Parcel Three, as described in a deed to Riverview Property, of record in Deed Book 3514, Page 220; Thence South 77° 14'32" West, along the northerly line of said Parcel Three and along a stone wall, passing an iron pin found at 72.88 feet, a total distance of 356.00 feet to an iron pin found at the northwesterly corner of said Parcel Three; Thence South 23° 46 40" Fast, along the westerly line of said Parcel Three, a distance of 21.93 feet to an iron pin found at the northeasterly corner of Parcel Two, also as described in said Deed Book 3514, Page 220; Thence South 83 00' 00' West, along the northerly line of said Parcel Two and along the nnrtherly right -of -way line of North Street, passing an iron pin found at the northwesterly comer of said Parcel Two at 19.80 feet, passing another iron pin found at 90.42 feet, a total distance of 96 42 feet to an iron pin set at the intersection of the easterly right -of -way line of a vacated 20 foot wide alley; Thence North 7° oo 00" West, along said easterly right - of - way line, a distance of 85,00 feet to a point; Thence through the vacated alleys the following three courses and distances: 1. North 18 02'27" West, a distance of 52.22 feet to a point in the centerline of said 20 foot wide alley; 2. North 25" 34'45" West, a distance of 31.38 feet to the point of into of the southerly right -of -way line of a vacated 16.5 foot wide alley with the westerly right -of -way line of said 20 foot wide alley; 3. North 52° 00' 00" West, crossing said 16.5 foot wide alley, a distance of 23.34 feet to a point in the northerly line of same; Deserip €ion of 7.:70 acres, page Z point; Thence South 83° 00'00" West, along said northerly line, a distance of 61.50 feet to a Thence South 7° 00'00" East, again crossing said 16.5 foot wide alley, a distance of 16.50 feet to a point in the southerly line of same; Thence South 83° 00'00" Wesl, along said southerly line, a distance of 88.00 feet to a point at the northwesterly corner of Lot 133 in the Village of Dublin and in the easterly right -of- way line of High Street; Thence North 7° 00'00" West, again crossing said 16.5 foot wide alley, a distance of 16.5 feet to a point in the northerly tine of same; Thence South 83° 00'00" West, a distance of 33.08 feet to the TRUE POINT OF BEGINNING and containing 7.270 acres of land. Bearings herein are based on those on the plat of record in Plat Book 17, Page 369. This description was prepared by M -E Engineering, Inc., Civil Division. �� .,r. 0,5�►� M-E Engineering, Inc. R00ERT'' ;� Civil Division S. WYNO 6872 Q�: By_ _LD 1 ° c ) �c Robert S, Wynd Registered Surveyor No. 6872 Excepting therefrom a 0.017 Acre tract of land as conveyed by River's Edge Two to River's Edge Four by Official Record 20649116, Recorder's Office, Franklin County Ohio, as described on Exhibit "B ". EXHIBIT "B" October 21, 1999 DESCRIPTION OF 0.017 ACRE NORTH OF NORTH HIGH STREET EAST OF HIGH STREET DUBLIN, OHIO Situated in the State of Ohio, County of Franklin, City of Dublin, being in Virginia Military Survey Number 2542, and being 0.017 acre out of that tract of land as conveyed to River's Edge Two, of record in Official Records Volume 6494, Page 009, Recorder's Office, Franklin County, Ohio, said 0.017 acre being more particularly described as follows: Rcgimmng, M- R RE —UMNLE. at o southwesterly cotnor of said tract and in the centerline of High Street (S.R- 745); thence Nnrth I V 18'00" West, along said centerline, a distance of 362.96 (cut to a point; theme into said tract North 86° 38'00" East, a distance of 144.16 feet to a point; thence continuing into said tract Nodb I V 47' 18" West. a distance of 106.90 feet to the TRUE POINT OF VITMINNMOQ Thence continuing through said tract the following six courses: 1. North I V 47'19" West, a distance of 2 28 feet to a point; 2. North 86 East, a distance of 178 96 feet to a point; 3. South 4" 22'00" East, a distance of 9.14 feet to a point; 4. South 85" 38'00" West, a distance of 60.00 feet to a point; 5. North 4° 22' f10" West, a distance of I O.OD feet to a point; 6. South 85 38'00" West, a distance of 118.64 feet to the TRUE POINT OF BEOINNING and containing 0.017 acre of land. Bearings herein are based on those on the plat of record in Plat Book 17, Page 369. This description was prepared by M -E Engineering, Inc., Civil Division. 4 -- P F Oy M -E Engineering, Inc. Civil Division R0BERT . �O '•• S. j 0 -LL * WYND by � °1°I p 6872 ,O; Robert S. Wynd Registered Surveyor No 6872 v_n' ]mx19'n5 � I>EES(:WY'TIO1V Vr+.RIFiED DEAN C. R1xt;t.F. r.E.rs, BY: 617 �y73 I)Mm /2 O ZDiLI X97 s X07 Return To, Porter Wright - CTA 41 S. Htgk 8t., Columbus, OH 43215 EXHIBIT A TRACT 1 Situated in the State of Ohio, County of Franklin, Village of Dublin, being a part of Virginia Military Survey Number 2542, being 3.225 acres of land consisting of part of that tract of land as described in Official Records Volume 6494, Page G -09 and all of that tract of land as described in Official Records Volume 9362, Page A -01, both as conveyed by deed to River's Edge Two (all references herein being to the records located in the Recorder's Office, Franklin County, Ohio), said 3.225 acre tract being more particularly described as follows; Bcgianing, FOR R.L•FERUQCIi, at the centerline intersection of North Street (formerly Darby Street), 66 feet in width, and High Street (S.R. 745), 66 feet in width, as delineated upon the Plat of Dublin, of record in Plat Book 3, page 199: thence North 7° 00'00" West, along the centerline of High street, a distance od 214.50 feet to a railroad spike; thence North 1 I ° 38'00" West, along the old centerliue of S.R. 745, it distance of 363.96 feet to the TRUE POINT OF BEGINNING: Thence North i V 38' 00" West, continuing along said centerline, a distance of 4.31 feet to a point of curvature; Thence with the arc of a curve to the right, having a radius of 2,200.00 feet, a central angle of 5° 08' 59 ", the chord of which bears North 9" 03'30" West, a chord distance of 197.67 feet to an iron pin at the northvresterly corner of the tract described in Official Record Volume 9362, Page A -01; Thence along the northerly I ine of said tract and along the southerly line of that 4 % acre tract of land as described in a deed to John H. and Victoria L. Kilbury, of record in Deed Book 3548, page 475, the following three courses and distances: 1) North 85° 50' 23" East, a distance of 90.75 feet to an iron pin; 2) North 73° 19'23" East, a distance of 198.00 feet to a P.K. nail in the root of a sycamore tree; 3) North 76° 29'23" East, a distance of 356.77 feet to an iron pin at the top of bank of the Scioto River; Thence South 11° 30'40" East, along said top of bank, a distance of 313.79 feet to a point; Thence through the tract described in Official Record Volume 6494, page G -09 the following five courses and distances: 1) South 86 38' 00" West, a distance of 282.69 feet to a point; 2) North 17 3T 00" West, a distance of 111.33 feet to a point; 3) South 86 38'00" West, a distance of 220.56 feet to a point; 4) South 11° 47'18" East, a distance of 109.18 feet to a point; 5) South 86° 38'00" West, a distance of 144.16 feet to the'FROE POINT OF BEGINNING and containing 3.225 aeres of land. The bearings used herein are based on those on the plat of record in Plat Book 17, Page 369 (new centerline of S.R. 745 North 7° 00'00" West). This description was prepared by M -E Building Consultants, Inc., Civil Engineering Division, based on information obtained from actual field surveys TRACT 2 Situated in the State of Ohio, County of Franklin, City of Dublin, being in Virginia Military Survey Number 2:542, and being 0.017 acre out of that tract of land as conveyed to River's Edge Two, of record in Official Records Volume 6494, Page G09, Recorder's Office, Franklin County, Ohio, said 0.017 acre being more particularly described as follows: Beginning, FOR REFERENCE, tit a southwesterly corner of said tract and in the centerline of High Street (S.R, 745); thence North I 1 ° 39'00" West, along said centerlinr:, a distance of 362.96 feet to a point; thence into said tract North 86 38' 00" East, a distance of 144.16 feet to a point; thence continuing into said tract North I I° 47' 18" West, it distance of 106.90 feet to the TRUE POINT OF BEGINNINNG: Thence continuing through said tract the following six courses; 1) North I V 47' 18" West, a distance of 2.28 feet to a point; 2) North 86° 38' 00" East, a distance of 178.96 feet to a point; 3) South 4° 22' 00" East, a distance of 9.14 feet to a point; 4) South 05° 38' 00" West, a distance of 60,00 feet to a point; 5) North 4° 22' 00" West, a distance of 10.00 foet to a point; 6) South 05° 38'00" West, a distance o €118.64 feet to the TRUE POINT OF BEGINNING and containing 0.017 acre of land. Bearings herein are based on those on the plat of record in Plat Book 17, Page 369. 91.G a� f p� This description was prepared by M -E Engineering, Inc., Civil Division. DESCRt"InN VES111T 16H DEAN C. RING LE, F isN Together with an Easement for Ingress and Egress as shown in Tract 3 below, fjy. 1 2 K, 1 TRACT 3: Situated in the State of Ohio, County of Franklin, City of Dublin, Virginia Military Survey Number 2542, being an ingress - egress casement within that tract of land as described In a deed to River's Edge Two, of record, in official Record Volume 6194, Page G -09 (all references herein being to records located in the Recorder's Office, Franklin County, Ohio), said easement being more particularly described es follows: Beginning, FOR REFERENCE', at a southwesterly corner of said tract, in the northerly right -of -way line of North Street (66 feet in width); thence North 83° 00'00" East, along the southerly line of said tract and said northerly right -of -way line, a distance of 32.78 feet to the TRUE POINT OF BEGINNING: Thence, through said tract, the following ten (10) courses and distances: 1) North 3 22'00" West, a distance of 333.36 to a point; 2) South 86° 38' 00" West, a distance 13.88 feet to a point; 3) North 3 22'00" West, a distance of 72.00 feet to a point; 4) South 86 8' 00" West, a distance of 174.37 feet to a point; 5) North 3° 22' 00" West, a distance of 228.00 feet to a point; 6) North 86° 38'00" East, a distance of 221.87 feet to a point; 7) South 17° 3700" East, a distance of 54.84 feet to a point; 8) South 3° 22'00" East, a distance of 359.50 feet to a point; 9) South 86° 38' 00" West, a distance of 25.12 feet to a point; 10) South 3° 22' 00" East, a distance of 219.30 feet to a point in the aforementioned southerly line of said tra and northerly right -of -way line of North Street; Thence South 83 00'00" West, along said southerly and northerly lines, a distance of 22.04 feet to the TRUE -POINT OF BEGINNING. Bearings herein are based on those of the referenced deed, of record, in Official Records Volume 6194, pace, G0-09. This description was prepared by M -E Building Consultants, Inc., Civil Engineering Division. Exhibit A -1 0.768 ACRE Situated in the State of Ohio. Cowtty of Franklin, Cily of Dublin, lying in Survey Number 2542 of* the Virginia Military District, and being pan of that 7.253 acre tract conveyed to 94 N. High Street Acquisition, LLC by deed of record in Instrument Number 201212210197480 and part of that 3.225 acre tract conveyed to 94 N. High Street Acquisition, LLC by dc4 d of record in 'fnstmnicnt Nutnber a 2 ► 9D2 D`I`] l io , being part of that 16,5 foot wide alley vacated by City of Dublin Ordinance Number 92 -86 (all references are to the records of the Recorder's Office, Franklin County, Ohio unless noted otherwise) and being more particularly described as follows; Beginning, for reference, at a magnetic nail set at the easterly centerline intersection of High Street (66 feet wide) and North Street (width varies); thence North 08° 24' 12" West, with the centerline of said High Street, a distance of 210.37 feet, to a southeasterly comer of the remainder of the 1.283 acre tract conveyed to the Village of Dublin by deed of record in Deed Book 3759, Page 134; thence North 12° 31' 24" West, with the original centerline of Dublin - Bellepoint Road (S.R. 745) (width varies) with the easterly line of said 1.283 acre tract, a distance of 5.14 feet, to a magnetic nail set at the southwesterly comer of said 7.253 acre tract, being the TRUE POINT OF BEGINNING; thence North 12° 31' 24" West, with the original centerline of said Dublin - Bellepoint Road (S.R. 745), said easterly line, the easterly line of the 2.2111 acre tract conveyed to Board of Trustees of the Columbus Metropolitan Library by deed of record in Official Record 30344303, and the easterly line of the remainder of the 18.15 acre tract conveyed to Board of Education: Washington Local School District, Franklin County, Ohio by deed of record in Deed Book 2067, Page 232 (passing a 314 inch iron pipe with a "Sands & Decker" cap found at 216.83 feet), a distance of 364.41 feet, to an iron pin set; thence North 09 51' 47" West, with the original centerline of Dublin - Bellepoint Road (S.R. 745), with the easterly line of said 18.15 acre tract, a distance of 196.31 feet, to the northeasterly confer of said 18.15 acre tract, on the southerly line of the tract conveyed to City of Dublin, Ohio by deed of record in Instrument Number 201311050185838 and the southerly line of Lot 5 of "Albert Chapman Estate Subdivision" of record in Complete Record Volume 120, Page 125, Franklin County, Ohio, Compton Pleas Court (reference a 314 inch iron pipe with a "Sands & pecker" cap found 0.58 feet southerly); thence North 81° 45' 20" East, with the northerly boundary of said 3.225 acre tract, a southerly line of said City of Dublin, Ohio tract, and a southerly line of said Lot 5, a distance of 72.83 feet, to an iron pin set; thence South 08° 16' 21" East, across said 3.225 and 7.253 acre tracts, a distance of 576.03 feet, to an iron pin set on a southerly line of said 7.253 acre tract and the northerly line of that tract conveyed to 84 High Company, Ltd. by deed of record in Instrument Number 200012290262387, the southerly line of a 16.5 foot wide Alley vacated by City of Dublin Ordinance 92 -86; thence with the southerly boundary of said 7.253 acre tract, the following courses: South 81° 36' 15" West, with the northerly line of said 84 High Company, Ltd. tract, the southerly line of said 16.5 foot wide vacated Alley, a distance of 6.96 feet, to an iron pin set on the easterly right -of -way line of High Street; North 08 24' 12" West, with said easterly right -of -way line, a distance of 16.50 feet, to an iron pin set; South 81° 36` 15" West, a distance of 33.37 feet, to the TRUE POINT OF BEGINNING, containing 0.768 acre, more or less, of which 0.765 acre lies within the present roadway occupied. Of said 0.768 acre tract, 0.321 acre is located within parcel number 273- 000108 (all of 0.768 ACRE -2- which is located within the preset roadway occupied), 0.446 acre is located within parcel number 273 - 000004 (of which 0.444 acre is located within the present roadway occupied), and 0.001 acre is located within parcel number 273 - 004078. Subject, however, to all legal rights -of -way and/or easements, if any, of previous record. Iron pins set, where indicated, are iron pipes, thirteen sixteenths (13/16) inch inside diameter, thirty (30) inches long with a plastic plug placed in the top bearing the initials EMHT INC. The bearings shown hereon are based on the Ohio State Plane Coordinate System South Zone as per NAD83 (1986 Adjustment). Control for bearings was from coordinates of monuments FRANK 73 and FRANK 74, having a bearing of South 73° 57' 18" East, established by the Franklin County Engineering Department. This description is based on an actual field survey performed by or under the direct supervision of Joshua M. Meyer, Registered Surveyor Number 8485 in March 2013 thru October 2013. EVANS, MECHWART, HAMBLETON & TILTON, INC. Ol O JC�SHU�} RI. j MEYER a p i- fi<b£t5 - Joshua M. Meyer Date a n Professional Surveyor No. 8485 . 01 1 0 1A 1Mhisg 0 768 ac 20130451 docx N A �4 ILL � No P i t1 i•• t! y of Dublin Z,0 ,0. r. Q underman, Planning Manager oao l 0'5 DESCR1pT1()N VERMED p D . RLNG .E, P E., P.s- 11 13Y DAT 1 . PRELIMINARY APPROVAL. ENGINEE RING DEFT. DATE: _ Exhibit A -2 6.780 ACRES Situated in the State of Ohio, County of Franklin, City of Dublin, lying in Survey Number 2542 of the Virginia Military District, and being part of that 7.253 acre tract conveyed to 94 N. High Street Acquisition, LLC by deed of record in Instrument Number 201212210197480 and part of that 3,225 acre tract conveyed to 94 N. High Street Acquisition, LLC by deed of record in InstrtunentNumber lq OA Iq I(a (all references are to the records of the Recorder's Office, Franklin County, Ohio) and being more particularly described as follows: Beginning, for reference, at a magnetic nail set at the easterly centerline intersection of High Street (66 feet wide) and North Street (width varies); thence North 81° 36' 15" East, with the centerline of North Street, a distance of 249.99 feet, to a point; thence North 08° 23' 45" West, across the right -of -way of North Street, a distance of 33,00 feet, to an iron pin set on a southerly line of said 7.253 acre tract and the northerly right -of- way line of North Street, the TRUE POINT OF BEGINNING; thence across said 7.253 and 3.225 acre tracts, the following courses: North 07° 38' 42" West, a distance of 148.24 feet, to an iron pin set at a point of curvature; with the arc of a curve to the right, having a central angle of 10 09' Ol ", a radius of 516.50 feet, an arc length of 91.50 feet, a chord bearing of North 02° 34' 1 t" West and a chord distance of 91.38 feet, to an iron pin set at a point of reverse curvature; with the arc of a curve to the left, having a central angle of 07° 12' 30 ", a radius of 483.50 feet, an are length of 60.83 feet, a chord bearing of North 01' 05' 56" West and a chord distance of 60.79 feet, to an iron pin set at a point of tangency; North 04° 42' 11" West, a distance of 408.15 feet, to an iron pin set; South 71° 58' 31" West, a distance of 257.84 feet, to an iron pin set; North 08 16' 21" West, a distance of 78.42 feet, to an iron pin set on the northerly line of said 3.225 acre tract, the southerly line of the tract conveyed to City of Dublin, Ohio by deed of record in Instrument Number 201311050185838, and the southerly line of Lot 5 of "Albert Chapman Estate Subdivision" of record in Complete Record Volume 120, Page 125, Franklin County, Ohio, Common Pleas Court; thence with the northerly boundary of said 3,225 acre tract, with the southerly boundary of said City of Dublin, Ohio tract, and with the southerly line of said Lot 5, the following courses: North 81 45' 20" East, a distance of 13.43 feet, to a 3/4 inch iron pipe found; North 71 58' 31" East, a distance of 198.00 feet, to an iron pin set; North 75 08' 31" East, a distance of 356.77 feet, to a northeasterly corner of said 3.225 acre tract on the westerly side of the Scioto River; thence South 12° 51' 32" East, with the easterly line of said 3.225 and 7.253 acre tracts, the westerly side of the Scioto River a distance of 761.00 feet, to a southeasterly corner of said 7.253 acre: tract and the northeasterly corner of the 0.619 acre tract conveyed to B.E.T. Investments 1, LLC by deed of record in 200506060108846; thence South 75° 52' 09" West, with a line common to said 7.253 acre and 0,619 acre tracts (passing a 3, inch iron pipe with a "Bird & Bull" cap found at 73.05), a distance of 356.00 feet, to a common corner thereof (reference a 3/4 inch iron pipe with a "Bird & Bull" cap found 0.18' southerly, 0.27' easterly); 6.780 ACRES -Z. thence South 25 09' 03" East, with said common line, a distance of 21.93 feet, to a 3/4 inch iron pipe with a "Bird & Bull" cap found at a common comer thereof, thence South 81° 36' 15" West, partly with said common line, partly with said northerly right- of-way Line, and with a southerly line of said 7.253 acre tract (passing a 3/4 inch iron pipe with a " Bitd & Bull" cap found at 18.80 feet), a distance of 65.65 feet, to the TRUE POINT OF BEGINNINGy containing 6.780 acres, more or less, of which 0,114 acre lies within the present roadway occupied. Of said 6.780 acre tract 2.446 acre is located within parcel number 273- 000108 (ofwhich 0.114 acre is located within the present roadway occupied), and 4334 acre is located within parcel number 273 - 000004, Subject, however, to all legal rights -of -way and/or easements, if any, of previous record. Iron pins set, where indicated, are iron pipes, thirteen sixteenths (13116) inch inside diameter, thirty (30) inches long with a plastic plug placed in the top bearing the initials EMHT INC. Thts bearings shown hereon are based on the Ohio State Plane Coordinate System South Zone as per NAD83 (1986 Adjustment). Control for bearings was from coordinates of monuments FRANK 73 and FRANK 74, having a bearing of South 73° 57' 18" East, established by the Franklin County Engineering Department. This description is based on an actual field survey performed by or under the direct supervision of Joshua M. Meyer, Registered Surveyor Number 8485 in March 2013 thru October 2013. tN -Y'\ SSA \-t q 2. DO000 `{ ovU o� D>✓.SCIt1T'7`t(3ty C.12L\ 5 M rL, P s By. 1 � 1 ' DA - Q No to Caa unGorrrtan, W-unrin8 t>l:s3a08r PRELIMINARY APPROVAL FRA Cp i .* t- r At,K ENGINE L- - DF� DATE 13� sy EVANS, MECHWART, HAMBLETON & TILTON, INC J03HUA M. NIEYER = `0 $8486 O : �O Joshua M. Meyer Date 8485 W Professional Surveyor No. 1N 3MM:sg 6 780 ac 2013045 Ldocx tN -Y'\ SSA \-t q 2. DO000 `{ ovU o� D>✓.SCIt1T'7`t(3ty C.12L\ 5 M rL, P s By. 1 � 1 ' DA - Q No to Caa unGorrrtan, W-unrin8 t>l:s3a08r PRELIMINARY APPROVAL FRA Cp i .* t- r At,K ENGINE L- - DF� DATE 13� sy [This Page Intentionally Left Blank] EXHIBIT C ZONING FOR DISTRICT C -1 I hereby certify that the following Exhibit °C" contains the applicable zoning regulations, including Sections 153.057 through 153.066 of the Bridge Street Corridor Development Code as adopted by Dublin City Council with Ordinance 07 -12 (Amended) on March 26, 2012 and as amended by Ordinance 84 -13, Ordinance 91 -13, Ordinance 76 -14 (Amended) and Ordinance 114 -14 (Amended). Anne C. Clarke Clerk of Council a Date City of Dublin Bridge Street District (BSD) Zoning Districts Zoning Code Sections 153.057 through 153.066 As Approved by Dublin City Council Monday, March 26, 2012 Ordinance 07 -12 (Amended) Last Amendment Monday, December 8, 2014 Amendments 153. 066 .............. ............................... Ord. 84 -13 153.057 - 153. 058 ... ...........................Ord. 91 -13 153.057 - 153.060, 153.062 - 153.063, 153. 065 ...........................Ord. 76 -14 (Amended) 153.057 - 153.066 .......... Ord. 114 -14 (Amended) BRIDGE STREET DISTRICT EFFECTIVE DATE DEVELOPMENT CODE JANUARY 7, 2015 BRIDGE STREET DISTRICT (BSD) DISTRICTS § 153.057 GENERAL PURPOSE (A) (B) The primary purpose of the Bridge Street District (BSD) zoning districts is to implement the Bridge Street District Area Plan for development and redevelopment of the Bridge Street District consistent with the directions articulated in the Community Plan (Bridge Street District Area Plan). This is with the full recognition that the Plan may be revised and acknowledging that the illustrations in the Plan are conceptual and not regulatory. The Community Plan identifies the Bridge Street District as the centerpiece of the city with a focus on historic and cultural acknowledgement, preservation and creation of outstanding open spaces, and the presence of mixed use districts. These features allow for a wider range of choices for housing and employment, create interesting places and walkable districts, and enable buildings of lasting, memorable and high quality architectural character that maintain Dublin's commitment to exemplary planning and design. The Bridge Street District zoning districts are intended to bring to life the five Bridge Street District Vision Principles by enhancing economic vitality, integrating the new center into community life, embracing Dublin's natural setting and celebrating a commitment to environmental sustainability, expanding the range of choices available to Dublin and the region, and creating places that embody Dublin's commitment to community. (C) Specific Purposes (1) (2) More specifically, the purpose of the Bridge Street District zoning districts is to promote development that creates an emerging center for urban lifestyles within a walkable, mixed -use urban environment that will enhance central Dublin's image as an exceptional location for high quality business investment. These districts are further intended to create places that embody Dublin's commitment to community through the preservation of those areas having architectural landmarks and traditional design, creating complete neighborhoods, and providing designs that honor human scale in their details. In addition, the Bridge Street District will continue to serve as a center of community for current and future Dublin residents. (3) The BSD zoning districts also provide a simplified, but thorough, development review process that provides a high degree of predictability and consistency. The process also sustains Dublin's reputation for high quality development while allowing BSD property owners to compete efficiently and effectively in the marketplace. (4) Because the Bridge Street District Area Plan is a transformative redevelopment concept designed for long -term implementation, a secondary purpose of the Bridge Street District zoning districts is to allow property owners the flexibility to take advantage of Streets should be capable of accommodating multiple modes of transportation and should facilitate the creation of a public realm designed primarily for people, characterized by: (a) Streets and blocks arranged to allow for comfortable walking distances, to disperse traffic and to reduce the length of automobile trips, (b) A connection to and enhancement of the existing street network; (c) A recognition of the role of buildings and landscaping that contributes to the physical definition of streets as civic places, (d) On- street public parking wherever possible, (e) Shared parking and other strategies to reduce the size of surface parking lots and enable efficient and creative site design, and new and innovative business opportunities that are consistent with the Plan. (D) Principles of Walkable Urbanism To advance the purposes of the Bridge Street District zoning districts as described in §153.057 (A) through (C), the following principles of walkable urbanism will serve as a guiding framework to be used in the review of zoning and development proposals subject to the requirements of § §153.058 through 153.066. Individual principles may not apply in all circumstances, but should be used where appropriate to ensure the requirements and standards of these zoning districts are applied in a manner that contributes to the creation of walkable, mixed use urban environments as envisioned by the Bridge Street District Plan. In addition to the development requirements throughout § §153.058 through 153.066 intended to support walkability in the Bridge Street District, Zoning Code Section 153.065(1) contains specific requirements for creating safe and comfortable pedestrian- oriented development desired by the City and consistent with the Principles of Walkable Urbanism. (1) General Principles The designs of buildings, streets, and open spaces within the Bridge Street District should contribute to the creation of an urban neighborhood pattern of development, characterized by: (a) Quality architecture and urban design emphasizing beauty and human comfort and creating a sense of place, (b) Pedestrian- friendly design that places a high priority on walking, bicycling and use of public transit, (c) Creation of interesting and convenient destinations within walking distance for visitors as well as ordinary activities of daily living, and (d) Respect for the natural environment. (2) Streets, Parking and Transit 2 § 153.057 EFFECTIVE DATE GENERAL PURPOSE JANUARY 7, 2015 (f) Residential and business uses that have convenient access to existing and future transit stops. (3) Open Space The Bridge Street District should have a variety of functional, well- designed open spaces that enhance the quality of life for residents, businesses, and visitors. Open spaces should: (a) Include a wide range of characters from small intimate spaces to larger neighborhood and community uses, including small parks and playgrounds to provide gathering spaces for neighborhoods; (b) Be arranged and designed as part of a district - wide open space network that defines and connects neighborhoods and the larger Dublin community; (c) Be located within convenient walking distance of all residents and businesses. (4) Buildings Buildings should have a range of high - quality residential, commercial, mixed -use and civic architectural styles to reinforce the unique identities of each part of the District. Buildings should be characterized by: (a) Easily convertible spaces that allow for uses to change over time; (b) Residential uses with a variety of housing types, sizes, and price levels, (c) Abroad mix of shops, offices, and housing integrated within and among a variety of building types; and (d) Architecture that reflects Dublin's commitment to high quality and enduring character. § 153.058 BRIDGE STREET DISTRICT (BSD) DISTRICTS SCOPE AND INTENT (A) Scope The following Bridge Street District .(BSD) districts are hereby created. The districts described by §.153.058 are intended to be used for all land within the Bridge Street District. Unless otherwise specifically noted, after the effective date of this amendment all development and redevelopment within the BSD zoning districts shall be consistent with §153.057, General Purpose and subject to the regulations of § §153.058 through 153.066. Other provisions of Chapters 152 and 153 of the Dublin Code of Ordinances apply in the BSD zoning districts. Where there are conflicts, the provisions of § § through 153.066 shall prevail. Nothing contained herein shall prohibit an application for rezoning to any non -BSD zoning . district provided in this Chapter. (B) Intent The Bridge Street District zoning districts are generally based on the District Framework of the Bridge Street District Area Plan. The purpose of the Framework is to allow development regulations to be adapted to the unique conditions present in each area. Although each district is unique, the five Vision Principles are intended to create a cohesive area, based on the concepts of walkability and urban vitality to support the quality of life for residents of all generations. The titles of each district are intended to describe the predominant land use character and/or special geographic locations rather than a single type of use. The following further describes the intent of each BSD zoning district (1) BSD Residential The intent of this district is to accommodate single - family, two- family, townhouse, live -work and multiple - family uses in mid -rise development. The BSD Residential district integrates existing and new residential developments to create true neighborhoods and add to the population base needed to help support nearby retail and office development. Uses are generally limited to residential and small -scale residential support uses, as listed in Table 153.059 -A. (2) BSD Office Residential The intent of this district is to accommodate amix of office and multiple - family residential development at higher densities and in larger buildings. This district offers great flexibility to take advantage of visibility and access for office uses, with opportunities to create residential neighborhoods to support the adjacent BSD zoning districts. Uses include a mix of residential, personal service, and commercial uses, as listed in Table 153.059 -A. (3) BSD Office The intent of this district is to allow a mix of offices and retail support uses, as listed in Table 153..059 -A. The BSD Office district provides significant additional development capacity and redevelopment opportunities that foster office uses with a walkable design along signature streets, and provides increased accessibility and an improved roadway network to ease traffic pressure along major roadways. (4) BSD Commercial This district applies generally to existing retail centers and other low -rise commercial uses, including single use freestanding retail buildings, as listed in Table 153.059 -A. Properties initially zoned into this district may be eligible for rezoning to the BSD Vertical Mixed Use District or to other surrounding BSD zoning districts when future redevelopment to higher densities is desired. (5) BSD Historic Core This district applies to the historic center of Dublin and reinforces the character of this area as the BRIDGE STREET DISTRICT §153.058 3 DEVELOPMENT CODE BSD DISTRICTS SCOPE & INTENT centerpiece of the Bridge Street District. The district focuses on ensuring sensitive infill development and redevelopment and providing an improved environment for walking while accommodating vehicles. The district accepts building types that are consistent with the historic development pattern of Historic Dublin, subject to review by the Architectural Review Board, and permit similar uses that support a highly walkable setting, as listed in Table 153.059 -A. (6) BSD Historic Residential The intent of this district is to permit the preservation and development of homes on existing or new lots that are comparable in size, mass, and scale, while maintaining and promoting the traditional residential character of the Historic Dublin area. The purpose of these regulations is to protect the scale and character of the original platted village by maintaining regulations consistent with the previous Historic Residential zoning in place prior to the adoption of this amendment, as listed in Table 153.059 -A. (7) BSD Sawmill Center Neighborhood This district applies to the majority of the commercial areas at the east end of the District. The standards of the BSD Sawmill Center Neighborhood create an active, walkable destination through integration of a strong mix of uses. Development within this district relies on the provision of physical and visual connections through improved access and enhanced visibility from Sawmill Road, and links to adjacent neighborhoods and open spaces. This district accommodates a wide variety of building types and permitted uses, as listed in Table 153.059 - A. Redevelopment of the BSD Sawmill Center area creates a walkable, mixed use core as the east anchor of the District. The district is subject to the specific neighborhood standards defined in §153.063(C), establishing open space patterns, location requirements for building types, and permitting pedestrian - oriented, mixed use shopping areas. (8) BSD Historic Transition Neighborhood This district complements the BSD Historic Core district by accommodating a variety of building types within a finer grained street and block network and uses consistent with that district. It accommodates uses similar to those in the BSD Historic Core district as listed in Table 153..059 -A. Development allows an extension of the walkable mixed use character of the BSD Historic Core district on the larger parcels within this district. The district is subject to the specific neighborhood standards defined in §153.063(D). These requirements establish open space patterns and location requirements for building types, provide additional residential opportunities, and extend the small scale commercial activities of the BSD Historic Core district. (9) BSD Indian Run Neighborhood This district applies to the larger parcels north and west of the Indian Run and south of I -270, including adjacent properties fronting the north side of Bridge Street. The BSD Indian Run Neighborhood district is intended to develop as a new walkable, mixed use district that takes advantage of excellent highway visibility, an improved road network, and proximity to Historic Dublin and the natural areas flanking the Indian Run. Development within the district relies on a comprehensive road network providing connections within the Indian Run district and to the rest of the District, as well as sensitivity of development at its edges given its proximity to Historic Dublin and the Indian Run. This district accommodates a wide variety of building types and permitted uses, as listed in Table 153.059 -A. Redevelopment of the area creates a walkable, mixed use core as the west anchor of the District. The district is subject to specific neighborhood standards defined in §153.063(E). These regulations are intended to establish natural and man -made open space patterns, build pedestrian, bicycle, and vehicular networks; provide location requirements for building types; and foster a pedestrian - oriented, neighborhood scale mixed use shopping area. (10) BSD Scioto River Neighborhood The standards of the BSD Scioto River Neighborhood are intended to create an active, walkable destination through integration of a vibrant mix of uses. Development in this district is oriented toward the Scioto River and the public spaces along the riverfront, and includes important vehicular and bicycle links to adjacent neighborhoods and open spaces. This district accommodates a wide variety of building types and permitted uses, as listed in Table 153.059 -A. Development of the BSD Scioto River Neighborhood area establishes a walkable, mixed -use core as the center of the Bridge Street District. The district is subject to the specific neighborhood standards defined in §153.063(F), establishing open space patterns, location requirements for building types, and permitting pedestrian - oriented, mixed -use shopping areas. (11) BSD Vertical Mixed Use The intent of this district is to allow a wide variety of mid -rise, mixed use development, including vertical mixed use with ground floor retail, and large format retail with liner buildings, as listed in Table 153.059 - A. It is intended to be available for areas initially zoned into the BSD Indian Run Neighborhood, BSD Scioto River Neighborhood and BSD Sawmill Center Neighborhood districts, once these areas are developed and the applicable neighborhood standards are no longer needed to establish the organization and hierarchy of places. The district may be applied to areas initially zoned to the BSD Commercial District 4 § 153.058 EFFECTIVE DATE BSD DISTRICTS JANUARY 7, 2015 SCOPE & INTENT or elsewhere in the Bridge Street District as may be deemed appropriate when future redevelopment to higher densities is desired. Accordingly, the district is not intended to be mapped at the time the BSD zoning districts are initially adopted. (12) BSD Public This district applies to a variety of public spaces and facilities, including but not limited to schools, parks, open spaces, and places that accommodate more intensive recreation, such as outdoor entertainment venues, as listed in Table 153.059 -A. It also applies to lands in and adjacent to rivers and creeks on which development is limited due to inclusion in a Federal Emergency Management Agency (FEMA) designated floodplain as regulated by this chapter, or lands that have special cultural or environmental sensitivity. BRIDGE STREET DISTRICT § 153.058 5 DEVELOPMENT CODE BSD DISTRICTS SCOPE & INTENT § 153.059 USES and compliance with any use specific standards referenced in the Use Table and the applicable (A) INTENT provisions of Chapter 153. (1) The intent of §153.059 is to establish uses for land and (e) An "S" in a cell indicates a use that is allowed buildings desired in each BSD zoning district based in that BSD zoning district only if limited in on the vision for each area described in the Dublin size, subject to compliance with any use specific Community Plan (Bridge Street District Area Plan) standards referenced in the Use Table and the and the Bridge Street District's five Vision Principles. applicable provisions of Chapter 153. This is achieved through the variety of permitted, (f) A "T" in a cell indicates a use that is allowed in conditional, accessory and temporary uses allowed in that BSD zoning district for a limited period of each zoning district In some cases, special siting and time pursuant to a permit from the City, subject size limitations to establish the development character to compliance with any use specific standards articulated in the Dublin Community Plan apply. referenced in the Use Table and the applicable (2) This section ensures vibrant, mixed -use, pedestrian- provisions of Chapter 153. oriented development by emphasizing certain uses in ( A blank cell indicates that the use is prohibited in each zoning district and positioning the Neighborhood that district. Districts to thrive as critical activity nodes by concentrating commercial activity in these special (3) Use Specific Standards character areas. Refer to § 153.063, Neighborhood (a) Additional standards may apply to either Standards, for the neighborhood district requirements. permitted or conditional uses in a BSD zoning (3) The titles of each zoning district describe the district. These additional standards are cross - predominant land use character and/or special referenced in the last column of Table 153.059 -A geographic locations rather than a single type of use. as use specific standards and detailed in Zoning district titles shall not be construed as requiring §153.059(C). a particular use and shall not preclude other uses from (b) In some cases, additional restrictions on uses being established in each district, as permitted in this apply to specific building types in §153.062(0) section. Refer to §153.058, BSD Districts Scope and and to the Bridge Street District neighborhood Intent, for the intent of each zoning district. districts in §153.063. (4) Similar Use Determination (B) GENERAL PROVISIONS (a) When a proposed land use is not explicitly listed (1) Permitted and conditional uses available in each in Table 153.059 -A, the Director shall determine BSD zoning district are shown in Table 153.059 -A. whether it is reasonably included in the definition Permitted and conditional uses may be restricted by of a listed use, or that the proposed use meets the location, size, period of operation, or other use - specific following criteria to the extent that it should be standards as designated in Table 153.059 -A. treated as a permitted or conditional use in the (2) Table 153 -059 -A - Explanation of Terms district. (a) Listed uses are defined in §153.002(A). 1. The use is not specifically listed in any other (b) A "P" in a cell indicates a use that is permitted BSD zoning district. by right in that BSD zoning district,. subject 2. The use is generally consistent with the intent to compliance with any use specific standards of the BSD zoning district and this chapter. referenced in the Use Table and the applicable 3. The use will not materially impair the present provisions of Chapter 153. or potential use of other properties within the (c) A "U" in a cell indicates a use that is allowed by same district or bordering districts. right in that BSD zoning district on any upper 4. The use has no greater potential impact on floor of the structure, subject to compliance with surrounding properties than those listed in any use specific standards referenced in the Use the district in terms of aesthetics, traffic Table and the applicable provisions of Chapter generated, noise, potential nuisances and 153. Unless otherwise restricted by specific other impacts related to health, safety and building type requirements of 153.062(0), welfare. permitted or conditional uses not specified as "U" 5. The use will not adversely affect the relevant may occur on any floor, including basements or elements of the Community Plan, including lower levels, subject to applicable use specific the Bridge Street District Area Plan. standards. (b) The Director's written determination shall be (d) A "C" in a cell indicates a use that is allowed provided to the applicant and may be appealed to in that BSD zoning district only upon approval the Board of Zoning Appeals. of a conditional use as described in §153.236 6 § 153.059 EFFECTIVE DATE USES JANUARY 7, 2014 (5) Existing Uses A. Utilities, such as water, gas or electricity The long range implementation of the Bridge Street to the property, have been disconnected, District Area Plan requires sensitive treatment of B. The property, buildings, or grounds have existing uses that represent significant investments in fallen into disrepair, the City of Dublin. While it is the intent of the BSD C. Signs or other indications of the presence zoning districts for development to ultimately meet of the use have been removed; the building and use requirements of this chapter, it is the intent of this section to permit Existing Uses D. Equipment or fixtures necessary for the to continue and to be considered conforming to this operation of the use have been removed, Code, even if the use or the building type is not or otherwise permitted in the district, provided that the E. Other actions which, in the opinion of the following requirements are met Director, constitute an intention on the (a) All uses that were permitted or conditional uses part of the property owner or lessee to under the zoning of a property immediately prior abandon the use. to its rezoning into a BSD zoning district shall 3. Once a use has been determined to be continue to be allowed as permitted or conditional abandoned, any subsequent use shall comply uses on the property. Expansions of uses within with the provisions of §153.059(B). Any Existing Structures as permitted by §153.062(B) new construction, including buildings, site (2) shall be permitted on the property provided features, parking areas, and other associated that at least one of the permitted or conditional construction shall comply with the applicable uses under the prior zoning has been operated provisions of § §153.057 -066. continuously in an Existing Structure and/or (d) Expansions of Existing Uses associated use areas on the property within the 12 months prior to the rezoning of the property into An Existing Use may be enlarged, increased or the BSD zoning district. extended to occupy a greater area of buildings and lands only after a finding by the required lies with the BSD zoning Once a use that complies p g reviewing body as required by § 153.066 that the district is established on a lot or parcel and all enlargement, increase or extension meets all of the Existing Uses have been abandoned or voluntarily following standards: discontinued, no non -BSD use of the prior zoning district may be re- established. 1. The expansion does not have a substantial detrimental effect on, or materially impair the 1. For parcels with a single Existing Structure use and enjoyment of, adjacent uses or lots, configured as a multi - tenant building, once and does not limit the ability for adjacent lots the entire multi- tenant building is abandoned, to develop in accordance with this Chapter, demolished and/or all tenant spaces have established uses under the applicable BSD 2. The buildings and area encompassing the zoning district, no non -BSD use permitted in expansion of the Existing Use complies the prior zoning district may be re- established with all parking, sign, or other regulations on the parcel. applicable to the area affected by the proposed enlargement, increase or extension 2. For parcels with multiple Existing Structures, of use area as required by the applicable only after all buildings have been abandoned, provisions of § §153.057 -066; and demolished and/or all buildings have established uses under the applicable BSD 3. The buildings and area encompassing the zoning district, no non -BSD use permitted in expansion of the Existing Use complies with the prior zoning district may be re- established any reasonable conditions imposed by the on the parcel. ART that are necessary to ensure that the proposed enlargement, increase, or extension (c) Abandonment of an Existing Use of use area will not prove detrimental to 1. If an Existing Use is abandoned for any adjacent properties or the surrounding reason for a period of more than 12 months, community. only those uses allowed in the Bridge Street (e) Any Existing Use may be extended throughout zoning district in which the property is any existing building or parts of a building which located may be established. With regard to were manifestly arranged or designed for that use a multi - tenant building, the tern "Existing at the time of adoption of this amendment, but Use" shall mean all of the existing uses in the Existing Use shall not be extended to occupy that building. any land outside the existing building except as 2. An Existing Use shall be determined by the permitted by § 153.059(B)(5)(d) and as approved Director to be abandoned if one or more of by the required reviewing body. the following conditions exist: BRIDGE STREET DISTRICT § 153.059 7 DEVELOPMENT CODE USES (f) Existing Structures Refer to §153.062(B)(2) for requirements related to Existing Structures. (g) Refer to § §153.065(A)(2) for requirements related to nonconforming sites. (6) Existing Planned Development Districts All planned developments that are effective on the date of adoption of the applicable BSD rezoning shall continue in effect and be considered conforming under this Code in addition to the permitted and conditional uses under the applicable BSD zoning district. This provision shall only apply to planned developments where no construction has commenced. The procedures for the implementation of these developments, including time limits for approval of final development plans or other time limits, must conform to the requirements of Chapter 153, to the extent the approved Planned Unit Development text does not address the requirements. (7) Principal Uses Any property is permitted any combination of principal uses in accordance with the requirements of this section and other applicable provisions of § §153.057 -066. (8) Accessory Uses (a) Accessory uses are permitted only in connection with a permitted or approved conditional use on the same property, and must be clearly subordinate and incidental to that use. (b) Temporary uses are governed by time limits as provided by this Code. (c) Any principal use listed in a zoning district in Table 153.059 -A shall be permitted as an accessory use in the same zoning district. (9) Use Table Refer to Table 153.059 -A. § 153.059 EFFECTIVE DATE USES JANUARY 7, 2014 TABLE 153.059 -A: PERMITTED AND CONDITIONAL USES IN BSD ZONING DISTRICTS KEY BSD Zoning Districts Use Specific Standards See §C) 3.059 H u ( C) P Permitted U Permitted on Upper floor only C Conditional Use S Size Limited T Time Limited m ++ y 0 IY J d a' d 0 d u 0 m i d E U i U N _ N _ 0 0 ns C L �a C ° ZZ 0 0 = s 0 = .0 Os o "Z L = 0 0 �s U 0 -.0 ; mz i 0 0 js .-0 �M mz d k M » u 0. PRINCIPAL USES Residential Dwelling, Single - Family P P (1)(a) Dwelling, Two - Family P Dwelling, Townhouse P P P P P P (1)(b) Dwelling, Live -Work C P P P P P P P P (1)(c) Dwelling, Multiple - Family P P P U U P P P P P (1)(d) Civic /Public /Institutional Cemetery P Community Center C C P P P P P (2)(a) Community Garden P P P P P P P P P P P P (2)(b) Day Care,. Adult or Child C P P P P P P P P P (2)(c) District Energy Plant C C C C C C C C C C (2)(d) Educational Facility C P P P P P P P P P P Elementary or Middle School P P P P P P P P P P P Government Services, Safety C C C C C C C C C P High School P P P P P P P P P P Hospital C/ S C/S C/S C/S C/S C/S C/S (2)(e) Library, Museum, Gallery P P P P P P P P P P P (2)(f) Municipal Parking Lot P P P P P P P P P P Religious or Public Assembly C/S C/S C/S C/S C/S C/S C/S C/S C/S C/S (2)(g) Parks and Open Space P P P P P P P P P P P P Transportation, Park & Ride C C C C C C C Transportation, Transit Station C C P P C C C Animal Care, General Services, Veterinary Offices, and Veterinary Urgent Care and Animal Hospitals C C P P P P P P P P (3)(a) Bank C P P P P P P P P P Bed and Breakfast P (3)(b) Conference Center C C C C C C Eating and Drinking C/S / �C P P P P P P P (3)(c) Interainment /Recreation, door C/S C /C /C C P P P P C (3)(d) Exercise and Fitness C/S C P P C / C P P P P (3)(e) Fueling / Service Station C I I (3)(f) Hotel P P P P P P P P P Office, General C P P P P P P P P U BRIDGE STREET DISTRICT § 153.059 (� DEVELOPMENT CODE USES TABLE 153.059 -A: PERMITTED AND CONDITIONAL USES IN BSD ZONING DISTRICTS KEY BSD Zoning Districts Use 0 0 L 0 0 d P Permitted M 0 = 0 = 0 i 0 k Specific U Permitted on m J � C .0 Ws js Standards upper floor only ++ d i i d M 0 � ` V `0 � G - a �a See C Conditional Use y a' d E U 6a = a m u §Cj 3.059 S Size Limited 0 d d s Os u ( C) T Time Limited H u E N N m 'o m m ° m a' 0 0 U _ _ mz mz » ZZ "Z 0. Office, Medical C P P P P P P P P P Parking, Structure P/C P/C P/C C P/C P/C P/C P/C P/C P/C (3)(g) Parking, Surface Lot C P C C P P C C (3)(h) all, Repair, & Rental C/S %C P P P P (3)(i) Servo C /C /C /C Research & Development P P P P P P P P U Retail, General C/S / /C P / % S P P P P (3)(j) Sexually Oriented Business C (3)(k) Establishment Skilled Nursing, Rehabilitation, Home for the Aging, and C C C C Nursing Homes Vehicle Sales, Rental and Repair C C (3)(1) Wireless Communications Refer to Chapter 99 of Dublin Code of Ordinances ACCESSORY AND TEMPORARY USES ATM, Walk -Up P P P P P P P P P P Bicycle Facilities P P P P P P P P P P P P Community Activity and Special T T T T T T T T T T T T (4)(a) Event Construction Trailer /Office T T T T T T T T T T T (4)(b) Day Care, Adult or Child P P P P P P P P P P P P (2)(c) Drive -in /Drive- through C C C C C C C (4)(c) Dwelling, Accessory P P P P P P P P P P (4)(d) Dwelling Administration, Rental, P P P P P P P P P P (4)(e) or Sales Office Eating & Drinking C P P P P P P P P P P Essential Utility Services P P P P P P P P P P P P Exercise and Fitness P P P P P P P P P P P Farmers Market C P P P P P P P P P Helipad /Heliports C C C C C C Home Occupation P P P P P P P P P P (4)(f) Outdoor Dining and Seating P/C P/C P/C P/C P/C P/C P/C P/C P/C P/C P/C (4)(g) Outdoor Display or Seasonal T T T T T T T T T T (4)(h) Sales Parking, Structure P/C P/C P/C P/C C P/C I P/C P/C P/C P/C P/C (3)(f) Parking, Surface Lot P P P P P P P P P P P (4)(i) Renewable Energy Equipment P P P P P P P P P P P P (4)(j) Renewable Energy Equipment, C C C C C C C C C (4)(k) Wind Residential Model Home T T T T T T T T T (4)(1) Retail or Personal Services C P P P P P P 1 P 1 P P 10 § 153.059 EFFECTIVE DATE USES JANUARY 7, 2014 TABLE 153.059 -A: PERMITTED AND CONDITIONAL USES IN BSD ZONING DISTRICTS KEY BSD Zoning Districts Use 0 0 L 0 0 d P Permitted m 0 0 = s = 0 ° i o k Specific U Permitted on m J ^s U .0 js Standards Upper floor only ++ i 6 m L 0 0 o See C Condition Use y d U �a = a -a m U §Cj 3.059 S Size Limited a w s O s �a H T Time Limite U U U E E "m "m "m :0 O U V)Z V)Z >D 2 2 ZZ Az 0. Swimming Pool P P P P P P P P Transportation, Transit Stop P P P P P P P P P P Vehicle Charging Station P I P P P P P I P P P P Wireless Communications Refer to Chapter 99 of Dublin Code of Ordinances (C) USE SPECIFIC STANDARDS Certain uses listed in this section maybe permitted or conditional only with additional use specific standards. Additional use specific standards may apply to uses within specific building types and neighborhood districts, refer to §153.062(0) for use and occupancy requirements based on building type and §153.063 for use requirements for neigh- borhood districts. (1) Residential Uses (a) Dwelling, Single- Family 1. Applications for development shall not contain more than 35 detached single - family dwelling units. 2. Development applications containing detached single - family dwelling units shall not be accepted if any of the property lines of the proposed units would be located within 400 feet of any single - family detached dwelling constructed or approved within the BSD Residential district after the effective date of this amendment. 3. No single- family detached dwelling unit may be constructed within 500 feet of the I -270 right -of -way as measured from the nearest property line. 4. Single - family detached dwellings shall have no more than one principal building and its permitted accessory structures located on each lot. 5. Single- family dwellings in the BSD Historic Residential District shall meet the requirements of §I53.063(B) and shall not be required to meet the standards of §153.062(0) (1). (b) Dwelling, Townhouse 1. If single- family attached residential units are located across the street from existing single - family detached dwellings, no more than eight attached units may be permitted in a building. Incidental sales of such products as refreshments, athletic supplies for activities conducted on the premises, and similar products are permitted. (b) Community Garden 1. Incidental sales of items grown on the premises are permitted. Areas used for sales shall be located at least 10 feet from the edge of the pavement of any street. Parking shall be located off - street or in permitted on- street locations. One, 24- square -foot sign shall be permitted, located at least 10 feet from the edge of the street and not within the public street right -of -way. 2. Refuse and compost bins must be constructed to be rodent - resistant and located as far as practicable from abutting residential uses. Refuse must be removed from the site at least once a week. 3. No outdoor work activity that involves power equipment or generators may occur after 9:00 pm or prior to 7:00 am. 2. Ground floor residential uses are not permitted on Bridge Street in the BSD Historic Transition Neighborhood District. (c) Dwelling, Live -Work 1. No more than two non - resident employees are permitted in addition to the resident(s) of the dwelling. 2. The non - residential use must be operated by a resident of the live -work dwelling unit. 3. Signs are permitted in accordance with §153.065(H). (d) Multiple - Family Multiple - family uses are not permitted on ground floor elevations fronting Principal Frontage Streets in the BSD Office Residential and Office districts. (2) Civic/Public/Institutional Uses (a) Community Center BRIDGE STREET DISTRICT § 153.059 11 DEVELOPMENT CODE USES 4. One accessory building, not exceeding 100 square feet in gross floor area, maybe permitted, provided the location meets all setback requirements applicable to accessory buildings as provided in §153.074. (c) Day Care, Adult or Child 1. The use shall at all times comply with the requirements of O.R.C. §5104. 2. Outdoor recreation areas shall be located to the side or rear of the principal structure and be enclosed with a permitted fence. The outdoor recreation area shall be screened using fencing and/or landscaping to provide a minimum 50% opaque screen. 3. All outdoor play equipment and shade structures visible from the right -of -way or adjacent properties shall use subdued, earth toned colors. 4. Adult and/or child day care uses are prohibited in civic building types as the sole principal use. (d) District Energy Plant Incidental sales of electrical energy to public utilities are permitted. (e) Hospital Hospitals shall be limited to no more than 75,000 square feet of gross floor area per structure, not including associated parking structures. (f) Library, Museum, Gallery Incidental sales of refreshments and items related to exhibits or activities at the facility are permitted. (g) Religious or Public Assembly Religious or public assembly structures shall be limited to no more than 100,000 square feet of gross floor area, not including associated parking structures. (3) Commercial (a) Animal Care, General Services, Veterinary Offices, and Veterinary Urgent Care and Animal Hospitals All activities shall be conducted indoors. No outdoor animal exercise or activity areas shall be permitted. (b) Bed and Breakfast 1. The property owner shall reside on the property and/or manage the facility. No more than eight guest units are permitted. 2. Guest accommodations are limited to short- term stays of no more than 14 days. (c) Eating and Drinking 1. Eating and drinking facilities shall be limited to no more than 3,500 square feet of gross floor area for single tenant buildings in the BSD Office, BSD Office Residential, and BSD Residential districts, unless otherwise permitted as a conditional use. 2. Eating and drinking facilities in multi - tenant buildings in the BSD Office, BSD Office Residential, and BSD Residential districts shall be limited to no more than 5,000 square feet of gross floor area, or 20 ° % of the gross floor area of the ground floor of the principal structure, whichever is smaller, unless otherwise permitted as a conditional use. (d) Entertainment or Recreation, Indoor 1. Indoor entertainment or recreation uses shall be limited to no more than 25,000 square feet of gross floor area in the BSD Office, BSD Office Residential, BSD Residential, BSD Commercial, and BSD Vertical Mixed Use districts, unless otherwise permitted as a conditional use. 2. In the BSD Public district, the use must be owned and operated by either a public or non- profit organization. (e) Exercise and Fitness To avoid large, single tenant uses that detract from the urban, walkable intent of the Bridge Street District, exercise and fitness uses shall be limited to no more than 10,000 square feet of gross floor area in the BSD Residential and BSD Historic Transition Neighborhood districts. Exercise and fitness facilities exceeding 10,000 square feet in this district may be permitted as conditional uses. (f) Fueling/Service Station 1. Fuel pumps shall be located on the same lot as a permitted building type. 2. Fuel pumps are not permitted between the principal structure and an adjacent principal frontage street. 3. Where pumps are facing any street type except for an alley or service street, a street wall at least three feet high shall be placed between the pumps and associated vehicular circulation area and the street. Refer to §153.065(E)(2) for street wall requirements. 4. Each fueling/service station shall be buffered from adjacent properties as required in §153.065(D)(4) and meet the applicable requirements of §153.065(D)(5). 5. Motor vehicles may be continuously stored outdoors on the property for no more than 24 hours. 6. Refer to §153.062(L) for vehicular canopy requirements. 12 § 153.059 EFFECTIVE DATE USES JANUARY 7, 2014 (g) Parking, Structure (j) Retail, General 1. Parking structures completely lined by space To avoid large, single tenant uses that detract available for occupancy along a public or from the urban, walkable intent of the Bridge private street frontage, and parking structures Street District, general retail uses in the located on the interior of blocks with other BSD Residential, Office Residential, Office, building types located between the parking Commercial, Historic Core and Public districts structure and the street, are permitted. All shall be limited to no more than 20,000 square other parking structures, including podium feet of gross floor area, unless otherwise permitted parking structures with non - occupied space as a conditional use. along public and private street frontages, are (k) Sexually Oriented Business Establishments conditional uses. 1. Sexually Oriented Business Establishments 2. When constructed as a principal use, either shall be subject to the provisions of Chapter as a public or a private parking structure, no 120 of the Dublin Code of Ordinances. more than 75% of the parking spaces shall be used to provide the required accessory 2. No person shall operate, locate, or permit parking for other principal uses located within the location of a sexually oriented business 600 feet of the structure, unless otherwise establishment within 750 feet (as measured approved with a parking plan in accordance from property line to property line) of with §153.065(B)(1)(f). any residential use or district, school, preschool, adult or child care, religious or 3. Where applicable, the building type public assembly, or any other civic /public/ requirements of §153.062(0)(12) — (13) shall institutional use (within the City of Dublin also apply. or other municipality), or another sexually (h) Parking, Surface Lot oriented business establishment. 1. All surface parking lots shall meet the (1) Vehicle Sales, Rental, and Repair surface parking lot design requirements of 1. There shall be not more than one full access §153.065(B)(6). driveway for each 100 feet of lot frontage or 2. When constructed as a principal use, surface portion thereof. parking lots shall not have frontage on or 2. Vehicular use areas are not permitted between have direct access from a principal frontage the principal structure and a principal frontage street unless permitted by the City Engineer. street. Where vehicular use areas are located (i) Personal, Repair, and Rental Services between a principal structure and any other 1. Personal, repair, and rental service street type, a street wall shall be installed establishments shall be limited to no more along that portion of the lot line between the than 10,000 square feet for single tenant vehicular use areas and the street. Refer to buildings in the BSD Office, BSD Office §153.065(E)(2) for street wall requirements. Residential, and BSD Residential districts, (4) Accessory and Temporary Uses unless otherwise permitted as a conditional (a) Community Activity and Special Event use. 1. The site of the activity or event shall be 2. Personal, repair, and rental services in multi- adequately served by utilities and sanitary tenant buildings in the BSD Office, BSD facilities. Office Residential, and BSD Residential districts shall be limited to no more than 2. The activity or event shall not become a 10,000 square feet of gross floor area, or 20 % safety hazard or public disturbance and of the gross floor area of the ground floor of shall not cause substantial adverse impacts the principal structure, whichever is smaller, on surrounding properties or land uses by unless otherwise permitted as a conditional creating excessive noise, glare, heat, dust, use. odors, or pollutants as determined by the Director and Fire Marshal. 3. Personal, repair, and rental service uses shall be limited to no more than 25,000 3. A permit shall be obtained for the Community square feet of gross floor area in all other Activity or Special Event from the City of BSD zoning districts except the BSD Indian Dublin Events Administration. Run Neighborhood, BSD Sawmill Center (b) Construction Trailer /Office Neighborhood and BSD Scioto River Construction trailers and/or offices shall comply Neighborhood, unless otherwise permitted as with the setbacks applicable to principal structures a conditional use. on the property, but are not required to comply with street frontage requirements for building BRIDGE STREET DISTRICT § 153.059 13 DEVELOPMENT CODE USES types. Construction trailers and/or offices shall comply with the provisions of §153.097. (c) Drive- in/drive- through 1. Drive- in/drive- throughs are permitted only as accessories to banks in the BSD Vertical Mixed Use and BSD Historic Transition Neighborhood districts following approval of a Conditional Use application by the Planning and Zoning Commission. 2. Drive - in/drive- through vehicular stacking areas and associated service locations shall not be on the side of a building facing a principal frontage street. Where drive -in/ drive- through access lanes are facing a non - principal frontage street, a street wall at least three feet high shall be placed between the access lanes and the street Refer to § I 53.065(E)(2) for street wall requirements. 3. No menu boards, speakers, or service windows shall be located between any fagade of the principal structure and a front or comer side property line. 4. Drive - in/drive- through vehicle stacking spaces shall be at least 20 feet long. Stacking spaces may not impede on -site or off -site vehicular, bicycle, or pedestrian circulation. Where five or more stacking spaces are provided, the individual stacking lanes shall be clearly delineated. The number of stacking spaces and a traffic and pedestrian circulation plan shall be submitted by the applicant with the conditional use application and approved by the Planning and Zoning Commission. 5. Uses with drive- in/drive- through facilities shall be buffered from adjacent properties as required in §153.065(D)(5). 6. Audible electronic devices such as loudspeakers, service order devices, and similar instruments shall not be located within 25 feet of the lot line of any residential district or use and shall be subject to §132.03(A)(6). 7. Refer to §153.062(L) for vehicular canopy location and design requirements. 8. Structures related to drive- in/drive- throughs shall not have frontage on, or be readily visible from, any shopping corridor. 9. Protective bollards, when used, shall be painted to match one of the colors used on the nearest structure with which the bollards are associated. (d) Dwelling, Accessory An accessory dwelling located in a single- family, two - family, or townhouse dwelling must comply with the following standards: 1. No more than one accessory dwelling unit is permitted on a lot with a single - family, two- family, or townhouse dwelling. Where townhouse dwellings do not have individual lots, no more than one accessory dwelling unit is permitted for each townhouse unit in the development. 2. An accessory dwelling unit shall be limited to no more than 800 square feet of gross floor area. 3. When accessory to a single- family dwelling, the accessory dwelling unit may be located either within the single - family dwelling structure or in a permitted accessory structure. 4. When accessory to a townhouse dwelling, the accessory dwelling unit may only be located in a permitted accessory structure or within the basement level of the principal dwelling. 5. When accessory to a single - family dwelling or two - family dwelling, the accessory dwelling unit shall have a separate entrance from the principal dwelling unit, and that entrance shall not face the front lot line and shall not be located on the same building fagade as the principal building entrance closest to the street. 6. The owner of the dwelling must occupy either the principal dwelling unit or the permitted accessory dwelling unit. 7. Ownership of the accessory dwelling unit may not be separate from the ownership of the principal dwelling unit. (e) Dwelling Adm inistration, Rental, or Sales Office These uses shall comply with the provisions of §153.073(D) and setbacks applicable to principal structures on the property, but are not required . to comply with street frontage requirements for building types unless the use is conducted within a permanent principal structure. (f) Home Occupations All home occupations in the BSD Historic Residential district shall comply with the provisions of §153.073. In all other BSD zoning districts, home occupations shall comply with the following standards. 1. The use must be conducted entirely within the principal dwelling or accessory buildings. 2. No business involving retail sales of goods on the premises is permitted. 3. No person not a member of the household residing on the premises shall work on the premises. 4. Not more than 25% of the ground floor gross floor area of the principal dwelling shall be devoted to the home occupation. 14 § 153.059 EFFECTIVE DATE USES JANUARY 7, 2014 5. The exterior of the structure shall not be modified to accommodate the home occupation. 6. No display or signs pertaining to the home occupation shall be visible from the street. 7. No equipment shall be used that creates noise, vibration, sound, smoke, dust, odors, heat, glare, X -Ray or electrical disturbance to radio or television that is discernible in adjacent dwelling units or at the property line. 8. All home occupations that require a license from the state or City shall maintain a valid license at all times and shall operate in compliance with the terms of that license and all applicable regulations of the state or City at all times. 9. Home occupations shall not include or involve motor vehicle or equipment repair, the sale of weapons or hazardous materials, or other activities that would constitute a nuisance in a residential area. (g) Outdoor Dining and Seating 1. Outdoor dining and seating areas, furniture, and enclosures shall be set back at least five feet from the curb and at least five feet from all street trees and street furniture. In no case shall these amenities be placed in a manner that would provide less than six feet of clear area for pedestrian use. 2. The use of outdoor speakers shall require a conditional use. Outdoor speakers shall comply with the provisions of § 132.03(A)(6) of the Dublin City Code. 3. Advertising is not permitted on dining furniture, accessories, or other similar amenities. 4. Dining furniture shall be of the same design, material and color for all furniture associated with the use. When not in regular use, outdoor furniture shall be stored in a location that is not visible to the public, unless the patio furniture is all- weather material, set up for use and not covered in any way, and weather conditions make the use of furniture possible. (h) Outdoor Display or Seasonal Sales 1. Outdoor seasonal plant display shall comply with the provisions of §153.099. 2. Outdoor sale of merchandise is permitted, and shall comply with the provisions of § I53.099(C)(2). Merchandise shall only be displayed during the hours of operation for the principal use. No permit is required. 3. Outdoor sales of Christmas trees and pumpkins shall comply with the provisions of Chapter 116 of the Dublin City Code. (i) Parking, Surface (Accessory) 1. Where the non - residential gross floor area of the principal structure is 100,000 square feet or more and the principal structure is on a lot that is four acres or less, surface parking shall not be used to provide required parking. However, surface parking may be used for a maximum of 5% of the required spaces provided the parking lot is located to the side or rear of the principal structure and not fronting on a public street. 2. This requirement applies only to principal structures constructed after the effective date of this amendment. 0) Renewable Energy Equipment 1. In the BSD Historic Core and BSD Historic Residential districts, only equipment for the collection of solar and geotherm al energy is permitted. 2. Ground - mounted equipment for the collection of geothermal energy is permitted only to the rear of and within five feet of the principal structure. 3. Ground - mounted equipment for the collection of solar energy is permitted to the side or rear of the principal structure, but not within five feet of a side or rear property line. Rooftop equipment for the collection of solar energy is permitted provided it extends no more than 18 inches beyond the maximum permitted height of the principal structure. 4. Building - mounted renewable energy equipment shall be integrated into the architectural character of the principal structure. 5. Ground- mounted renewable energy equipment shall be sited to minimize view from the public right -of -way and adjacent properties, and shall be camouflaged to the extent that the equipment can function normally. (k) Renewable Energy Equipment, Wind 1. Ground - mounted equipment for the collection of wind energy is permitted to the rear of the principal structure, may not exceed the maximum permitted height of the principal structure by more than 40 feet, and must be set back from each property line a distance equal to the height of the equipment that exceeds the height of the principal structure. 2. As an exception, within 200 feet of the I -270 right -of -way, ground - mounted wind energy BRIDGE STREET DISTRICT § 153.059 15 DEVELOPMENT CODE USES equipment shall be limited to 150 feet and must be set back from each property line a distance equal to the height of the equipment. 3. Height of the equipment is measured to the farthest extent of any part of the equipment 4. Building- mounted equipment for the collection of wind energy must be integrated into the architectural character of the principal structure. 5. Rooftop- mounted equipment for the collection of wind energy shall be permitted to exceed the maximum permitted height of the principal structure by no more than 15 feet (1) Residential Model Home Residential model homes shall comply with the provisions of §153.073(D). 16 § 153.059 EFFECTIVE DATE USES JANUARY 7, 2014 § 153.060 LOTS AND BLOCKS (A) INTENT The intent of §153.060 is to establish a network of interconnected streets with walkable block sizes organized to accommodate multiple modes of transportation. The street network includes certain streets designated as principal frontage streets to create continuous, pedestrian - oriented block faces of front building fapades and limited driveway interruptions. It is intended that block configurations encourage and support the principles of walkable urbanism provided in §153.057(D) and the walkability standards of §153.065(1). (B) APPLICABILITY The requirements of this section apply to developments within all BSD zoning districts that require Development Plan Review in accordance with §153.066, and for land within all BSD zoning districts proposed for subdivision in accordance with Chapter 152. (C) GENERAL BLOCK AND LOT LAYOUT (1) Interconnected Street Pattern The network of streets within the Bridge Street District is intended to form an interconnected pattern with multiple intersections and resulting block sizes as designated in §153.060(0)(2). (a) The arrangement of streets shall provide for the continuation of existing or planned streets from adjoining areas into new developments where practicable as determined by the City Engineer. This provision shall not be construed as prohibiting the termination of streets at public street intersections where appropriate, provided that the overall connectivity of the street network is maintained, and intersections are adequately spaced as determined by the City Engineer. (b) Cul -de -sac and dead end streets are not permitted, except as specified in §153.060(C)(1)(t). (c) Wherever practicable, streets should be designed to follow natural features rather than interrupting or dead - ending at the feature. (d) Streets shall terminate at either an open space type or a front or comer side building fagade. Refer to §153.0620 for building requirements at these locations. (e) Refer to §153.061 and the City's Thoroughfare Plan for the general locations and configurations of existing and planned streets within the Bridge Street District. (t) Exceptions Where an existing barrier limits the extension of the street network, streets shall be created to match the above requirements to the maximum extent practicable. Existing barriers include such features as a highway, waterway, open space, utility line, roadways with limited access restrictions, or development that is expected to rem ain. (2) Maximum Block Size (a) Required Subdivision Unless otherwise permitted by this chapter, all developments requiring Development Plan Review in accordance with §153.066(E)(1)(b)2- 4 shall subdivide consistent with the maximum block sizes as required by Table 153.060 -A, Maximum Block Dimensions. TABLE 153.060 -A. MAXIMUM BLOCK DIMENSIONS BSD Districts Len th Perimeter (fttl (ft) Residential 500 1,750 Office Residential 500 1,750 Office 500 1,750 Commercial 500 1,750 Historic Residential 200 800 Historic Core 200 800 Historic Transition 300 1,000 Neighborhood Indian Run Neighborhood 500 1,750 Sawmill Center Neighborhood 500 1,750 Scioto River 500 1,750 Neighborhood Vertical Mixed Use 500 1,750 Public 300 1,000 (b) Measurement 1. Block length shall be the distance along one side of a block measured between two parallel or approximately parallel property lines on the opposite sides of the block. 2. Block perimeter shall be the aggregate block length along all sides of a block measured along the property lines. 3. Alleys and service streets shall not be used to measure block length. (c) Shopping Corridors Additional block requirements for shopping corridors are noted in § 153.063, Neighborhood Standards. (d) Exception When existing barriers limit extension of the street network, blocks shall be created to match the above requirements to the maximum extent practicable. Barriers may include such features BRIDGE STREET DISTRICT § 153.060 17 DEVELOPMENT CODE LOTS & BLOCKS as a highway, waterway, open space, utility line, roadways with limited access restrictions, or development that is expected to remain. (3) Block Configuration Refer to Figure 153.060 -A for an illustration of typical block elements. (a) The shape of a block shall be generally rectangular, but may vary due to natural features or other site constraints. (b) Blocks shall be arranged with front property lines along at least two sides. (4) Principal Frontage Streets Principal frontage streets are designated to ensure certain streets are lined with continuous, pedestrian - oriented block faces of front building fagades or public open space, with limited conflicts between pedestrians and vehicular traffic. (a) Principal frontage streets are as designated in §153.061, Street Types. Additional principal frontage streets may be designated by the required reviewing body as development progresses within the neighborhood districts in §153.063, Neighborhood Standards. (b) Access to blocks shall be located to comply with the principal frontage street requirements in §153.060(C)(5). (c) The principal frontage street shall be used to determine lot frontage orientation, as described in §153.060(C)(9). FIGURE 153.060 -A. TYPICAL BLOCK ELEMENTS Block — Perimeter L a+ m J L: Block (5) Block Access Configurations (a) Access for alleys, service streets and driveways shall not be permitted from a principal frontage street, unless the City Engineer determines that access from any other street is impracticable. The determination shall be based on locations of existing and proposed vehicular access points of other developments along the principal frontage street and the number of principal frontage streets bordering the property. (b) Blocks shall include alleys /service streets or driveway entrances with the following recommended configurations unless otherwise permitted by the City Engineer. See Figure 153.060 -B, Typical Block Access Configurations. 1. Mid -Block Access. This configuration includes an alley or drive running through or near the center of the block. 2. "T" Configuration. This configuration includes two perpendicular alleys or drives within a block, forming a "T," allowing development to front on three block faces. FIGURE 153.060 -B. TYPICAL BLOCK ACCESS CONFIGURATIONS Mid -Block Access v v W m Y c 2 LL 6 u G a` f � I . • 7 a Lot i �f+..u.ru�.v..u.a.a I I i Lot I is A nw L v a � !vi 1 I: i M I. 0 a iU) v0 j Lot v yl Lot I; w w ko ; 7u0 I• ] U) g j � Lot j i Lot I I: Block (5) Block Access Configurations (a) Access for alleys, service streets and driveways shall not be permitted from a principal frontage street, unless the City Engineer determines that access from any other street is impracticable. The determination shall be based on locations of existing and proposed vehicular access points of other developments along the principal frontage street and the number of principal frontage streets bordering the property. (b) Blocks shall include alleys /service streets or driveway entrances with the following recommended configurations unless otherwise permitted by the City Engineer. See Figure 153.060 -B, Typical Block Access Configurations. 1. Mid -Block Access. This configuration includes an alley or drive running through or near the center of the block. 2. "T" Configuration. This configuration includes two perpendicular alleys or drives within a block, forming a "T," allowing development to front on three block faces. FIGURE 153.060 -B. TYPICAL BLOCK ACCESS CONFIGURATIONS Mid -Block Access v v W m Y c 2 LL 6 u G a` f � I I I r -k A nw L v I� I w U) W I m Y 0 I o I LL a U I c i a` J "T" Configuration scree I Y c I m y 2 Principal Frontage Street - H" Configuration Service Sheet I �i Il i >I I I 0� Principal Frontage Street Principal Frontage Street 18 § 153.060 EFFECTIVE DATE LOTS & BLOCKS JANUARY 7, 2015 3. "H" Configuration. Similar to the "T" configuration, this configuration allows development to front on all four block faces. (c) Wherever practicable, as determined by the City Engineer, vehicular access to blocks shall be aligned with other access points on opposite sides of the same block as well as aligned across the street from vehicular access points to other blocks. (6) Nid- B1ockPedestrianways Refer to §153.065(I)(2)(a) for requirements for mid - block pedestrianways. (7) Typical Lot Dimensions (a) Any lot shall be created to meet the requirements of one or more of the building types permitted by the district in which it is located, as provided in §153.062, Building Types. (b) Minimum lot width shall be measured at the front property line. (8) Typical Lot Configuration (a) To avoid creating irregular lots, interior side lot lines shall be perpendicular to the street right -of- way to the extent practicable. (b) Flag lots are prohibited. (9) Street Frontage All lots shall have at least one lot frontage along a public street. (a) Front Property Line 1. A lot line bordering a single street right -of- way shall be the front property line. 2. A lot line bordering a principal frontage street shall be the front property line unless otherwise specified in this section. (b) Comer Side Property Lines 1. For corner lots occupied by a single building, one lot line shall be the front property line and one lot line shall be the corner side property line. 2. For corner lots occupied by multiple buildings, lot lines shall be designated as front or corner side property lines as necessary to meet the building type street frontage requirements along both frontages. (c) Lots bordering more than two principal frontage streets shall meet the street frontage requirements as provided in §153.062(1) along at least two of the streets. Subject to approval by the required reviewing body, the street frontage requirements shall be maximized to the extent practicable along the other principal frontage streets. (d) Lot lines along alleys or service streets or I -270 are not permitted to be designated as front or comer side property lines. (e) Alleys or service streets shall not be considered street frontage and shall not be subject to street frontage requirements described in § §153.059 to 153.065. (f) Where lot lines cannot be determined by the requirements of this section, the required reviewing body shall designate which lot lines shall serve as the front, rear and comer side property lines. To designate lot lines, the required reviewing body may consider all relevant factors and information, including but not limited to 1. The street types and the intended character of existing or proposed streets on which the lot has, or is proposed to have, frontage, 2. The proximity of existing or proposed principal frontage streets; 3. The locations of front and comer side property lines on adjacent lots or lots located on the opposite side of the street; and 4. Adjacency to an existing or planned shopping corridor. 2. The proximity of existing or proposed principal frontage streets; and 3. The locations of front and comer side property lines on adjacent lots or lots located on the opposite side of the street BRIDGE STREET DISTRICT § 153.060 19 DEVELOPMENT CODE LOTS & BLOCKS § 153.061 STREET TYPES (A) INTENT The intent of §153.061 is to develop a comprehensive network of streets throughout the Bridge Street District that are configured to accommodate multiple modes of transportation, organized by a hierarchy of street character families, and consistent with the placemaking principles of the Bridge Street District Area Plan of the Dublin Community Plan and guided by the Thoroughfare Plan. It is intended that the street network encourage and support the principles of walkable urbanism provided in §153.057(D) and the walkability standards of §153.065(1). (B) APPLICABILITY The requirements of §153.061 apply to all new and existing streets and alleys or parts thereof as developed or reconfigured in the Bridge Street District, whether public or private. (C) STREET NETWORK Streets shall form an interconnected street pattern with walkable block sizes as required in §153.060. (1) Street Families Existing and planned streets within the Bridge Street District are classified by street families. The intent of the street family designation is to provide a wide range of street configurations to accommodate different land use contexts and transportation needs while establishing a broader framework of street character throughout the area. The purpose and intended application of each street family is described below. (a) Corridor Connector Streets The corridor connector street family provides a series of street types that balance non - motorized and vehicular travel options along high- capacity thoroughfares. This street family serves multiple types of development and provides crosstown connections, while accommodating various transitions in land use and street character. (b) District Connector Streets The district connector street family provides a series of high- to medium - capacity street types that serve a wide variety of uses and development densities. District connector streets provide connections between districts throughout the Bridge Street District along high - visibility frontages, and typically serve as prime locations for destination- oriented development such as shopping corridors. (c) Neighborhood Streets The neighborhood street family provides a series of low- to medium - capacity street types applicable to a wide variety of land use contexts, but often to residential areas or neighborhood - serving commercial uses. Neighborhood streets provide a finer - grained network of street connections that allow for multiple, interconnected travel routes, but typically serve more localized destinations rather than cross - corridor travel. (d) Alleys and Service Streets Alleys and service streets are very low capacity, low speed streets located to the rear of lots that minimize driveway interruptions in the pedestrian realm. Alleys and service streets provide access to parking facilities, loading facilities, and service areas for refuse and utilities. Alleys may also serve as mid -block pedestrianways if designed according to the requirements of §153.060(C)(6). (2) Street Types Street families are comprised of multiple street types, each configured to accommodate specific transportation and land use needs while reinforcing the intended character and function of the applicable street family. New streets shall be designed using the principles and characteristics defined by each street type. The City Engineer shall determine which street type is applicable and may require modifications to right -of -way and/or pavement widths, or require additional street infrastructure elements depending on unique site characteristics. Available street type configurations shall be reviewed with the applicant during the Pre- Application Review process, as described in §153.066. (3) Existing Streets Where existing streets are planned to be realigned, relocated or removed, the City shall reserve the right to maintain those rights -of -way and to incorporate them into the planned street network. The City Engineer shall designate the street family and street type(s) and required improvements appropriate for these streets. (4) Street Network Map (a) Refer to Figure 153.061 -A for a map of the planned Bridge Street District street network and street family designations. In addition to the Thoroughfare Plan, the Street Network Map shall be used as a guide in determining the appropriate locations and alignments of new streets during the Development Plan approval process as required in § 153.066. (b) Actual street alignments and locations will be determined through the Development Plan Review process as individual properties are developed and through the City's Capital Improvements Program process, as applicable. Alignments may be subject to change pending further engineering analysis and land use programming. Where existing alignments are shown to remain, these streets may be subject to improvements necessary to bring them into conformance with a permitted street type. 20 § 153.061 EFFECTIVE DATE STREETTYPES JANUARY 7, 2015 (c) Graphic Intent The street network depicted in Figure 153.061 -A is intended to illustrate one result of the block size and connectivity requirements in §153.060 and is representative of a general development pattern for the Bridge Street District. Figure 153.061 -A is not intended to represent all requirements or actual development, nor is it intended to designate the precise locations for specific street types. (d) Illustrated Corridor Connector Streets Corridor connector streets illustrated in Figure 153.061 -A include existing high- capacity thoroughfares in existing and potentially realigned configurations. (e) Illustrated District Connector Streets District connector streets illustrated in Figure 153.061 -A include existing, realigned and potential new streets representing major street connections necessary to ensure connectivity throughout the Bridge Street District. (f) Illustrated Neighborhood Streets Neighborhood streets illustrated in Figure 153.061 -A include existing and potential new street connections generally consistent with the block size requirements of §153.060. (g) Alleys and Service Streets The locations of new alleys and service streets are subject to the block access requirements of §153.060 and are not illustrated on Figure 153.061 -A. Actual locations of new alleys and service streets will be determined through the Development Plan and Site Plan Review processes. (D) PRINCIPAL FRONTAGE STREETS Principal frontage streets are designated to ensure certain street types are lined with continuous, pedestrian- oriented block faces of front building fagades, and to limit conflicts between pedestrians and vehicular traffic. Refer to Figure 153.061 -A for principal frontage street designations in the planned Bridge Street District street network. (1) Street Frontage Requirements (a) All lots and blocks with frontage along a principal frontage street shall meet the requirements of § I 53.060(C)(4) and all development requirements associated with principal frontage streets described elsewhere in this Chapter, as may be applicable. (b) In addition to the principal frontage streets depicted in Figure 153.061 -A, all lots, blocks and associated development with frontage along a street or street segment which also has any open space type frontage as listed in § 153.064, with the exception of pocket park and pocket plaza open Where a lot or block is fronted by multiple principal frontage streets, and where access from a principal frontage street is determined to be necessary as permitted by §153.061(D)(2) the following street family hierarchy shall be considered by the City Engineer in determining permitted vehicular access locations to the maximum extent practicable: (a) Neighborhood streets shall be the preferred means of providing vehicular access for alleys, or for driveways where no alley is present. Where a neighborhood street is designated as a principal frontage street, any other neighborhood street shall be used to provide vehicular access wherever practicable. (b) District connector streets shall take precedence over neighborhood streets in maintaining the principal frontage street character. Vehicular access shall not be permitted from a district connector street if suitable alternative access from a neighborhood street is available. (c) Corridor connector streets shall take precedence above all other street types in maintaining the principal frontage street character. Vehicular access shall not be permitted from a corridor connector street if a suitable alternative access location is available. space types, shall meet all applicable principal frontage street requirements. (c) Alleys and service streets shall not be designated as principal frontage streets. (2) Vehicular Access (a) Vehicular access shall not be permitted from a principal frontage street, unless the City Engineer determines that access from any other street is impracticable. Where this determination is made, all other applicable principal frontage street requirements described elsewhere in this Code shall continue to apply. (b) Vehicular access refers to private driveways or lanes and to alleys or service streets whether public or private. Other public street intersections are not restricted by principal frontage street designations, but may be subject to access management limitations as determined by the City Engineer. (c) Alleys and service streets are the preferred means of vehicular access to lots and blocks. If used, alleys and service streets shall provide access from a non - principal frontage street wherever practicable. Refer to § I53.060(C)(5) for block access configurations. (3) Multiple Principal Frontage Streets BRIDGE STREET DISTRICT § 153.061 21 DEVELOPMENT CODE STREET TYPES (E) TYPICAL STREET ELEMENTS Typical elements of a street right -of -way are divided into the vehicular and pedestrian realm. Each street Type outlines which facilities are applicable and provides typical design specifications. The required types and configurations of street elements for specific street types shall be reviewed with the applicant during the Pre - Application Review process, as described in §153.066. Appropriate street elements shall be determ tried by the City Engineer. (1) Bicycle Facilities A variety of bicycle accommodations are permitted in the street right -of -way, including cycletracks, bicycle lanes, and shared lanes. Appropriate bicycle facilities for specific street types shall be determined by the City Engineer. (2) Vehicular On- Street Parking The appropriate configuration and dimensions of on- street parking for specific street types shall be determined by the City Engineer. (a) On- street parking spaces may be counted toward the minimum required parking for a parcel, subject to the requirements of §153.065(B)(2). (b) On- street parking spaces may be used for loading and delivery, subject to the requirements of §153.065(B)(7). (3) Crosswalks Refer to the walkability standards of §153.065(I)(3)(a) for requirements for crosswalks. (F) CURB RADII AT INTERSECTIONS Curb radii at intersections shall be minimized to the greatest extent practicable to shorten pedestrian crossing distances, reduce vehicle turning speeds, and improve sight distance between pedestrians and motorists, balancing the ease of vehicular, bicycle and pedestrian travel. (1) Typical Design Vehicle Intersections shall be designed for the typical design vehicle as opposed to the maximum design vehicle, as determined by the City Engineer. When the design vehicle requires a larger curb radius, approval of the City Engineer is required. (2) Permitted Radii The maximum curb radius for intersections along State Route 161, Riverside Drive, and Sawmill Road is 35 feet. Curb radii at all other intersections may range between 15 and 25 feet, as approved by the City Engineer. (G) FIRE ACCESS Street configurations have been calculated to provide appropriate fire truck access. Where applicable, the following fire access accommodations shall also be required at the determination of the Fire Chief: Building access zones provide dedicated space within the street right -of -way for fire trucks and other emergency vehicles to position necessary equipment and to access adjacent buildings. (a) A building access zone of 40 feet in length shall be provided for buildings with a height of 30 feet or greater, unless this requirement is waived by the Fire Chief where sufficient alternate access is available. (b) Building access zones should be located as close as practicable to the structure's principal entrance. Where possible, building access zones should be located to provide access to multiple buildings. (c) Where present, fire hydrant zones may be included within the building access zone. (d) A building access zone shall be striped and signed as a fire lane to restrict on- street parking within the zone. (e) Where on- street parking is provided, building access zones should be designed and located to minimize the reduction of parking spaces to the greatest extent practicable by co- locating with other zones or facilities in the street right -of- way, such as intersection visibility triangles and dedicated bus stops. (f) All or portions of a building access zone are encouraged to be designed as a curb bump -out, expanding the width of the street buffer into the on- street parking lane. This design should be co- located with mid -block pedestrian crossings where present. (g) Hardscape areas within building access zones shall be designed and constructed to provide sufficient physical support for emergency vehicles as required by the Fire Chief. (1) Room to Pass Where the total width of all travel lanes is narrower than 22 feet, the following shall apply: (a) Unless otherwise required by the Fire Chief, each block shall provide at least one 22 -foot opening in the on- street parking or a 22 -foot dedicated pull -off space on each side of the street to allow vehicles to pull over for a fire truck to pass. (b) A driveway, alley entrance, bus stop, building access zone or fire hydrant zone may be used to fulfill this requirement (2) Building Access Zone 22 § 153.061 EFFECTIVE DATE STREETTYPES JANUARY 7, 2015 This page has been left blank intentionally. BRIDGE STREET DISTRICT § 153.061 23 DEVELOPMENT CODE STREET TYPES FIGURE 153.061 -A. BRIDGE STREET DISTRICT STREET NETWORK GRAPHIC INTENT The street network depicted in this map is intended to illustrate one result of the block size and connectivity requirements in §153.060 and is representative of a general development pattern for the Bridge Street District. This map is not intended to represent all requirements or actual development, nor is it intended to designate the precise locations for specifi� street types. 0 �RdWff to. 53.063(E)for devebpmeM In In the BSC on Neighborhood Run d Dishid P TF 0ST oar \, �N0i9 z 3` x c IN D.AN PVN0X �<., irvolaN sN Refer to §153.053(D)for N oaTN'T development intent in the !p BSC Historic Transition a Neighborhood Dlstrkl ' ti Ill , r r -.. a c IN D.AN PVN0X �<., irvolaN sN Refer to §153.053(D)for N oaTN'T development intent in the !p BSC Historic Transition a Neighborhood Dlstrkl O J K a JQ pE0. METR0 pL � Z x £ I m ILL Street Families Existing Potential = m av Corridor Connector Streets Mile District Connector Streets' �. Neighborhood Streets (Not Depicted) Alleys /Service Streets Refer to §153.061(C) fora description of the purpose and intended application of each street family. Principal Frontage Streets Refer to §153.060(C)(4) and §153.061(D) for principal frontage street requirements. Z 1 D a 0 D A 4 24 § 153.061 EFFECTIVE DATE STREET TYPES JANUARY 7, 2015 0 O z 4 S J . 1 1 Re Re I I� — 't—L-At __ , Tu<< e Rererb$753.063(C) for c development intent in the BBC Sawmill Center Neighborhood Diabict Re J__ ! e. Re I < I 1 A 8 5 NKER DR 11 1 A 0 c _ d f z 1 v 1 3 J J m O -; C STONERIO e� ti n m m z A • Intersections with Corridor Connector Streets may be subject to access restrictions as detemtined by the City Engineer. '•Future District Connector Street depicted crossing the South Fork Indian Run is intended to be shown in the approximate location of the e>asting sewer line. Actual location to be determined during the capital programming process. N 0 500 1,000 o Feet BRIDGE STREET DISTRICT DEVELOPMENTCODE § 153.061 STREET TYPES 25 1 1 1 1- -T - -r- / 1 1 1 " t" _ - - -JL W D UBLIN -G— RA . I 1 A 8 5 NKER DR 11 1 A 0 c _ d f z 1 v 1 3 J J m O -; C STONERIO e� ti n m m z A • Intersections with Corridor Connector Streets may be subject to access restrictions as detemtined by the City Engineer. '•Future District Connector Street depicted crossing the South Fork Indian Run is intended to be shown in the approximate location of the e>asting sewer line. Actual location to be determined during the capital programming process. N 0 500 1,000 o Feet BRIDGE STREET DISTRICT DEVELOPMENTCODE § 153.061 STREET TYPES 25 § 153.062 BUILDING TYPES (A) INTENT The building types detailed in this section outline the required building forms for new construction and renovated structures within the Bridge Street District zoning districts. The intent of these building types is to provide a range of high quality residential, commercial, mixed -use and civic building options to reinforce the character of each district. (B) GENERAL BUILDING TYPE REQUIREMENTS (1) Applicability (a) As provided in §153.062, the building type standards shall be applied to all new development within the Bridge Street District. (b) New structures constructed after the date of this amendment that are subsequently made nonconforming by an amendment to this chapter shall meet the requirements of §153.004(C). (2) Existing Structures (a) At the effective date of this amendment, where one or more lawful principal buildings exist on a site that do not comply with the requirements of this chapter because of restrictions such as front property line occupation, lot coverage, required building zone or setback, buildable area or other requirements related to siting or height, the structure(s) may be continued as existing at the effective date of this amendment if the requirements of §153.062(B)(2) are met. (b) Existing Structures may be extended, enlarged, altered, remodeled or modernized after approval by the required reviewing body upon finding that all of the following conditions are met: 1. That the Existing Structure meets all height, area, setback and parking and loading provisions that were applicable immediately prior to the rezoning of the property into a BSD zoning district. 2. That the enlargement or extension is limited to the same parcel on which the Existing Structure was located on at the time of the adoption of this amendment. 3. That the improvement does not interfere with the use of other properties located contiguous to or directly across the street from the parcel on which the Existing Structure is located. 4. That the enlargement or extension does not exceed 50% of the gross floor area of the Existing Structure at the time of the adoption of this amendment. 5. That the improvements do not make the structure any further from conformance with the requirements of the applicable BSD zoning district. 6. That the improvements to the Existing Structure are architecturally appropriate, at the determination of the required reviewing body. (c) Parking for Existing Structures 1. Existing Structures improved as permitted in §153.062(B)(2)(b) shall provide the minimum parking and loading spaces required by Tables 153.065 -A and 153.065 -C. 2. Required parking for Existing Structures may be modified through an approved parking plan as described in §153.065(B)(1)(f). (d) Reconstruction or Movement 1. Should an Existing Structure be damaged or destroyed by an act of God, or other action outside the control of the owner/lessee, that Existing Structure may be repaired or reconstructed as it existed prior to the action causing it to be damaged or destroyed. 2. Any permitted reconstruction shall be started within 12 months of the time of damage and be continued until completed. If this requirement is not met, the structure shall either be removed or reconstructed to meet the requirements of a new building. 3. Should the property/building owner or lessee demolish more than 50% of the gross floor area of an Existing Structure, then all of the improvements on the property associated with that Existing Structure must be constructed and/or brought into conformance with the requirements of this chapter. (e) Determination of Building Type 1. The required reviewing body may designate an Existing Structure as a specific building type upon a finding that the structure is substantially similar in form and design to one of the permitted building types for the district in which the structure is located. 2. Should the required reviewing body designate an Existing Structure as a specific building type, then all further improvements on the property associated with the Existing Structure must be constructed and/or brought into conformance with the requirements of this chapter to the maximum extent practicable, as determined by the required reviewing body. (f) Exceptions 1. Once subsequent modifications are made to the Existing Structure that bring it into compliance with the specific building type requirements for the designated building type, 26 § 153.062 EFFECTIVE DATE BUILDING TYPES JANUARY 7, 2015 those modifications to the Existing Structure (g) Refer to §153.059(A)(6) for requirements for shall not be further modified in a manner Existing Uses. that brings the Existing Structure out of (3) General Requirements compliance with those specific requirements. 2. For Existing Structures within the BSD Every building, erected, altered or moved, shall be Historic Core and Historic Residential located on a lot as defined herein, or as otherwise Districts, the Architectural Review Board permitted by this chapter. All building types shall meet shall determine those building type the following requirements. requirements that will apply to specific (a) Zoning Districts buildings. Each building type shall be constructed only 3. All new construction in the BSD Historic within its designated BSD zoning district. Table Core District shall meet the requirements of 153.062 -A, Permitted Building Types in Each §153.062, §§153.170 through 153.180, and BSD Zoning District, outlines which building the Historic Dublin Design Guidelines. types are permitted in which BSD zoning districts. 4. All new construction in the BSD Historic Refer to §153.058, BSD Districts Scope and Residential District shall meet the Intent for a description of each district. requirements of §153.063(B), § §153.170 (b) Uses through 153.180 and the Historic Dublin Each building type may house the uses allowed in Design Guidelines, in addition to the the district in which it is located. Refer to Table requirements of §153.062 as determined 153.059 -A. Additional use restrictions may apply to be architecturally appropriate by the based on the specific building type requirements Architectural Review Board. V BSD DISTRICTS Single Family Detached Single Family Attached Uf a Apartment Building Loft Building 0 Z Corridor Building w N Mixed Use Building 7 m Commercial Center W W Large Format Commercial Building H w � Historic Mixed Use Building W Historic Cottage Commercial a Civic Building Parking Structure Podium Apartment Building i m 0 7 c 0 'O 01 'O A 01 0 C0 i O O 'O O O O k d 10 v V HL C 7r 010 VL �r f a' c 0 u U 0 Q�p � 0 0! 0 A u '00 01 01 E is Er 0 • u w u w O 0 O A W O 0 0 O 01 C 01 1 01 0 u 01 7 Q! O O V X SZ "Z W W > a X i is « • is « • • BRIDGE STREET DISTRICT § 153.062 27 DEVELOPMENT CODE BUILDING TYPES (c) No Other Building Types Principal buildings shall meet the requirements of Table 153.062 -A, Permitted Building Types in Each BSD Zoning District. (d) Permanent Structures All buildings constructed, including principal buildings and accessory structures, shall be permanent constructions without a chassis, hitch, wheels, or other features that would make the structure mobile. (e) Accessory Structures Accessory structures shall be permitted to be constructed in the buildable area of the lot in locations not required to be occupied by principal buildings. Accessory structures shall comply with § I53.062(E), or as otherwise approved by the required reviewing body, except that one primary fagade material may be used. All other applicable provisions of §153.074, Accessory Uses and Structures, shall be met. (C) GENERAL BUILDING TYPE LAYOUT AND RELATIONSHIPS The following outlines how BSD zoning districts and building types relate to one another. (1) Incompatible Building Types Incompatible building types are not permitted directly across the street from one another or on the same block face, unless otherwise permitted by the required reviewing body following approval of a Waiver in accordance with § 153.066. Refer to Table 153.062 -B, Incompatible Building Types. (2) Shopping Corridors At least one street or street segment shall be designated as a shopping corridor in the BSD Indian Run, BSD Sawmill Center, and BSD Scioto River neighborhood districts meeting the requirements of §153.063, Neighborhood Standards. Shopping corridors shall include building types that accommodate retail uses on ground floors, such as mixed use, large format commercial, loft, or corridor buildings. (a) These building types shall be clustered into continuous street frontages uninterrupted by other building types, parking areas or curb cuts for a minimum of 300 linear feet, as measured along the sidewalk. (b) The required shopping corridor shall be designated along a principal )f ght TABLE 153.062 -B. INCOMPATIBLE BUILDING TYPES NP = Not Permitted Existing Building Type NP'= Not Permitted w v unless accessory r to the residential Single Family buildings, wrapped 0 Q by occupied space, or Apartment otherwise permitted E by the required LE LE reviewing body 0 0 through approval of a c c Waiver. in in Civic Building Parking Structure frontage street unless otherwise permitted by the required reviewing body. (c) Shopping corridors are encouraged to turn the comer and continue along an intersecting street provided the minimum required length of the shopping corridor is located along the principal frontage street. FIGURE 153.062 -A. PARAPET. Parapet Height upper floor of building Expression r r7 r7 Line � Single Family Detached Single Family Attached T Apartment 6 Building 0 y Loft Building y Corridor '0 Building C Mixed Use Commercial Center d CL Large Format H Commercial C Historic Mixed 9 Use 7 Historic Cottage M Commercial Civic Building Parking Structure frontage street unless otherwise permitted by the required reviewing body. (c) Shopping corridors are encouraged to turn the comer and continue along an intersecting street provided the minimum required length of the shopping corridor is located along the principal frontage street. FIGURE 153.062 -A. PARAPET. Parapet Height upper floor of building Expression r r7 r7 Line � � Y D 0 E 'O U a+ V m Ot u t!' c =p u u u v N `v U _ r/7 Q .� o ] �`v u 'o u`v 'oE m m v_ v E vE °o c �� 0 Y V N_ N_ > OO Q U 2 U �U 2 2U U d am NP NP NP NP NP NP NP NP NP' NP' NP' Podium NP' Apartment Bldg. NP' NP' NP' NP' NP NP NP NP 28 § 153.062 EFFECTIVE DATE BUILDING TYPES JANUARY 7, 2015 (D) ROOF TYPE REQUIREMENTS All buildings shall use one or a combination of the following roof types, as permitted per building type. Refer to §153.062(0) for specific building type requirements. (1) Parapet Roof Type (Refer to Figure 153.062 -A) (a) Parapet Height 1. Parapet height is measured from the highest point of the roof deck adjacent to the top of the parapet. 2. Parapets shall be high enough to screen the roof and any roof appurtenances from view from the street(s) and any adjacent building of similar height or lower, provided that parapets shall be no less than two feet and no more than six feet high. Where a six foot parapet is insufficient to screen rooftop mechanical equipment a screening structure shall be required as provided in §I53.065(E) (3). (b) Parapets shall wrap around all sides of the building. (c) Horizontal Shadow Lines Expression lines are encouraged to distinguish the parapet from the upper stories of the building and to define the top of the parapet, as determined to be architecturally appropriate by the required reviewing body. (d) Occupied space or a half story shall not be incorporated within this roof type. (2) Pitched Roof (Refer to Figures 153.062 -13 through 153.062 -D) (a) Roof Structure Hipped and gabled roofs are permitted, in addition to roofs with combinations of hips and gables with or without dormers. (b) Pitch Measure 1. The principal roof shall have a pitch appropriate to the architectural style. Roofs shall not be sloped less than a 6:12 (rise:run) or more than 12:12, unless otherwise determined to be architecturally appropriate by the required reviewing body. 2. Slopes greater than 12:12 may be used on pitched roofs without a closed ridge used to screen flat roofed mechanical areas. This determination shall be based on the appropriateness to the architectural style and building type. 3. Where pitched roofs without closed ridges are used, the roof ridge must be designed to appear closed as viewed from all directions, and to the extent practicable from buildings of similar height in adjacent BSD zoning districts. 4. Unless determined to be appropriate to the architectural style of the building, a pitch greater than 3:12 is required on roofs of dormers, porches, balconies, or other minor roofs. (c) Parallel Ridge Line (See Figure 153.062 -D) 1. When appropriate to the architectural character of the building and where the principal ridge line of any building type runs parallel to any street, gabled ends, perpendicular ridge lines, or dormers shall be incorporated to interrupt the mass of the roof. 2. Perpendicular ridge lines are not required to intersect the primary ridge line (i.e. the secondary roof mass may be physically lower than the primary ridge line), provided the appearance is determined to be architecturally appropriate by the required reviewing body. (d) Dormer Design Dormers shall be scaled and detailed appropriate to the architectural character of the building type. Roof Dormer windows should be sized in relation Height to the windows used in the upper story, and dormers should be no wider than necessary to accommodate the window and coordinated trim. Visibility into permanently unfinished space is prohibited where dormer windows are installed. FIGURE 153.062 -D. PARALLEL RIDGE LINE. Ridge Parallel to C o� I m I m (e) Gable Ends An architecturally appropriate element such as a vent, window or other decorative element is required on street - facing gable ends. (f) Roof Height 1. In the BSD Historic Core district, roofs without occupied space and/or dormers shall have a maximum height on street- facing elevations equal to the maximum floor BRIDGE STREET DISTRICT § 153.062 29 DEVELOPMENT CODE BUILDING TYPES FIGURE 153.062 -C. LOW PITCH ROOF (HIP ROOF). height permitted for the building type, or as otherwise approved by the Architectural Review Board. 2. In all other districts, roofs without occupied space and/or dormers shall be a maximum of one and a half times the maximum floor height permitted for the building type on street - facing fagades, unless otherwise appropriate to the building type and location. (g) A half story of occupied space may be incorporated within a pitched roof type. (h) Gambrel and Mansard Roofs 1. Gambrel and mansard roofs are permitted only for single family detached buildings, unless otherwise determined by the required reviewing body to be architecturally appropriate for other building types. 2. For all building types, when the ridge of a gambrel or mansard roof runs parallel to the street, dormers or cross gables must be incorporated with spacing and scale appropriate to the length and architectural character of the building. (3) Flat Roof (Refer to Figure 153.062 -E) (a) Flat roofs are permitted in all districts except the BSI) Historic Core district, unless otherwise determined by the required reviewing body to be architecturally appropriate. (b) Eaves are encouraged on street facing fagades. FIGURE 153.062 -E. FLAT ROOF. Eave Depth Verticall Wall Plane F� Eave Thickness r� i n FIGURE 153.062 -F. TOWER. Tower Width Tower Roof Tower Height Expression Line (a) A minimum of 80% of each fagade visible from a street or adjacent property, exclusive of windows and doors, shall be constructed of permitted primary materials. Other facades shall use a combination of permitted primary and secondary materials, as determined by the required reviewing body. Use of a secondary material for an entire fagade is not permitted. (b) For individual fagades over 1,000 square feet, exclusive of windows and doors, a combination of permitted primary materials shall be used to meet the 80% requirement, unless otherwise approved by the required reviewing body. For building designs using glass as an integral fagade material (e.g., glazed aluminum or steel curtain walls), windows and doors incorporated into the curtain (c) Interrupting vertical walls may interrupt the eave and extend above the top of the eave with no discernible cap. (d) Not more than one -half of the front fagade can consist of an interrupting vertical wall. (e) Flat roof sections located behind parapets or pitched roofs to screen mechanical equipment are not considered flat roofs. (4) Towers (Refer to Figure 153.062 -F) (a) Quantity Where permitted by building type, only one tower is allowed per building unless otherwise approved by the required reviewing body. (b) Tower Height Towers may exceed the maximum building height and do not count as an additional story. Maximum tower height shall be measured from the top of the roof deck to the base of the parapet or eave of the tower's roof, and the tower shall not be greater than the height of one additional upper floor of the building to which the tower is applied. The width of a tower shall not exceed its height. Towers may be occupied by the same uses allowed in upper stories of the building type to which they are applied. (d) Towers maybe capped by any permitted roof (c) Occupied Space type. (5) Other Roof Types (a) Other roof types not listed as a specific type but are deemed architecturally appropriate to the proposed building may be approved by the required reviewing body. (b) Green roofs and roof gardens are encouraged. (E) MATERIALS (1) Fagade Materials 30 § 153.062 EFFECTIVE DATE BUILDING TYPES JANUARY 7, 2015 ( ( wall system maybe included in the calculated facade area when determining compliance with this requirement. (c) Permitted primary building materials shall be high quality materials including but not limited to stone, manufactured stone, full depth brick and g lass. Refer to §153.062(0) for permitted primar tumbling materials for individual building types. (d) Permitted secondary materials are limited to details and accents and include glass fiber reinforced gypsum, glass fiber reinforced gypsum, wood siring, fiber cement si(Eng, metal, and exterior architectural metal panels and cladding. (e) Exterior Insulation andFiNSwn s (EIFS) is pen itted for turn only, except as provided in 153.062(E)(1)(f). (f) EIFS and architectural metal panels and cladding shall not be used in the Ifistoric Core district. (g) To provide visual depth and strong shadow lines, clapboard siding must have a ninimum bull thickness of a quarter of an inch (h) Other high quality synthetic materials may be approved as penmtted primary or secondary materials by the required reviewing body with examples of successful, high quality installations in comparable climates. Facade Material Transitions (a) Vertical trarusitiour in facade materials shall occur at inside comers. (b) Where more than one facade material is proposed vertically, the `heavier' material in appearance shall be incorporated below the'fighter' material (e.g. masoru below siding). (c) Transitions between different colors of the same material shall occur 9locations deemed architecturally appropriate by the required reviewing body, such as inside comers and vertical andhonzontal facade divisions. RoofMaknals (a) Permitted pitched roof materi a] s include dimensional asphalt composite shingles with a 25 year or greater warranty, wood shingles and shakes, metal tiles or standing seam, slate, and ceramic tile. (b) Flat roofs are pemutted to use any roof material appropriate k maintain proper drainage. (c) Roof materials for gambrel and mansard roofs shall be cedar shake, slate or metal. Other high quality simulated examples of these materials may be approved by the required reviewing body with examples of successful, high quality installations in comparable climates. (d) Engineered wood or slate may be approved by the required reviewing body with examples of successful, high quality installations in comparable climates. (e) Roofpenetrations (fans, exhaust, vents, etc.) shall be concealed and shall not be visible from principal frontage streets. (4) Color Colors for all building materials shall be selected from appropri ate historic color palettes from any major paint manufacturer, or as detemuned appropriate by the required reviewing body. This requirement shall not apply to building- mourted signs. (E) ENTRANCES B, PEDESTRIANWAYS Also see §153.062(1). (1) Eammee quantities and locations are required according to building types outlived in §153.062 (0). (2) Recessed Erdrances Entry doors shall be recessed a minimum of three feet from the property line, except as required for specific bulking t outlined in §153.062(0). (3) Eammee Design O Principal entrances on all budding types shall be 9 a pedestrian scale, effectively address the street and be given prominence on the building facade. This may be satisfied through the use of architectural features including, but not limited to, entranceway roofs; sideli ght windows, transom window, or other adjacent windows; additional mouldings with expression lines; a bay of uni que width; or raised stoop of at least three steps and nmdepth of five feet and width of five feet. Refer k Figure 153.062 -G for one example of this requirement. (b) Principal entrances on all single family detached and single family attached building types shall incorporate open porches or stoops as required by §153.062(1). (c) Doors for commerci a] uses along all street frontages shall be consistent with the design of principal entrances and include glass and full operating hardware in the design of the door. Exterior doors for residential uses shall also include glass, but this requirement may be met BRIDGE STREET DISTRICT § 153.06231 DEVELOPMENT CODE BUILDING TYPES through the use of transom and/or sidelight windows. (d) Roll -up security grilles shall not be permitted. (e) Building Entrances Refer to the walkability standards of §153.065(1) (4)(b) for building entrance requirements. (4) Mid - Building PedesManways Refer to the walkability standards of §153.065(I)(2)(b) for mid - building pedesManway requirements. (G) ARTICULATION OF STORIES ON STREET FACADES Facades shall be designed to follow the stories of the buildings with fenestration organized along and occupying each Floor. Floor to Floor heights are set to limit areas of the facade without fenestration. Refer to Figure 153.062 -11 for an example illustration of this requirement. (H) WINDOWS, SHUTTERS, AWNINGS AND CANO- PIES (1) Windows (a) Transparency percentage is required according to building type as outlined in §153.062 (0). (b) Highly reflective glass is probibited. For the purposes of this section, highly reflective glass has an exterior visible reflectance percentage greater than 20 %. (c) Spandrel glass, or heavily tinted glass that impedes views into the interior of the building, ca nnot be used to meet the minimum transparency requirements. (d) Windows maybe wood, anodized aluminum, metal -clad or vinyl clad wood, steel, or fiberglass. FIGURE 153.062 -H. ARTICULATION OF STORIES ON STREET FACADES S BUILDING VARIETY. Y r ( V! 011 4 r -=� The required reviewing body may approve other high quality synthetic materials with examples of successfid, high quality installations in comparable climates. (e) To highlight the wall thickness as an important architectural feature conveying a substantial, high - quality appearance, Flush - mounted windows are prohibited for single - family detached, single - family attached, apartment, historic mixed use, and historic cottage commercial building types. (f) Windows in masonry walls shall have architecturally appropriate lintels and projecting sills. (g) Windows within siding clad walls shall have a projecting sill to serve as a base for either a numm o ne by four (nominal) trim or brick mould casing. (h) Windows in single - family detached, single - family attached, apartment building, historic mixed use, and historic cottage commercial building types shall have vertical proportions with architecturally or historically appropriate window divisions. Horizontally- oriented windows are permitted for these building types ody on non -street facing building facades. (2) Shutters (a) If installed, shutters shall be sized to provide c omplete coverage to the windows when closed and shall include finctioning hardware. (b) Shutters shall be wood or engineered wood. The required reviewing body may approve other materials with examples of successfid, high quality installations in comparable climates. (3) Awnings and Canopies [Also see §153.062(N)(1)(a)] (a) General 1. Awnings andcanopies maybe usedif they function as suitable protection from the elements To provide suitable protection an awning or canopy may encroach over the sidewalk, provided the lowest portion is at least eight feet above the sidewalk. 2. Awnings and canopies may be mounted i nside frames, above openings and/or below transoms, but installation methods shall be consistent on a building. 3. Awnings and canopies shall be designed to be consistent with the architecture of the building and other existing awnings and canopies on a building. (b) Awnings 1. Awnings shall be open on the underside. 2. Awnings shall he made of durable and fade - resistant canvas, decorative metal with metal used for the internal structure, or an 32 8 153.062 EFFECTIVE DATE B IMM TYPES JANUARY J, 2015 alternative, nigh- quality, durable material, if determined to be architecturally appropri ate by the required reviewing body. 3. Awnings shall not be internally illuminated, but may be lighted from above by downcast fixtures mounted to the building wall. (c) Canopies 1. Canopies maybe clad with glass, metal, wood, or a combination of these materials. 2. Canopies maybe cantilevered or supported from the building wall by metal cables or rods. 3. Canopies may include downward casting light fixtures and may be lighted from above by downcast fixtures mounted to th e building wall. (I) BALCONIES, PORCHES, STOOPS, AND CHIMNEYS Th a following provisions apply where balconi es, open porches, or stoops are incorporated into th e facade des go facing any street or parking lot. (1) Balconies (a) Size Balconies shall be a minimum open area of six feet deep and five feet wide (b) Cunnecfiun to Building Balconies may be recessed into a building facade Balconies that are not recessed into the facade shall be independently secured and unconnected to other balconies above and below. Balconies may project into the RBZ or forward of the RBZ, but may not extend into a right -of -way or be considered as part of a structure used to meet front or comer RBZ requirement. (c) Facade Coverage A maximum of 40% of each of the front and comer side facades may be covered with balconies. (d) Juliet Balconies 1. Juliet balconies are pertained only un upper floors of buildings where windows extend to the door or where doors are present. 2. Juliet balconies may pry ect up to 24 inches and shall not extend more th an six inches past th e fenestration. 3. Juliet balconies used with windows must be secured to th e outside window and. (2) Open Porches For the purposes of §153.062, an open porch shall mean a porch that is not enclosed by walls, windows, or screens greater than 24 inches above the porch level on street facing facades of the building. Open porches may be covered with a roof. (a) Size Porches shall be appropriate to the architectural style of the building and have a minimum clear depth of six feet and sufficient width as necessary to be functional for use. (b) Street Frontage Porches shall not be used to meet the front or comer Required Building Zone (RBZ) requirement Porches are permitted to extend forward of the RBZ but shall not encroach within the right -of -way. (3) Stoops (a) Size Stoops shall have a minimum width and depth of five feet of open area and may be located un the front and/or comer side facades of the building. (b) Street Frontage Stoops and steps shall not be used to meet the front or corner RBZ requirement Stoops and steps are permitted to extend forward of the RBZ but shall not encroach within the right -of -way. (4) Chimneys and Vents (a) Chimneys on exterior walls shall be treated as architectural elements. (b) Chimneys on exterior walls shall extend full height from the ground and vertically past the eave line and must be finished in masonry. Cantilevered and shed -type chimneys are prohibited (c) Vents shall befinishedto match the color of the exterior wall. (J) TREATMENTS AT TERMINALVISTAS When a street terminates at a parcel or otherwise creates a terminal view at a parcel, the parcel shall be occupied by one of the following: (1) If the tenuous occurs at an open space, arty open space type shall be used and a vertical element shall terminate the view. Acceptable vertical elements FIGURE 153.062 -I. BUILDINGS AT TERMINAL VISTAS. BRIDGE STREET DISTRICT R 153.062 33 DEVELOPMENTCODE B ILDIN TWES include, but are not limited to, a stand or grid of trees, a sculpture, or fountain. Refer to §153.064 for additional open space requirements. (2) If the terminus does not occur at an open space type, the front or comer side of a building, whether fronting a principal frontage street or not, shall terminate the view. The building shall incorporate one of the following treatments to terminate the view: a tower, a bay window, courtyard with a sculpture, pronounced increase in building height, or other similar treatment incorporating a distinct vertical element. Refer to Figure 153.062 -I for an example illustration of this requirement. (K) BUILDING VARIETY Refer to Figure 153.062 -H for one illustration of this requirement. Building design shall vary from adjacent buildings by the type of dominant material or color, scale, or orientation of that material. Building design shall also vary through at least two of the following: (1) The proportion of recesses and projections. (2) A change in the location of the entrance and window placement. If storefronts are used, no change to the entrance and window placement is required and one of the criteria is satisfied. (3) Changes to the roof design, including roof type, plane, or material, unless otherwise stated in the building type requirements. (4) Pronounced changes in building height. (L) VEHICULAR CANOPIES (1) For buildings facing a principal frontage street, vehicular canopies shall be located on the rear fagade of the principal structure or in the rear of the lot behind the principal structure, where permitted by use Refer to Figure 153.062 -J for an example illustration. FIGURE 153.062 -3. VEHICULAR CANOPIES. OR 21_ f Front Property Line Principal Frontage Street 1. More than one principal building is permitted . on one lot for those building types indicated. Unless otherwise noted, all requirements of the building type shall be met for all principal structures. 2. The fagade of the principal building shall be located within the RBZ. When noted as a setback rather than an RBZ, the principal structure shall be located at or behind the setback line. 3. Where specified, front fagades of principal buildings are required to cover a minimum portion of the front property line within the required building zone (RBZ). 4. A street wall in accordance with §153.065(E) (2) may be used to meet up to 10% of the front property line coverage requirement. 5. Front property line coverage is determined by measuring the length of the principal structure and length of a street wall within the RBZ and parallel to the front property line, divided (2) If attached to the principal structure, design of the vehicular canopy shall be coordinated with the architecture of the principal structure to which it is associated. Regardless of whether the canopy is attached to or detached from the principal structure, supporting columns shall be coordinated with the design of the principal structure. (3) Canopies shall not exceed the maximum ground floor height permitted for the specific building type, and in no case shall the canopy exceed the height of the principal structure to which it is associated. (M)SIGNS (1) All signs attached to the principal structure shall be coordinated with the architecture of the building in terms of design, color scheme, location and lighting. (2) Locations of all signs intended to be affixed to the principal structure and/or on an attached awning or canopy initially, or at any time in the future by subsequent tenants, shall be identified on the architectural elevations submitted with the Minor Project or Site Plan applications, as applicable. (3) Other sign requirements not specified in this section shall meet the requirements of §153.065(H). (N) INDIVIDUAL BUILDING TYPE REQUIREMENTS The following defines the requirements included in the tables for each building type listed in §153.062 (0). Not all line items listed below appear within every building type's individual requirements table. The following requirements shall be met unless otherwise noted in the building types of §153.062(0). (1) Building Siting General Requirements (a) Street Frontage 34 § 153.062 EFFECTIVE DATE BUILDING TYPES JANUARY 7, 2015 by the maximum length of the front RBZ (not including side setbacks). 6. Unless otherwise permitted, a comer of the principal structure, a street wall, or a permitted open space type shall be located at the intersection of the front and comer RBZs. Refer to §153.065(E)(2) for street wall requirements and § 153.064 for open space requirements. 7. Any part of the front or comer RBZ or setback not occupied by building shall have an approved open space type, parking areas in accordance with § 153.062(N)(1)(c), or the area shall be designed with landscape, patio, or streetscape RBZ treatment Refer to §153.065(D)(6) for RBZ treatment requirements. 8. Subject to approval of the City Engineer or City Council where required, certain building components, such as awnings and canopies, may be permitted to extend beyond the front property line and encroach within the right -of -way to within five feet of the curb. If permitted, these building components shall maintain a minimum eight -foot height clearance above the public sidewalk and shall not conflict with required street trees or landscaping. Porches, stoops, and balconies are not permitted to encroach into the right - of -way. (b) Buildable Area 1. The side and rear yard setbacks apply to principal and accessory structures. 2. Unless otherwise noted, the side and rear yard setbacks are required to be landscaped and/or paved for pedestrian paths. FIGURE 153.062 -K. MEASURING IMPERVIOUS COVERAGE. muu uuuuuuumuuuuuui Parking m Additional (a) Required minimum and maximum numbers of Semi- stories are provided for all building types. The Pervious w Maximum Impervious Coverage; Coverage. 4Building Coverage + (Permeable paving) :Impervious Surfaces. -. 3. Open spaces permitted in accordance with § 153.064 are not required to meet side and rearyard setbacks. 4. Driveways are permitted within the side and rear yard setbacks only in the following conditions: A. One drive, a maximum of 22 feet wide, is permitted to connect adjacent parking lots or alleys /service streets. B. Unless shared with the adjacent property, the drive shall be at least three feet from the property line C. Refer to §153.065(B)(7) for loading area requirements. 5. Each lot is subject to the requirements of this chapter for impervious surface coverage, measured as shown in Figure 153.062 -K. Additional semi - pervious coverage may be permitted through methods such as use of semi - pervious materials, green roofs or other methods approved by the City Engineer. (c) Parking Location and Loading 1. Permitted locations for packing and loading facilities on development parcels and within buildings are specked for individual building types. Refer to §153.065(B) for additional parking requirements. 2. Parking may be located within the front or comer RBZ where consistent with the permitted parking locations for the applicable building type Such parking is subject to the street wall requirements of §153.065(E) (2), except that surface parking shall not be located in any portion of an RBZ required to be occupied by a principal structure. 3. Parking shalt not be located within a required setback, except as permitted by §153.065(B) ( 4. Alleys or service streets, when present, shall always be the primary means of vehicular access to parking lots or buildings. Refer to §153.060(C)(5) for block access requirements. 5. When alleys are not present, driveways may be permitted from streets not identified as principal frontage streets, except as permitted by § 153.061(D), and subject to the access management requirements of the City Engineer. Refer to §153.065(B)(6) for additional driveway requirements. e (2) Height 7 (a) Required minimum and maximum numbers of �flnm�• stories are provided for all building types. The �Nmu uNU. minimum number of required stories shall be Fmnt Pmperty Line provided for all building facades within the RBZ, except as required in &153.062(Nu21(d). BRIDGE STREET DISTRICT DEVELOPMENTCODE § 153.062 BUILDING TYPES 35 (b) Half stories are located either completely within the roof structure with street - facing windows or in a visible basement exposed a maximum of one half story above guide. (c) A building incorporating both a half story within the roof and a visible basement shall count the height of the two half stories as one full story. (d) Each building type includes a permitted range of height in feet for each story. 1. Unless otherwise specified, story height is measured in feet between the floor of a story to the floor of the story above it 2. For single story buildings and the uppermost story of a multiple story building, story height shall be measured from the floor of the story to the eave line m pitched roofs and to the tallest point of the roof deck on parapet and flat roofs. 3. Story height requirements apply only to street facing facades; however, no portion of the building shall exceed the maximum permitted height of any street facing facade 4. Accessory building height shall not exceed the height of the principal building. (3) Uses and Occupancy Requirements (a) Certain building types have limitations or requirements for uses which may occupy the ground story of a building or are permitted only on upper stories. Refer to Table 153.059 -A for additional use requirements. (b) The area(s) of a building in which parking is permitted within the structure of the building type shall meet the following requirements. 1. Basement parking shall meet street facade transparency requirements where more than 50%ofthe street - facing basement story height is visible above grade, unless otherwise permitted for individual building types. 2. Freestanding packing structures are addressed by the parking structure building type provisions of §153.062(0)(12). 3. When parking is permitted within the building, an active, occupied space must be incorporated along the building facade, meeting the location and minimum dimensional requirements indicated for individual building types. Occupied space does not include storage areas, utility space, or parking. (4) Facade Requirements (a) Facade Transparency 1. Facade transparency percentages required for a building type shall be met with highly One Story transparent, low reflective (minimum 60% visible light transmittance) glass windows (Figure 153.062 -L). Ground story transparency is measured between two and eight feet above the sidewalk elevation on all ground story facades, regardless of whether a sidewalk is adjacent to the facade. One example illustration of storefront transparency is shown in Figure 153.062 -M. Blank, windowless walls are prohibited. No more than 30% of each building facade per story, as measured from floor to floor, and no horizontal distance greater than 15 feet per story shall be blank or windowless. Windows may be clustered along an elevation, provided the minimum facade transparency requirements and blank wall limitations are met using other architectural features, such as material transitions, facade divisions, projecfions or shadow lines, corbelling or alternate brick course details, or other design details that will add visual interest to windowless wall sections, as determined to be architecturally appropriate by the required reviewing body.5. Vents, air conditioners and other utility elements shall not be part of any street - facing building facade, unless otherwise permitted TRANSPARENCY PER STORY. m Blank Wall Limitations Each Window Opening Area of Each Story FIGURE 153.062 -M. STOREFRONT TRANSPARENCY ON GROUND STORY. r Measure Percent of Ground Story Storefront Transparency between 2 and 8 feet from the sidewalk. — 36 fi 153.062 EFFECTIVE DATE B IMING TYPES JANUARY 7, 2015 for individual building types. Where these elements are part of other facades, particular care must be taken to render these elements less visible to public view through architectural integration or other means of screening as approved by the required reviewing body. These elements shall not be used to meet blank wall requirements. (b) Fagade Divisions 1. Architectural elements or forms shall be used to divide the surface of the fagade into pedestrian scaled vertical increments appropriate to the architectural character of the building type. Acceptable divisions include, but are not limited to A. Arecess or projection along the building . fNade for a minimum of 18 inches in depth. B. Use of a distinctive architectural element protruding from or recessed into the fagade a minimum of three inches, including pilasters, entranceways, or storefronts. 2. Architectural elements, forms, or expression lines may be used to divide portions of the fagade into horizontal divisions appropriate to the architectural character of the building type. Elements may include a cornice, belt course, corbelling with table, moulding, stringcourses, pediment, or other continuous horizontal ornamentation with a minimum one - and -a -half inch depth. 3. Where changes in roof plane are required by the building type, they shall be used to divide the roof mass into increments no greater than the dimensions permitted for each building type and shall correspond to recesses and projections in building mass. Permitted changes include a change in roof type and/ or horizontal or vertical variations in the roof plane. 4. Unless otherwise determined to be architecturally appropriate by the required reviewing body, minimum increments shall be provided pursuant to the building type tables. (0) BUILDING TYPES The following defines the building types permitted in the BSD zoning districts. Refer to Table 153.062 -C for the list of symbols used on the building type tables to illustrate the individual building type requirements. Because some of the individual building type requirements do not apply to every building type, not every symbol is represented on every building type. TABLE 153.062 -C. BUILDING TYPE TABLE LEGEND Symbol Building Type Requirement Symbol Building Type Requirement A Multiple Principal Buildings W Upper Story B Front Property Line Coverage X Parking within Building C Occupation of Corner Y Occupied Space D Front Required Building Zone (RBZ) Z Ground Story Street Facade Transparency E Corner Side RBZ AA Upper Story Transparency F Front Setback BB Transparency (Street Facing Facades) G Corner Side Setback CC Blank Wall Limitations (Street Facing Facades) H Side Yard Setback DD Garage Openings I Rear Yard Setback EE Parking Lot Ground Story Transparency J Minimum Lot Width FF Transparency (Non - Street Facing Facades) K Maximum Lot Width GG Blank Wall Limitations (Non - Street Facing Facades L Maximum Building Length or Depth HH Principal Entrance Location M Minimum Lot Depth II Number of Street Facade Entrances N Parking Location JJ Number of Parking Lot Entrances O Loading Facility Location KK Mid - Building Pedestrianway P Entry for Parking Within Building LL Facade Divisions Q Access MM Vertical Increments R Minimum Building Height NN Horizontal Facade Divisions S Maximum Building Height 00 Required Change in Roof Plane or Type T Accessory Structure Height PP Permitted Roof Types U Minimum Finished Floor Elevation QQ Tower V Ground Story BRIDGE STREET DISTRICT § 153.062 37 DEVELOPMENT CODE BUILDING TYPES (1) Single - Family Detached' (a) Building Siting 1. Street Frontage Front, corner, or side; porches are required Street Facades: Number of Entrances Multiple Principal Buildings Not permitted Not applicable Front Property. Line Coverage Minimum 65% O Occupation of Corner Not required None Front RBZ 5 -20 ft. O Corner Side RBZ 5 -15 ft. RBZ Treatment Landscape; Porches are permitted in the RBZ 6. Roof Types Right -of -Way Encroachment None Pitched roof; other types may be permitted with approval (refer to §153.062(D)) 2. Buildable Area Permitted where architecturally appropriate Minimum Side Yard Setback 5 ft. Minimum Rear Yard Setback 5 ft. Minimum Lot Width 30 ft. O Maximum Lot Width 60 ft. Minimum Lot Depth 100 ft. Maximum Building Length Not applicable Maximum Impervious Coverage Additional Semi - Pervious Coverage 50% 20% 3. Parking Location &Access Parking Location Rear yard Entry for Parking within Building Rear Access Alley /service street only' • O (b) He Minimum Height 1.5 stones Q Maximum Height 3 stories Stories: Minimum Height Maximum Height 9 ft. 12 ft. Accessory Structure Height 2 stories maximum2 0 Minimum Finished Floor Elevation 2.5 ft. above the adjacent sidewalk elevation O (c) Uses & Occupancy Requirements Ground Story No additional requirements Upper Story No additional requirements Parking within Permitted in the rear of the first Floor and Building fully in any basement(s) Q Occupied Space Minimum 15 ft. depth from the front facade (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Transparency Minimum 25% Blank Wall Limitations Required 2. Non - Street Fagade Transparency Transparency Minimum 15% Wall Limitations Required 3. Building Entrance Principal Entrance Location Front, corner, or side; porches are required Street Facades: Number of Entrances 1 minimum per unit Parking Lot Facades: Number of Entrances Not applicable Mid - Building Pedestrianway Not required 4. Fagade Divisions Vertical Increments None Horizontal Facade Divisions None Required Change in Roof Plane or Type None 5. Fagade Materials Permitted Primary Materials Stone, Brick 6. Roof Types Permitted Types Pitched roof; other types may be permitted with approval (refer to §153.062(D)) Tower Permitted where architecturally appropriate Notes: 1 All new construction in the BSD Historic Residential District shall meet the requirements of §153.063(B), § §153.170 through 153.180 and the Historic Dublin Design Guidelines, in addition to the requirements of §153.062 as determined to be architecturally appropriate by the Architectural Review Board. Z Garage doors shall be no taller than nine feet. No single garage door shall be wider than 18 feet. 3 Where alley /service street access is not feasible at the determination of the City Engineer, driveways for single - family detached buildings shall meet the requirements of §153.210, except that driveways shall be limited to 10 feet in width at the right -of -way. 38 § 153.062 (0) (1) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 SINGLE - FAMILY DETACHED Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. ■ Permitted Parking within Building J Required Building Zone FIGURE 153.062 -N SINGLE - FAMILY DETACHED BUILDING TYPE DIAGRAM. BRIDGE STREET DISTRICT § 153.062 (0) (1) 39 DEVELOPMENT CODE BUILDING TYPES - SINGLE -FMILY DEIFlCFED (2) Single - Family Attached (a) Building Siting 1. Street Frontage Principal Entrance Location Multiple Principal Buildings Permitted stoops required Front Property Line Coverage Minimum 75 % Entrances Occupation of Corner Required If parking lot or detached garage, Front RBZ 5 -20 ft. Mid - Building Pedestrianway Corner Side RBZ 5 -15 ft. RBZ Treatment Landscape; Porches or stoops are permitted in the RBZ Right -of -Way Encroachment None None 2. Buildable Area None Plane or Type Minimum Side Yard. Setback 5 ft., 10 ft. between buildings ID Minimum Rear Yard Setback 5 ft. 6. Roof Types Minimum Lot Width 16 ft. per unit Parapet, pitched roof, Flat roof; other types may be permitted with Z Maximum Lot Width None Maximum Length None terminal vistas, corners at two Maximum Impervious Coverage Additional Semi - Pervious Coverage 70% 20% 3. Parking Location &Loading Parking Location Rear yard or within building (refer to (c) Uses) Entry for Parking within Building Rear or corner side facade Access Alley /service street only (b) Height Minimum Height 1.5 stories Q Maximum Height 4 stories Stories: Minimum Height Maximum Height 10 ft. 12 ft. Accessory Structure Height 2 stories maximum O Minimum Finished Floor Elevation 2.5 feet above the adjacent sidewalk elevation O (c) Uses & Occupancy Requirements Podium parking structures are conditional Ground Story uses in accordance with §153.059(C)(3) (g)- Upper Story No additional requirements Parking within Permitted in the rear of the first Floor and Building fully in any basement(s) Occupied Space Minimum 10 ft. depth from the front facade O (d) Fayade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Transparency Minimum 20% Blank Wall Limitations Required 2. Non - Street Fagade Transparency Transparency Minimum 15% (� Wall Limitations Required 3. Building Entrance Principal Entrance Location Front, corner, or side; porches or stoops required Street Facades: Number of 1 per unit minimum Entrances Parking Lot Facades: Number If parking lot or detached garage, of Entrances 1 per unit Mid - Building Pedestrianway 1 required for buildings longer than 250 feet 4. Fagade Divisions Vertical Increments Every two units or no greater than 40 ft. Horizontal Facade Divisions None Required Change in Roof None Plane or Type 5. Fagade Materials Permitted Primary Materials. Stone, Brick 6. Roof Types Permitted Types Parapet, pitched roof, Flat roof; other types may be permitted with Z approval (refer to §153.062(D)) Permitted on facades only at Tower terminal vistas, corners at two principal frontage streets, and /or adjacent to an open space type Notes: 1 One of every five principal buildings may front an open space type or a courtyard with a minimum width of 30 feet. Z An open and unenclosed landscaped courtyard meeting the open space type requirements of §153.064 may contribute up to 35% of the front property line coverage requirement. 3 No more than eight single - family attached units in a building may be permitted when single - family attached residential units are located across the street from existing single - family detached dwellings. 4 Where alley /service street access is not feasible at the determination of the City Engineer, driveways for single - family attached buildings shall meet the requirements of §153.210. 5 Garage door height shall be no greater than 9 feet. No single door shall be wider than 18 feet. 40 § 153.062 (0) (2) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 SINGLE - FAMILY ATTACHED Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. Hung within (ding Zone FIGURE 153.062 -0: SINGLE - FAMILY ATTACHED BUILDING TYPE DIAGRAM. BRIDGE STREET DISTRICT §153.06200 (2) 41 DEVELOPMENT CODE BUILDING TYPE$ SINGLE- FAMILY ATTACHED (3) Apartment Building (a) Building Siting 1. Street Frontage Minimum 15% Multiple Principal Buildings Permitted O Front Property Line Coverage Minimum 75 % O Occupation of Corner Required Front RBZ 5 -20 ft. Principal Entrance Location Corner Side RBZ 5 -20 ft. Landscape or less than 1 per 75 ft. of fagade minimum RBZ Treatment 50% Patio; porches, stoops, and balconies Parking Lot Fagades; Number are permitted in the RBZ Right -of -Way Encroachment None 2. Buildable Area Mid - Building Pedestrianway Minimum Side Yard Setback 5 ft. Minimum Rear Yard Setback 5 ft. than 250 ft. Minimum Lot Width 50 ft. O Maximum Lot Width None Maximum Impervious Coverage 70% No greater than 40 ft. Additional Semi - Pervious Coverage 20% 3. Parking Location &Loading Rear yard 2 ; within Parking Location building (refer to (c) required within 3 ft. of the top of Uses & Occ. Req.) Loading Facility Location Rear Entry for Parking within Building Rear & side fagade No greater than every 80 ft. Access Refer to §153.062(N)(1)(c) 5. Fagade Materials (b) Height Minimum Height 2 stories Stone, Brick, Glass Maximum Height 4.5 stories 6. Roof Type Stories: Minimum Height 10 ft. Maximum Height 14 ft. Parapet, pitched roof, Flat roof; 2.5 ft. above the Minimum Finished Floor Elevation adjacent O S idewalk elevation approval (refer to §153.062(D)) (c) Uses & Occupancy Requirements Podium parking structures are conditional Ground Story uses in accordance with §153.059(C)(3) terminal vistas, corners at two (g)- Upper Story No additional requirements Parking within Permitted in the rear of the first 3 Floors adjacent to an open space type Building and fully in any basement(s) Occupied Space Minimum 20 ft. for the ground story O facing street(s) (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Transparency Minimum 20% Blank Wall Limitations Required 2. Non - Street Fagade Transparency Transparency Minimum 15% Z Blank Wall Limitations Required 3. Building Entrance Principal Entrance Location Primary street facade of building Street Facades: Number of Entrances 1 per 75 ft. of fagade minimum Parking Lot Fagades; Number Not required of Entrances Mid - Building Pedestrianway 1 required for buildings longer than 250 ft. 4. Fagade Divisions Vertical Increments No greater than 40 ft. On buildings 3 stories or taller, Horizontal Fagade Divisions required within 3 ft. of the top of the ground story Required Change in Roof Plane or Type No greater than every 80 ft. 5. Fagade Materials Permitted Primary Materials Stone, Brick, Glass 6. Roof Type Parapet, pitched roof, Flat roof; Permitted Types other types may be permitted with approval (refer to §153.062(D)) Z Permitted on fagades only at Tower terminal vistas, corners at two principal frontage streets, and /or adjacent to an open space type Notes: 1 A publicly accessible open and unenclosed landscaped courtyard meeting the open space type requirements of §153.064 may contribute up to 35% of the front property line coverage requirement. Z Basement level structured parking is permitted to extend between buildings, screened from the street and covering a maximum of 10% of the length of the RBZ. Structured parking visible between principal buildings must be set back a minimum of 15 ft. from the street facing fagades. 3 Where the principal building entrance is a lobby or other common space, the minimum finished Floor elevation is not required. 42 § 153.062 (0) (3) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 APARTMENT BUILDING Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. ❑A H r'1 A M ■ Permitted Parking within Building FIGURE 153.062 -P: APARTMENT BUILDING TYPE DIAGRAM. BRIDGE STREET DISTRICT § 153.062 SOj (3) 43 DEWLOPMENTCODE BUH-DING T PE - APARTMENT BUILDING (4) Loft Building (a) Building Siting 1. Street Frontage Multiple Principal Buildings Permitted Front Property Line Coverage Minimum 75% O Occupation of Corner Required O Front RBZ 0 -15 ft. Oi Corner Side RBZ 0 -15 ft. Minimum Lot Width Landscape, Patio, or Maximum Lot Width Streetscape; along West Facing Transparency Dublin- Granville Road, RBZ Treatment Streetscape required; where Access residential uses are located O on the ground Floor, porches §153.062(N)(1)(c) or stoops are permitted in (b) Height the RBZ Right -of -Way Encroachment Awnings, canopies, eaves,. Refer to §153.062(D) through §153.062(N) for design patios & projecting signs 2. Buildable Area Minimum Side Yard Setback 5 ft. Minimum Rear Yard Setback 5 ft. Minimum Lot Width 50 ft. Maximum Lot Width None O Maximum Impervious Coverage 80% Additional Semi - Pervious Coverage 10% 3. Parking Location & Loading Parking Location Rear yard; within building (refer to (c) Uses & Refer to §153.062(D) through §153.062(N) for design Occupancy Requirements) Loading Facility Location Rear & side facade Where non - residential uses are Rear &.side facade, corner Ground Story Street Entry for Parking within Building side on non - principal Facing Transparency Floor, minimum 60% required; frontage streets Access O Minimum 60% §153.062(N)(1)(c) Blank Wall Limitations (b) Height Minimum Height 2 stories Q Maximum Height 4.5 stories Blank Wall Limitations. Ground Story: Minimum Height 12 ft. 3. Building Entrance Maximum Height 16 ft. Upper Stories: Minimum Height 10 ft. Maximum Height 16 ft. Principal Entrance Location Where residential uses are located on Minimum Finished Floor Elevation the ground Floor, 2.5 ft. above the adjacent sidewalk elevation (c) Uses & Occupancy Requirements Podium parking structures are conditional Ground Story uses in accordance with §153.059(C)(3) (g)- Upper Story No additional requirements Parking within Permitted in the rear of the first 3 Floors Building and fully in any basement(s) Occupied Space Minimum 30 ft. depth from the front facade v (d) Fagade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Where non - residential uses are Ground Story Street incorporated on the ground Facing Transparency Floor, minimum 60% required; otherwise minimum 60% Transparency Minimum 60% Blank Wall Limitations Required 2. Non - Street Fagade Transparency Transparency Minimum 20% Blank Wall Limitations. Required 3. Building Entrance Primary street facade of building; where residential units are Principal Entrance Location individually accessed on the I � ground Floor, porches or stoops are requir at each e ntrance Where ground story dwelling units Street Facades: Number of or tenant spaces are incorporated, Entrances 1 per full 30 ft.; otherwise, 1 per 75 ft. Parking Lot Facades: Number of Entrances 1 per 100 ft. of facade (minimum) Mid - Building Pedestrianway 1 required for buildings longer than 250 ft. 4. Fagade Divisions Vertical Increments No greater than 40 ft. On buildings 3 stories or taller, required within 3 ft. of the top of the ground story and any visible Horizontal Fagade Divisions basement. When 14 to 16 -foot upper stories are used, horizontal 'W divisions are required between each Floor. Required Change in Roof No greater than every 80 ft, for Plane or Type pitched roof type; none for other r oof types. 5. Fagade Materials Permitted Primary Materials Stone, Brick, Glass 6. Roof Types Parapet, pitched roof, Flat roof; Permitted Types other types may be permitted with approval (refer to §153.063(D)). Permitted on fagades only at Tower terminal vistas, corners at two principal frontage streets, and /or adjacent to an open space type. Notes: 1 Sixteen foot height in an upper Floor counts as 1.5 stories. 44 § 153.062 (0) (4) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 LOFT BUILDING Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual BFUDOESmEETDISFFICr § 153.062(0) (4) 45 DEVSFOPMEVT CODE BBILDING TYPES - LOFT BUILDING FIGURE 153.062 - Q: LOFT BUILDING TYPE DIAGRAM. (5) Corridor Building (a) Building Siting 1. Street Frontage Multiple Principal Buildings Permitted Front Property Line Coverage Minimum 75 %1 O Occupation of Corner Required O Front RBZ 0 -15 ft. Facing Transparency Corner Side RBZ 0 -15 ft. Landscape, Patio, or Minimum 30% RBZ Treatment Streetscape; along West Blank Wall Limitations Dublin- Granville Road, Streetscape required Right -of -Way Encroachment Awnings, canopies, eaves, Minimum 15% patios & projecting signs Blank Wall Limitations 2. Buildable Area Minimum Side Yard Setback 5 ft. Minimum Rear Yard Setback 5 ft. Principal Entrance Location Minimum Lot Width 50 ft. Maximum Lot Width None O Maximum Impervious Coverage 80% Entrances Additional Semi - Pervious Coverage 10% 3. Parking Locatio & Load 1 per 100 ft. of fagade minimum Rear yard Z ; within building Parking Location (refer to (c) Uses & Occupancy Requirements) Loading Facility Location Rear & side fagade buildings greater than 250 ft. in Rear & side fagade; corner Entry for Parking within Building side fagade on non - principal frontage streets 4. Fagade Divisions Access Refer to §153.062(N)(1)(c) (b) Height No greater than 45 ft. Minimum Height 3 stories Q Maximum Height 6 stories. Ground Stories: required within 3 ft. of the top of Minimum Height 12 ft. Maximum Height 16 ft. ��ll►► Stories: Minimum Height 10 ft. building step -back. Maximum Height 14 ft. Required Change in Roof None (c) Uses & Occupancy Requirements Residential and general office uses are 5. Facade Materials Ground Story prohibited in shopping corridors; Podium parking structures are conditional uses in Stone, Brick, Glass accordance with §153.059(C)(3)(g). 6. Roof Types Upper Story No additional requirements Parking within Permitted in the rear of the first 3 Floors and Building fully in any basement(s) Occupied Space Minimum 30 ft. depth facing street(s)2 O (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparen Ground Story Street Minimum 60% required Facing Transparency Transparency Minimum 30% Blank Wall Limitations Required 2. Non - Street Fagade Transparency Transparency Minimum 15% Blank Wall Limitations Required 3. Building Entrance Principal Entrance Location Primary street fagade of building Street Fagades: Number of 1 per 75 ft. of fagade minimum Entrances Parking Lot Fagades: Number of Entrances 1 per 100 ft. of fagade minimum In shopping corridors, required for Mid - Building Pedestrianway buildings greater than 250 ft. in length 4. Fagade Divisions Vertical Increments No greater than 45 ft. On buildings 3 stories or taller, Horizontal Fagade Divisions required within 3 ft. of the top of i 11► i the ground story. Required at any ��ll►► building step -back. Required Change in Roof None Plane or Type 5. Facade Materials Permitted Primary Materials Stone, Brick, Glass 6. Roof Types Parapet, pitched roof, Flat roof; Permitted Types other types may be permitted with approval (refer to §153.062(D)). Permitted on facades only at Tower terminal vistas, corners at two principal frontage streets, and /or adjacent t o an open space type. Notes: 1 A publicly accessible open and unenclosed landscaped courtyard meeting the open space type requirements of §153.064 may contribute up to 35% of the front property line coverage requirement. Z Parking decks are permitted to extend between buildings, screened from street and covering a maximum of 10% of the length of the RBZ. Parking decks visible between principal buildings must be set back a minimum of 15 feet from the street facing fagades. 46 § 153.062 (0) (5) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 CORRIDOR BUILDING ended to more of I do not actual irking udthin Iding Zone BRIDGE STREET DISTRICT 153.062 (0) (5) 47 DEVELOPMENT CODE BUILDING TYPES - CORRIDOR BUILDING FIGURE 153.062 -R: CORRIDOR BUILDING LVPE DIAGRAM. (6) Mixed Use Building (a) Building Siting (d) FaSade Requirements 1. Street F rontage Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. Multiple Principal Buildings Permitted 1. Street Fagade Transparency Property Line Coverage Minimum 95 °k O Front Ground Story Street Storefront with minimum 70 °k; Occupation of Corner Required O Facing Transparency otherwise, 65% 0 -10 ft. with up to 25% Upper Story Transparency Minimum 30% Front RBZ of the front facade O permitted between Blank Wall Limitations Required 10 -20 ft. 2 • Non - St FaSade Transparency Corner RBZ o -10 ft. © Transparency Minimum 15% RBZ Treatment Patio or Streetscape Blank Wall Limitations Required Projecting signs, eaves, Right -of -Way Encroachment awnings, patios, & 3. Buil Entranc canopies 2. Buildable Area Principal Entrance Location Principal frontage street facade of building ,wR iY Minimum Side Yard Setback 0 ft. CD Entrance must be recessed if Entrance Requirements located within 5 ft. of front Minimum Rear Yard Setback 5 ft. © property line Minimum Lot Width 50 ft. O Street Facades: Number of 1 per 75 ft. of facade minimum Maximum Lot Width None Entrances Maximum Impervious Coverage 85% Parking Lot Fagades: Number Minimum of 1 Additional Semi - Pervious Coverage 10% of Entrances 3. Parking Location & Loading In shopping corridors, 1 required Mid - Building Pedestrianway for buildings greater than 250 ft. Rear; within building in length Parking Location (refer to (c) Uses CD &Occupancy 4. FaSade Divisions Requirements) Vertical Increments No greater than 45 ft. Loading Facility Location Rear On buildings 3 stories or taller, or Rear, side, or corner Entry for Parking within Building fagade on non - principal Horizontal Fa ade Divisions q where the maximum ground Floor height is used, required within 3 fron streets ft. of the top of the ground story (b) Height Required Change in Roof No greater than every 80 ft. Plane or Type Height 2 stories Q Minimum S. FaSade Materials Maximum Height 5 stories © Ground Story: Minimum Height 16 ft. Permitted Primary Materials Stone, Brick, Glass Maximum Height 2 4 ft. 6. Roof Types Upper Stories: Minimum Height 10 ft. Maximum Height 14 ft. Parapet, pitched roof, Flat roof, (c) Uses & Occupancy Requirements Permitted Types other types permitted with approval (refer to §153.062(D)) Residential and general office uses Permitted on fagades only at Ground Story prohibited in shopping corridors; Podium terminal vistas, corners at parking structures are conditional uses in Tower two principal frontage streets, accordance with §153.059(C)(3)(g). adjacent to an open space type, and /or with a civic use Upper Story No additional requirements Parking within Permitted in the rear of all Floors and fully Building in any basement Occupied Space Minimum 30 ft. depth from the front and/ O or corner side fagades 4$ § 153.062 (0) (6) EFFECTIVE DATE BUILDING TYPES JANUARY 7, 2015 MIXED USE BUILDING Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual FIGURE 153.062 -S: MIXED USE BUILDING WINE DIAGRAM. BRIDOESIRffTDDB ICT § 153.062 (0) (6) 49 DEVSLOPMEVT CODE BBILDING TYPES - MIXED USE BUILDING ■ Permitted Parking within Building (7) Commercial Center (a) Building Siting 1. Street Frontage Multiple Principal Buildings Permitted O Front Property Line Coverage Minimum 45% O Occupation of Corner Required Storefront with minimum 65% Front RBZ 5 -25 ft. Upper Story Transparency Corner Side RBZ 5 -25 ft. RBZ Treatment Landscape, Patio, or Required Streetscape 2. Non-Street FaSade Transparency Right -of -Way Encroachment None Parking Lot Ground Story Transparency 2. Buildable Area Minimum Side Yard Setback 5 ft. Minimum 15% Minimum Rear Yard Setback 5 ft. Blank Wall Limitations Minimum Lot Width 50 ft. O Maximum Lot Width None Maximum Impervious Coverage 75% Principal Entrance Location Additional Semi - Pervious 15% Coverage 1 per 75 ft. of principal frontage street facade 3. Parking Location &Loading Parking Lot Facades: Number of Entrances Rear & side yard; within building (refer to (c) Uses & Not required Occupancy Requirements). 4. FaSade Divisions Parking may be forward of Parking Location principal buildings provided No greater than 45 ft. the minimum front property Horizontal Facade Divisions line coverage and RBZ treatment requirements None are met by other principal 5. FaSade Materials buildings. Loading Facility Location Rear Stone., Brick, Glass Side, rear, or corner side 6. Roof Types Entry for Parking within Building facades on non - principal frontage streets Parapet, pitched roof, Flat roof; other types permitted with approval (refer to §153.062(D)) Access Refer to O §153.062(N)(1)(c) (b) Height Minimum Height 1 story Q Maximum Height 3 stories Ground Story: Minimum Height 12 ft. Maximum Height 18 ft. Upper Stories: Minimum Height 10 ft. Maximum Height 14 ft. (c) Uses & Occupancy Requirements Residential uses prohibited; Podium Ground Story parking structures are conditional uses in accordance with §153.059(C)(3)(g). Upper Story No additional requirements Parking within Permitted in the rear of the first floor and Building fully in any basement(s) Minimum 30 ft. depth from the front and/ O Occupied Space or corner side elevations if the side is a principal frontage street (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Ground Story Street Facing Transparency Storefront with minimum 65% Upper Story Transparency Minimum 20% Blank Wall Limitations Required 2. Non-Street FaSade Transparency Parking Lot Ground Story Transparency Storefront with minimum 50% Transparency Minimum 15% Blank Wall Limitations Required 3. Building Entrance Principal Entrance Location Not Applicable Street Facades: Number of Entrances 1 per 75 ft. of principal frontage street facade ' Parking Lot Facades: Number of Entrances 1 per 100 ft. of facade minimum Mid - Building Pedestrianway Not required 4. FaSade Divisions Vertical Increments No greater than 45 ft. Horizontal Facade Divisions On 3 -story buildings, required within 3 ft. of the top of the ground story Required Change in Roof Plane or Type None 5. FaSade Materials Permitted Primary Materials Stone., Brick, Glass 6. Roof Types Permitted Types Parapet, pitched roof, Flat roof; other types permitted with approval (refer to §153.062(D)) Tower Permitted on facades only at terminal vistas, corners at two principal frontage streets, and /or adjacent to an open spa type Notes: 1 Minimum front property line coverage shall be met, but not all principal buildings must be located within a Required Building Zone. 50 § 153.062 (0) (7) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 COMMERCIAL CENTER Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. - rermic eu narking within Building FIGURE 153.062 -T: COMMERCIAL CENTER BUILDING TYPE DIAGRAM. BRIDGE STREET DISTRICT § 153.062 (7) 51 DEVELOPMENT CODE BUILDING Pes COMMERCIAL CENTER (8) Large Format Commercial (a) Building Siting 1. Street Frontage Multiple Principal Buildings Permitted Front Property Line Coverage Minimum 95% O Occupation of Corner Required O 0 -10 ft. with up to 25% Ground Story Street Front RBZ of the front facade O permitted between principal frontage street: minimum 10 -20 ft. Corner Side RBZ 0 -10 ft. RBZ Treatment Patio or Streetscape Minimum 20% Projecting signs, eaves, Blank Wall Limitations Right -of -Way Encroachment awnings, patios, & canopies 2. Buildable Area Minimum 15% Minimum Side Yard Setback 0 ft. Blank Wall Limitations Minimum Rear Yard Setback 5 ft. Minimum Lot Width 250 ft. O Maximum Lot Width None Principal Entrance Location Maximum Impervious Coverage 85% Additional Semi - Pervious Coverage 10% building 3. Parking Location & Loading Street Facades: Number of Rear yard, within Parking Location building (refer to (c) Uses & Occupancy Parking Lot Facades: Number of Entrances Requirements) Loading Facility Location Rear Not required Rear, side, or corner 4. Fagade Divisions Entry for Parking within Building side facade on non- principal frontage O streets No greater than 45 ft. (b) Height Minimum Height 2 storied Maximum Height 5 stories where the maximum ground floor Ground Story: Minimum Height 15 ft. Maximum Height 24 ft. 1; Additional height �WY' may be permitted with Site feet of the top of the gro story Plan approval for theaters Required Change in Roof Plane or Type and other special indoor entertainment/recreation uses Permitted Primary Materials Upper Stones: Minimum Height 10 ft. Maximum H eight 14 ft. (c) Uses & Occupancy Requirements Permitted Types Residential uses prohibited; Residential and general office uses prohibited in shopping approval (refer to §153.062(D)) Ground Story corridors; Podium parking structures are conditional uses in accordance with §153.059(C)(3)(g). terminal vistas, corners at Upper Story No additional requirements Tower Parking within Permitted in the rear of all floors and fully Building in any basement adjacent to an open space type, Occupied Space Minimum 30 ft. depth from the front and/ O or corner side facades (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Storefront with minimum 65 %; Ground Story Street corner side facade on non - Facing Transparency principal frontage street: minimum 30% Upper Story Transparency Minimum 20% Blank Wall Limitations Required 2. Non Fagade Transparency Transparency Minimum 15% Blank Wall Limitations Required 3. Building Entrance Principal Entrance Location Principal frontage street facade of building Street Facades: Number of Minimum of 1 per 75 ft. of facade Entrances Parking Lot Facades: Number of Entrances Minimum of 1 per 150 ft. Mid - Building Pedestrianway Not required 4. Fagade Divisions Vertical Increments No greater than 45 ft. On buildings 3 stories or taller, or Horizontal Facade. Divisions where the maximum ground floor height is used, required within 3 �WY' feet of the top of the gro story Required Change in Roof Plane or Type No greater than every 80 ft. 5. Fagade Materials Permitted Primary Materials Brick, Stone, Glass 6. Roof Types Permitted Types Parapet, pitched roof, flat roof; other types permitted with approval (refer to §153.062(D)) Permitted on facades only at terminal vistas, corners at Tower two principal frontage streets, adjacent to an open space type, .and /or with a theater use Note: 1 Any ground story height of 20 feet or taller counts as two stories. 52 § 153.062 (0) (8) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 LARGE FORMAT COMMERCIAL Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. C1 BRIDGE STREET DISTRICT § 153.062 O (8) 53 DEVELOPMENT CODE &IILDING LARGE FORMAL COMMERCIAL FIGURE 153.062 -U: LARGE FORMAT COMMERCIAL BUILDING TYPE DIAGRAM. (9) Historic Mixed Use (a) Building Siting (d) FaSade Requirements 1. Street Frontage Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. Multiple Principal Buildings Permitted 1. Street Fagade Transparency Front Property Line Coverage Minimum 80% O Occupation of Corner Required O Ground Story Street Facing Transparency Storefront with minimum 40% Front RBZ 0 -20 ft. O Upper Story Transparency Min imum 20% T Corner Side RBZ 0 -10 ft.1 © Blank Wall Limitations Required Patio or Streetscape; 2. Non - Street Fagade Transparency RBZ Treatment Porches, stoops, and balconies are permitted Transparency Minimum 15% in the RBZ Blank Wall Limitations Required Right -of -Way Encroachment Projecting signs, awnings, eaves, patios, 3. Building Entrance & canopies Principal Entrance Location Principal frontage street facade of 2. Buildable Area building {{► Minimum Side Yard Setback 0 ft. Street Facades: Number of 1 per 40 ft. of facade for buildings Entrances over 60 ft. minimum Minimum Rear Yard Setback 0 ft. Parking Lot Facades: Number Minimum 1 Minimum Lot Width 30 ft. of Entrances of Maximum Lot Width None O Mid- Building Pedestrianway 1 required for buildings greater Maximum Impervious Coverage 85% than 150 ft. in length Additional Semi - Pervious Coverage 5 °k 4. Facade Divisions 3. Parking Location & Loading Vertical Increments No greater than 30 ft. Parking Location Rear Horizontal Facade Divisions N/A Loading Facility Location Not applicable Required Change in Roof Entry for Parking within Building Not applicable Plane or Type At every vertical division (b) H eight 5. Fagade Materials Minimum Height 1.5 stories Q Permitted Primary Materials Stone, Brick, Wood Siding Maximum Height 2.5 stories © 6. Roof Types Ground Story: Minimum Height 10 ft. Pitched roof; other types Maximum Height 12 ft. Permitted Types permitted with approval (refer to §153.062(D)) Upper Stories: Minimum Height Maximum Height 9 ft. 12 f t. Permitted on facades only at Tower terminal vistas, corners at two (c) Uses & Occupancy Requirements principal frontage streets, and /or adjacent to an open space type Residential uses prohibited; Podium Ground Story parking structures are conditional uses in accordance with §153.059(C)(3)(g). Upper Story . No additional requirements Note: Parking within 1 When any front or corner property line is within five feet or less of the Building Not permitted back of curb, the RBZ shall begin five feet off the back of curb to allow for adequate sidewalk width. Occupied Space Not applicable 54 § 153.062 (0) (9) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 HISTORIC MIXED USE Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual FIGURE 153.062 -V: HISTORIC MIXED USE BUILDING TYPE DIAGRAM. a jilding BRIDGE STREET DISTRICT § 153.062 (0) (9) 55 DEVELOPMENT CODE BUILDING TYPES - HISTORIC MIXED USE (10) Historic Cottage Commercial (a) Building Siting 1. Street Frontage Transparency Multiple Principal Buildings Permitted Blank Wall Limitations Front Property Line Coverage Minimum 50% O Occupation of Comer Required O Front RBZ 0 -25 ft .1 Street Facades: Number of Entrances Corner Side RBZ 0 -15 ft1 Parking Lot Facades: Number of Entrances RBZ Treatment Landscape, Patio, or Streetscape 4. Fagade Divisions Right -of -Way Encroachment Projecting signs, eaves, awnings, patios, & canopies Vertical Increments 2. Buildable Area Horizontal Fagade Divisions Minimum Side Yard Setback 3 ft. Required Change in Roof Plane or Type Minimum Rear Yard Setback 5 ft. S. Fagade Mater Minimum Lot Width Maximum Lot Width 30 ft. None O Maximum Building Leng or Depth 70 ft. 6. Roof Types Maximum Impervious Coverage Additional Semi - Pervious Coverage 75% 10% Permitted Types 3. Pa Location & Loading Tower Parking Location Rear or side, provided the minimum front property line coverage is met Loading Facility Location Not applicable Entry for Parking within Building Not applicable Access Refer to §153.062(N)(1)(c) //�� `' (b) Height Minimum Height 1 story Q Maximum Height 2 stories Ground Story: Minimum Height Maximum Height 8 ft. 11 ft. Upper Stories: Minimum Height Maximum Height 7.5 ft. 11 ft. (c) Uses & Occupancy Requirements Ground Story Residential uses prohibited Upper Story No additional requirements Parking within Not permitted Building Occupied Space Not applicable (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Transparency Minimum 25% Blank Wall Limitations Required on ground story only 2. Non - Street Fagade Transparency Transparency Minimum 15% S Blank Wall Limitations Not required 3. Building Entrance Principal Entrance Location Principal frontage street facade of building Street Facades: Number of Entrances 1 per every 30 ft. for buildings over 50 ft. minimum Parking Lot Facades: Number of Entrances Not applicable 4. Fagade Divisions Vertical Increments No greater than 30 ft. Horizontal Fagade Divisions Not applicable Required Change in Roof Plane or Type At every vertical division S. Fagade Mater Permitted Primary Materials Stone, Brick, Wood Siding 6. Roof Types Permitted Types Pitched roof; other types permitted with approval (refer to §153.062(D)) Tower Not permitted Note: 1 When any front or corner property line is within five feet or less of the back of curb, the RBZ shall begin five feet off the back of curb to allow for adequate sidewalk width. 56 § 153.062 (0) (10) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 HISTORIC COTTAGE COMMERCIAL I zone FIGURE 153.062 -W: HISTORIC COTTAGE COMMERCIP BUILDING TYPE DIAGRAM. BRIDGE STREET DISTRICT Cj 153.062 f01 (10) 57 DEVELOPMENT CODE BUILDING PS - HIRMRIC COTTAGE COMrERUI Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. (11) Civic Building (a) Building Siting 1. Street Frontage Multiple Principal Buildings Permitted Occupation of Corner Not required Minimum Front Setback 15 ft. O Minimum Corner Side Setback 15 ft. O Setback Treatment Landscape, Patio, or Maximum Lot Width Streetscape Right -of -Way Encroachment None 2. Buildable Area Minimum Side Yard Setback 10 ft. Minimum Rear Yard Setback 20 ft. Minimum Lot Width 50 ft. Maximum Lot Width None O Maximum Impervious Coverage 65% Additional Semi - Pervious Coverage 10% 3. Parking Location & Loading Rear & side yard, within Minimum 25% Parking Location building (refer to (c) Blank Wall Limitations Uses & Occupancy Requir Loading Facility Location Rear Minimum 20% Rear, side, corner side Blank Wall Limitations Entry for Parking within Building facades on non - principal frontage streets Access Refer to O §153.062(N)(1)(c) �fR, ''iWY (b) Height 1 per 75 ft. of facade minimum Minimum Height 1.5 stories Q Maximum Height 5 stories; 3 stories in BSD Historic Core District Not required Ground .Story: Minimum Height 12 ft. 4. Fagade Divisions Maximum Height 24 ft. Upper Stories: Minimum Height 9 ft. No greater than 60 ft. Maximum Height 14 ft. Horizontal Facade Divisions (c) Uses & Occupancy Requirements VY Civic /Public /Institutional only except None Ground Story day care as a principal use; Podium 5. Fagade Materials parking structures are conditional uses in accordance with §153.059(C)(3)(g). Brick, Stone, Glass Upper Story Civic /Public /Institutional only 6. Roof Types Parking within Permitted in the rear of the first 3 Floors Building and fully in any basement(s) Parapet, pitched roof, Flat roof; other types permitted with approval (refer to §153.062(D)) Occupied Space Minimum 30 ft. depth from the front and/ O or corner side fagades (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency Transparency Minimum 25% Blank Wall Limitations Required 2. Non - Street Fagade Transparency Transparency Minimum 20% Blank Wall Limitations Required 3. Building Entrance Principal Entrance Location Principal frontage street facade of building �fR, ''iWY Street Facades: Number of Entrances 1 per 75 ft. of facade minimum Parking Lot Facades: Number o f Entrances 1 per 100 ft. of facade minimum Mid - Building Pedestrianway Not required 4. Fagade Divisions Vertical Increments No greater than 60 ft. Horizontal Facade Divisions On buildings 3 stories or taller, or where the maximum ground Floor height is used; required within 3 ft. of the top of the ground story VY Required Change in Roof Plane or Type None 5. Fagade Materials Permitted Primary Materials Brick, Stone, Glass 6. Roof Types Permitted Types Parapet, pitched roof, Flat roof; other types permitted with approval (refer to §153.062(D)) T ower Permitted Note: I Any ground story height of 20 feet or taller counts as two stories. 58 § 153.062 (0) (11) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 CIVIC BUILDING Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual vithin BRIDGESTFEETDISTBICT § 153.062(0)(11) 59 DEb OPMENTCODE BGILDINGTVPEB - CIVIC BUILDING FIGURE 153.062 - X: CIVIC BUILDING T DIAGRAM. (12) Parking Structure' (a) Building Siting 1. Street Frontage. Street frontage requirements apply only when no buildings are planned between the street and the parking structure. Multiple Buildings Not permitted Minimum Front Property Line Coverage 90% O Occupation of Corner Required O Front RBZ 5 -25 ft. Corner Side RBZ 5 -25 ft. RBZ Treatment Landscape, Patio, or Streetscape Right -of -Way Encroachment None 2. Buildable Area Minimum Side Yard Setback 5 ft. Minimum Rear Yard Setback 5 ft. Minimum Lot Width 80 ft. Maximum Lot Width None O Maximum Building Length 300 ft. Maximum Impervious Coverage 80% Additional Semi- Pervious Coverage 10% 3. Pa Loc & Loading Within building Parking Location only (refer to (c) Uses & Occupancy Requirements) Rear, side, corner side Entry for Parking within Building fagades on non - principal frontage streets Access Refer to §153.062(N)(1)(c) (b) Height Minimum Height 2 stories Q Maximum Height 5 stories 3,4 Ground Story: Minimum Height 8 ft. / 12 ft. 1 Maximum Height 18 ft. Upper Stories: Minimum Height 8.5 ft .1 Maximum Height 12 ft. (c) Uses & Occupancy Requirements Commercial uses are required only when Ground Story fronting a principal frontage street, a O shopping cor or a gree Upper Story No additional requirements Rear of ground story where there is Parking within frontage on a principal frontage street, a Building shopping corridor, or a greenway; all Floors above ground story Minimum 20 ft. depth where the ground Occupied Space story fronts on a principal frontage street, O a shopping corridor, or a greenway (d) FaSade Requirements Refer to §153.062(D) through §153.062(N) for design requirements general to all buildings. 1. Street Fagade Transparency. This section applies only parking structures fronting streets. Storefront with minimum 65% Ground Story on principal frontage streets, Street Facing Transparency shopping corridors, or greenways; otherwise, refer to the blank wall limitations Blank Wall Limitations Required 5 Garage Openings Parked cars shall be screened from the street 2. Non - Street Fagade Transparency Blank Wall Limitations Required 6 3. Building Entrance. This section applies only to parking structures fronting streets. Principal Pedestrian Entrance All street facades of building Location Street Facades: Number of 1 per 75 ft. of fagade minimum Entrances Parking Lot Fagades; Number of Entrances Not applicable Mid - Building Pedestrianway Not required 4. Fagade Divisions. This section applies only to parking structures fronting streets. Vertical Increments No greater than 30 ft. Horizontal Fagade Divisions Required within 3 ft. of the top of Ii the ground story Required Change in Roof None Plane or Type Garage. Floors Garage Floors shall be horizontal along all street fagades. 5. Fagade Materials Permitted Primary Materials Brick, Stone, Glass 6. Roof Type Parapet, pitched roof, Flat roof; Permitted Types other types may be permitted with �!�!. approval (refer to §153.062(D)) C Permitted on fagades only at Tower terminal vistas, corners at two principal frontage streets, and /or adjacent to an open space type Notes: 1 The requirements of §153.065(B)(5) Parking Structure Design shall be met. Z Vehicular entrance openings shall not exceed 30 feet in width. 3 Height may not exceed overall height in feet of any adjacent building or any conforming building immediately across the street. 4 Parking is permitted on roof level. 5 No open area greater than 30% of a story's fagade, as measured from Floor to Floor, shall be windowless on the ground story and solid on the upper stories. 6 No rectangular area greater than 30% of a story's fagade, as measured from Floor to Floor shall be solid. 60 § 153.062 (0) (12) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 PARKING STRUCTURE Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. �PO�mmal 6v�4inn v�i�6in Zone FIGURE 153.062 - Y: STRUCTURED PARKING BUILDING TVPE DIAGRAM. BFUDOESITEETDISTCICr § 153.062(0) (12) 61 DEV�OPMEVT CODE BGILDINGTWES- PPRKING STRUCTURE (13) Podium Apartment Building (a) Building Siting (d) FaSade Requirements 1. Street Fr ontage Refer to §153.062(D) through §153.062(N) for design Multiple Principal Buildings Permitted Additional Semi- Pervious Coverage Front Property Line Coverage Minimum 75 % O Occupation of Corner Required Front RBZ 5 -20 ft. building (subject to Corner Side RBZ 5 -20 ft. Maximum Lot Width Landscape or less than O 50% Patio; porches, RBZ Treatment stoops, and balconies 2. Non - Street Fagade Transparency are pgrmitted in the Minimum 90% opacity on RBZ Right -of -Way Encroachment None Additional Semi- Pervious Coverage 2. Buildable Area 3. Parking Location & Loading Minimum Side Yard Setback 5 ft. Minimum Rear Yard Setback 5 ft. building (subject to Minimum Lot Width 50 ft. Maximum Lot Width None O Maximum Impervious Coverage 70% Additional Semi- Pervious Coverage 20% 3. Parking Location & Loading Ground Floor of residential Parking Location building (subject to applicable screening requirements) ' Loading Facility Location Rear Entry for Parking within Building Rear & side. facade. Access Refer to O §153.062(N)(1)(c) (b) Height Minimum Height 3 stories Maximum Height 4.5 s Stories: Minimum Height 10 ft. Maximum Height 14 ft. 2.5 ft. above the Minimum Finished Floor Elevation adjacent 4 i dewalk elevation (c) Uses & Occupancy Requirements Podium parking structures are conditional Ground Story uses in accordance with §153.059(C)(3) (g). Upper Story No additional requirements Permitted; podium garage parking shall be screened to at least 90% opacity through Parking within the use of building materials that are Building compatible with and integrated into the remainder of the facade that is located above parking area Occupied Space None required in ground story, except as O provided in footnote 8. requirements general to all buildings 1. Street Fagade Transparency Minimum 90% opacity on portion of ground Floor or visible Transparency basement occupied by podium garage parking; minimum 20% transparency otherwise and for all other portions of the building. Blank Wall Limitations Required 2. Non - Street Fagade Transparency Minimum 90% opacity on portion of ground Floor or visible Transparency basement occupied by podium ,J'a 'Y o garage parking; minimum 15% transparency otherwise and for all other portions of the building Blank Wall Limitations Required 3. Building Entrance Principal Entrance Location Primary street fagade(s) of building Street Facades: Number of Entrancesb 1 per 75 ft. of facade minimum Parking Lot Facades; Number Not required of Entrances 1 required for buildings longer Mid - Building Pedestrianway than 250 ft, except as provided in §153.063, Neighborhood Standards 4. Fagade Divisions Vertical Increments No greater than 40 ft. On buildings 3 stories or taller, Horizontal Fagade Divisions required within 3 ft. of the top of the ground story Required Change in Roof Plane or Type No greater than every 80 ft. 5. Fagade Materials Permitted Primary Materials Stone, Brick, Glass6 6. Roof Types Parapet, pitched roof, Flat roof; Permitted. Types other types may be permitted with Olt approval (refer to §153.062(D)). Permitted on fagades only at terminal vistas, corners at two Tower principal frontage streets, and/ or adjacent to plaza open space type. Notes: 1 An open and unenclosed landscaped courtyard meeting the open space type requirements of §153.064 may contribute up to 35% of the front property line coverage requirement. z A landscape buffer a minimum of five feet in width as measured from the base of the building is required. In addition to the foundation planting requirements of §153.065(D)(7), the required reviewing body may require enhanced foundation plantings, including but not limited to vertical landscape materials, to add visual interest to the ground floor or exposed basement level parking facade. 62 § 153.062 (0) (13) EFFECTIVE DATE BUILDING TYPES - JANUARY 7, 2015 PODIUM APARTMENT BUILDING Notes, Continued 3 Basement level structured parking is permitted to extend between buildings, screened from the street and covering a maximum of 10% of the length of the RBZ. Structured parking visible between principal buildings must be set back a minimum of 15 ft. from the street facing facades. 4 The minimum finished floor elevation applies to the residential units, common areas, and other occupied spaces and is not intended to apply to the parking structure. Where the principal building entrance is a lobby or other common space, the minimum finished floor elevation is not required. 5 I lieu of transparency requirements, the ground story or exposed basement facade shall incorporate architectural elements equal to the degree of detailing used on the stories above the parking level. Blank wall limitations may be met using these architectural enhancements, as determined by the required reviewing body. 6 The required reviewing body may reduce . the number of entrances along street facades as functionally appropriate to the apartment building with parking fully or partially below grade, provided the building has an adequate number and frequency of entrances to be convenient for residents and visitors and the entrances are conducive to establishing a safe and attractive pedestrian realm. 7 Masonry, as described in §153.062(E)(1), shall be used as the primary building material for ground story or exposed basement facades. BRIDGE STREET DISTRICT § 153.062 (0) (13) 63 DEVELOPMENT CODE BUILDING P S- PODIUM APARTMENT BUILDING Required Building Zone 8 The incorporation of active, Note: Graphic figures are intended to occupied spaces along street illustrate one result of one or more of facades is strongly encouraged the general requirements and do not wherever practicable. common represent all requirements or actual spaces including but not limited development. to a clubhouse, fitness facility, or administration /rental /sales office, should be designed so that those buildings or uses FIGURE 153.062 -P: PODIUM APARTMENT BUILDING TYPE DIAGRAM. have ground story street frontage. BRIDGE STREET DISTRICT § 153.062 (0) (13) 63 DEVELOPMENT CODE BUILDING P S- PODIUM APARTMENT BUILDING Required Building Zone § 153.063 NEIGHBORHOOD STANDARDS (A) INTENT Certain Bridge Street District zoning districts require special attention to locations and character of buildings, streets, and open spaces to accommodate larger scale, coordinated development and redevelopment to permit a wide variety of uses. The intent of §153.063 is to establish requirements for the creation of signature places in the city consistent with the Community Plan (Bridge Street District Area Plan)by incorporating long -term phasing plans, transitional development conditions, and adaptability to future market needs. The neighborhood standards guide the development of streets, open spaces, buildings, and other placemaking elements over time. They are not intended to designate the precise locations for approved street types, use areas, open spaces or other required elements of this Code, actual locations and specific development requirements will be determined through the Development Plan and Site Plan Reviews as required in §153.066 for individual neighborhoods. However, where conflicts with other sections of the zoning regulations applicable to the Bridge Street District exist, the provisions of §153.063 shall apply. (1) The BSD Historic Residential District is a singularly unique residential neighborhood with a historic development pattern. The requirements for the BSD Historic Residential District ensure that the scale and placement of new or modified buildings are compatible with the historic character of the existing residential uses and streets. (2) The BSD Sawmill Center Neighborhood and BSD Indian Run Neighborhood districts anchor the Bridge Street District through the creation of mixed use neighborhoods with signature development characters. Each neighborhood is intended to be anchored by a critical mass of commercial uses located in highly walkable shopping corridors with streets, blocks, buildings and open spaces designed to encourage park -once visits, window shopping, impromptu public gatherings and sidewalk activity. (3) The BSD Historic Transition Neighborhood District serves as a bridge between the existing historic scale of the BSD Historic Core District and the more contemporary, larger scale of the BSD Indian Run Neighborhood District. (4) The standards of the BSD Scioto River Neighborhood are intended to create an active, walkable destination through integration of a vibrant mix of uses. Development in this district is oriented toward the Scioto River and the public spaces along the riverfrom, and includes important vehicular and bicycle links to adjacent neighborhoods and open spaces. (B) BSD HISTORIC RESIDENTIAL DISTRICT (1) Development Intent While included as part of the Neighborhood Standards, it is the intent of this district to maintain the existing conditions of this important neighborhood. The BSD Historic Residential neighborhood represents a snapshot in time that should be maintained, preserved, and protected. (2) The following standards for arrangement and development of land and buildings are required. (a) LotArea For each dwelling unit, there shall be a lot area not less than 8,712 square feet (0.2- acre). (b) Lot Width Lots shall be a minimum of 60 feet in width with a minimum frontage of 60 feet along a public street. (c) Height No residential structure shall exceed 35 feet in height. Maximum height for other structures shall not exceed a safe height as determined by the Fire Chief and as reviewed and accepted by the Architectural Review Board. (d) Lot Coverage Combined square footage of all principal and accessory structures and impervious surfaces shall not exceed 50% of the lot area, unless otherwise approved by the Architectural Review Board. (e) Front, Side, and Rear Yards All lots shall have minimum setbacks as noted in Table 153.063 -A. (C) BSD SAWMILL CENTER DISTRICT (1) Development Intent The Sawmill Center Neighborhood offers a unique opportunity to provide a vibrant, active mixed use environment with a wide variety of shopping, service and entertainment activities. This neighborhood will have a strong pedestrian friendly streetscape and a well - defined network of streets connecting to the major roadways of Sawmill Road and West Dublin - Granville Road. Supporting residential and office uses may be incorporated in a variety of ways, including upper floors in vertical mixed use areas and in stand- alone buildings. Additionally, the neighborhood will have connections to greenways planned for the Bridge Street District to connect to other development areas to the west. (2) Refer to §153.058 for the BSD Sawmill Center Neighborhood District intent and the Zoning Map for the actual limits of the BSD Sawmill Center Neighborhood District. Refer to Figure 153.063 -A for an illustration of a conceptual development pattern 64 § 153.063 EFFECTIVE DATE NEIGHBORHOOD STANDARDS JANUARY 7, 2015 TABLE 153.063 -A. MINIMUM YARD REQUIREMENTS FOR BSD HISTORIC RESIDENTIAL DISTRICT For properties Front Yard Side Yard Total Side Yard Rear Yard fronting onto: (feet) (feet) (feet) (feet) Dublin Road 15 4 16 15 Franklin Street 25 4 12 25 High Street (north & 15 4 16 15 south) South Riverview Street 0 3 12 15 (east side) South Riverview Street 20 3 12 15 (west side) North Riverview Street 0 3 6 15 (east side) North Riverview Street 20 3 6 15 (west side) Short Street 20 3 12 15 Streets not listed above 20 3 12 15 desired for this district. Actual locations of elements depicted on the graphic will be determined through the Development Plan and Site Plan Review processes. (3) Block, Access, and Street Layout (a) Block Length Refer to Table 153.060 -A, Maximum Block Dimensions. (b) Access Refer to § §153.060 and 153.061 for existing and planned principal frontage streets within the BSD Sawmill Center Neighborhood District and general block access configurations. (c) Mid- Block Pedestrianways Blocks consisting entirely of residential uses that are located in predominantly residential development areas may be exempted from the mid -block pedestrianway requirements of §153.060(C)(6), subject to approval by the required reviewing body, except where a block has frontage on a principal frontage street. (d) Street Types Refer to §153.061 for existing and potential streets and street family designations within the BSD Sawmill Center Neighborhood District. (4) Building Types. Refer to §153.062. (a) Permitted Building Types Refer to §153.062(B)(3)(a) for permitted building types in the BSD Sawmill Center Neighborhood District. (b) Building Types Permitted in Shopping Corridors Corridor Building, Loft Building, Mixed Use Building, Large Format Commercial Building (c) Commercial Center Building Types Commercial Center building types are permitted to front only on the north side of the east/west- oriented portions of Village Parkway and Sawmill Road as depicted on Figure 153- 063(A). (5) Placemaking Elements 1. The intent for designated shopping corridors in the BSD neighborhood districts is to provide continuous mixed -use street frontages with retail uses and eating and drinking facilities occupying the ground floor of buildings located on streets that have a well - defined and detailed pedestrian realm. Buildings with frontage on designated shopping corridors should be sited to accommodate a mix of outdoor activities, such as patios, seating areas, pocket plazas and spacious walkways. 2. At least one continuous shopping corridor is required and shall be located along at least one principal frontage street in the approximate location shown on Figure 153.063 -A. 3. The minimum required length of the required shopping corridor shall be measured as the aggregate length of the block faces along both sides of the principal frontage street. The required length shall be based on the total area of the development site as noted in Table 153.063 -B. TABLE 153.06 SHOPPING CORRIDOR LENGTH - BSD SAWMILL CENTER NEIGHBORHOOD DISTRICT Development Area Required Shopping Corridor Length Less than 5 acres No minimum 5 to 20 acres 600 linear feet minimum Over 20 acres 1,200 linear feet minimum BRIDGE STREET DISTRICT § 153.063 (C) 65 DEVELOPMENT CODE NEIGHBORHOOD STANDARDS - BSD SAWMILL CENTER NEIGHBORHOOD FIGURE 153.063 -A. ILLUSTRATION OF SAWMILL CENTER DEVELOPMENT STANDARDS 4. Any block exceeding 300 feet within a shopping corridor shall provide a mid -block pedestrianway meeting the requirements of §153.060(C)(6). 5. The required shopping corridor is permitted to turn the corner of a block provided the minimum required length of the shopping corridor is located along the principal frontage street. (b) Nlaster Sign Plans 1. The BSC Sawmill Center Neighborhood District is intended to accommodate a wide variety of building types and uses to create vibrant, mixed use shopping and entertainment districts. The sign and graphic standards shall contribute to the vibrancy of the district and the creation of a high quality environment with effective graphics intended for navigation, information, and identification primarily for pedestrians and secondarily for vehicles. 2. Amaster sign plan shall be submitted as required by §153.0660. The approved master sign plan may include alternative sign types, number, size, heights, locations, colors, and lighting, provided the purpose and intent of the sign and graphic standards for the BSC Sawmill Center Neighborhood District are maintained. (c) Street Terminations Refer to §153.062(J) for Treatments at Terminal Vistas. Open Space Commercial Center Node Building Type Potential dol"t Premitted Gateway % Locations Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. The Development Standards illustration is intended to be representative of a general development pattern. It is not intended to show the precise locations for approved street types, use areas, open spaces or other required elements of this Code. Actual locations and standards will be provided with the approval of the Development Plan and Site Plan as required in §153.066 for individual neighborhood areas. (d) Gateways 1. Gateways shall be provided in the approximate locations shown in Figure 153.063 -A. Gateway designs shall be approved with the Site Plan Review, but locations shall be identified with the Development Plan Review and shall be coordinated with the street network. 2. Gateways are points of identification that provide a sense of arrival to the area. Gateway designs shall be pedestrian- oriented in scale and shall include a combination of architectural elements, landscape features, and /or public open spaces. Gateway elements should enhance the character of the public realm consistent with the Principles of Walkable Urbanism of §153.057(D) and should be coordinated with the design of the nearby streetscape, open spaces and architecture as may be applicable. (6) Open Spaces. Refer to §153.064. (a) Open Space Character The BSD Sawmill Center Neighborhood district is intended to accommodate a wide variety of 66 NEIG a § 153.063 EFFECTIVE DATE BORHOOD STA D RDS - JANUARY 7, 2015 BSD SAWMILL CENTER NEIGHBORHOOD Shopping Corridor Connector PP 9 District Connector S Corridor Streets Corridor Open Space building types and uses to create vibrant, mixed use shopping and entertainment districts accented by a high quality open space network that balances a variety of natural and hardscape areas designed to provide intimate gathering spaces appropriate for an urban setting. (b) Required Open Space Open space shall be provided in accordance with the requirements of §153.064(C). All open spaces fulfilling this requirement shall meet the intent and design requirements of an open space type permitted in the BSD Sawmill Center Neighborhood District as described in §153.064(G). Required open spaces shall be publicly accessible and accommodate community activity and gathering spaces. (c) Permitted Open Space Types Refer to §153.064(G) for permitted open space types in the BSD Sawmill Center Neighborhood District. (d) Open Space Network 1. Open spaces within the BSD Sawmill Center Neighborhood district shall be organized as a series of interconnected nodes and corridors appropriate to the scale and character of surrounding streets, buildings and land uses. The purpose of this requirement is to create highly accessible public gathering spaces and activity areas along a continuous open space network weaving through this urban neighborhood. 2. The open space network shall be provided, at a minimum, in the approximate locations shown in Figure 153.063 -A. Open space designs shall be approved with the Site Plan Review, but locations and types shall be identified with the Development Plan application and shall meet the following criteria: A. Open space corridors and nodes shall be coordinated with the street network and with gateways where applicable. B. Open space corridors may be provided as a greenway open space type or by using approved street types, provided that open space nodes are located along the street with no greater than three full blocks between each open space node, and if pedestrian and bicycle movement between the open spaces is emphasized in the street design. C. The open space network shall connect to existing or planned greenways within the vicinity, providing pedestrian and bicycle access to nearby residential districts, the Scioto River, other destinations throughout the Bridge Street District, and to the city's larger open space system. D. Open space nodes shall be provided at prominent street intersections as identified during the Development Plan and Site Plan Reviews, such as those serving as entrances to a designated shopping corridor and other gateway locations, with other appropriately scaled open space types integrated along the corridor as appropriate to the character of the street. (D) BSD HISTORIC TRANSITION NEIGHBORHOOD DISTRICT (1) Development Intent The Historic Transition Neighborhood presents a unique opportunity within the Bridge Street District. Transitional elements include building on the BSD Historic Core District's strong gridded pedestrian and street network and providing appropriate connections to the BSD Indian Run Neighborhood. A balance of land uses will be important to support the smaller scale retail, service, and entertainment uses in the BSD Historic Core. Other limited areas of BSD Historic Transition Neighborhood border the Historic District and require sensitive treatment to maintain complementary relationships to adjacent districts. (2) Refer to §153.058 for the BSD Historic Transition Neighborhood District intent and refer to the Zoning Map for the actual limits of the BSD Historic Transition Neighborhood District. Refer to Figure 153.063 -13 for an illustration of a conceptual development pattern desired for this district. Actual locations of elements depicted on the graphic will be determined through the Development Plan and Site Plan Review processes. (3) Block, Access, and Street Layout (a) Block Length 1. Refer to Table 153.060 -A, Maximum Block Dimensions. 2. Developable lots are not permitted between greenways and the street adjacent to the Indian Run west of North High Street. (b) Access Refer to § §153.060 and 153.061 for existing and planned principal frontage streets within the BSD Historic Transition Neighborhood District and acceptable block access configurations. (c) Mid- B1ockPedestrianways Blocks consisting entirely of residential uses that are located in predominantly residential development areas may be exempted from the mid -block pedestrianway requirements of §153.060(C)(6), subject to approval by the BRIDGE STREET DISTRICT § 153.063 (C) 67 DEVELOPMENT CODE NEIGHBORHOOD STANDARDS - BSD SAWMILL CENTER NEIGHBORHOOD required reviewing body, except where a block has frontage on a principal frontage street. (d) Street Types Refer to § 153.061 for existing and potential streets and street family designations within the BSD Historic Transition Neighborhood District. (4) Building Types. Refer to §153.062. (a) Permitted Building Types Refer to §153.062(B)(3)(a) for permitted building types in the BSD Historic Transition Neighborhood District. (b) Building Height Buildings located across a street from or adjacent to the BSD Historic Core District shall be limited to two and a half stories. (5) Placemaking Elements (a) Historic Sites and Structures Historic sites and structures listed on the National Register and/or the Ohio Historic Inventory shall be preserved to the extent practicable with redevelopment unless otherwise approved by the Architectural Review Board pursuant to § 153.171. (b) Use Limitations Ground floor residential uses are not permitted on Bridge Street. (c) Gateways 1. Gateways shall be provided in the approximate locations shown in Figure 153.063 -B. Gateway designs shall be approved with the Site Plan Review, but locations shall be identified with the Development Plan Review and shall be coordinated with the street network. 2. Gateways are points of identification that provide a sense of arrival to the area. Gateway designs shall be pedestrian - oriented in scale and shall include a combination of architectural elements, landscape features and/or public open spaces. Gateway elements should enhance the character of the public realm and should be coordinated with the design of the nearby streetscape, open spaces and architecture as may be applicable. (6) Open Spaces. Refer to §153.064. (a) Permitted Open Space Types Refer to §153.064(G) for permitted open space types in the BSD Historic Transition Neighborhood District. (b) Open Space Character 1. The BSD Historic Transition Neighborhood District is intended to complement the BSD Historic Core District by accommodating a variety of building types within a finer grained street and block network and uses consistent with the district Development shall be planned to allow an extension of the walkable mixed use character of the BSD Historic Core District. 2. Open spaces shall be planned in a manner appropriate to the smaller scaled urban environment consistent with the Historic District, with a network of open spaces to serve the residential presence in the BSD Historic Transition Neighborhood District, a high quality public green to serve as a community gathering space, and connections to the Indian Run greenway and the Scioto River. (c) Required Open Space Open space shall be provided in accordance with the requirements of §153.064(C). All open spaces fulfilling this requirement shall meet the intent and design requirements of an open space type permitted in the BSD Historic Transition Neighborhood District. Required open spaces shall be publicly accessible and accommodate community activities and gathering spaces. (d) Open Space Network 1. Open spaces within the BSD Historic Transition Neighborhood District are intended to be organized as a series of interconnected nodes and corridors appropriate to the scale and character of surrounding streets, buildings and land uses. The purpose of this is to create highly accessible public gathering spaces and activity areas along a continuous open space network weaving through and around the edges of this urban neighborhood. 2. The open space network shall be provided, at a minimum, in the approximate locations shown in Figure 153.063 -B. Open space designs shall be approved with the Site Plan Review, but locations and types shall be identified with the Development Plan Review and shall meet the following criteria: A. Open space corridors and nodes shall be coordinated with the street network and with gateways where applicable. B. Greenways are required along all branches of the Indian Run and shall be designed to facilitate pedestrian and bicycle travel. Greenways shall be designed with publicly accessible street frontage for a minimum of one third of the greenway length along all branches of the Indian Run within the BSD Historic Transition Neighborhood District. C. Required greenways shall connect to existing or planned greenways within 68 § 153.063 (D) EFFECTIVE DATE NEIGHBORHOOD STANDARDS - JANUARY 7, 2015 BSD HISTORIC TRANSITION FIGURE 153.063 -B. ILLUSTRATION OF ORIC TRANSITION DEVELOPMENT STANDARDS Open Space Corridor �� Limited Building Height Boundary Open Space Node Potential Gateway Locations the vicinity, providing pedestrian and bicycle access to the BSD Indian Run Neighborhood District, the Scioto River, other destinations throughout the Bridge Street District, and to the city's larger open space system. D. Building frontage directly along a greenway with no intervening street shall be treated as street frontage and shall meet street- facing fagade requirements, except the minimum front property line coverage requirements are reduced to 50% along the greenway. E. Other required open space corridors may be created by using approved street types, provided that open space nodes are located along the street with no greater than three full blocks between each open space node and pedestrian and bicycle movement between the open spaces is emphasized in the street design. p I rao Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. The Development Standards illustration is intended to be representative of a general development pattern. It is not intended to show the precise locations for approved street types, use areas, open spaces or other required elements of this Code. Actual locations and standards will be provided with the approval of the Development Plan and Site Plan as required in §153.066 for individual neighborhood areas. r Corridor Connector & District Connector Streets 1919 Building s F. A minimum of one permitted open space type shall be provided north of Bridge Street, with continuous pedestrian and bicycle connections to the Indian Run greenway. G. Other open space nodes shall be provided at gateway locations as identified during the Development Plan and Site Plan Reviews, such as at prominent street intersections, with other appropriately scaled open space types integrated along the corridor as appropriate to the character of the street. (E) BSD INDIAN RUN NEIGHBORHOOD DISTRICT (1) Development Intent The BSD Indian Run Neighborhood District provides a significant opportunity for a well - planned and designed mixed use neighborhood. Special attention at the boundaries of the neighborhood will be required to deal with the sensitivity of the Indian Run and the BRIDGE STREET DISTRICT § 153.063 (D) 69 DEVELOPMENT CODE NEIGHBORHOOD STANDARDS - BSD HISTORIC TRANSITION opportunities for prominent visibility from I -270. Land use opportunities include a complementary residential presence, especially in those areas nearest the Indian Run, with office employment and supporting service and commercial uses. A comfortable, walkable street network is intended to convey a strong sense of connection between each of these diverse but balanced land uses. the mid -block pedestrianway requirement of §153.060(0)(6), subject to approval by the required reviewing body, except where a block has frontage on a principal frontage street. (d) Street Types 1. Streets fronted by a required open space type shall be designated as principal frontage streets. (2) Notwithstanding the foregoing, any real property that had a Planned Unit Development (PUD) classification 2. Refer to §153.061 for existing and planned pursuant to §153.052 immediately prior to its rezoning streets and street family designations within into the BSD Indian Run Neighborhood District the BSD Indian Run Neighborhood District. shall be permitted to be developed, at the election of (5) Building Types. Refer to §153.062. the property owner or other applicant, in one of the (a) Permitted Building Types following manners: Refer to §153.062(B)(3)(a) for permitted building (a) Per the terms of the PUD zoning text that was types in the BSD Indian Run Neighborhood approved in accordance with §153.052, if the District. approved PUD zoning text is silent on any (b) Building Types Permitted in Shopping Corridors particular matter, issue, restriction, or requirement, then the Dublin Zoning Code, as it existed Corridor Building, Loft Building, Mixed Use immediately prior to the adoption of § §153.057 Building, Large Format Commercial Building through §153.066, shall provide the applicable (c) Commercial Center Building Types zoning requirements. Aproperty owner or Commercial Center building types are permitted applicant that desires to develop their property m to front only on Bridge Street. accordance with this provision shall be required to file and obtain approval of a Final Development (6) Placemaking Elements Plan application as required under §153.053 of the (a) Shopping Corridor Dublin Zoning Code, or 1. The intent for designated shopping corridors (b) A property owner or applicant that desires to in the BSD neighborhood districts is develop their property in accordance with the to provide continuous mixed -use street requirements of § §153.057 through §153.065 frontages with retail uses and eating and shall be required to follow all of the procedures drinking facilities occupying the ground of §153.066 required for approval of development floor of buildings located on streets that projects under the BSD Indian Run Neighborhood have a well- defined and detailed pedestrian District. realm. Buildings with frontage on designated (3) Refer to §153.058 for the BSD Indian Run shopping corridors should be sited to Neighborhood District intent, and refer to the Zoning accommodate a mix of outdoor activities, Map for the actual limits of the BSD Indian Run such as patios, seating areas, pocket plazas Neighborhood District. Refer to Figure 153.063 -C for and spacious walkways. an illustration of a conceptual development pattern 2. At least one continuous shopping corridor desired for this district. Actual locations of elements is required and shall be located along at depicted on the graphic will be determined through the least one principal frontage street in the Development Plan and Site Plan Review processes. approximate location shown on Figure (4) Block, Access, and Street Layout 153.063 -C. (a) Block Length 3. The minimum required length of the required Refer to Table 153.060 -A, Maximum Block shopping corridor shall be measured as the Dimensions. aggregate length of the block faces along both sides of the principal frontage street. The (b) Access required length shall be based on the total Refer to § §153.060 and 153.061 for existing and area of the development site as noted in Table potential principal frontage streets within the BSD 153.063 -C. Indian Run Neighborhood District and acceptable block access configurations. (c) Mid- Block Pedestrianways Blocks consisting entirely of residential uses that are located in predominantly residential development areas may be exempted from 70 § 153.063 (E) EFFECTIVE DATE NEIGHBORHOOD STANDARDS - JANUARY 7, 2015 BSD INDIAN RUN NEIGHBORHOOD FIGURE 153.063 -C. ILLUSTRATION OF INDIAN RUN DEVELOPMENT STANDARDS \\ Shopping Corridor NEIGHBORHOOD DISTRICT Development Area Open Space Corridor Corridor Length Less than 5 acres No minimum 5 to 20 acres Open Space Node Over 20 acres 1,200 linear feet minimum Potential Gateway ��►, Locations 1 4.0 I Corridor Connector District Connector Streets 0=4 © � y Commercial Center Building Type Permitted Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. The Development Standards illustration is intended to be representative of a general development pattern. It is not intended to show the precise locations for approved street types, use areas, open spaces or other required elements of this Code. Actual locations and standards will be provided with the approval of the Development Plan and Site Plan as required in §153.066 for individual neighborhood areas. TABLE 153.063 -C SHOPPING CORRIDOR LENGTH - BSD INDIAN RUN NEIGHBORHOOD DISTRICT Development Area Required Shopping Corridor Length Less than 5 acres No minimum 5 to 20 acres 600 linear feet minimum Over 20 acres 1,200 linear feet minimum 4. Any block exceeding 300 feet within a shopping corridor shall provide a mid -block pedestrianway meeting the requirements of §153.060(C)(6). shall be treated the same as front fagades on principal frontage streets. Parking lots parking structures, garages, and loading facilities are not permitted in the rear yards of lots with frontage along the Indian Run greenway. 2. Eating and drinking establishments are encouraged along the Indian Run greenway, with an additional 10% semi - pervious area permitted for outdoor dining and seating where the outdoor dining area is within 20 feet of the principal structure. (c) Street Terminations 5. The required shopping corridor is permitted Refer to §153.062(1) for Treatments at Terminal to turn the corner of a block provided the Vistas. minimum required length of the shopping (d) Gateways corridor is located along the principal 1. Gateways shall be provided in the frontage street. approximate locations shown in Figure (b) Indian Run Frontage 153.063 -C. Gateway designs shall be 1. If buildings are fronted directly along the approved by the required reviewing body, Indian Run greenway, ground floor fagades but locations shall be identified with the BRIDGE STREET DISTRICT § 153.063 (E} 1 DEVELOPMENT CODE NEIGHBORHOOD STANNDAARDS - BSD INDIAN RUN NEIGHBORHOOD Development Plan Review and shall be and design requirements of an open space type coordinated with the street network. permitted in the BSD Indian Run Neighborhood 2. Gateways are points of identification that District as described in §153.064(G). Required provide a sense of arrival to the area. open spaces shall be publicly accessible and Gateway designs shall be pedestrian - oriented accommodate community activity and gathering in scale and shall include a combination of spaces. architectural elements, landscape features, (c) Permitted Open Space Types and/or public open spaces. Gateway elements Refer to §153.064(G) for permitted open space should enhance the character of the public types in the BSD Indian Run Neighborhood realm consistent with the Principles of District. Walkable Urbanism of §153.057(D) and (d) Open Space Network should be coordinated with the design of the nearby streetscape, open spaces and 1. Open spaces within the BSD Indian Run architecture as may be applicable. Neighborhood District shall be organized as a (e) Sign Plans series of interconnected nodes and corridors appropriate to the scale and character of 1. The BSD Indian Run Neighborhood District surrounding streets, buildings and land uses. is intended to accommodate a wide variety The purpose of this requirement is to create of building types and uses to create vibrant, highly accessible public gathering spaces and mixed use shopping and entertainment activity areas along . a continuous open space districts. The sign and graphic standards network weaving through and around the shall contribute to the vibrancy of the edges of this urban neighborhood. district and the creation of a high quality environment with effective graphics intended 2. The open space network shall be provided, for navigation, information, and identification at a minimum, in the approximate locations primarily for pedestrians and secondarily for shown in Figure 153.063 -C. Open space vehicles. designs shall be approved by the required reviewing body, but locations and types shall 2. Am aster sign plan shall be submitted be identified with the Development Plan for buildings within designated shopping and Site Plan Reviews and shall meet the corridors and as required by § I53.065(H) following criteria: and §153.066(L)(8). The approved master sign plan may include alternative sign types, A. Open space corridors and nodes shall be number, size, heights, locations, colors, and coordinated with the street network and lighting. with gateways where applicable. (7) Open Spaces. Refer to §153.064. B. Greenways are required along and on both sides of all branches of the Indian (a) Open Space Character Run and shall be designed to facilitate 1. The BSD Indian Run Neighborhood District pedestrian and bicycle travel. Greenways is intended to accommodate a wide variety shall be designed with publicly accessible of building types and uses to create vibrant, street frontage for a minimum of one mixed use shopping and employment districts third of the greenway length along all accented by a high quality open space branches of the Indian Run within the network that balances a variety of stunning Indian Run district. natural greenways and hadscape areas C. Required greenways shall connect to designed to provide intimate gathering spaces existing or planned greenways within the appropriate for an urban setting. vicinity, providing pedestrian and bicycle 2. Greenways shall be provided to connect the access to Historic Dublin, the Scioto BSD Indian Run Neighborhood District with River, other destinations throughout the the BSD Historic Transition Neighborhood Bridge Street District, and to the city's District to the east, creating pedestrian and larger open space system. bicycle connections and natural corridors D. Where buildings front directly onto from this mixed use activity center to the greenways, semi - pervious outdoor dining Scioto River and throughout the Bridge Street areas are permitted within 20 feet of District. the principal structure adjacent to the (b) Required Open Space greenway. Open space shall be provided in accordance with E. Other required open space corridors the requirements of §153.064(C). All open spaces may be created by using approved street fulfilling this requirement shall meet the intent types, provided that open space nodes are 72 § 153.063 (E) EFFECTIVE DATE NEIGHBORHOOD STANDARDS - JANUARY 7, 2015 BSD INDIAN RUN NEIGHBORHOOD located along the street with no greater than three full blocks between each open space node and pedestrian and bicycle movement between the open spaces is emphasized in the street design. F. Open space nodes shall be provided at prominent street intersections, such as those serving as entrances to a designated shopping corridor and other gateway locations, with other appropriately scaled open space types integrated along the corridor as appropriate to the character of the street. G. Where a conference center use is provided, an adjacent plaza or square shall be required to serve as an open space node. (F) BSD SCIOTO RIVER NEIGHBORHOOD DISTRICT (1) Development Intent The BSD Scioto River Neighborhood District provides a significant opportunity for a well - planned and designed neighborhood with a balanced mix of land uses. Predominant land uses include a residential presence to complement and support a strong mix of uses, with office employment and supporting service and commercial uses. Acomfortable, walkable street network is intended to convey a strong sense of connection between each of these diverse but complementary land uses. (2) Refer to §153.058 for the BSD Scioto River Neighborhood District intent, and refer to the revised Zoning Map for the actual limits of the BSD Scioto River Neighborhood District. Refer to Figure 153.063 - D for an illustration of a conceptual development pattern desired for this district (3) Block, Access, and Street Layout (a) Refer to §153.060 for Lots and Blocks; refer to §153.061 for Street Types; refer to §153.062(0) for access permitted for specific building types. (b) Block Length 1. Refer to Table 153.060 -A, Maximum Block Dimensions, for block length requirements. 2. Blocks with frontage on Riverside Drive/ State Route 161 facing the roundabout (conceptually shown on Figure 153.063 -D) may exceed the maximum block length, but shall be required to provide mid - block pedestrianways in accordance with § I 53.060(C)(6). 3. For the purposes of measuring block length, the limits of private street sections designed and constructed to public street standards and defined on the Development Plan shall be used in lieu of right -of -way. (c) Access Refer to § §153.060 and 153.061 for existing and potential principal frontage streets within the BSD Scioto River Neighborhood District and acceptable block access configurations. (d) Street Types Refer to §153.061 for existing and planned streets and street family designations within the BSD Scioto River Neighborhood District (4) Building Types & Uses. Refer to §153.062. (a) Permitted Building Types Refer to § 153.062(B)(3)(a) for permitted building types in the BSD Scioto River Neighborhood District. (b) Vehicular Canopies In addition to the requirements of §153.062(L), canopies shall be located per Figure 153.062 - J, and are permitted on the side of a building located on a comer lot, provided the vehicular use area is screened from any principal frontage streets and shopping corridors in accordance with § 153.059(C)(4)(c). (c) Ground Story Use & Occupancy Requirements. Residential, Office and all related support spaces including lobbies, common areas, mechanical and service uses are permitted on the ground floor. Mechanical rooms, service uses, and other related areas shall not front a shopping corridor. (5) Placemaking Elements (a) Shopping Corridor 1. The intent for designated shopping corridors in the BSD neighborhood districts is to provide continuous mixed -use street frontages with retail uses and eating and drinking facilities occupying the ground floor of buildings located on streets that have a well- defined and detailed pedestrian realm. Buildings with frontage on designated shopping corridors should be sited to accommodate a mix of outdoor activities, such as patios, seating areas, pocket plazas and spacious walkways. 2. At least one continuous shopping corridor is required and shall be located on and perpendicular to a principal frontage street in the approximate location shown on Figure 153.063 -D. 3. The minimum required length of the required shopping corridor shall be measured as the aggregate length of the block faces along both sides of the principal frontage street, except where portions of the shopping corridor have frontage along Riverside Drive. The required length shall be based on the total area of the BRIDGE STREET DISTRICT § 153.063 (F) 73 DEVELOPMENT CODE NEIGHBORHOOD STANDARDS - BSD SCIOTO RIVER NEIGHBORHOOD development site as noted in Table 153.063 - D. 63 -D SHOPPING CORRIDOR LENGTH - BSD SCIOTO RIVER NEIGHBORHOOD DISTRICT Development Area Required Shopping Corridor Length Less than 5 acres No minimum 5 to 20 acres 600 linear feet minimum Over 20 acres 1,200 linear feet minimum Shopping Potential l4 Corridor Shopping � Corridor Open Space Corridor Conceptual Open Space Street Network #m4 Node Potential �� Riverside Dr./ Gateway �I S.R. 161 Locations Frontage Note: Graphic figures are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. The Development Standards illustration is intended to be representative of a general development pattern. It is not intended to show the precise locations for approved street types, use areas, open spaces or other required elements of this Code. Actual locations and standards will be provided with the approval of the Development Plan and Site Plan as required in §153.066 for individual neighborhood areas. 4. Any block exceeding 300 feet within a shopping corridor shall provide a mid -block pedestrianway meeting the requirements of §153.060(C)(6). 5. The required shopping corridor is permitted to turn the corner of a block provided the minimum required length of the shopping corridor is located along the principal frontage street. (b) John Shields Parkway Frontage If buildings are fronted directly along the John Shields Parkway greenway, ground floor fagades shall be treated the same as front fagades on principal frontage streets. (c) Pedestrian - Oriented Streetscape A minimum of 12 feet of clear sidewalk width shall be provided along designated shopping corridors through the combination of public right - of -way and required building zone area with public access easements. Outdoor dining and seating areas shall not be permitted within this clear area. (d) Street Terminations Refer to § 153.062(7) for Treatments at Terminal Vistas. (e) Gateways 1. Gateways are points of identification that provide a sense of arrival to the area. Gateway designs shall be pedestrian- oriented in scale and shall include a combination of architectural elements, landscape features, and /or public open spaces. Gateway elements should enhance the character of the public reahn consistent with the Principles of Walkable Urbanism of §153.057(D) and should be coordinated with the design of the nearby streetscape, open spaces and architecture as may be applicable. 2. Gateways shall be provided in the approximate locations shown in Figure 153.063 -D. Gateway designs shall be approved with the Site Plan Review, but locations shall be identified with the 74 § 153.063 (F) EFFECTIVE DATE NEIGHBORHOOD STANDARDS - JANUARY 7, 2015 BSD SCIOTO RIVER NEIGHBORHOOD FIGURE 153.063 -D. ILLUSTRATION OF SCIOTO RIVER DEVELOPMENT STANDARDS Development Plan Review and shall be coordinated with the street network. (f) Sign Plans 1. The BSD Scioto River Neighborhood District is intended to accommodate a wide variety of building types and uses to create vibrant, mixed use shopping and entertainment districts. The sign and graphic standards shall contribute to the vibrancy of the district and the creation of a high quality environment with effective graphics intended for navigation, information, and identification primarily for pedestrians and secondarily for vehicles. 2. A master sign plan shall be submitted for buildings within designated shopping corridors and as required by §153.065(H) and §153.066(L)(8). The approvedmaster sign plan may include alternative sign types, number, size, heights, locations, colors. (6) Open Spaces. Refer to §153.064. (a) Open Space Character 1. The BSD Scioto River Neighborhood District is intended to accommodate a wide variety of building types and uses to create vibrant, mixed use shopping and employment districts accented by a high quality open space network that balances a variety of stunning natural greenways and hardscape areas designed to provide intimate gathering spaces appropriate for an urban setting. 2. A pedestrian bridge will connect the BSD Scioto River Neighborhood District with the Historic District and BSD Historic Transition Neighborhood, establishing an iconic focal point and a key pedestrian and bicycle connection linking the two sides of the Scioto River. 3. A greenway connecting the BSD Scioto River Neighborhood District with the BSC Sawmill Center Neighborhood District to the east is intended to create pedestrian and bicycle connections and natural corridors from this mixed use activity center to the Sawmill Center and throughout the Bridge Street District. (b) Required Open Space Open space shall be provided in accordance with the requirements of §153.064((). All open spaces fulfilling this requirement shall meet the intent and design requirements of an open space type permitted in the BSD Scioto River Neighborhood District as described in §153.064(G). Required open spaces shall be publicly accessible and accommodate community activity and gathering spaces. (c) Permitted Open Space Types All open space types are permitted. (d) Open Space Network 1. Open spaces within the BSD Scioto River Neighborhood District shall be organized as a series of interconnected nodes and corridors appropriate to the scale and character of surrounding streets, buildings and land uses. The purpose of this requirement is to create highly accessible public gathering spaces and activity areas along a continuous open space network weaving through and around the edges of this urban neighborhood. 2. The open space network shall be provided, at a minimum, in the approximate locations shown in Figure 153.063 -D. Open space locations shall be approved with the Site Plan Review, but locations and types shall be identified with the Development Plan Review and shall meet the following criteria: A. Open space corridors and nodes shall be coordinated with the street network, and with gateways where applicable. B. A greenway is required along John Shields Parkway and shall be designed to facilitate pedestrian and bicycle travel. C. Open space nodes shall be provided at prominent street intersections, such as those serving as entrances to a designated shopping corridor, the open spaces associated with the pedestrian bridge landing, and other gateway locations, with other appropriately scaled open space types integrated along the corridor as appropriate to the character of the street D. Where a conference center use is present, an adjacent plaza or square shall be provided to serve as a required open space. BRIDGE STREET DISTRICT § 153.063 (F) 75 DEVELOPMENT CODE NEIGHBORHOOD STANDARDS - BSD SCIOTO RIVER NEIGHBORHOOD This page has been left blank intentionally. 76 § 153.064 EFFECTIVE DATE OPEN SPACE TYPES JANUARY 7, 2015 § 153.064 OPEN SPACE TYPES (A) INTENT AND PURPOSE The intent of the open space type requirements is to ensure a variety of functional, well - designed open spaces carefully distributed throughout the Bridge Street District, located and planned to enhance the quality of life for residents, businesses, and visitors. The purpose of these requirements is to ensure that individual open spaces complement adjacent land uses and contribute to the creation of a comprehensive, district -wide open space network. In addition, these regulations are intended to guide the design of each open space so that it properly responds to its unique location and the needs of the primary users. (B) APPLICABILITY All required open space shall conform to one of the open space types of §153.064. (C) PROVISION OF OPEN SPACE (1) Residential There shall be a minimum of 200 square feet of publicly accessible open space for each residential dwelling unit. Required open space shall be located within 660 feet of the main entrances of the residential units or the main entrance of a multiple - family building, as measured along a pedestrian walkway. (2) Commercial There shall be a minimum of one square foot of publicly accessible open space for every 50 square feet of commercial space or fraction thereof. Required open space shall be located within 660 feet of the main entrance to the commercial space as measured along a pedestrian walkway. (3) Mixed Use Open space requirements for mixed use developments shall be calculated based on the open space required for each use as noted in §I53.064(C)(1) -(2). (4) Civic No open space is required for civic uses in civic building types except as may be required by the landscape provisions of this chapter. Where civic uses are located in other permitted building types, there shall be a minimum of one square foot of publicly accessible open space for every 50 square feet of civic space or fraction thereof. Where required, open space shall be located within 660 feet of the main entrance to the building as measured along a pedestrian walkway. (5) Existing Open Spaces An existing open space may be used to meet the area requirements for open space for an individual development if approved by the required reviewing The payment of fees -in -lieu of open space shall be collected prior to the issuance of a building permit body. The applicant shall either add to the existing open space, create a new open space in accordance with §153.064, pay a fee in lieu of provision of open space as required by §153.064(E) where permitted by the Planning and Zoning Commission, or a combination thereof. (6) Variation of Open Space Types More than one open space type may be used in combination to meet the open space requirement. Where three or more individual open spaces are proposed to meet the requirement, at least two different types must be provided. (D) SUITABILITY OF OPEN SPACE (1) The ART or required reviewing body shall review all proposed open space types during the Minor Project, Site Plan and Development Plan application review processes to determine the suitability of the open space. In determining the suitability of areas to be set aside for new open space types or in considering the ability of existing open space types to meet the requirement, the ART or other reviewing body may consider all relevant factors and information, including but not limited to (a) The goals and objectives of the Community Plan (including the Bridge Street District Area Plan) and Parks and Recreation Master Plan; (b) Suitability of the open space for active or passive recreational use or preservation of natural features; (c) The need for specific types of open space and recreation in the Bridge Street District and particularly in the general vicinity of the proposed development taking into account the anticipated users of the open space and nearby land uses, (d) The proximity or potential connectivity to other open space types. (2) If the ART determines the open space proposed (or portions thereof) to be inconsistent with any of these considerations, a fee -in -lieu of the provision of open space, or a combination of fee and provision of open space may be used to meet the requirement if approved by the Planning and Zoning Commission in accordance with §153.064(E). (E) FEE -IN -LIEU OF OPEN SPACE (1) The following requirements shall be met where the required reviewing body has determined that a payment of a fee -in -lieu of open space is permitted. Refer to §153.066 for the procedures for open space fee in lieu determination. (2) Fee -In -Lieu Calculation BRIDGE STREET DISTRICT § 153.064 77 DEVELOPMENT CODE OPEN SPACE TYPES for each phase of development and shall be calculated using the following method: (a) Calculate the total acreage of required open space from §153.064(C)(1) -(4) as applicable; (b) Multiply the acreage of required open space by its estimated average value per acre. This value shall be established from time to time by resolution of City Council. (c) Multiply the value of the required open space as determined in §153.064(E)(2)(b) by the required open space to obtain the open space fee. (3) Use of Open Space Fee Unless otherwise specifically directed by City Council, all fees collected shall be deposited in a fund which shall be used only for land acquisition, development, maintenance and operation of publicly accessible open spaces in the Bridge Street District as outlined in §153.064. (4) Fee -In -Lieu of Determination Except as noted in § I 53.064(E)(5), the required reviewing body shall determine whether a request to pay a fee -in -lieu of open space dedication should be approved, upon a finding that all of the following considerations are met: (a) That the amount of open space required by the nature and development intensity of the use would yield a lesser benefit than paying the fee. (b) That open space is available in adjacent or nearby developments (within 660 feet of the principal entrance(s) to each building) that is equal to or in excess of the calculated area for all developments individually. (c) That physical conditions unique to the site make it impractical to provide the required open space. (d) That providing the required open space would hamper an efficient site layout, as determined by the required reviewing body. (e) That providing the required open space would conflict with the Principles of Walkable Urbanism as provided in §153.065(I). (5) If the open space requirement for any individual development proposal is less than the minimum required by Table 153 -064 -A for the smallest permitted open space type, the applicant may be permitted to pay the calculated fee -in -lieu of open space, subject to the approval of the Director of Parks and Open Space. (F) OPEN SPACE TYPES (1) Pocket Plaza Pocket plazas are intended to provide a formal open space of relatively small scale to serve as an impromptu gathering place for civic, social, and commercial purposes. The pocket plaza is designed as a well defined area of refuge separate from the public sidewalk These areas contain a greater amount of impervious coverage than other open space types. Seating areas are required and special features, such as fountains and public art installations, are encouraged. Refer to Table 153.064 -A for an illustration of a typical pocket plaza. (2) Pocket Park Pocket parks are intended to provide small scale, primarily landscaped active or passive recreation and gathering spaces for neighborhood residents within walking distance. The design and programming of pocket parks should respond to the needs of residents in the immediate vicinity. Refer to Table 153.064 -A for an illustration of a typical pocket park. (3) Green Greens are intended to provide informal, medium scale active or passive recreation for neighborhood residents within walking distance. Refer to Table 153.064 -A for an illustration of a typical green. (4) Square Squares are intended to provide formal open space of medium scale to serve as a gathering place for civic, . social, and commercial purposes. Squares are generally rectilinear and bordered on all sides by a vehicular right -of -way, which together with adjacent building fapades define the space. Squares contain both hardscape areas, such as paths, fountains, gazebos, public art, and street furniture, as well as landscaping. Refer to Table 153.064 -A for an illustration of a typical square. (5) Plaza Plazas are intended to provide formal open space of medium scale to serve as a gathering place for civic, social, and commercial purposes. Plazas are usually located in areas where land uses are more diverse and there is potential for a greater level of pedestrian activity. The plaza may contain a greater amount of impervious coverage than any other open space type. Special features, such as fountains and public art installations, are encouraged. Refer to Table 153.064 - A for an illustration of a typical plaza. (6) Park Parks are intended to provide informal active and passive larger -scale recreational amenities to city residents and visitors. Parks have natural plantings and can be created around existing natural features such as water bodies or tree stands. Parks can be used to define edges of neighborhoods and districts. Refer to Table 153.064 -A for an illustration of a typical park. O Greenway Greenways are intended to provide a combination of informal and well organized, primarily linear open spaces that serve to connect open space types and major destinations within and outside of the Bridge Street Corridor. Portions of greenways may follow and 78 § 153.064 EFFECTIVE DATE OPEN SPACE TYPES JANUARY 7, 2015 preserve a natural feature, such as a river or stream edge, ravine, or tree row, or man -made features, such as streets. Greenways can be used to define edges of neighborhoods and districts and may be directly adjacent to other open space types. Refer to Table 153.064 -A for an illustration of a typical greenway. (G) GENERAL REQUIREMENTS The following defines the general requirements for all open space types in the Bridge Street District as provided in Table 153.064 -A, Summary of Open Space Type Requirements. Land not meeting the requirements of §153.064(G) and Table 153.064 -A shall not be counted toward an open space requirement unless the required reviewing body finds that unique site conditions, a creative design, or other considerations unique to the site are present that justifies a deviation from the requirements. (1) Size Minimum and maximum size of open space is measured along the parcel lines of the property. (a) Minimum Dimension The minimum length and the minimum width of an open space is measured along the longest two straight lines intersecting at a right angle. Refer to Figure 153.064 -A, Examples of Measuring the Minimum Length and Width of Open Space Types. (b) Proportion Requirement With the exception of the greenway, open space types shall be sized at a ratio of not more than three to one (3:1), length to width. (2) Access All open space types shall provide public pedestrian access from a street right -of -way. (a) Minimum Percentage of Street Right -of -Way Frontage Required The minimum percentage of street right -of -way frontage required is measured as the minimum percentage of the open space perimeter, as measured along the outer parcel line or edge of the space, that shall be located directly adjacent to a street right -of -way, excluding alley frontage. This requirement provides access and visibility to the open space. (b) Continuity Pedestrian paths, sidewalks, cycletracks and multi -use paths shall connect to existing or planned bicycle or pedestrian paths or other open space types when the open space abuts an existing or planned path right -of -way, a parcel zoned in the BSD Public District, or other open space types. For greenways, pedestrian and/or bicycle access points may be required by the ART or the required reviewing body. Designated sports fields are ball fields or courts designed for one or more sports including, but not limited to, baseball fields, softball fields, soccer fields, basketball courts, football fields, and tennis courts. For the purposes of §153.064, small scale recreational courts and activity areas such as bocce, shuffleboard or game tables are not classified as designated sports fields. (b) Playgrounds For the purposes of §153.064, playgrounds are defined as areas with play structures and equipment typically for children, such as slides, swings, climbing structures, and skate parks. (c) Site Fumishings High quality, City- approved site furnishings including but not limited to benches, bicycle racks, and waste receptacles are permitted and encouraged in all open spaces. (d) Public Art The incorporation of public art is highly encouraged as an amenity in all open spaces. Public art includes, but is not limited to, works of two- or three- dimensions and may be freestanding, or incorporated into walls, pavement or other surfaces. (e) Structures 1. Design Ancillary structures in open spaces shall not be subject to the physical requirements of the building types, but shall be designed and Famished to be consistent with the district in which they are located and consistent with the building material requirements of §153.062(E). Structure consistency maybe achieved through frontage, massing, and (3) Districts Permitted (a) The districts permitted are the BSD zoning districts in which each open space type is permitted. Refer to §153.058 for the intent of all BSD zoning districts. (b) Frontage Orientation of Adjacent Buildings/ Parcels The frontage orientation of adjacent buildings/ parcels is the preferred orientation of the adjacent buildings' and/or parcels' frontages to the open space. Front, comer, side, and rear refers to the property line either adjacent to the open space or facing the open space across the street. (4) Improvements The following types of development and improvements may be permitted on an open space type. (a) Designated Sports Fields BRIDGE STREET DISTRICT § 153.064 79 DEVELOPMENT CODE OPEN SPACE TYPES character similar to adjacent development, as determined by the required reviewing body. 2. Fully- Enclosed Structures A. Maximum Area Where permitted, fully enclosed structures are limited to a maximum building coverage as a percentage of the open space area. In no case shall an individual fully enclosed structure exceed 500 square feet in area unless approved by the required reviewing body. B. Fully enclosed structures may include such accessory uses as maintenance sheds, refreshment stands, newsstands, and restrooms. Refer to §153.059, Uses, for additional information about permitted principal and accessory uses. B. Walls shall not exceed 36 inches as measured from the established grade. 2. Opacity Fence opacity shall not exceed 60 %. Walls maybe 100% opaque. 3. Type A. Chain -link fencing is not permitted, with the exception of designated sports fields, court fencing, and other similar types of recreational facilities approved by the required reviewing body. Vinyl fencing is prohibited. B. Walls may be constructed of masonry, consistent with the street wall design requirements of §153.065(E)(2). Semi - Enclosed Structures Open -air structures, such as gazebos, open air pavilions, picnic shelters, outdoor theaters, and similar structures, are permitted in all open spaces. (f) Maximum Impervious and Semi- Pervious Surface Permitted In Table 153.064 -A, the amounts of impervious and semi - pervious coverage are provided separately to allow an additional amount of semi - pervious surface, such as permeable paving, for paved surfaces including but not limited to parking facilities, driveways, sidewalks, paths, and structures. (g) Open Water 1. The maximum amount of area within an open space that may be covered by open water is provided in Table 153.064 -A for all open space types. This includes but is not limited to water features above grade, such as fountains, as well as ponds, lakes, and pools. FIGURE 153.064 -A. EXAMPLES OF MEASURING THE MINIMUM LENGTH AND WIDTH OF OPEN SPACE TYPES. 2. Open water within an open space shall be located at least 20 feet from a property line unless the required reviewing body determines that a lesser distance will ensure public safety. (h) Fencing and Walls Open spaces may incorporate fencing and walls provided that the following requirements are met. 1. Height A. Fencing shall not exceed 42 inches, unless otherwise approved by the required reviewing body for special circumstances such as proximity to highway right -of -way and/or use around swimming pools, ball fields, and ball courts. CG �l c l- Note: Graphic figures on this page and the following on Table 153.064 -A, Summary of Open Space Type Requirements, are intended to illustrate one result of one or more of the general requirements and do not represent all requirements or actual development. gp § 153.064 EFFECTIVE DATE OPEN SPACE TYPES JANUARY 7, 2015 4. Spacing of Openings An opening or gate permitting access to an open space type shall be provided at a minimum of every 200 feet of street frontage. (5) Ownership Open spaces may either be publicly or privately owned. If privately owned, required open space must be publicly accessible along a street right -of -way. (6) Parking Requirements Off - street parking is not required for open spaces but is encouraged for open space types three acres or larger. Refer to §153.065(B), Parking and Loading, for more information on parking requirements. (7) Stormwater Management Stormwater management practices, such as storage and retention facilities, may be integrated into open spaces. Refer to Chapter 53 for design requirements. (a) Stormwater Features Stormwater features in open spaces may be designed as formal or natural amenities with additional uses other than stormwater management alone, such as an amphitheater, sports field, or a pond or pool as part of the landscape design. Stormwater features shall not be fenced and shall not be designed or placed so as to impede public use of the land they occupy. (b) Qualified Professional Stormwater management features incorporated into open spaces shall be designed by a licensed design professional. BRIDGE STREET DISTRICT O i DEVELOPMENT CODE Ol T.A * *O$,464 -A. SUMMAItYOFO" $AAGFTY'p'F kE(Q(MnPIE/v IHT'- Size Minimum Qpan Space Type Perimeter Along Street/ Minimum Maximum Minimum (Acres) (Acres) Dimension (Feet) Building J 30% of C Pocket Plaza 300 sg. ft. 1200 so. ft. 10 perimeter along street / building ' -I Ill 1 Pocket Park .lo .50 None 30% L Green .] 3 45 ove r150a for over ;5 acres __ I F EU�l I � ❑ Square .25 ,. 80 100% � �� rr Plaza .25 1 60 300% of perimeter alobuildingt/ 17 Park 2 Non,= 100 30% up to 5 acres, over 5 acre acres L Greenways-° 1 None 30; average of 60 50% Table Notes (Continued on following page) ' Small sale recreation murk; and activity arms suds as bocce, shuffleboard, or game tables are permited. Ponds and lakes are not permitted. 82 § 153.064 EFFECTIVE DATE OP N SPACE TYPES JANUARY 7, 2015 TABLE 153.064 -A. SUMMARY OF OPEN SPACE TYPE REQUIREMENTS (CONTINUED) Permitted Uses /Structures Frontage Impervious Designated Fully Districts Orientation + Semi- Maximum Open Water Permitted Building s/ Sports Playgrounds Enclosed Pervious ( /O) Parcels Fi elds Structures Surface ( %) All, except BSD Minimum: Residential, BSD Office Front or Corner No No No 40 %, Maximum: 80% 20 %z Residential + 10% All Any No' Yes No 30% + 10% 20 %'- All Front or Corner No Yes No 20% + 15% 30% All Front or Corner No No Maximum 5% of area 40% + 20% 20% Minimum: All, except BSD Front or Corner No No Maximum 5% 40 %' o Maximum: 80 /0 o z 30 /o Residential of area + 10% All, except If 3 acres BSD Historic Any Yes Yes or greater; 25% + 10% 20% Transition maximum 2/0 Neighborhood of area All Any No Yes No 20 + 10% 30% Coordination. Greenways shall be continuous and connected. Any private greenway developed shall be adjacent to or directly across a street from another existing Greenway, a proposed Greenway, a Park, or buffer areas adjacent to the Scioto River or either fork of the Indian Run. 4 Building Frontage. When the rear or side of a building is adjacent to a Greenway, that facade of the building shall be treated as if it were located on a principal frontage street. BRIDGE STREET DISTRICT § 153.064 83 DEVELOPMENT CODE OPEN SPACE TYPES § 153.065 SITE DEVELOPMENT determined by the Director. For a multi-tenant STANDARDS building, when a portion of the building or lot changes to a use requiring 25% or more (A) PURPOSE AND APPLICABILITY parking spaces, only that parking for the new (1) The purpose of the site development standards is to use shall be required. If applicable, a shared facilitate the implementation of the Bridge Street parking plan as described in §153.065(B)(2) District Area Plan and establish a walkable, mixed- may also be submitted to ensure adequate use urban core for the City of Dublin consistent parking while accommodating changes of use pa with the principles and directions articulated in the ngs. in multi-tenant buildings. Community Plan (Bridge Street District Area Plan). 4. Required parking and loading spaces shall It is intended that all site development encourage and be installed and completed prior to building support the principles of walkable urbanism provided occupancy. The Director of Building in §153.057(D). Standards may grant one, six month extension (2) As provided in §153.065, the site development following occupancy approval if adverse standards shall be applied to all new development in weather conditions or unusual delays beyond the Bridge Street District, including modifications to the control of the property owner prevent Existing Uses and Existing Structures. completion of parking and loading areas. Adequate parking areas and spaces shall (3) With the exception of provisions related to Existing be available, either on or off -site, during Uses in § 153.059(B)(5) and Existing Structures in the extension period under the following §153.062(B)(2), site development standards covered conditions: by this section that are nonconforming at the effective A. On -site parking areas, if not in a finished date of this amendment or made nonconforming by a condition, shall be adequately surfaced change to this chapter shall meet the requirements of to accommodate anticipated traffic, §153.004(C). stormwater drainage and snow removal, at the determination of the Director of (B) PARKING AND LOADING Building Standards; and/or The intent of §153.065(B) is to ensure the provision of B. Parking may be provided off -site, subject adequate vehicular and bicycle parking facilities in all to the requirements of §153.065(B)(1)(b). BSD zoning districts based on the vision for each area 5. The provisions of §153.207, Parking in described in the Dublin Community Plan (Bridge Street Residential Districts, shall apply in the BSD District Area Plan) and the District's five Vision Principles. Residential and BSD Historic Residential This is achieved through the emphasis placed on required districts. bicycle facilities, well - designed parking structures and the use of on- street parking spaces while minimizing off- 6. Parking and loading spaces for uses not street surface parking lots and encouraging shared parking addressed in §153.065(B) shall be determined arrangements. by the Director based on the anticipated parking impacts of the proposed use, its (1) General Provisions similarity to characteristics of other listed (a) Applicability uses, and supporting documentation that may 1. Vehicular and bicycle parking as required be provided by the applicant. by §153.065(B) shall be provided for the 7. Parking for Existing Structures is governed use of occupants, employees and patrons of by the provisions of § I53.062(B)(2)(c). each new building or addition constructed. (b) Parking Location Required parking shall be provided as permitted by this section, including, but not 1. On -Site Parking limited to, shared parking arrangements. A. Surface parking provided on -site may 2. Parking meeting the requirements of this only be located on those areas of section shall be provided for buildings that each development parcel that are not are expanded by more than 25% of the gross required by §153.062 to be occupied by floor area existing on the effective date of a a principal structure. Off- street parking rezoning to a BSD zoning district. may also be provided within a principal structure as permitted by §153.062(0). 3. Whenever the use of a building or lot is The parking areas shall be readily changed to a use requiring 25% or more accessible by vehicles, bicycles, and parking spaces than the required parking pedestrians. for the previous use, parking shall be brought into full compliance as required by B. Parking shall not be located within §153.065(B) within a reasonable time as a setback as required for individual 4 § 153.065 EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING building types in § 153.062(0), except of the parcel extended into the street right - that parking . areas may extend across of -way. On comer lots, on- street spaces on contiguous lots in developments both street frontages may be counted in the with coordinated site design, shared same manner. Credit for on- street parking access points and/or shared parking spaces shall apply to parking for all uses arrangements. on the parcel rather than any specific use. C. Where on -site surface parking is On- street parking spaces shall not be signed provided on a site included as part of a or otherwise designated for exclusive use by Development Plan Review, parking may any specific use, building or lot. be permitted by the required reviewing (c) Electric Car Charging Points body to encroach required setbacks to Parking lots and structures are strongly facilitate coordinated site design and encouraged to provide at least one electric plug -in contiguous parking areas with future service point for every 200 parking spaces. Plug - development phases. in points shall be associated with an individual 2. Off -Site Parking parking space and shall be installed according Required off - street parking shall be provided to appropriate design standards, as approved either on -site, or in a parking structure or by the Director. Plug -in points are exempt from surface parking lot located within 600 feet the service structure screening requirements of of the subject parcel as permitted by the §153.065(E). BSD zoning district in which the parking (d) Parking Lot/Structure Lighting lot or structure is located and shall be Parking lot and parking structure lighting shall readily accessible by vehicles, bicycles, and comply with the requirements of §153.065(F). pedestrians. (e) Parking Lot Landscaping A. The use of off -site parking to meet the minimum parking requirement shall Parking lot landscaping shall comply with the require an approved parking plan as requirements of §153.065(D). described in §153.065(B)(1)(f). If not (f) Parking Plan Required under single ownership, provisions A. Applications for Site Plan Review, for off -site parking shall be made by binding agreements between two or more B. Applications that include a request for property owners. Written easements off -site parking or in any case where a which provide for continued use and modified parking agreement necessitates maintenance of the parking shall be a new or modified parking plan as submitted to the City for approval. Any described in §153.065(B)(1)(b), agreement shall include provisions to C. Applications involving a use listed in address changes in use or ownership. Table 153.065 -A for which the parking B. If an off -site parking agreement is requirement is specifically noted as being severed or modified with the result of determined by an approved parking plan, eliminating required parking for one or D. Applications that include a request for an more properties, parking for the affected adjustment to required vehicle parking properties shall be brought into full as permitted in §153.065(B)(2)(b), or compliance as required by §153.065(B), where a change in conditions renders an and approval of a new or modified approved adjustment insufficient to meet parking plan shall be required, the parking needs of a use, building or C. If located off -site, distances to required lot, parking areas shall be measured along E. Applications that include a request a walkway from the nearest pedestrian for an adjustment to the number or entrance to the parking area to the main location of required loading spaces as entrance to the principal structure or use permitted in §153.065(B)(7), which may being served. be approved by the Director where a 3. On- Street Parking change in conditions renders an approved adjustment insufficient to meet the On- street parking spaces may be counted loading needs of a use, building or lot; toward meeting the minimum parking requirement for a parcel provided that the F. Applications fora Zoning spaces are on the same side of the street and Plan Approval for a change o u a ch ge e o f u se that more than one -half the length of the parking or more parking spaces space lies between the two side lot lines an the previous use; or than e than pr BRIDGE STREET DISTRICT § 153.065 (B) 85 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - PARKING & LOADING TABLE 153.065 -A: REQUIRED VEHICLE PARKING. USE MINIMUM REQUIRED MAXIMUM PERMITTED Principal Uses Residential Dwelling, Single - Family 2 per dwelling unit 2 per dwelling unit Dwelling, Two - Family Dwelling, Townhouse Dwelling, Live -Work 2 per dwelling unit 3 per dwelling unit Dwelling, Multiple - Family Studio /eff iciency and one bedroom: 1 per dwelling unit 2 per dwelling unit Two bedrooms: 1.5 per dwelling unit Three or more bedrooms: 2 per dwelling unit Age- restricted Housing: 2 per 3 dwelling units if 80 0 /6 of units are restricted for occupancy by those 65 or older Handicapped Housing: 1 per 2 dwelling units if 80 0 /6 of units are reserved for those meeting the definition of "handicap" under the federal Fair Housing Act Amendments Civic /Public /Institutional Cemetery Per approved parking plan Community Center Per approved parking plan Community Garden Per approved parking plan Day Care, Adult or Child Per approved parking plan demonstrating adequate site circulation, including pick -up and drop -off areas District Energy Plant Per approved parking plan Educational Facility 1 per 3 persons maximum occupancy of largest seating area or maximum building capacity, whichever is higher, as shown on the building permit 125% of minimum Elementary or Middle School Per approved parking plan demonstrating adequate site circulation, including pick -up and drop -off areas Government Services, Safety 2 per 1,000 sq. ft. 150% of minimum High School Per approved parking plan demonstrating adequate site circulation, including pick -up and drop -off areas Hospital Per approved parking plan Library, Museum, Gallery Library: 3.3 per 1,000 sq. ft. 125% of minimum Museum or Gallery: 1 per 1,000 sq. ft. Religious or Public Assembly 1 per 6 persons maximum capacity in the largest seating area, as shown on the building permit 200% of minimum Parks and Open Space Per approved parking plan Transportation, Park and Ride Per approved parking plan Transportation, Transit Station Per approved parking plan Commercial Animal Care, General Services, Veterinary Offices, and Veterinary Urgent Care and Animal Hospitals 2.5 per 1,000 sq. ft. 150% of minimum Bank 2.5 per 1,000 sq. ft. 125% of minimum Bed and Breakfast 1 per guest bedroom, plus 1 for operator 150% of minimum Conference Center 1 per 6 persons maximum capacity in the largest seating area, as shown on the building permit 125% of minimum Eating and Drinking 10 per 1,000 sq. ft. 125% of minimum Entertainment /Recreation, Indoor Theater: 1 per 4 persons maximum capacity in the largest seating area, as shown on the building permit 150% of minimum Sports courts: 2 per court Other uses: Per approved parking plan § 153.065 (B) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING TABLE 153.065 -A: REQUIRED VEHICLE PARKING. USE MINIMUM REQUIRED MAXIMUM PERMITTED Exercise and Fitness 2 per 1,000 sq. ft. 150% of minimum Fueling / Service Station 4 per 1,000 sq. ft., plus 1 per dispensing station 150% of minimum Hotel 2 per 3 guest rooms, plus 4 per 1,000 sq. ft. of accessory use area 125% of minimum Office, General Less than 50,000 sq. ft. 2.5 per 1,000 sq. ft. 125% of minimum 50,000- 150,000 sq. ft. 3 per 1,000 sq. ft. Greater than 150,000 sq. ft. 4 per 1,000 sq. ft. Office, Medical 2.5 per 1,000 sq. ft. 125% of minimum Parking, Structure N/A N/A Parking, Surface Lot N/A N/A Personal, Repair & Rental Services 2 per 1,000 sq. ft. 125% of minimum Research & Development 2 per 1,000 sq. ft. 125% of minimum Retail, General 3 per 1,000 sq. ft. 125% of minimum Sexually Oriented Business Establishments P approved parking plan Skilled Nursing, Rehabilitation, Home for the Aging, and Nursing Homes Per approved parking plan Shopping Center 5 per 1,000 sq. ft. 125% of minimum Vehicle Sales, Rental and Repair 2 per 1,000 sq. ft., plus 1 per 2,000 sq. ft. of outdoor I vehicle display area 150% of minimum Wireless Communications I N/A N/A Accessory and Temporary Uses Day Care, Adult or Child 2 per 1,000 sq. ft. 125% of minimum Dwelling Administration, Rental or Sales Office 2 spaces N/A Residential Model Home 1 space plus 1 per employee on largest shift N/A Swimming Pool Per approved parking plan G. Other circumstances determined by the Director to require a parking plan, which shall be reviewed with the Certificate of Zoning Plan Approval application. 2. Each parking plan for a parking area that contains 50 or more parking spaces shall demonstrate compliance with the pedestrian circulation standards of §153.065(I)(3)(b). 3. A parking plan shall include, at a minimum, the following, as applicable: (2) Required Vehicle Parking (a) Minimum Amount Required and Maximum Amount Permitted 1. Each use shall provide the minimum amount of parking required for that use listed on Table 153.065 -A, and shall be permitted to provide up to the maximum amount of parking on -site, as indicated for that use in Table 153.065 -A, except as maybe modified by the provisions of §I53.065(B). 2. When calculating minimum and maximum 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 153.065 -A, no additional parking is required for accessory or temporary uses when the square footage of the uses are included in the parking calculation for the gross floor area of the principal use. (b) Adjustments to Required Vehicle Parking The maximum on -site parking requirements may not exceed that permitted by Table 153.065 -A unless a parking plan meeting the criteria of §153.065(B)(2)(b)6, below is approved by the required reviewing body. T h e m inimum amount of parking required by Table 153.065 -A may be reduced by approval of a parking plan meeting the requirements of §153.065(B)(2)(b)1 -6. BRIDGE STREET DISTRICT § 153.065 (B) 87 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - PARKING & LOADING The cumulative reduction of minimum parking 3. requirements permitted by §153.065(B)(2)(b)1- 5 shall not exceed 30 % of required parking, regardless of the number of these adjustments applied. Additional reductions may be permitted by §153.065(B)(2)(b)6. 1. Shared Parking Calculations Where a mix of land uses creates staggered peak periods of parking, shared parking plans that have the effect of reducing the total amount of needed parking spaces may be approved. Parking spaces included in shared parking plans should be equally accessible and available to each of the affected users. The collective provision of off- street parking for two or more buildings or uses may be permitted subject to the following: A. Shared parking plans may include any lot or structure meeting the parking location requirements of § I 53.065(B)(1) (b). Adjacent lots included in the shared arrangement shall be connected for vehicular passage and shall provide safe and efficient pedestrian access to all uses served by the parking area(s). B. A request for a shared parking reduction shall be based on a shared parking analysis, including, but not limited to, the following factors: i. The number of originally required spaces for different uses or facilities sharing the same parking areas as noted in Table 153.065 -A, and ii. Documentation of required parking needed for different uses at different days and times. C. The adjusted required parking for shared parking areas shall be the largest number of spaces needed for all uses during the most intensive time period of use expected on a typical basis. 2. Auto -Share Parking Spaces The required minimum number of off - street parking spaces may be reduced by four spaces for each parking space reserved for auto - share parking not to exceed a 10 % reduction in the required minimum number of spaces provided in any one parking lot or structure. Auto -share parking spaces shall be designated on a parking plan and signed for the exclusive use of auto -share vehicles and evidence of written measures shall be provided to the City to ensure that the auto -share spaces are used only for that purpose. Transit Proxim ity The required minimum number of off - street parking spaces may be reduced by 10 % if more than 50% of the land in a proposed development is located within 1,320 feet of any public transit stop. If an existing transit stop is subsequently eliminated, any previously permitted parking reduction shall remain valid, provided that an active transit route remains within 1,320 feet of the development. 4. Shower Facilities The required minimum number of off - street parking spaces for a non - residential development may be reduced by 5% if a development contains shower and clothing locker facilities for bicycle commuting employees or patrons. The reduction shall apply only to that portion of the minimum parking requirement attributable to the tenant(s) or user(s) that have access to the shower and locker facilities. If the shower or locker facilities are later eliminated, the reduction of the minimum required parking shall no longer apply and parking shall be provided in accordance with §I53.065(B). 5. Transportation Demand Management As an alternative or supplement to the other adjustments in subsection §153.065(B)(2) (b), off - street parking requirements may be reduced by up to 30 %° through the use of a Transportation Demand Management (TDM) program approved by the Director and the City Engineer. A. Parking Demand Study Required Before a TDM program may be approved, the applicant shall submit • parking demand study prepared by • traffic engineer or other qualified transportation professional determined to be acceptable to the Director and the City Engineer. The study shall document that the use of alternative modes of transportation, including transit, bicycles, walking, and/or the special characteristics of the customer, client, employee, or resident population will reduce expected vehicular use and parking space demands for the use, as compared to the Institute of Transportation Engineers vehicle trip generation rates and the minimum parking requirements established in Table 153.065 -A. B. Transportation Demand Management (TDM) Activities The TDM program must include at least two of the following established and § 153.065 (B) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING maintained activities in order to qualify may require additional parking for a reduction in off - street parking facilities to be constructed or a fee requirements: from the owner of the parcel or i. Carpooling, vanpooling, primary structure to be used for the ridesharing, guaranteed ride home, construction of additional parking telecommuting, and/or shuttle facilities or improvements to offset service programs, the impact of the single- occupancy vehicles. ii. Staggered or alternative work scheduling, allowing employees 6. Demonstration of Parking Need to arrive and depart at different In addition to or in lieu of parking times so that peak parking demands adjustments as described in §153.065(B)(2) associated with mass shift changes (b)(1) -(5), the required reviewing body shall are minimized, be permitted to approve a parking plan for iii. Dissemination of information to fewer than the minimum required parking employees, residents, and visitors spaces or more than the maximum permitted to the site regarding the TDM plan parking spaces based on a demonstration of and alternatives to single- occupancy parking need by the applicant. The required vehicle travel to the site through an reviewing body shall consider: on -site office or project- specific web A. The land use and development character site; or of the area to be served by the parking iv. Use of alternative TDM activities facility, including the relative intensity that the Director and the City of uses requiring parking, availability of Engineer determine are likely, transit, proximity of nearby employment in combination with other TDM centers and residential uses, and other measures, to result in at least 30% relevant factors, reduction in single- occupancy B. The availability of other publicly vehicle travel to and from the site, available parking in the area, including as compared to the Institute of information such as number of spaces, Transportation Engineers vehicle trip any applicable restrictions (time limits, generation rates. dedicated parking areas, etc.), or other C. TDMAnnual Report uses also counting spaces in the same parking area for meeting parking i. The owner of the parcel or requirements; principal structure must provide an annual report to the Director C. The timing of parking use relative and City Engineer describing the to other uses in the area including implementation strategies for the information regarding hours of operation approved TDM plan as approved. or other operational parking needs that The report shall include a description would permit use of the spaces, of the TDM activities, a list of D. The parking requirement for similar current tenants and number of uses where applicable, as may be employees for each tenant, and a determined by the Director, as described parking- reduction analysis based in §153.065(B)(1)(a), on employee and/or resident use of E. Whether the location of all provided ridership programs or alternative parking meets the requirements of transportation options. §153.065(B)(1)(b); ii. If the report does not document F. Whether compliance with Table 153.065 - reasonable progress toward a A is made to the maximum extent 30% reduction in the Institute of practicable taking into account parking Transportation Engineers vehicle lot design and efficiency of the layout, trip generation rate of single - G. Whether other adjustments as occupancy vehicle travel to and from the site, then the report shall described in this section should apply identify what changes to the TDM in conjunction with or in lieu of the plan or activities are being made requested need -based adjustment, and to further reduce single- occupancy H. Whether supporting documentation, if vehicle travel to and from the site. provided, adequately demonstrates that The Director and the City Engineer BRIDGE STREET DISTRICT § 153.065 (B) gg DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - PARKING & LOADING § 153.065 (B) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING sufficient parking is available to meet to be locked to a structure, attached to the projected typical demand. pavement, building, or other permanent (c) Accessible Parking Spaces structure, with two points of contact to an individual bicycle frame. Racks, docks, and 1. Within the total number of off - street parking posts shall be designed to allow the bicycle spaces provided, a minimum number of frame and one or both wheels to be locked spaces shall be designated, installed, and with a U -lock when used as intended. managed for use by the physically disabled in compliance with the Ohio Building Code, 3. Bicycle parking racks, docks or posts current edition, Chapter on Accessibility and provided within the street right -of -way the Referenced Standards therein. shall be of a consistent design on all streets included within a Development Plan or Site 2. All handicapped park rig spaces shall be Plan Review site. Facility types, designs and designated by freestanding signs as provided locations within the street- right -of -way shall in the Ohio Manual of Uniform Traffic require approval by the City Engineer. Control Devices or as approved by the City Engineer. (d) Location (3) Required Bicycle Parking 1. Required bicycle parking shall be located within a reasonable walking distance of the (a) Applicability principal building entrances being served. Bicycle parking is required for any development Bicycle parking may be provided in and/ or use with six or more required vehicle parking or adjacent to open spaces where provided spaces. in accordance with §153.064. The location (b) Minimum Number of Bicycle Parking Spaces and design shall ensure that bicycle parking Required and facilities do not obstruct vehicle parking 1. Bicycle parking spaces shall be required as or pedestrian walkways as required by the follows: Ohio Building Code, the Americans with Disabilities Act, and other applicable state A. For residential uses, except attached and and federal laws, policies and guidelines. detached single - family, one space for Bicycle facilities and parking areas shall every two dwelling units. Up to 50% of meet the sight visibility requirements of this required spaces may be provided within Chapter. garages for multiple - family uses provided 2 Outdoor bicycle parking areas shall be the required reviewing body determines located in well -lit areas in accordance with that the garage size and dedicated bicycle §153.065(F). parking facilities are generally adequate to accommodate these spaces. 3. Apedestrian- accessible walk shall be B. For civic /public /institutional uses, one available between the outdoor bicycle parking space for every 20 required vehicle area and the principal building entrance. parking spaces. Public sidewalks may be used to meet this requirement. C. For commercial uses, one space for every 4. Bicycle lockers shall be located inside or to 10 required vehicle parking spaces. the side or rear of the principal structure, but 2. Provided that bicycle parking is not not within any required setback or required completely eliminated, required bicycle building zone. parking may be increased or reduced by 5. Covered Bicycle Parking Areas the required reviewing body when it is demonstrated that the level of bicycle activity A. Bicycle parking areas are encouraged to at that location warrants a different amount. be sheltered from natural elements by (c) Facility Type locating them inside or under principal or accessory structures, in bicycle lockers, 1. Designs of bicycle racks, docks, posts, and under roof extensions, overhangs, lockers are encouraged to be decorative, awnings, carports or enclosures, or other unique, and appropriate to the surrounding similar methods. area. Bicycle parking design should be B. If bicycle parking is covered, the cover incorporated whenever possible into building must be permanently attached to the design and coordinated with the design of ground or a structure and have at least street furniture when it is provided. seven feet of clearance above the surface 2. Bicycle parking racks, docks, or posts shall to which it is attached. be designed and installed to allow a bicycle § 153.065 (B) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING FIGURE 153.065 -A: OFF - STREET PARKING SPACE AND AISLE DIMENSIONS. Parallel 30° - 75' 76 ® ® Y Aisle Width 1 -Way AISLE =12' m AISLE= 12' Parking T T / / / , , Z / Space regular space regular space 13' 2\1 18 2 -Way AISLE= 18' Way 30' AISLE =22' AISLE 22' Width Length Parallel 12 ft. 18 ft. 9 ft. com pact space— compact space TABLE 153.065 -B: OFF - STREET PARKING SPACE AND AISLE DIMENSIONS. Aisle Width Regular Space Compact Parking Space Pattern 1 2 Way Way Width Length Width Length Parallel 12 ft. 18 ft. 9 ft. 23 ft. 8 ft. 20 ft. 30 -75 12 ft. 22 ft. 9 ft. 21 ft. 8 ft. 18 ft. 76 -90 N/A 22 ft. 1 9 ft. 18 ft. 8 ft. 16 ft. 'A maximum of 10% of parking spaces may be designed as compact parking spaces, and all spaces shall be clearly marked and reserved for that use. C. Covered bicycle parking areas shall be in accordance with building type requirements and are not permitted within any required setback or required building zone unless the shelter is part of the principal structure and at least five feet of clear area is available for pedestrian use. Public bicycle parking provided by the City and located within the street fight -of -way may be counted toward meeting the minimum bicycle parking requirement for a parcel provided that the spaces are on the same side of the street and located between the two side lot lines of the parcel. Credit for public bicycle parking spaces shall apply to parking for all uses on the parcel rather than any specific use. For parcels within the Architectural Review District boundaries, public bicycle parking provided by the City and located within the street fight -of -way may be counted toward meeting the mifumum bicycle parking requirement provided that the spaces are on the same block face as the subject parcel. 8. On comer lots, public bicycle parking spaces on both street frontages may be counted. 9. Public bicycle parking spaces shall not be designated for exclusive use by any specific use, building or lot. (e) Installation Bicycle parking shall be installed according to the dimensional requirements set forth by the manufacturer and the latest edition of the APBP Bicycle Parking Guidelines, or similar industry publication acceptable to the Director. (4) Off -Street Parking Space and Aisle Dimensions Parking spaces and maneuvering aisles shall comply with Table 153.065 -B. Refer to Figure 153.065 -A for a graphic depiction of these requirements. (5) Parking Structure Design Parking structures shall be designed in accordance with the minimum requirements of this section. Refer to the building type requirements for Parking Structures in §153.062(0) for additional information. (a) Entrance /ExitLanes 1. One entrance lane shall be required for each 300 spaces or part thereof. One exit lane shall be provided for each 200 spaces or part thereof. 2. Single entrance and exit lanes from the street shall be no wider than 16 feet. Double entrance and exit lanes shall be no wider than 24 feet at the street fight -of -way. Where more than two entrance or exit Imes are required, a separate entrance /exit shall be provided. 3. No entrance or exit lanes shall be permitted directly onto a principal frontage street except as may be pefmitted by the City Engineer in §153.061(D)(2). 4. On other street frontages, only one entrance and one exit lane shall be permitted for each 200 feet of frontage unless otherwise approved by the City Engineer. 5. To reduce the width of sidewalk intermptions and promote walkability, only single entrance Imes may be used unless access is provided from an alley /service street. (b) Stacking Spaces Two vehicle lengths of stacking space, each measuring at least 20 feet long, shall be provided between the street and the garage entry gate. The stacking area shall not be located across a sidewalk or in the public right -of -way. Additional stacking may be required by the City Engineer based upon traffic patterns and street types, or may be requested by the applicant pursuant to § 153.066(H) based on a circulation plan demonstrating need for the additional stacking spaces. DEVELO MENT CODE RICT SITE D &ELO M NTTSTANDARDS- 91 PARKING & LOADING (c) Interior Circulation 2. As an alternative, off- street parking areas The interior of the structure shall be designed in may be surfaced with permeable asphalt, accordance with the requirements of this section. permeable concrete or turf blocks, or 1. Maxim um aisle length shall not exceed 400 some combination of permeable and non - permeable surfaces, subject to review by feet without providing a cross - aisle. the City Engineer and the Fire Chief. The 2. Cross aisles shall be a minimum of 18 feet City Engineer may approve an adjustment and no greater than 24 feet in width. to the calculations for required stormwater 3. Aminimum ceiling clearance height of 12 management and retention measures to reflect feet is required where the parking structure greater stormwater volume control through has street frontage, excluding the driveway the use of permeable paving. opening, and the parking structure shall be 3. All parking and loading surfaces shall be designed and constructed to allow potential maintained in compliance with §I53.065(B) occupancy of the first 20 feet of building (8) at all times. depth by a commercial or a civic /public/ (c) Driveways institutional use permitted by §153.059(B). 4. Design of all other parking structures and 1. Adequate access a parking lot shall be provided by clearly defined driveways upper levels shall include a minimum ceiling designed so that vehicles entering or leaving clearance height of eight and one half feet. the parking lot will be traveling in a forward 5. Below -grade parking structure levels shall motion, unless the City Engineer confirms provide minimum clear heights as required by that an alternative design will protect traffic the Ohio Building Code and the Americans flow and traffic safety. with Disabilities Act. 2. No driveway shall be permitted directly (d) Pedestrian Safety onto a principal frontage street unless 1. Stairways on the parking structure's perimeter approved by the City Engineer as provided by shall be visible from outside of the structure. §153.061(D)(2). The maximum distance between parking 3. On other street frontages, driveways shall be spaces and the nearest exit stairwell shall be limited to one per lot or parcel, whichever 200 feet. requires the fewer number of access points, 2. At least one elevator shall be provided to unless vehicular access is provided from serve a parking structure. The maximum an alley or service drive or the need for an distance between any parking space and an additional driveway on a street is documented elevator shall be 350 feet. based on an access management study 3. Pedestrian flow shall be channeled through approved by the City Engineer. openings to permit surveillance, either by a 4. If it is determined that shared driveways will booth cashier or by cameras being monitored better protect traffic flow or traffic safety from a remote location. If 24 -hour coverage on surrounding streets, the City Engineer is unavailable, active techniques with security may require that access to two or more personnel who monitor television or sound adjacent surface parking or loading areas equipment may also be used. shall be provided through one or more shared (6) Surface Parking Lot and Loading Area Design and driveways. Construction 5. Driveway aprons connecting parking lots to (a) Grading public roadways may not be constructed with permeable materials. All off - street parking and loading areas including 6. Driveways shall be no wider than 22 feet at spaces, driveways, aisles and circulation drives the intersection with the adjacent street right - shall be graded and maintained so that water does of -way. Alternative driveway throat width not unreasonably accumulate on the surface areas may be requested by applicants and approved or flow or drain onto adjacent public or private pursuant to §153.066(H). (b) properties. Surfacing 7. Curb radii for driveways connecting parking lots to public roadways shall not exceed 1. All off - street parking and loading areas 20 feet. Alternative radii may be requested including spaces, driveways, aisles and by applicants and approved pursuant to circulation drives shall be hard - surfaced with §153.066(14). asphalt, concrete or a combination of those g Any driveways not provided for or regulated materials approved by the City Engineer. by these provisions shall be governed by § 153.065 (B) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING §153.210. Where conflicting regulations exist between §153.210 and this section, this section shall prevail. (d) Curbs and Wheel Stops 1. Raised or rolled concrete curbs or wheel stops at least five inches high shall be installed where necessary 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. 2. 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.. 3. 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. (e) Striping Parking areas shall be striped and maintained in good condition to be clearly visible with lines to indicate parking space limits. All striping shall comply with the Ohio Nlanual of Uniform Traffic Control Devices unless an alternative is approved by the City Engineer. (f) Pedestrian Circulation Refer to the walkability standards of §I53.065(I) (3)(b) for requirements for pedestrian circulation plans. (7) Required Loading Spaces (a) Applicability The provisions of §153.065(B)(7) apply to all uses: 1. That are located in any BSD zoning district with the exception of BSD Residential and BSD Historic Residential districts, 2. That are contained within a principal structure with more than 25,000 square feet of gross floor area; and 3. Where the regular or periodic receipt or distribution of materials or merchandise by vehicles with a gross weight over 25,000 pounds is required or expected on a typical basis. (b) Location 1. Off - street loading spaces may only be located on areas of a lot that are not required to be occupied by a principal or accessory structure pursuant to §153.062(0). 2. Off - street loading areas may not be located on any parking spaces or parking aisles designated to meet the minimum parking requirements of this section, unless approved in a required parking plan demonstrating that the location and timing of loading activities will not conflict with typical parking use on the site or with vehicular or pedestrian circulation. 3. An alley or service street may be used instead of a separate off - street loading space, subject to approval as part of a required parking plan demonstrating that the loading and delivery activities will be coordinated with other users of the alley to minimize access and circulation conflicts. 4. On- street parking spaces may be counted toward meeting the minimum loading space requirement for a parcel provided that the spaces meet the same requirements for parking location as described in §153.065(B) (1)(b)(3), and subject to approval as part of a required parking plan demonstrating that the on- street spaces are of adequate size, number and availability to serve the intended delivery vehicle(s) without creating conflicts with surrounding vehicular, bicycle or pedestrian traffic and circulation. 5. Fire access zones, as described in §153.061(G), may not be used to meet loading space requirements. 6. No loading dock, or any loading area used for the storage or staging of materials being transported to or from the site associated with commercial uses, shall be located closer than 50 feet to any lot in a residential district unless entirely contained within a completely enclosed building, or screened as required by §153.065(E)(3)(e), nor shall any loading dock or loading area directly face a residential district. (c) Number Required 1. The number of off- street loading spaces required is based on the size of the principal structure and is listed in Table 153.065 -E. 2. The required number of loading spaces may be increased or reduced by the required reviewing body when it is demonstrated that BRIDGE STREET DISTRICT § 153.065 (B) 93 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - PARKING & LOADING the frequency and type of loading activities at that location warrant a different number. 3. For principal structures of 25,000 square feet or less in gross floor area, loading and delivery activities may be conducted using an alley or service street, on- street parking spaces, or other on -site parking area as described in §153.065(B)(7)(b), unless the required reviewing body determines that a dedicated off - street loading space is necessary based on the frequency and type of loading activities anticipated for the use. TABLE 153.065 -C: MINIMUM LOADING SPACES REQUIRED PER PRINCIPAL STRUCTURE 25,001 - 50,000 sq. ft. gross floor area 1 space 50,001- 100,000 sq. ft. gross floor area 2 spaces 100,001 sq. ft. gross floor area or higher 3 spaces (d) Design 1. All off - street loading spaces shall be at least 12 feet wide and 30 feet long with a height clearance of 14 feet, unless the required reviewing body determines that the typical delivery vehicle(s) designated in an approved parking plan can be adequately accommodated by reduced loading space dimensions. 2. Refer to §153.065(E)(3)(e) for off - street loading area screening requirements. 3. Truck loading and unloading docks and maneuvering areas shall be designed so that truck movements do not interfere with traffic on public streets or off - street parking when vehicles are parked for loading and unloading. Loading areas requiring vehicles to back in from the street are prohibited on principal frontage streets, unless otherwise permitted by the City Engineer. Vehicles loading or unloading may not extend over any sidewalk or into any public right -of -way between the hours of 6:00 am and midnight, unless located entirely within a designated on- street parking lane or within the vehicular travel lane of an alley or service street as permitted in an approved parking plan. (8) Maintenance and Use (a) General Provisions 1. Unless an equal number of required spaces conforming to §153.065(B) are provided, parking and loading areas shall be maintained and not used for any other purpose while the principal structure or use remains in operation. Other parking arrangements for temporary community activities and special events may be permitted with approval from the City of Dublin Events Administration. 2. All parking lots shall be maintained free of potholes, litter, debris, glass, nails or other dangerous materials. 3. Surfacing, curbing, wheel stops, lighting fixtures, signs, and related appurtenances shall be maintained in good condition. The visibility of pavement markings delineating parking spaces and directional control shall be maintained. 4. Except on a temporary basis in the event of heavy rainfall or snowfall, all off - street parking and loading facilities shall be maintained free of accumulated snow or standing water which may prevent their full use and occupancy. 5. All permeable paving materials shall be maintained in an unbroken condition and shall be regularly swept and vacuumed to prevent blockages of sand, sediment, or other materials that would impair their permeability to water as originally designed. 6. Signs designating the use of individual private parking spaces for specific users, buildings or lots shall not be legible from a public right -of -way, except where such a sign is otherwise required by this Chapter. (b) Use Restrictions 1. It is unlawful for any person to park or store any vehicle in a parking lot or parking structure without the consent of the owner, holder, occupant, lessee, agent or trustee of the property. 2. All vehicles parked in a parking lot or parking structure shall be capable of being started and driven and have a valid registration and license within the most recent 12 -month period. 3. Arecreational and utility vehicle may be located outside of an enclosed structure for up to 72 hours in any 30 -day period, provided the owner or person in charge of the recreational and utility vehicle is the owner or a guest of a resident of that property. The vehicle shall be parked on a hard surface and shall not be used for overnight sleeping or living. 4. Off- street parking and loading areas may not be used for material storage, storage or display of vehicles and/or merchandise, or for vehicle or machinery repair or maintenance. If located within an off - street parking or loading area, refuse storage stations and dumpsters shall be located and designed in accordance with §153.065(E) and shall not § 153.065 (B) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 PARKING & LOADING interfere with driveway circulation or access benefits to be achieved through intensities to parking spaces and loading areas. of planting or other forms of screening as an 5. Except on parcels where the sale of vehicles alternative to wide planted areas. Quantitative is a permitted or approved conditional use of requirements for landscape materials are intended the property, no vehicle may be parked in any to provide minimum amounts based on the scale off - street parking or loading area for the sole and intensity of development. Unless otherwise purpose of displaying the vehicle for sale. specified, these requirements should not be 6. Unless no other parking area is reasonably interpreted as requiring regular, symmetrical available, no vehicle that, at the determination or standardized intervals of vegetation within of the Director, is intended for the display of landscape areas. Required landscaping should advertising to the public may be parked so be creatively and architecturally designed to add as to be visible to traffic on a public street or four seasons of visual interest and preserve natural parking area. integrity, and be appropriate to the character of the surrounding area. (2) General (C) STORMWATER MANAGEMENT (1) Intent (a) The provisions of § §153.132 through 153.148 shall apply in the BSD zoning districts unless The City's goal for stormwater management is to enact specifically modified or waived through the standards reflecting the most innovative, creative, . provisions of §153.065(D). Landscaping for environmentally effective and cost - effective practices existing sites shall be brought into compliance available. Through the standards and practices with the minimum requirements of this section in incorporated in the City's Stonmwater Management accordance with the provisions of §153.132(B). Design Manual, the City encourages the use of (b) Each application for development or stormwater treatment and engineering methods that redevelopment shall include a landscape plan allow for groundwater recharge and that manage showing compliance with the provisions of stormwater as close to its source as possible. The §153.065(D). The siting of buildings shall avoid use of Environmentally Sensitive Development the removal of desirable trees n good or fair (ESD) methods such as conservation design, smart condition where alternatives consistent with the growth, green infrastructure, integrated site design and provisions of §153.062 are available. sustainable development are practices and methods that can help achieve these goals. These practices are (c) Protected trees, as defined in this Chapter, encouraged to be used in Dublin where suited to site removed from any portion of a lot consistent with and development conditions, and particularly in the an approved Minor Project, Development Plan, or Bridge Street District, consistent with the standards Site Plan Review shall be replaced in accordance in the Stormwater Management Design Manual and with §153.146 except as provided by §153.065(D) the Principles of Walkable Urbanism provided in ( §153.057(D). (d) Existing trees which are incorporated into (2) All stormwater shall be managed as required by the landscape plan shall be protected during Chapter 53 of the Dublin City Code. construction as required by § 153.145. (e) Landscape plans shall exhibit diversity in tree (D) LANDSCAPING AND TREE PRESERVATION selection, as determ ined to be appropriate by the City Forester and the Director of Parks and Open (1) Purpose Space. (a) The intent of §153.065(D) is to improve the (f) In all areas where landscaping is required, appearance of the BSD zoning districts, reduce the surface area of any landscape bed shall be noise and air pollution, reduce heat island predominantly covered within four years after impacts, protect the character and value of installation by living materials, rather than bark, surrounding neighborhoods, and promote public mulch, gravel or other non - living materials. health and safety through appropriate urban - Areas included in rain gardens or other vegetated scale landscaping of street frontages and surface site features to meet stormwater management parking lots. This section is also intended to requirements are excluded from this requirement ensure buffering between significantly different with prior approval from the Director. land uses, and that trees are preserved and replaced in a manner appropriate to urban (g) Areas included in rain gardens or vegetated site environments. features created to meet stormwater management requirements may be counted towards any (b) Because the BSD zoning districts reflect a more landscaping required §153 ements. - (6) if urban, mixed -use character than other areas of the meet t e landscaped to meet the requirements. o city, these standards generally allow landscaping BRIDGE STREET DISTRICT § 153.065 (D) 95 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - LANDSCAPING & TREE PRESERVATION (h) All irrigation systems shall be designed, installed, and operated to minimize run -off and over -spray of irrigation water onto roadways, sidewalks, and adjacent properties, and shall be installed with rain sensors to turn the system off during rainy conditions. (i) Shrubs and plants that exceed two and one- half feet in mature height are prohibited in required sight visibility triangles for site access points as defined in Appendix C and are prohibited in required sight visibility triangles for street intersections as defined by the City Engineer. O If two or more conflicting landscape requirements apply to the same area, . the one requiring the most landscaping shall apply. (k) A registered landscape architect shall be used to prepare landscape plans required for applications for Site Plan Review. (3) Street Trees TABLE 153.065 -D: STREET TREE SPACING REQUIREMENTS Requirement Small Medium Large Tree Tree Tree Spacing range between trees 20 -25 ft. 30 -35 ft. 40 -45 ft. Minimum distance between trunk and face of curb (at 3 ft. 3 ft. 3 ft. planting) Minimum distance from 20 ft. 20 ft. 20 ft. intersection Minimum distance from fire 10 ft. 10 ft. 10 ft. hydrants and utility poles May be planted within 10 lateral Yes No No feet of overhead utilities When a property is developed or redeveloped in any BSD zoning district the applicant shall be required to plant and maintain trees in the street right -of -way pursuant to the following requirements. No existing street trees shall be required to adhere to the following requirements unless they are required to be removed and replaced consistent with an appropriate approved application as provided in §153.066. (a) A minimum of one tree is required per 40 linear feet of street frontage or fraction thereof. Refer to Table 153.065 -D, Street Tree Spacing Requirements, for spacing based on tree size and site characteristics. (b) Street trees shall be planted within streetscape planting zones in tree wells, tree lawns based or open planting beds based on the applicable street type design requirements. Refer to §153.061 for more information regarding street types. (c) Street trees shall be planted in topsoil approved by the Director of Parks and Open Space or the City Forester. Structural soil or an equivalent material approved by the City Forester shall be placed under paved areas adjacent to tree wells or planting beds, parallel to and behind the curb, and connecting planting beds or tree wells to one another beneath the paved surface within the streetseape planting zone. The City Forester may require additional structural soil to extend horizontally beyond the planting zone beneath sidewalks or other paved surfaces, as necessary to ensure the long term health of street trees, depending on the planting and paving conditions within individual street types. Structural soil shall not be used in planting beds. (d) The street tree openings shall be a minimum of five feet wide and five feet long and excavated to a minimum depth of three feet. The City Forester may require a deeper excavation based on specific tree species, site conditions, and/or conditions related to the adjacent street type. (e) Tree wells shall be covered with a tree grate, permeable pavers (block or stone) or by plant material, where appropriate for the street type and site conditions as approved by the City Forester. (f) Species and Size 1. Street trees shall be from the approved Urban Street Tree List for Dublin, Ohio or other species approved by the City Forester. 2. Street trees shall have a clear trunk of at least seven feet above the ground. The minimum trunk caliper measured at six inches above the ground for all street trees shall be no less than two and one -half inches. Existing trees in good or fair condition may be used to satisfy these requirements with prior approval of the City Forester. 3. Small tree species are permitted for use in planting zones where overhead utility lines exist. Small tree species may also be planted in medians, in addition to medium and/ or large tree species, where medians are provided. (g) Spacing and Location Street trees shall be spaced as set forth in Table 153.065 -F below unless modified by the City Forester based on unusual site conditions or obstructions. (h) Maintenance and Replacement by Property Owner The property owner shall be required to maintain the street trees for one year after the trees are planted and replace any tree which fails to survive or does not exhibit normal growth characteristics of health and vigor, as determined by the City Forester. The one -year period after the approval of the City Forester shall begin at each planting and shall recommence as trees are replaced. § 153.065 (D) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 LANDSCAPING & TREE PRESERVATION (i) Prohibited Activities 1. No person shall top any tree within the public right -of -way unless specifically authorized by the City Forester. Topping is defined as the severe cutting back of limbs to stubs larger than three inches in diameter within the tree's crown to such a degree so as to remove the normal canopy and disfigure the tree, as determined by the City Forester. 2. Unless specifically authorized by the City Forester, no person shall intentionally damage, cut, carve, transplant, or remove any tree or shrub; attach any rope, wire, nails, advertising posters, or other contrivance to any tree or shrub, allow any gaseous liquid, or solid substance which is harmful to trees or shrubs to come in contact with them, or set fire or permit fire to bum when fire or heat will injure any portion of any tree or shrub. 3. No person shall excavate any tunnels, trenches, or install a driveway or sidewalk within a radius of ten feet from the trunk of any public tree or shrub without first obtaining the prior written approval from the City Forester. 4. No person shall remove a tree or shrub from the City -owned tree lawn, streetscape planting zone or other public property without first obtaining the prior written approval of the City Forester. 5. No person shall by any type of construction reduce the size of a tree lawn or streetscape planting zone without prior written approval of the City Engineer. 6. Decorative lights, strings of lights, electrical cords or wires are not permitted to be attached to any tree for more than four consecutive months. 0) Municipal Rights public improvements, or is affected with any injurious fungi, insect or other pest. 3. The City Forester shall have the right to enter private property to access trees adjacent to public areas for the purposes of proper pruning, after reasonable prior written notice has been given to the property owner. 4. Wherever it is necessary to remove a tree(s) or shrub(s) from a public planting zone or other public property, the City shall endeavor to remove and replant or replace the trees or shrubs. No protected tree within the public right -of -way or on other public grounds shall be removed without prior review by the City Forester, and the trees shall only be removed if the City Forester determines there are no other means available to preserve the tree. 5. The City Forester shall have the right to cause the removal of any dead or diseased tree(s) located on private property within the city and/or cause the removal of branches of trees located on private property that overhang or impede access to public property, when those trees constitute a hazard to life and property, or harbor an epiphytotic disease which constitutes a potential threat to other trees within the city. The City Forester shall notify in writing the owners of the trees to be removed. Removal shall be done by the owners at their own expense within 60 days after the date of service of written notice, unless a longer period is agreed to in writing by the City Forester, to allow time to attempt to treat and cure a salvageable diseased tree. In the event of failure of owners to comply within 60 days, the City Forester shall notify in writing the owners of the trees of the City's authority to remove any tree(s) and charge the cost of removal to the owner as provided by law. 1. The City shall have the right to plant, prune, (4) Perimeter Landscape Buffering maintain and remove trees, plants and shrubs Perimeter landscape buffering is intended to provide within public rights -of -way and other public a buffer between land uses of significantly different grounds as may be necessary to ensure intensities. The buffering is intended to obscure public safety or to preserve or enhance the the higher - intensity land use from view and block environmental quality and beauty of public potential negative impacts related to noise, lighting grounds. This section shall not prohibit the levels, and activity through the use of denser landscape planting of street trees by adjacent property screening and/or a fence or wall visually softened owners providing that the prior written by clustered plantings, creatively and architecturally permission of the City Forester has been designed, as appropriate to the character of the granted. surrounding area, and approved by the required 2. The City Forester may cause or order to be reviewing body. removed any tree or part of a tree that is in (a) Perimeter landscape buffering is required: an unsafe condition or which by reasons 1. When development or redevelopment in of its nature is injurious to sewers, electric accordance with §153.062(B)(1) in any BSD power lines, gas lines, water lines, or other zoning district abuts property in a non -BSD zoning district, or BRIDGE STREET DISTRICT § 153.065 ( D g, DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - LANDSCAPING & TREE PRESERVATION 2. With the exception of the BSD Historic Core thereof, of a parking lot boundary facing district, when a non - residential land use is the public street shall be installed, with a adjacent to a parcel containing only single- mature height of at least three feet. Required family detached building types (regardless of landscaping shall be installed within five whether there is an intervening street, alley, feet of the edge of the parking lot and may or driveway). be creatively clustered and architecturally (b) These requirements apply when a site subject to designed, as appropriate to the character of these requirements is developed or redeveloped the surrounding area. in accordance with §153.062(B)(2). No existing 2. Where a surface parking lot/vehicular use development shall be required to install perimeter area is located within 20 feet of any street landscape buffering because of a change in the right -of -way, the property owner shall install nature, character, or zoning classification of an a street wall in accordance with §I53.065(E) adjacent parcel. (2) and at least five deciduous or evergreen (c) The required perimeter landscape buffer area may shrubs per 25 lineal feet, or fraction thereof, be located within a utility or other easement with of a parking lot boundary facing the public the prior approval of the City Engineer provided street. Trees are permitted to be installed all of the landscape requirements are met. but not required. Required landscaping may (d) Required buffer materials must be placed on the be creatively clustered and architecturally designed, as appropriate to the character of parcel where development or redevelopment is the surrounding area. occurring, unless both the parcel providing the buffering and the parcel being buffered are in 3. Where a surface parking lot /vehicular use common ownership, in which case the buffer area is located within 20 feet of a principal may be provided on either or portions of both frontage street, the property owner shall properties. install a masonry or wrought iron street (e) Vehicles or other objects shall not overhang or wall in accordance with § I 53.065(E)(2). In addition, least five deciduous evergreen otherwise intrude upon the required perimeter shrubs per r 25 lineal feet, or fraction thereof, landscape buffer. Refer to §153.065(B)(6)(d) for of a parking lot boundary facing the public curb and wheel stop requirements. street shall be installed. Trees are permitted (f) Existing landscape material in good or to be installed but not required. Required fair condition may be used to satisfy these landscaping may be creatively clustered and requirements with the prior approval of the architecturally designed, as appropriate to the Director. character of the surrounding area. (5) Surface Parking and Circulation Area Landscaping 4. Unless otherwise approved by the required All surface parking lots containing ten or more parking reviewing body, where a surface parking lot/ spaces, vehicular circulation areas for fueling /service vehicular use area is located within 40 feet stations, drive in/drive throughs, and other vehicular of an alley or service street, the property use areas shall provide the landscaping required by owner shall install at least five deciduous or §153.065(D)(5). evergreen shrubs with a mature height of at (a) Street Frontage Screening least three feet, per 25 lineal feet or fraction thereof of the parking lot boundary. Required Surface parking lots and other vehicular use landscaping shall be installed within five areas located within 40 feet of apublic street feet of the edge of the parking lot and may shall either be landscaped, or a street wall shall be creatively clustered and architecturally be installed in accordance with §153.065(E)(2) designed, as appropriate to the character of along the parking lot boundary facing the street to the surrounding area. create a visual edge along the public right -of -way. 5. Where temporary conditions are anticipated, The required street frontage treatment shall be in such as developments planned in phases, accordance with the following: the required reviewing body may consider 1. Where a surface parking lot /vehicular use alternative street frontage screening area is located between 20 feet and 40 feet treatments consistent with an appropriate of any street right -of -way the property owner approved application as provided in shall install at least one deciduous tree per 40 §153.066. lineal feet, or fraction thereof, of a parking lot 6. Where the surface parking lot/vehicular use boundary facing the public street, in addition area's proximity to the public right-of-way to the street trees required by §I53.065(D) vanes such that different treatments s detailed (3). In addition, at least five deciduous or in §153.065(D)(5)(a)1 -3 are required, the evergreen shrubs per 25 lineal feet, . or fraction § 153.065 (D) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 LANDSCAPING & TREE PRESERVATION street frontage screening required for the majority of that side of the parking lot/ vehicular use area shall be required along the entire frontage of that same side of the parking lot/vehicular use area. (b) Perimeter Buffering Where a surface parking lot is located within 30 feet of a side, corner side, or rear lot line, and the adjacent property contains only single - family detached building types or is a non -BSD district (regardless of whether there is an intervening street, alley, or driveway), the property owner shall install perimeter buffering meeting the requirements of §153.065(D)(4). (c) Interior Landscaping 1. In addition to required street frontage and perimeter buffering described in §153.065(D) (5)(a) -(b) above, a minimum of 5% of the interior parking lot area, calculated as the total of the area in all parking spaces and drive aisles, shall be landscaped. 2. Interior landscape areas shall be landscaped with one or more of the following options: A. Option A: Landscape Peninsula or Island — The minimum width of a landscape peninsula or island shall be 10 feet with a minimum area of 150 square feet, with a maximum run of 12 parking spaces permitted without a tree island. One medium deciduous tree as defined by Appendix E or as otherwise approved by the City Forester shall be planted for every 12 parking spaces. Trees shall be planted in topsoil approved by the Director of Parks and Open Space or the City Forester. The Director of Parks and Open Space or the City Forester may require structural soil to be placed beneath paved areas surrounding the peninsula or island, as necessary to ensure the long term health of trees, depending on the planting and paving conditions. All islands and peninsulas shall be excavated to a depth of three feet. Structural soil shall not be used in planting beds. B. Option B: Interior Tree Lawn - The minimum width of an interior tree lawn shall be 10 feet with a minimum area of 300 square feet. One medium or large deciduous tree as defined by Appendix E, or as otherwise approved by the City Forester, shall be planted for every 12 parking spaces or every 30 linear feet, whichever provides more canopy cover. Trees may be grouped or spaced within the interior lawn area. All interior tree lawns shall be excavated to a depth of three feet and filled with amended clean soil or equivalent material as approved by the City Forester. C. Option C: Large Consolidated Island —The minimum dimensions of a large consolidated landscape island interior to the parking lot shall be a minimum of 36 feet wide with a minimum area of 1,300 square feet. One medium or large deciduous tree as defined by Appendix E, or as otherwise approved by the City Forester, shall be planted for every 12 parking spaces. Trees may be grouped or spaced within the large consolidated island. Existing trees which are to be preserved may be incorporated into the large consolidated island, as approved by the City Forester. Where existing trees are not being preserved within the large consolidated island, the area shall be excavated to a depth of three feet and filled with amended clean topsoil or equivalent material as approved by the City Forester. 3. All trees planted in interior landscaped areas shall have a three foot minimum dimension from the tree trunk to the back of curb or edge of pavement, as applicable. 4. When a landscape peninsula or island abuts the length of a parking space, a clear space for persons entering and exiting parked vehicles shall be provided by turf or pavers, mulch, and other similar non - vegetative material. 5. Each interior landscaped area must include at least one deciduous shade tree (from the approved Urban Street Tree List) to be counted toward the required landscape area. Trees shall have a clear trunk of at least seven feet above the ground, and the remaining area shall be landscaped with hardwood mulch, shrubs, perennials or ground cover. Interior tree lawns and large consolidated islands may also use turf. Shrubs or perennials shall not exceed two feet in mature height. 6. Required on -site drainage shall be incorporated into interior landscaped areas to the maximum extent practicable consistent with the standards in the City of Dublin Stormwater Management Design Manual. If a curb is located at the edge of a landscaped area, planted areas shall be installed at a lower grade than the parking lot pavement and curbing shall have openings or gaps allowing drainage from the pavement to enter and percolate through the landscaped BRIDGE STREET DISTRICT § 153.065 (D 99 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - LANDSCAPING & TREE PRESERVATION areas. Plantings in landscaped areas intended to be used for biofiltration shall be those appropriate for rain gardens. (6) Required Building Zone (RBZ) Treatment Refer to §153.065(t)(2)(a) for RBZ treatment requirements. (7) Foundation Planting Building foundation landscaping is required for all fagades of all principal structures as described below: (a) Building foundation landscaping is required along all sides of a building not otherwise occupied by building entrances, sidewalk, parking, or loading areas, or other similar areas. Building foundation landscaping is not required for portions of the front or corner side building fagades located within 10 feet of the front property line and where a streetscape or patio RBZ treatment is provided. (b) Where building foundation landscaping is required, at least one shrub shall be provided per each 10 linear feet of building fagade, or fraction thereof, within a landscape bed or raised planter extending a minimum of 42 inches beyond the foundation. Shrub spacing shall be at the industry minimum standard by species. Building foundation landscaping shall be continuous. Plantings should be designed and creatively clustered by species, and respond to the character of the adjacent architecture and surrounding area. (c) Where streetscape or patio RBZ treatment is provided, raised planting beds, raised planters, and flower boxes may be used. (d) Building foundation landscaping may be installed at building foundation grade level or in a raised planter. The planter shall not be higher than three feet above the building foundation grade level. Roof top gardens do not count towards meeting this requirement. (e) The surface area of any foundation planting landscape bed shall be predominantly covered by living materials, rather than bark, mulch, gravel or other non - living materials in accordance with §153.065(D)(2)(e). (8) Credit to Preserve Existing Trees (a) Credit Available Property owners who demonstrate they have preserved mature, non - diseased trees with a six - inch caliper as measured at diameter breast height (DBH) during development or redevelopment may obtain credits toward required landscaping. Trees intended to be preserved shall be indicated on the landscape plan and shall be protected during construction through use of tree protection fencing around the critical root radius. The total amount of tree credits shall not exceed 50% of the required tree landscaping requirement. (b) Amount of Credit Credit for preserved trees is shown in Table 153.065 -E. Any preserved trees for which credit is given and that are lost to damage or disease within five years after the credit is awarded, shall be replaced by the land owner with the number of trees for which the credit was granted. TABLE 153.065 -E: TREE PRESERVATION CREDITS. DBH of Preserved Tree (in inches) Numbers of Trees Credited Over 12 in. 3 8 in. to 11.9 in. 2 6 in. to 7.9 in. 1 (9) Tree Preservation (a) General Provisions 1. Applicability §153.065(D)(9) applies to protected trees on all public and private properties. 2. Tree Preservation Plan Required C. D. A. Due to unique and/or noteworthy characteristics including size, species, age, and historical significance, landmark trees and significant groups of mature, healthy trees are community amenities that should be preserved to the maximum extent feasible. B. Applicants shall submit a tree preservation plan for approval by the required reviewing body that demonstrates the site landscaping complies with the provisions of §153.065(D). At either the preliminary plat or initial application stage, the property owner shall submit a copy of the tree preservation plan to the appropriate public utilities in order to alert those public utilities to the proposed placement of the trees in relation to utility service lines. A tree survey prepared by a certified arborist shall be submitted with the tree preservation plan for all Development Plan, Site Plan and/or Minor Project Review applications for lots containing existing trees. The tree survey shall include the location, size, condition and species of all existing trees over four inches caliper as measured at DBH. The tree preservation plan submitted as part of the Development Plan, Site Plan and/or Minor Project Review application shall identify all landmark trees and/ § 153.065 (D) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 LANDSCAPING & TREE PRESERVATION or significant tree stands on the site, including critical root zones to establish the limits of tree preservation zones, as determined by the required reviewing body. E. The property owner shall replace inch for inch any protected trees that are removed or lost due to damage, regardless of their location on the lot, except as provided in §153.065(D)(9)(b). 3. Site Layout and Design Where practicable, site design and architectural layout activities shall preserve existing protected trees and avoid risk of protected tree loss through changes of grade and soil moisture, both on the subject parcel and on adjacent parcels. This includes, but is not limited to, the layout and design of buildings and any associated site improvements including auguring, jacking, or boring to install utilities (as opposed to open cutting). The critical root zones of protected trees on the subject parcel and adjacent parcels shall be reviewed and land disturbance within those zones avoided to the extent reasonable. 4. Tree Removal Permit The provisions of §153.143 shall apply, except as provided in § 153.065(D)(9)(b). A. Protected trees used as credit to meet a required tree landscape requirement which die shall be replaced by the land owner with the number of trees for which the credit was granted. Replacement trees may count towards the credit amount for the development. B. Replacement trees provided pursuant to §153.065(D)(9) shall count towards landscaping required under other portions of this section if they meet the size, type, and location standards for the landscaping required. (b) Exemptions The following activities are not subject to the tree replacement requirements for protected trees as described in §153.146 provided the proposed tree removal is included in the required application as described in §153.066. 1. Trees planted due to a requirement of a previously approved development plan or as a condition to a previously issued Certificate of Zoning Plan Approval prior to the date this provision takes effect, 2. Removal of trees that, at the determination of the City Forester, are undesirable with respect to structure, species, and/or condition, 3. Removal of trees on any portion of a site required to be occupied by a public street as approved by the City Engineer and the required reviewing body with a Development Plan Review application, 4. Removal of trees on any portion of a lot required to be occupied by a structure pursuant to the standards of §153.062 as approved by the required reviewing body with applications for Minor Project or Site Plan Review; 5. Removal of trees which are an obstruction to traffic signals or traffic signs, power lines, or other utilities; 6. Removal of trees necessary for rescue in an emergency or for cleanup after a natural disaster_ and 7. Removal of trees deemed hazardous by the City Forester or a certified arborist, and approved by the City Forester. (10) Maintenance and Replacement (a) Street Trees and Public Trees Each property owner shall comply with those standards for maintenance, replacement, protection and management of street trees and public trees in §153.065(D)(3). (b) Other Required. Landscaping on Private Property For landscaping other than public trees and street trees, each property owner shall: 1. Maintain all required landscaping in good condition, as determined by the City Forester, 2. Remove any landscaping or tree that dies or is required to be removed due to damage or disease within three months after the loss of that landscaping or tree, and 3. Replace the landscaping or tree within three months of its removal. (c) The City Forester may extend times for performance if weather or other conditions prevent performance within the times stated above. (11) Alternative Landscaping In lieu of compliance with the specific requirements of §153.065(D)(3) -(9) an owner may propose alternative approaches consistent with the intent of §153.065(D) (2) to accommodate unique site conditions, abutting or surrounding uses, or other conditions, as deemed appropriate by the required reviewing body. Requests for alternative landscaping shall be reviewed by the required reviewing body with the Minor Project or Site Plan Review application and approved only if the proposed alternative is equal to or better than the aesthetic, environmental, and buffering functions anticipated with the provisions of §153.065(D). BRIDGE STREET DISTRICT § 153.065 (E) 101 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - FENCING, WALLS, & SCREENING (E) FENCING, WALLS AND SCREENING (1) Fence and Wall Standards The provisions of this section are required for all fences, walls, and screening materials in the BSD zoning districts. Notwithstanding the provisions of this section, the provisions of §I53.064(G)(4)(h) shall be met with respect to fencing and walls for open spaces. (a) Prohibited Materials Chain link, vinyl and temporary plastic fences (such as snow fences) are prohibited except during construction as security for construction sites and materials. Fences that are electrically charged, constructed of barbed wire, and razor wire are prohibited. No fence, wall or retaining wall shall be constructed of materials not designed to be used for that purpose. High quality synthetic materials may be approved with the Minor Project or Site Plan Review by the required reviewing body with examples of successful, high quality installations. (b) Fence and Wall Height and Opacity 1. No fence or wall located between the principal structure on a lot and the front property line shall exceed four feet in height, or be more the 50% opaque unless otherwise required by §153.065(E)(2) or § §153.059 through 153.065. These provisions apply to all street frontages on multiple frontage lots. 2. No fence or wall located between the principal structure on a lot and the side or rear property line shall exceed six feet in height. 3. The height provisions of §153.065(E)(1)(b)1- 2 shall not apply to fences or walls required to comply with the screening standards of §153.065(D). 4. The provisions of §153.065(E)(1)(b)1 -2 shall apply to all portions of retaining walls that extend above grade level, as measured from the elevated side of the retaining wall. Where a fence is located on top of a retaining wall, the combined height of the retaining wall and fence shall not exceed the maximum height permitted for a fence, as measured from the elevated side of the retaining wall. (2) Street Wall Standards (a) Intent Street walls are intended to screen vehicular use areas or service areas and/or to define the pedestrian realm. (b) Street Wall Design and Location 1. Street walls are intended to be placed within the front and/or comer side RBZ where an RBZ exists. If an RBZ is occupied by a building, the street wall shall be installed along the same plane as the nearest building fagade. 2. Street walls shall be designed to coordinate with the architectural character of the building to which it is associated. Street walls shall be constructed of brick, stone, , wrought iron fencing combined with landscaping (wrought iron street wall type), or a hedgerow combined with landscaping and masonry posts (solid hedge and post type). The required reviewing body may require specific or alternative street wall designs, such as stacked stone walls, based on the design of the associated building and/or the development character of the lots surrounding the site. 3. Street walls in the BSD Historic Core shall be constructed as stacked stone walls, unless otherwise approved by the required reviewing body. 4. Street walls shall be a minimum of 22 inches where seating is intended, all other street walls shall be a minimum of 30 inches. No street wall shall exceed 36 inches in height. 5. Street walls are prohibited in required sight visibility triangles for site access points as defined in Appendix C and are prohibited in required sight visibility triangles for street intersections as determined by the City Engineer. (c) Street Wall Landscaping In all areas where landscaping is required, within four years after installation a minimum of 80% of the surface area of any landscape bed shall be covered by living materials, rather than bark, mulch, gravel, or other non - living materials. 1. 2. 3. § 153.065 (E) SITE DEVELOPMENT STANDARDS - FENCING, WALLS, & SCREENING Masonry Street Wall For masonry street walls, the property owner shall provide at least five shrubs per 25 feet of linear street frontage or fraction thereof on the street side of the masonry wall where the Landscape RBZ treatment is used. Required landscaping may be clustered for a more natural design. Wrought Iron Street Wall For a wrought iron street wall, the property owner shall provide at least five shrubs per 25 feet of linear street frontage or fraction thereof on the side of the fence interior to the lot. Solid Hedge and Post Street Wall For a solid hedge, the property owner shall install dense, closely spaced living plant material composed of trees, deciduous or evergreen shrubs, or a combination thereof, EFFECTIVE DATE JANUARY 7, 2015 with a masonry post every 25 feet of linear street frontage or fraction thereof. The ground on the street side of the hedge shall be landscaped with ground cover exclusive of grass. (d) Alternative Street Wall Design and Landscaping In lieu of compliance with the specific requirements of §153.065(E)(2)(b) -(c), an owner may propose alternative approaches consistent with the intent of §153.065(E)(2) to accommodate unique site conditions, abutting or surrounding uses, the architectural character of adjacent buildings or other conditions as deemed appropriate by the required reviewing body. Requests for alternative landscaping shall be reviewed by the required reviewing body with the Minor Project or Site Plan Review application and approved only if the proposed alternative is equal to or better than the intent of the provisions of §153.065(E)(2). (3) Screening (a) Prohibited Materials Chain link, vinyl, EIFS, and unfinished or non - decorative CMU are prohibited screening materials. No screen shall be constructed of materials not designed to be used for that purpose. High quality synthetic materials may be approved with the Minor Project or Site Plan Review by the required reviewing body with examples of successful, high quality installations. (b) Roof Mounted Mechanical Equipment All roof - mounted mechanical equipment (including but not limited to HVAC equipment, exhaust 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 and, to the extent practicable, from adjacent buildings of similar height in a BSD zoning district. Screening shall be provided by: A. A parapet wall or similar feature that is an integral part of the building's architectural design (refer to §153.062(D) for roof requirements for building types), or B. A screening structure located around the equipment that incorporates at least one of the primary materials and colors on a street- facing fapade of the principal structure; or C. A living wall or vertical garden which is covered by vegetation to provide a minimum of 50% year round opacity. 2. The parapet wall or screening structure shall be fully opaque year round and shall be at least as tall as the height of the mechanical equipment being screened. 3. The standards of §153.065(E)(3)(b) shall not apply if the only feasible location for screening would impede the functioning of solar, . wind or geothermal energy equipment or systems. (c) Ground Mounted Mechanical Equipment 1. 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 using one of the following options: A. Landscape material which provides a minimum of 50% year round opacity, or B. A living wall or vertical garden which is covered by vegetation to provide a minimum of 50 % year round opacity, or C. A decorative wall or fence that incorporates at least one of the primary materials and colors of the nearest wall of the principal structure and that provides 75% year round opacity. 2. The wall or screen shall be at least one foot taller than the height of the mechanical equipment being screened, up to a maximum of 12 feet. 3. The standards of §153.065(E)(3)(c) shall not apply if the only feasible location for screening would impede the functioning of solar, wind or geothermal energy equipment or systems. 4. Utility boxes shall be oriented with access doors facing away from the street right -of- way or adjacent property to the maximum extent practicable. (d) Outdoor Waste and Storage Containers and Enclosures I. All waste, refuse, and recycling containers and enclosures shall be incorporated within the footprint of a principal or accessory structure to the maximum extent practicable. If incorporation within the building footprint is not practicable, outdoor waste and storage containers and enclosures shall be fully screened from view on all sides by landscaping or by a decorative wall or fence finished and constructed to match the materials and design of the nearest wall of the principal structure and shall be fully opaque year round. 2. The wall or screen shall be at least one foot taller than the height of the waste or storage container or enclosure being screened, up to a maximum of 12 feet. BRIDGE STREET DISTRICT § 153.065 (E) 103 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - FENCING, WALLS, & SCREENING (e) Off -Skeet Loading Areas Off- street loading docks or loading areas used for the storage and staging of materials shall be screened from view on all sides facing a street right -of -way or adjacent property, as practicable, by a decorative wall or fence between six and 12 feet in height, as necessary to sufficiently screen the area, constructed and finished to match the materials and design of the nearest wall of the principal structure. This requirement does not apply to the side of a loading area facing an alley/ service street, the side by which vehicles enter and leave the loading area, maneuvering areas used for vehicles to approach the loading area, or alternative loading area locations permitted by §153.065(B)(7)(b). (f) Access Doors Screening structures may contain access doors to accommodate servicing of equipment and emptying or replacement of containers. The access doors shall be self - closing, and shall be constructed and finished to coordinate with the materials and design of the nearest wall of the principal structure. Access doors shall remain closed and all containers fully within the structure when not being used. Offset openings may be used in lieu of man doors provided the service structures remain fully screened from view. (g) Vegetative Screening If vegetative screening is used to meet the requirements of §153.065(E)(3), evergreen and deciduous species may be used provided the plant size and opacity meet the required height and opacity requirements within four years after planting. The minimum planting bed width shall be 42 inches. (h) Alternative Screening In lieu of compliance with the requirements of §153.065(E)(3), an alternative approach to accommodate unique site conditions or surrounding uses may be approved if the required reviewing body determines that the proposed alternative achieves the aesthetic, environmental, and screening results better than compliance with the standards of §153.065(E)(3). (F) EXTERIOR LIGHTING (1) Intent The standards of §153.065(F) are intended to allow adequate night time lighting to protect public safety while protecting residential uses from excessive night time light and glare, protecting motorists from glare along public rights -of -way, reducing consumption of electricity for lighting purposes, and prohibiting excessive light trespass beyond property lines. (2) Applicability The provisions of §153.149 shall apply to all development within the BSD zoning districts, in addition to the requirements of §153.065(F), except as noted in this section. (3) Exemptions The following types of lighting are exempt from the requirements of §153.065(F): (a) Lighting for single family detached and single family attached dwellings. (b) Pedestrian walkway ground lighting. (c) Lighting for designated sports fields. (d) Street lighting. (4) Fixture Power and Efficiency All light fixtures shall meet the standards in Table 153.065 -H for power and efficiency. TABLE 153.065 -F: FIXTURE POWER AND EFFICIEN r . BSD Indian Run, BSD Sawmill All other Requirement Center, BSD BSD Scioto River Districts Neighborhood Districts Maximum permitted 9.7 lumens/ initial lamp lumens 13.9 lumens /sq. ft. sq. ft. per sq. ft. Maximum lamp 60,000 lumens 44,000 allowance lumens Minimum lumens per watt or energy consumed (as documented by 80 lumens/ manufacturers 80 lumens /watt watt specifications or results of an independent testing laboratory) (5) 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 for glare and unnecessary diffusion on adjacent 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 adjacent property in a residential district. (6) Lighting Uniformity Lighting across a horizontal surface shall have an average range from one to three footcandles. § 153.065 (F) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 EXTERIOR LIGHTING O Light Trespass Light generated on site shall not add more than one footcandle to illumination levels at any point at grade level 10 feet beyond the property line. (8) Lighting Plans Lighting plans submitted as part of applicable Minor Project or Site Plan Reviews shall include existing lighting from streets and adjacent buildings developed under these standards, and proposed lighting generated from light poles and building lighting. (9) Light Poles The base of light poles in parking areas shall be either flush with grade or mounted on a concrete foundation projecting no more than 36 inches above grade. The base of light poles in non - parking areas shall be either flush with grade or mounted on a concrete foundation projecting no more than six inches above grade. (10) Wall Lighting (a) Decorative wall lighting may be used to provide uplighting, downlighting, or other types of lighting accents for buildings in all BSD zoning districts. Decorative lighting shall not exceed 900 lumens unless installed and shielded in accordance with §153.065(F)(5)(a). (b) Ground or pole - mounted floodlights are not permitted for fagade lighting. (11) Canopy Lighting (a) All canopy lighting shall use recessed luminaire fixtures and shall be designed and located so as to prevent glare onto adjacent properties. (b) Highly reflective material shall not be installed on the underside of the canopy. (12) Prohibited Lighting Types Sodium vapor light fixtures are prohibited in all BSD zoning districts. (G) UTILITY (1) In all BSD 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. (H) SIGNS (1) Intent and General Purpose (a) General The intent of §153.065(H) is to enhance the physical appearance of the BSD zoning districts and the City of Dublin as a whole by encouraging high quality, effective outdoor graphics for the purposes of navigation, information and identification; and to protect the health, safety, and general welfare of the community. More specifically, it is the intent of this section to 1. Provide sign standards that allow fair competition while ensuring that signs used by individual businesses will contribute to the urban vitality, interest, and uniqueness of the Bridge Street District. 2. Provide aesthetic standards that ensure adherence to the high level of design and construction quality expected by the community. 3. Provide the public with a safe and effective means of locating businesses, services and points of interest by multiple modes of transportation. 4. Provide standards for signs that are appropriately scaled to the pedestrian realm and designed to enliven the pedestrian experience. 5. Regulate signs in accordance with applicable federal and state law. (b) BSD Residential, Office Residential, Office, Commercial, and Public Districts The purpose of signs in these districts is to provide identification with high visual quality in a manner that respects the character and scale of residential areas while providing clear visibility for larger office, commercial and residential developments. Signs should provide high quality awareness through graphics that effectively assist in navigation, information and identification for both pedestrians and vehicles. (c) BSD Indian Run Neighborhood, Sawmill Center Neighborhood, Scioto River Neighborhood and Vertical Mixed Use Districts The purpose of signs in these districts is to accommodate a wide variety of building types and uses to create vibrant, mixed -use shopping and entertainment districts. Sign and graphic standards shall contribute to the vibrancy of the districts and the creation of high quality environments with effective graphics intended for navigation, information, and identification primarily for pedestrians and secondarily for vehicles. BRIDGE STREET DISTRICT § 153.065 (H) 105 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - SIGNS (d) BSD Historic Core and Historic Transition Neighborhood Districts The purpose of signs in these districts is to provide for pedestrian- oriented signs that match the general character and scale of Dublin's original village commercial center. Signs should provide business identification in a manner consistent with the historic appearance and character of the districts, while encouraging a more interesting streetscape. (2) General Provisions (a) All applicable requirements of § §153.150 through 153.163 shall apply to the BSD zoning districts except as modified by §153.065(H). In the event of a conflict with the provisions of §§ 153.150 through 153.163, the provisions of §153.065(H) shall govern. (b) Where noted for the purposes of permitted signs, street frontages shall apply only to public streets. (c) Nonconforming signs shall be subject to the provisions of §153.161(J). (d) Approval Authority 1. All permanent signs shall require a permanent sign permit unless otherwise exempted for a specific sign type. 2. Required reviewing bodies shall not address the content of the sign message. 3. Off- premise signs are only permitted with the approval of a master sign plan. 4. All signs located within or projecting over the public right -of -way shall be approved by the City Engineer prior to placement 5. Notwithstanding any other provision of this Code, the design and placement of City - sponsored banners for special events or public announcements affixed to public facilities in the right -of -way within the Bridge Street District shall be approved by the City Manager prior to placement (e) Master Sign Plans 1. The purpose of a master sign plan is to allow a greater degree of flexibility and creativity in sign design and display. Further, master sign plans are intended to be used for multiple signs for either a single building or a group of related buildings to ensure that the requested signs work in a coordinated fashion to meet the general intent of signs in the District It is not intended to simply permit larger or more visible signs or additional signs than may be permitted, without any consideration for unique sign design and display. Master sign plans shall maintain the purpose and intent of the sign and graphic standards for the applicable BSD zoning district Master sign plans may be submitted for the purposes described below. A. Any applicant may request approval for a master sign plan for signs that depart from the requirements of §153.065(H). The required reviewing body shall be permitted to approve alternative requirements for sign design, number, type, size, height, location, and lighting. B. Am aster sign plan maybesubmitted for a single building to ensure that sign locations and designs are properly coordinated with the building. Once the master sign plan is approved, no subsequent approvals are required provided the signs are consistent with the approved master sign plan. C. Amaster sign plan may be submitted for multiple buildings and sites. A master sign plan is required for shopping corridors. Once the master sign plan is approved, no subsequent approvals are required provided the signs are consistent with the approved master sign plan. 2. The Planning and Zoning Commission shall review all master sign plans, except for those in the BSD Historic Core District and areas of the BSD Public and Historic Transition Neighborhood Districts that fall within the Architectural Review District boundaries, as provided in §153.065(H)(2)(e)(6). 3. Applications for Basic Plan Review as required in §153.066(D) may include a description of the general design intent for proposed signs, demonstrating coordination with proposed building architecture and compatibility with the surrounding development context. Information provided at the Basic Plan Review should demonstrate that signs will meet all requirements of §153.065(H), or that the applicant intends to request master sign plan as provided in § 153.065(H)(2)(e). A master sign plan may be reviewed concurrently with a Basic Plan Review. 4. Am aster sign plan shall include, at a minimum: the proposed locations, types, number, heights and sizes of signs, indicated on scaled plans and/or building elevation drawings; proposed materials to be used for sign structures and sign faces, fabrication details; and proposed types of illumination. 5. Where applicable, all signs located within a development shall meet the requirements established in an approved master sign plan. Where an approved master sign plan does not contain specific sign elements (such as height, § 153.065 (H) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - SIGNS JANUARY 7, 2015 colors, placement, etc.), then the provisions of §153.065(H) shall apply. 6. The Architectural Review Board may approve master sign plans that depart from the requirements of §153.065(H), providedthe purpose and intent of the sign and graphic standards for the BSD Historic Core and Historic Transition Neighborhood districts and the historic character of Historic Dublin are maintained. The Board shall determine the appropriateness of signs and their placement given the architecture of buildings within these districts. (3) BSD Zoning Districts with Special Sign Provisions (a) BSD Historic Residential District The requirements of § §153.150 through 153.163 shall apply in the BSD Historic Residential District without modification. (b) BSC Indian Run Neighborhood, Sawmill Center Neighborhood, Scioto River Neighborhood and Vertical Mixed Use Districts 1. Signs in these districts shall be subject to the requirements of §153.065(H)(6) through (7) as applicable, unless amaster sign plan is approved by the Planning and Zoning Commission (refer to §1 53.065(11)(2)(b)6)). 2. Am aster sign plan is required for a planned shopping corridor regardless of whether the signs meet the requirements of the district in which they are located. The master sign plan may be submitted at any time, but no sign permits shall be issued until the master sign plan is approved. (c) BSD Historic Core and Historic Transition Neighborhood District 1. Signs in these districts shall be subject to the requirements of §153.065(H)(6) through ( ) as applicable, unless a master sign plan is approved by the Architectural Review Board (refer to § I 53.065(H)(2)(b)6). 2. All new ground and building - mounted signs in those parts of the BSD Historic Core and Historic Transition districts that fall within the Architectural Review District boundaries shall be subject to review and approval by the Architectural Review Board. (4) Sign Design and Lighting All signs shall be designed with the maximum of creativity and the highest quality of materials and fabrication. It is strongly recommended that all signs be designed by a professional sign designer and be installed by a qualified sign builder or contractor. (a) All signs shall be designed to fully integrate with the building architecture and overall site design, and to enhance the pedestrian experience in the Bridge Street District. Signs attached to principal structures shall be coordinated and fit appropriately with the architecture of the building in accordance with § I53.062(M). Signs placed on windows, awnings and canopies shall meet the requirements of §153.062(H). (b) The illumination of signs is strongly encouraged to help add a sense of liveliness and activity to the area. Unless otherwise noted, signs may be externally illuminated, provided that all exterior lighting meets the requirements of §153.065(F). Internally illuminated pan channel or cabinet signs are permitted, provided that the sign is creatively designed with high quality materials and fabrication, as determined by the required reviewing body. Awning signs and sandwich board signs may not be internally illuminated. Illuminated signs shall be constructed so that raceways, conduit and piping for electrical sources are not exposed to view. (c) The provisions of §153.158(C)(3) (limitations on sign shape), shall not apply in the BSD zoning districts. (d) Sign Colors and Secondary Images 1. Signs shall be limited to three colors, including black and white. The background color shall be considered one of the three permissible colors, unless channel letters are used, in which case the background is not considered one of the three colors. 2. Logos, registered corporate trademarks and/ or symbols, or other secondary images used to convey information about the business or use of the building or lot must be compatible with the size, design, and scale of the sign. Colorful logos and signs are encouraged to help add character and interest to the building and streetscape. 3. Logos, Registered Corporate Trademarks and/ or Symbols A. For signs incorporating a registered corporate trademark or symbol, colors used in the registered corporate trademark or symbol shall not be limited in number, but shall be considered as one of three permissible colors. Sign copy or background shall use one of the colors used in the registered corporate trademark or symbol. B. Signs with a registered corporate trademark or symbol that is less than 20% of the sign area shall be limited to three colors as provided in §§ 153.065 (H)(4)(d)l and 153.065(H)(4)(d)3A. The cumulative area of registered corporate trademarks or symbols and other BRIDGE STREET DISTRICT § 153.065 (H) 107 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - SIGNS secondary images shall not exceed 20% of the sign area. C, Where a registered corporate trademark or symbol exceeds 20% of the sign area, signs shall have a maximum of five colors including symbols, sign copy, and background color. The background color is included in the maximum permissible colors, unless channel letters are used and affixed directly to a building or other support structure, in which case the background is not considered one of the permissible colors. No additional secondary images are permitted. 4. Other Secondary Images Secondary images used on signs that do not include a registered corporate trademark or symbol shall not exceed 20% of the sign area. Signs are limited to a total of three colors as provided in §153.065 (11)(4)(d)l. 5. All signs shall adhere to the size limitations of §153.158(0)(2). (e) Sign Materials 1. All permitted sign types shall be designed with the highest quality of materials and fabrication. High quality, durable and low maintenance materials are required. The type of material should be compatible with the associated building's fagade and other materials in the surrounding area. Traditional materials, such as wood, are preferred over plastic signs. 2. Signs shall be fabricated, constructed and installed to conceal fasteners and/or other methods of attachment that not integral to the sign design. 3. Rusted and/or deteriorating materials shall be replaced. 4. The following primary materials are required for sign faces. Other materials may be used for sign construction provided they are only used in supplementary parts of the sign, such as framing materials or other similar uses. The required reviewing body may approve other materials if it determines that the materials provide appropriate high quality, durability, and design features. A. Metal faces :.125 -inch aluminum or 4mm composites for 3 foot and greater spans to avoid "oil canning" (rippling) of faces. Thinner material may be used for shorter spans. (or equivalent) to avoid fading, typically no less than. 125-inch. C. Metal returns: Etched (sanded) primed and painted aluminum. D. Paints, when used, shall be acrylic polyurethane paint systems with zinc chromate primers, or equivalent. E. Wood materials: HDU, cedar, redwood and treated lumber. Wooden signs shall be properly sealed to prevent moisture from soaking into the wood. F. Window sign materials shall be of pressure sensitive vinyl and similar. For exterior use "High Performance" materials that have higher tack values and avoid premature fading shall be used. Printed PSV /decals shall have an exterior laminate added to ensure exterior durability. (5) Sign Types Permitted in BSD Zoning Districts (a) All sign types permitted in the BSD zoning districts are listed in Table 153.065 -G. Refer to §153.065(H)(6) for number of signs permitted, and §153.065(H)(7) for requirements for specific sign types. (b) Different sign types may be used on the same frontage. (c) Where required, setbacks shall be measured from the public street right -of -way, lot line, or minimum Required Building Zone, as applicable. (6) Number of Permitted Signs Refer to §153.065(H)(6)(d) for the number of signs permitted in the BSD Historic Core and Historic Transition Neighborhood Districts and to §§ 153.150 through 153.163 for the BSD Historic Residential district. For all other BSD zoning districts, the number of permitted signs shall be in accordance with subsections §153.065(H)(6)(a) -(c). Refer to Table 153.065 -G, Sign Types Permitted in BSD zoning districts, for the list of permitted signs and the intent of each sign type. (a) Ground Signs In addition to any other signs permitted by §153.065(H)(6)(b) -(c), one ground sign is permitted per building or parcel for each street frontage, not to exceed a maximum of two ground signs. Refer to §153.065(H)(7)(a), Ground Signs, for specific requirements for size, location, and height. (b) Single Tenant Buildings and Multiple Tenant Buildings without Storefronts B. Moldable Synthetic Materials: Solar Refer to §153.065(H)(7)(b), Building- Mounted Grade (SG) acrylics and polycarbonates Signs, for specific requirements for sign types, sizes, locations, and heights. § 153.065 (H) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - SIGNS JANUARY 7, 2015 I . Multiple tenant buildings without storefronts 2. One additional building- mounted sign is and single tenant buildings are permitted a permitted for each tenant with a storefront with maximum of one building- mounted sign per a public entrance facing an off - street parking street frontage. area or parking structure in the same block, 2. A directory sign may be used at each public provided that the entrance is located on the side entrance to identify tenants in multiple tenant or rear fagade of the building. buildings without storefronts. For buildings 3. A directory sign may be used to identify tenant with fewer than three stories an additional spaces located above the ground floor. For projecting sign not exceeding eight square buildings with fewer than three stories, an feet may be located adjacent to a common additional projecting sign is permitted provided public entrance providing access to the upper it is located adjacent to a common public floor tenant spaces. entrance providing access to the upper floor (c) Multiple Tenant Buildings with Storefronts tenant spaces. Refer to §153.065(H)(7)(b), Building - Mounted 4. A single, one - square -foot window sign Signs, for specific requirements for building- indicating the name of the business and/or mounted sign types, sizes, locations, and heights. a logo, shall be permitted only on a public 1. Buildings with ground floor storefronts entrance to the tenant space and shall not require a permanent sign permit, provided not more than are permitted a maximum of two building- one low chroma color is used, such as black, mounted signs for each ground floor tenant white, or gray. with a storefront. The two permitted building - §153.065(H)(7)(c) Table 153.065 -3 mounted signs shall not be of the same sign type. EIMN , ZONING DIS Sign Type Code Section Reference Sign Intent Ground Sign Ground Sign §153.065(H)(7)(a); Ground signs are intended primarily for buildings with Table 153.065 -H greater front and corner side setbacks. Building- Mounted Signs Wall Sign Building- mounted signs are intended to provide Awning Sign §153.065(H)(7)(b); Table 153.065 -I visibility for pedestrians and vehicles approaching from different directions and to create a diversity of Projecting Sign signs along an active streetscape. Window Sign Building Identification Sign Building identification signs are intended to identify major building tenants and large -scale commercial Building Identification Sign development in the Bridge Street Corridor. Building names or street address numerals may be used in lieu of a tenant name. §153.065(H)(7)(c) Table 153.065 -3 Plaques, medallions, or other smaller identification signs intended for pedestrian use may be used to Identification Plaques identify individual building names or addresses, denote significant historical or other building characteristics, and other similar purposes. Other Permitted Signs Directory signs are intended to provide identification for upper story tenants and /or tenants that are Directory Sign otherwise not permitted an individual identification sign. Directory signs may also be used for restaurant §153.065(H)(7)(d); menus and other similar uses. Display signs are intended to advertise goods or Table 153.065 -K services. Display signs may change frequently and Display Sign may be attached to or located within 3 feet of a window on the interior of the building. Examples include products for sale or display, and signs that show or describe goods or services offered. Sandwich Board Sign Sandwich board signs are intended to be used in areas with high pedestrian and commercial activity. BRIDGE STREET DISTRICT § 153.065 109 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - SIGNS (d) Number of Permitted Signs in the BSD Historic that the secondary public entrance is located Core and Historic Transition Neighborhood on the side or rear fagade of the building. Districts 4. Tenant spaces located above the ground floor Refer to § I 53.065(H)(7)(a)-(b) for specific may be identified by a directory sign or by requirements for ground and building- mounted a window sign or projecting sign located sign types, sizes, locations, and heights. adjacent to a common public entrance 1. Single Tenant Buildings providing access to the upper floor tenant A combination of two different sign types, spaces. including ground signs and building- mounted 5. A single, one - square -foot window sign signs, are permitted for each street - facing indicating the name of the business and/ building fagade or frontage. For lots with or a logo, shall be permitted on each public more than one street frontage, one additional entrance to a tenant space and shall not ground or building- mounted sign is permitted require a permanent sign permit provided not along the second lot frontage, not to exceed a more than one low chroma color is used. total of three signs. (7) Specific Sign Type Requirements 2. Multiple Tenant Buildings (a) Ground Signs A combination of two different sign types, 1. Ground sign height is measured from the including ground signs and building - mounted established grade of the base of the sign to signs, are permitted for each ground floor the top of the sign or its frame /support. The tenant with a storefront. The permitted height may not be artificially increased. signs may be on separate elevations where 2. All ground signs shall comply with the storefronts are on multiple elevations. provisions of Table 153.065 -H, Ground Sign 3. An additional building- mounted sign is Requirements. permitted for each tenant with a storefront where the tenant also has a dedicated public entrance facing an off - street parking area or parking structure in the same block, provided TABLE 153.065 -H: GROUND SIGN REQUIREMENTS BSD Historic Core District; and BSD Public and Historic Transition Neighborhood Districts within the Architectural Review All Other BSD Zoning Districts District Boundaries Number Refer to §153.065(H)(6)(d) 1 per building or parcel, per street frontage, not to exceed 2. Size Maximum 8 sq. ft. Maximum 24 sq. ft. Historic Cottage Commercial building type only. 8 ft. from the minimum required building zone, setback, or street right -of -way, as appropriate for Location the building type. Refer to §153.062(0) for more information regarding building types. If two ground Minimum setback of 8 ft. from the street right -of -way or any property line. signs are used, the signs shall be located on different street frontages. Height Maximum 6 ft. Maximum 8 ft. Permitted ground signs may be attached to a freestanding wall or other similar structure on the same lot as the building or use. Sign foundations shall not be exposed. Ground signs shall either be mounted on a masonry base or a base clad in material compatible with the material used for the sign and the principal structure containing the use General with which the sign is associated. Ground signs shall be landscaped where appropriate to site conditions.. § 153.065 (H) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - SIGNS JANUARY 7, 2015 TABLE 153.065 -I: BUILDING - MOUNTED SIGN REQUIREMENTS BSD Historic Core District; and BSD Public and Historic Transition Neighborhood All Other BSD Zoning Districts Districts within the Architectural Review District Boundaries Wall Sign Number Refer to §153.065(H)(6)(d). Refer to §153.065(H)(6)(a) through (c) for requirements based on building type. Size Maximum 8 sq. ft. 1 /2 sq. ft. per each lineal foot of building wall or storefront width up to a maximum of 50 sq. ft. On walls facing a public street For multiple tenant buildings, signs shall be located on the portion of the wall associated with the tenant space or storefront, and /or within 6 ft. of the common public entrance, where not associated with a Location storefront. Wall signs shall not extend more than 14 inches from the face of the structure to which it is attached unless determined by the required reviewing body to address unique architectural conditions associated with the building on which the sign is mounted. Located within the first story as appropriate to each building type of §153.062(0) and shall not Height Maximum 15 ft., and shall not extend above the extend above the roofline. Wall signs for Existing Structures shall maintain roofline. a maximum height of 15 ft., and shall not extend above the roofline. Awning Sign Refer to §153.065(H)(6)(a) through (c) for requirements based on building type. Number Refer to §153.065(H)(6)(d). Only 1 sign permitted per awning, regardless of the number of tenants or storefronts. Size 20% of the cumulative surface of all awnings, not to exceed 8 sq. ft. in total. Location Awning signs may be on any portion of the awning, and affixed flat to the surface and shall not extend vertically or horizontally beyond the limit of the awning. Maximum 15 ft. Located within the first story as appropriate to Height each building type of §153.062(0). The lowest portion of an awning sign shall be at least 8 ft. above the sidewalk. Projecting Sign Number Refer to §153.065(H)(6)(d). Refer to §153.065(H)(6)(a) through (c) for requirements based on building type. Size Maximum 8 sq. ft. I Maximum 16 sq. ft. For multiple tenant buildings, within 6 ft. of the principal entrance, as measured horizontally along the building fa5ade. Projecting signs shall be separated by at least 10 ft. from another projecting sign, as Location measured along the building fa5ade. Projecting signs shall not extend more than 6 ft. from the face of the structure to which it is attached and maintain at least 8 ft. of clearance above the sidewalk. Maximum 15 ft., or not extending above the sill of Located within the first story as appropriate to each building type of §153.062(0) and shall not Height the second story window, whichever is lower. extend above the roof line. The lowest portion of a projecting sign shall be at least 8 feet above the sidewalk. Window Sign Number Refer to §153.065(H)(6)(d). Refer to §153.065(H)(6)(a) through (c) for requirements based on building type. 20% of the cumulative surface area of the window to which it is attached, not to exceed 8 sq. ft. Window Size panes separated by muntins shall not be counted separately as windows but shall be included in the cumulative total square footage of window area. Location Ground floor only, except as permitted by Ground floor only §153.065(H)(6)(d)4. General Window signs shall only be permitted in lieu of display signs affixed to a window. Refer to Table 153.065 - K, Requirements for Other Permitted Signs, for Display Sign Requirements. BRIDGE STREET DISTRICT § 153.065 (H) 111 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - SIGNS TABLE 153.065 -J: BUILDING IDENTIFICATION SIGN REQUIREMENTS BSD Historic Core District; and BSD Public and Historic Transition Neighborhood All Other BSD Zoning Districts Districts within the Architectural Review District Boundaries Number 1 wall sign per building or street frontage, not to exceed 2. Location On a building facade facing a street. Size 1 /2 sq. ft. per each lineal foot of building frontage, each sign not Not Permitted to exceed 100 sq. ft. Height Shall not extend above the roofline. Individual channel or pin- mounted letters or characters are required. General Buildings with frontage on the I -270 right -of -way are permitted an additional sign in accordance with §153.161(A). TABLE 153.065 -K: REQUIREMENTS FOR OTHER PERMITTED SIGNS BSD Historic Core District; and BSD Public and Historic Transition All Other Neighborhood Districts within the Architectural Review District BSD Zoning Boundaries Districts Directory Signs Number 1 per public entrance. Location Located within 6 ft. of the entrance and mounted flat to the wall. Size Maximum 4 sq. ft. Height Ground floor only. Identification Plaques Number 1 per building Location Located within 6 ft. of an entrance, pedestrian walkway or open space type and mounted flat to the wall. Size Maximum 2 sq. ft. Identification plaques are not intended to provide information advertising tenants or services located within the building. Information is limited to identification of building names, addresses, historical characteristics, or General other similar building information. Maximum 3 colors Display Signs Display signs located within 3 feet of the window shall not exceed 20% of the surface area of the window on which the signs are displayed. Size Display signs affixed to a window shall not exceed 20% of the surface area and shall only be permitted if a window sign is not also used. Other additional building- mounted signs for multiple tenants with storefronts are permitted. Refer to Table 153.065 -I, Building- Mounted Sign Requirements, for window sign requirements. Height Ground floor only. Sandwich Board Signs Number 1 per ground floor storefront tenant. Sandwich board signs are permitted only immediately in front of the building containing the activity described on the sign. Signs shall be placed within 6 ft. of the primary ground floor public entrance of the Location business and generally along the same plane as other sandwich board signs to ensure a consistent sidewalk clearance, unless otherwise permitted by the Director based on specific site conditions. Signs shall maintain a minimum unobstructed 5 -ft. clearance on sidewalks and shall not Not Permitted impede the safe movement of pedestrians or the safe operation of vehicles. Size 6 sq. ft. per side. Height 3 ft. Sandwich board signs may include chalkboard and whiteboard elements. The sandwich board sign structure shall be constructed with subdued colors. General Sandwich board signs shall be removed and stored indoors or in a location not visible to the public during non - business hours. § 153.065 (H) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - SIGNS JANUARY 7, 2015 (b) Building- Mounted Signs 2. Building identification signs shall comply 1. Building- Mounted Sign Types and with Table 153.065 -J, Building Identification Measurements Sign Requirements. If street address numbers are used in lieu of the name of a major tenant, A. Building- mounted signs include wall the street address numbers shall require a signs, awning signs, projecting signs, and permanent sign permit and shall comply with window signs. Table 153.065 -J, Building Identification Sign B. Wall sign height is measured directly Requirements. beneath the sign from the established grade at the base of the structure to (I) WALKABILITY STANDARDS which the sign is attached to the top of the sign. (1) Intent and Purpose C. Wall sign areas for buildings with (a) These regulations are intended to provide specific storefronts shall be determined by taking requirements that promote the walkable urbanism the length of the storefront applicable principles of §153.057(D). to each tenant and computing sign (b) The intent of the walkability standards is to requirements for that portion of the total enhance connectivity, improve pedestrian safety, wall. and promote comfortable walking and sitting D. Projecting sign height is measured environments. directly beneath the sign from the (c) The walkability standards promote healthier established grade at the base of the lifestyles by encouraging walking and bicycling structure to which the sign is attached over the use of an automobile for most daily to the top of the sign, but shall not activities. It also provides the means by which include brackets or equipment which residents and visitors can be more engaged with are necessary to attach the sign to their neighbors, coworkers and fellow visitors. the structure. Necessary brackets or (d) The walkability standards promote a safer and equipment shall not be counted as part of more comfortable atmosphere for pedestrians and the sign area. bicyclists. 2. All building- mounted signs shall comply with (e) The walkability standards promote recognition the provisions of Table 153.065 -I, Building- that some streets are clearly designed to Mounted Sign Requirements, except that accommodate both bicycles and automobiles A. Any building - mounted sign associated within traffic lanes. with a secondary public entrance as (f) Pedestrian facilities are intended to be designed described in §153.065(H)(6)(c) -(d) above and installed to provide the maximum degree shall not exceed six square feet in size of connectivity between destinations within the and shall be located within six feet of the Bridge Street District, including convenient secondary public entrance, as measured access between places of work, shopping, dining, horizontally along the building fagade. recreation, public transit stops, and home. B. Any projecting sign associated with ( Pedestrian facilities include sidewalks and a common public entrance providing required building zone (RBZ) treatments, street access to upper floor tenant spaces as crossings, mid -block pedestrianways, mid - described in § 153.065(H)(6)(c) -(d) building pedestrianways, building entrances, above shall not exceed eight square feet seating areas within pocket parks and plazas and/ and be located within six feet of the or the furnishing zone within the right -of -way, and common public entrance. greenways. (c) Building Identification Signs In addition to any other permitted signs, one building identification sign is permitted per street frontage for buildings with three or more stories. Building identification signs are not permitted in the BSD Historic Residential, Historic Core, or portions of the Historic Transition Neighborhood districts that fall within the Architectural Review District boundaries unless approved by the Architectural Review Board through a master sign plan (refer to § 153.065(H)(2)(b)6). (2) Walkability Objective: Connectivity (a) Mid- Block Pedestrianways Mid -block pedestrianways are required on all blocks exceeding 400 feet in length, unless otherwise required or exempted by §153.063, Neighborhood Standards. 1. When combined with mid -block street crossings, pedestrianways shall align as nearly as practicable to encourage continuous pedestrian pathways. BRIDGE STREET DISTRICT § 153.065 (I) 113 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - WALKABILITY STANDARDS 2. Mid -block pedestrianways shall be publicly accessible at all times. 3. Mid -block pedestrianways shall be located within the middle third of a block with access from the sides of a block exceeding 400 feet. Refer to Figure 153.060 -A, Typical Block Elements, for an illustration of the middle third of a block. 4. Design A. The ends of the mid -block pedestrianway shall terminate at either a public right - of -way, an open space meeting the requirements of §153.064, or another publicly accessible space as approved by the required reviewing body. B. Mid -block pedestrianways shall be • minimum of 14 feet in width, with • minimum five foot sidewalk, and designed as a continuation of the streetscape, including materials and furnishings. C. The mid -block pedestrianway shall be lighted using footlights, bollard lights, building lights, and/or adjacent street lights to provide for safety and visibility. D. The mid -block pedestrianway shall be landscaped except as required by § 153.065(I)(2)(a)5. 5. Amid - building pedestrianway, as described in §153.065(I)(2)(b),may serve as a mid -block pedestrianway provided it meets the applicable design and location requirements of mid - blockpedestrianways described in this section in addition to other applicable requirements for mid - building pedestrianways; however, landscaping shall not be required. 6. Alternatively, the pedestrianway requirement may be fulfilled by a permitted alley when located in the middle third of a block and when a minimum five foot sidewalk is provided. Design requirements shall be based on the applicable street type specifications, as described in §153.061, Street Types. 7. The required reviewing body may require additional mid -block pedestrianways when necessary to create a cohesive, walkable block configuration and ensure consistency with the Principles of Walkable Urbanism provided in §153.057(D). (b) Mid - Building Pedestrianways 1. Mid - building pedestrianways are intended to provide safe, well -lit, and attractive paths providing convenient pedestrian access to and from areas such as parking lots, parking structures, and/or service streets from the opposite side of a building. 2. Access through buildings to parking lots behind buildings with a pedestrian walkway through the first floor of the building is required based on building types. The walkway shall be a minimum of eight feet wide. One door, window, or opening shall be provided along the pedestrianway for every full 30 feet of length. A minimum of 20% ground floor transparency, measured along the length of the walkway, shall be provided on building fagades facing pedestrianways in shopping corridors. 3. Amid - building pedestrianway may serve as a mid -block pedestrianway as described in § 153.065(I)(2)(a). (3) Walkability Objective: Safety (a) Crosswalks 1. Crosswalks shall be required at the stop - controlled legs of unsignalized intersections and all legs of signalized intersections or as otherwise required by the City Engineer. Crosswalks may be permitted at mid -block locations for areas where heavy pedestrian traffic is anticipated, such as shopping corridors, at the determination of the City Engineer. The locations of mid -block crosswalks should be aligned with the locations of mid -block pedestrianways where practicable. 2. To encourage pedestrian activity, typical crosswalks shall not exceed 38 feet in length without a landscape median, curb extension and/or other pedestrian refuge to mitigate the effects of vehicular traffic on crossing and increase pedestrian safety and comfort. These design measures shall be implemented wherever practicable, as determined by the City Engineer. (b) Pedestrian Circulation Plans Each surface parking area that contains 50 or more parking spaces, or contains any parking spaces located more than 350 feet from the front fagade of the principal structure, shall contain at least one pedestrian walkway or sidewalk allowing pedestrians to pass from the row of parking farthest from the primary building fagade to the primary building entrance. The required walkway must be at least five feet wide, shall not be located within a driving aisle, and, where possible, shall be located in a landscaped island running perpendicular to the primary building fagade. § 153.065 (I) EFFECTIVE DATE SITE DEVELOPMENT STANDARDS - JANUARY 7, 2015 WALKABILITY STANDARDS (4) Walkability Objective: Comfort and Convenience (c) Seating Areas (a) Required Building Zone (RBZ) Treatment 1. Outdoor seating areas are required for all All areas between the front or comer side property pocket plazas, and may be required by the lines and the back of the RBZ or setback not required reviewing body for other public and occupied by a building shall be treated with either private outdoor spaces, including all other a landscape, patio, or streetscape treatment as open space types provided in §I53.064(E). required by §153.062(0). 2. Where required, there shall be a minimum of 1. Where necessary to provide adequate one linear foot of seating for every two linear sidewalk width in areas expected to have feet of public or private street frontage. The high volumes of pedestrian activity, such as required reviewing body may modify this in a shopping corridor, a streetscape RBZ requirement where conditions warrant greater treatment may be required by the required or lesser seating. reviewing body. 3. Seating requirements may be met through 2. If a building is proposed to be constructed the use of moveable seating, fixed individual with a zero lot line setback, with the building seats, fixed benches, seatwalls, planter fagade adjacent to the public sidewalk at the ledges, seating steps, and other creatively right-of-way, and the required reviewing body designed seating areas that invite resting determines that additional sidewalk width and gathering. Acombination of seating is is necessary to ensure consistency with the encouraged. Principles of Walkable Urbanism, the required 4. To ensure that adequate seating invites use by reviewing body may require the building to the public, a portion of the required seating be set back with a streetscape RBZ treatment, must be located within at least 10 feet of a provided the building remains within the RBZ public sidewalk where provided. as required by building type. A public access 5. At least one waste receptacle for each easement shall be required. outdoor seating area is required. Additional 3. The streetscape RBZ treatment shall be receptacles may be required for areas required for all designated shopping corridors, containing food service, such as open air and in all cases, a minimum 8 feet of clear cafes. sidewalk width shall be provided through the combination of public right -of -way and required building zone area with public access easements. 4. Where parking is permitted to the side or rear of a principal structure pursuant to the building type requirements of §153.062(0), surface parking areas and associated driveways may encroach into the front and/ or comer side RBZ provided a street wall is installed in accordance with §153.065(E)(2) to screen the parking area. The area on the street- facing side of the street wall shall be treated with landscape, patio, or streetscape RBZ treatment as permitted by the building type. (b) Building Entrances 1. A principal building entrance shall be on any principal frontage street or the front fagade of the building. Principal entrance doors shall be fully functioning during regular business hours and shall connect to the public sidewalk along the street. 2. The number and spacing of entrances on a building fagade with street frontage and on a rear fagade facing a parking lot shall be provided as required by building type. BRIDGE STREET DISTRICT § 153.065 (I) 115 DEVELOPMENT CODE SITE DEVELOPMENT STANDARDS - WALKABILITY STANDARDS § 153.066 REVIEW AND APPROVAL PROCEDURES AND CRITERIA (A) INTENT The intent of §153.066 is to provide an efficient and predictable review process for rezoning and/or development applications within the Bridge Street District zoning districts and to enhance Dublin's reputation for high quality development while allowing property owners to compete for development consistent with the direction articulated in the Community Plan (Bridge Street District Area Plan). The review and approval procedures and criteria help ensure that new development and redevelopment is served by adequate and efficient infrastructure so as not to burden the fiscal resources of the City, and to protect the health, safety, and general welfare of residents, occupants, and users of property in the BSD zoning districts and surrounding areas of the city. (B) REQUIRED REVIEWS (d) Pre- Application Reviews do not result in a development decision or permit, and shall not obligate the City or the developer to take any action on the proposal. (2) Review Procedure (a) A request for a Pre - Application Review shall be made in accordance with the provisions of §153.066(N)(1). (b) The City shall notify the applicant in writing at least five days prior to the Pre - Application Review meeting. (c) The ART and other applicable departments shall be promptly notified of the ART Pre - Application Review meeting. Prior to the meeting the Director shall distribute the submitted materials to the ART and other applicable departments for input and recommendations. (1) This section outlines the requirements and procedures for development review specifically within the BSD zoning districts. The review procedures of §153.066 shall be used for all development applications in a BSD zoning district. Table 153.066 -A, Summary Procedure Table, describes the review procedures applicable in all BSD zoning districts. (2) The following abbreviations and terms are used in §153.066: ART — Administrative Review Team ARB — Architectural Review Board BZA — Board of Zoning Appeals PZC or Commission —Planning and Zoning Commission CC or Council— City Council Director — Planning Director (C) PRE - APPLICATION REVIEW (1) Purpose and Applicability (d) The ART shall review the submitted materials and provide non - binding input and recommendations. The ART shall complete its review of the application not more than 14 days from the date the request was submitted. (e) A written summary of the Pre- Application Review meeting shall be provided to the applicant not more than 10 days after the Pre - Application Review meeting. (f) Additional Pre- Application Review meetings with the ART may be requested prior to filing a request for a Basic Plan Review. (g) The written summary of the Pre - Application Review shall be forwarded to the required reviewing body with the application for a Basic Plan Review. (D) BASIC PLAN REVIEW (1) Purpose and Applicability (a) The purpose of the Pre- Application Review is to (a) Purpose provide a potential applicant with a non- binding 1. The purpose of the Basic Plan Review is to review of a development proposal and to provide outline the scope, character, and nature of the information on the procedures and policies of the proposed development and to determine the City, including application review procedures. applicable review process. (b) Pre- Application Review with the Administrative 2. The Basic Plan Review allows the required Review Team (ART) is required for any proposal reviewing body to evaluate the proposal for that requires Development Plan or Site Plan its consistency with commonly accepted Review under the provisions of §153.066(E) and principles of walkable urbanism as described (F). in § §153.057 and 153.058, the Community (c) Pre - Application Reviews maybe submitted and Plan, including the Bridge Street District processed simultaneously with a request for a Plan, and other related policy documents Basic Plan Review as provided in § I53.066(D). adopted by the City, and to consider the proposal within the context of existing and § 153.066 EFFECTIVE DATE REVIEW & APPROVAL JANUARY 7, 2015 PROCEDURES & CRITERIA TABLE 153.066 -A: SUMMARY PROCEDURE TABLE R = Recommendation D = Decision RF = Review & Feedback Type of Application ART ARB BZA PZC Council* Zoning Code Reference Zoning Code Approvals Zoning Map or Tent R R R D §153.234 Amendment Conditional Use ** R R D D/A §153.236 Special Permit D A §153.231(G) Use Variance R R D §153.231(H)(3) Non -Use (Area) Variance R D §153.231(H)(2) Other Approvals Building Code Appeal D §153.231(I) Bridge Street District Zoning Districts Pre - Application Review RF §153.066(C) Applications with Development R D §153.066(D) Agreements Architectural R D §153.066(D) Basic Plan Review Review District §153.066(3) Other BSD R D §153.066(D) Zoning Districts Architectural R D D §153.066(3) Development Review District Other BSD Plan Review ** Zoning Districts R/D D D §153.066(E)(2) Architectural R D D §153.066(]) Site Plan Review District Review ** Other BSD R/D D D §153.066(F)(2) Zoning Districts Architectural R D §153.066(3) Minor Project Review District Reviews Other BSD D §153.066(G) Zoning Districts Architectural R D D §153.066(3) Review District Waivers ** Other BSD R D D §153.066(I) Zoning Districts Architectural R D §153.065(H)(L)(8)/ Master Sign Review District §153.065(H)(2)(c)6 Other BSD R D §153.065(L)(8)/ Plan Review ** Zoning Districts §153.065(H)(2)(c)6 Parking Plans D/R D D §153.065(B)(1)(f)/ §153.066(G) Administrative Departure D §153.066(H) Open Space Fee in Lieu R D §153.066(L)(1)/ §153.064(D) -(E) Minor Modifications §153.066(K) Certificate of Director Approval Zoning Plan §153.233/ Approval §153.066(N)(3) (Building & Site Modifications) * See also §153.066 (L) Conditional Uses and §153.066 (M) Appeals 153.066(M) ** As determined by the required reviewing body at Basic Plan Review §153.066(D)(3) BRIDGE STREET DISTRICT § 153.066 117 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA planned development within the vicinity of (b) A public review of a Basic Plan application shall the project. be held in accordance with the provisions of 3. The Basic Plan Review provides an §.153.066(1)(1)(f). opportunity for public input at the earliest (c) Applications for Basic Plan Review shall be stages of the development process. approved, approved with conditions, or denied 4. The Basic Plan Review provides clear based on the Development Plan Review criteria direction to the applicant and the required of § I53.066(E)(3) and/or the Site Plan Review reviewing body in its evaluation of an criteria of §153.066 (17)(3). If denied, the applicant application for Development Plan and/or Site shall be perm tried to submit an application for Plan Review. another Basic Plan Review. (b) Applicability (d) The decision on the Basic Plan Review shall be provided not more than 28 days from the filing 1. Due to the significant amount of of a complete Basic Plan Review application. infrastructure that will be required as part of The required reviewing body shall schedule the development of the Bridge Street District, meetings as necessary to meet the review period key private development projects will require requirement. partnerships with the City to be feasible. To ensure early Council understanding and (e) The Basic Plan Review decision provided by support for the proposed development, City the required reviewing body shall be forwarded Council shall conduct the basic plan review in writing to the applicant not less than 10 days for proposals that will involve development following the review. agreements with the City and shall determine (f) The decision and findings of the Basic the required reviewing body for subsequent Plan Review shall be incorporated into the development plan and/or site plan review Development Plan and/or Site Plan Review applications. For purposes of this section, application. "development agreement" shall mean an (g) If a Development Plan and/or Site Plan Review agreement between an individual or other application is not submitted within one year from private entity and the City Council to develop the date of the approved Basic Plan Review, a parcel of land for a use permitted by the the applicant shall be required to submit a new City. The development agreement may set application for a Basic Plan Review prior to out responsibilities of the parties for items submitting an application for a Development Plan such as development time frame, property and/or Site Plan Review involving the same site. limits, infrastructure development terms, public and private contributions, development (3) Required Reviewing Body Determination restrictions and other related terms. (a) For Basic Plan Review applications submitted in 2. All other basic plan applications not requiring accordance with the provisions of §153.066(D) a development agreement shall be reviewed (1)(b)(1) the City Council shall determine the by the Planning and Zoning Commission, or required reviewing body for the subsequent the Architectural Review Board as provided Development Plan and/or Site Plan Review in §153.066(D)(1)(b)(3). applications. 3. For applications not requiring a development (b) For Basic Plan Reviews conducted by the agreement, a Basic Plan Review is at the Planning and Zoning Commission, the option of the applicant for any proposal that Commission shall determine the required requires Development Plan and/or Site Plan reviewing body for the subsequent Development Review by the Architectural Review Board Plan and/or Site Plan Review applications. In under the provisions of §153.0660. Provided making its determination, the Commission will that a Basic Plan Review may be required by consider any of the following factors: the ART if it concludes that the application 1. Whether the application raises complex includes major site or building improvements issues, including but not limited to, the need that would benefit from a Basic Plan Review for major infrastructure improvements and by the ARB. other neighborhood or community -wide (2) Review Procedure effects that would benefit from a Commission decision. (a) An application for a Basic Development Plan Review or Basic Site Plan Review shall be made 2 Whether the application is generally in accordance with the provisions of §153.066(N) consistent with the principles of walkable (1) urbanism as described in § §153.057 and 153.058, the five Bridge Street District Vision § 153.066 EFFECTIVE DATE REVIEW & APPROVAL JANUARY 7, 2015 PROCEDURES & CRITERIA Principles, the Community Plan or other applicable City plans. 3. Whether the application involves a substantial number of Waivers or the scope of requested Waivers would result in a significant deviation from the requirements of § §153.059 through 153.065. (c) The Council or Commission's determination of the required reviewing body shall be forwarded in writing to the applicant not less than five days following the determination. (d) An application for Development Plan Review and/ or Site Plan Review may be submitted as provided in § 153.066(N ). 1. The required reviewing body shall review applications in accordance with the provisions of § §153.066(E)(2)(c) and 153.066(F)(2)(c). 2. Applications for which the Administrative Review Team is the required reviewing body shall be reviewed in accordance with § §153.066(E)(2)(d) and 153.066(F)(2)(d). (e) Applications for which the Architectural Review Board is the required reviewing body shall be reviewed in accordance with §153.0660. (E) DEVELOPMENT PLAN REVIEW (1) Purpose and Applicability (a) The purpose of the Development Plan Review is to 1. Ensure that the street network and block framework meet the requirements of §§153.060, 153.061 and §153.063, as applicable; 2. Ensure that proposed street types are consistent with the principles of walkable urbanism as described in § §153.057 and 153.058; 3. Ensure that planned open spaces and building types, when known, will meet the applicable general siting requirements of § §153.062 and 153.064; 4. Ensure 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 5. Ensure that the proposed development will contribute to the creation of signature places in the city consistent with the Bridge Street District Plan through an evaluation of long- term phasing plans, transitional development conditions, and planned placemaking elements. 6. The Development Plan review process is not intended to be a review of the individual development regulations of §153.059 and § §153.062 through 153.065, which are intended for the Site Plan Review process. (b) An application for a Development Plan Review is required if at least one of the following conditions is satisfied: 1. The application involves the construction of more than one principal structure on one or more parcels, 2. The application includes five or more gross acres of land; 3. The application involves the design or construction of new streets, or a proposed realignment or relocation of any other street in the general pattern of street development conceptualized by the Bridge Street District Street Network map in § 153.061 that is required or permitted by the City, 4. The application involves subdivision in accordance with Chapter 152 of the Dublin Code of Ordinances is required. (2) Review Procedures (a) Applications for Development Plan Review shall be submitted in accordance with the provisions of §153.066(N)(1). (b) The required reviewing body for a Development Plan Review application shall be determined under the provisions of § I53.066(D)(3) and the application shall be reviewed under the provisions of §153.066(E)(2)(c), (d) or (e) as applicable. (c) Required Reviewing Body Review Procedures 1. Administrative Review Team Recommendation A. The ART make a recommendation to the required reviewing body for approval, approval with conditions, or denial of the Development Plan application under the criteria of §153.066(E)(3). The recommendation shall be made not more than 28 days from the receipt of a completed application. The ART's recommendation shall be provided to the applicant in writing not more than 5 days after the ART's recommendation. B. Following the review, the applicant shall be given the opportunity to revise the application in response to the ART's comments. The applicant may request additional subsequent meetings with the ART, which may be subject to up to an additional 28 day time limit for a decision. BRIDGE STREET DISTRICT § 153.066 119 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA 2. The required reviewing body shall review the Development Plan application and the recommendation of the ART and render its decision based on the criteria of §I53.066(E) (3) for approval, approval with conditions, or denial not more than 14 days after the date of the determination by the ART. The required reviewing body's decision shall be provided to the applicant in writing not more than 14 days after the date of the decision. (d) Administrative Review Team (ART) Review 1. The ART shall review the application for Development Plan Review and render a determination based on the criteria of §153.066(E)(3) for Development Plans for approval, approval with conditions, or denial. 2. The ART shall make a decision on the application not more than 28 days from the date of the submission of a complete application for a Development Plan Review. (e) Applications for which the Architectural Review Board is the required reviewing body shall be reviewed in accordance with §153.0660. (3) Review Criteria for Development Plans Each required reviewing body shall make its recommendation or its decision on an application for Development Plan Review based on each of the following criteria and the recommendation of the ART and the required reviewing body during the Basic Plan Review: (a) The Development Plan shall be substantially similar to the approved Basic Development Plan, (b) The lots and blocks proposed are consistent with the requirements of §153.060; (c) The application is consistent with the general pattern of street development conceptualized by the BSD Street Network as shown in §153.061 and the expected traffic from the development can be accommodated on existing or proposed streets consistent with that system, (d) The proposed street types are consistent with the principles of walkable urbanism as described in § §153.057 and 153.058 and are designed to coordinate with the scale, intensity and character of development planned on adjacent lots and blocks, (e) The proposed buildings and open spaces are appropriately sited and consistent with the requirements of § §153.062 and 153.064; (f) The application is consistent with the requirements of §153.063, Neighborhood Standards, if applicable, (g) If the development is to be implemented in phases, each phase is able to be considered independently, without the need for further phased improvements, (h) The application demonstrates consistency with the five Bridge Street District Vision Principles, Community Plan and other related policy documents adopted by the City; and (i) The application provides adequate and efficient infrastructure to serve the proposed development, consistent with the City's most recently adopted Capital Improvements Program. (F) SITE PLAN REVIEW (1) Purpose and Applicability (a) The purpose of the Site Plan Review is to confirm that the proposed development of an individual site, building, and/or open space is consistent with the BSD zoning district regulations. (b) The Site Plan Review process is intended as a review of the individual development regulations of §153.059 and § §153.062 through 153.065. Approval of the Site Plan Review includes assuring that the dimensions of a parcel meet the lot size requirements for the applicable building type(s) and that the surrounding street network meets the applicable requirements of § §153.060 and 153.061. (c) A Site Plan Review is required for any development application within the BSD zoning districts, including those applications for which a Development Plan is required, with the exception of applications meeting the requirements for a Minor Project as provided in §153.066(G)(2). (2) Review Procedures (a) Applications for Site Plan Review shall be submitted in accordance with the provisions of §153.066(N)(1). (b) The required reviewing body for a Site Plan Review application shall be determined under the provisions of §153.066(D)(3) and the application shall be reviewed under the provisions of §153.066(F)(2)(c), (d) or (e) as applicable. (c) Required Reviewing Body Review Procedures 1. The ART shall provide a recommendation to the required reviewing body for approval, approval with conditions, or denial of the Site Plan Review application under the criteria of §153.066(F)(3). The recommendation shall be made not more than 28 days from the receipt of a completed application. The ART's recommendation shall be provided to the applicant in writing not more than 5 days after the ART's recommendation. 2. Following the review, the applicant shall be given the opportunity to revise the application in response to the ART's comments if the § 153.066 EFFECTIVE DATE REVIEW & APPROVAL JANUARY 7, 2015 PROCEDURES & CRITERIA application is not recommended for approval a high quality community with a commitment to by the ART. The applicant may request exemplary planning and design, additional subsequent meetings with the ART (t) The application is consistent with the which may be subject to up to an additional requirements for types, distribution, and suitability 28 day time limit for a decision. of open space in §153.064 and the site design 3. The required reviewing body shall review the incorporates natural features and site topography Site Plan application and the recommendation to the maximum extent practicable, of the ART and render its decision based on (g) The scale and design of the proposed development the criteria of §153.066(F)(3) for approval, allows the adequate provision of services approval with conditions, or denial not currently furnished by or that may be required more than 14 days from the date of the by the City or other public agency including, but determination by the ART. The required not limited to, fire and police protection, public reviewing body's decision shall be provided water and sanitary sewage services, recreational to the applicant in writing not more than 14 activities, traffic control, waste management, and days after the date of the decision. administrative services; (d) Administrative Review Team (ART) Review (h) Stormwater management systems and facilities 1. The ART shall review the application for will not cause alterations that could increase Site Plan Review and render a determination flooding or water pollution on or off the site, and based on the criteria of § I53.066(F)(3) removal of surface waters will not adversely affect for Site Plans for approval, approval with neighboring properties, conditions, or denial. (i) If the development is to be implemented in 2. The ART shall make a decision on the phases, each phase is able to be considered application not more than 28 days from independently, without the need for further phased the date of the submission of a complete improvements; and application for a Site Plan Review. O The application demonstrates consistency with (e) Applications for which the Architectural Review commonly accepted principles of walkable Board is the required reviewing body shall be urbanism as described in § §153.057 and 153.058, reviewed in accordance with § 153.0660. the five Bridge Street District Vision Principles, (3) Review Criteria for Site Plans Community Plan and other related policy documents adopted by the City. The required reviewing body shall make its recommendation or its decision on an application for Site Plan Review based on each of the following (G) MINOR PROJECT REVIEW criteria and the recommendation of the ART and (1) Purpose and Applicability the required reviewing body during the Basic Plan The purpose of the Minor Project Review is to provide Review: an efficient review process for smaller projects that (a) The Site Plan Review shall be substantially do not have significant community effects. The Minor similar to the approved Basic Site Plan. Project review is necessary to ensure that applications (b) If a Development Plan has been approved that meet the requirements of this Chapter. includes the property, the application is consistent (2) The following shall be considered Minor Projects: with the Development Plan, (a) Individual single family detached dwelling units. (c) The application meets all applicable (b) Multiple family and townhouse buildings of 8 or requirements of §153.059 and § §153.062 fewer dwelling units in a single building on an through 153.065 except as may be authorized by individual lot and not part of a larger development AdrninistrativeDeparture (s)orWaiver(s)pursuantto complex. §153.066(H) and §153.066(1), respectively; (d) The internal circulation system and driveways (c) Development of mixed-use and non-residential provide safe and efficient access for residents, principal structures of 10,000 square feet or less occupants, visitors, emergency vehicles, bicycles, gross floor area, and associated site development and pedestrians; requirements. (e) The relationship of buildings and structures to (d) Additions the that each other and to other facilities provides for the area by not t more than 25 structures gross floor aea by o/0, or not or no coordination and integration of the development more than 10,000 square feet gross floor area, within the surrounding area and the larger whichever is less, existing as of the effective date community and maintains the image of Dublin as of this amendment, or when first constructed, and associated site development requirements. BRIDGE STREET DISTRICT § 153.066 121 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA (e) Exterior modifications to principal structures involving not more than 25% of any individual fapade elevation of the structure. (f) Signs, landscaping, parking, and other site related improvements that do not involve construction of a new principal building. Parks when used to meet requirements as an open space type, as provided in §153.064, . shall require Site Plan Review. (g) Accessory structures and uses. (h) Modifications to Existing Structures in accordance with §I53.062(B). (i) Parking plans when not associated with a Development Plan or Site Plan Review. requirements caused by unusual site or development conditions or conditions unique to a particular use or other similar conditions that require reasonable adjustments, but remain consistent with the intent of this Chapter. Examples include, but are not limited to, minor adjustments to building setbacks, parking requirements, landscaping, building materials, or other similar features or elements. (2) Review Procedure (a) A request for an Administrative Departure may be submitted with an application for a Development Plan, Site Plan, or Minor Project Review, or at any time after those applications have been submitted and before a decision or (3) Review Procedure recommendation by the ART has been made. If a (a) An application for a Minor Project Review shall request for Administrative Departure is made after be made in accordance with the provisions of any application for which a time limit is provided §153.066(N)(1). the Director may require that the time period for (b) Following acceptance of a complete application ART review start over on the day the request for an Administrative Departure is received. for a Minor Project, the ART shall approve, deny, or approve with conditions the application not (b) A request for an Administrative Departure may be more than 14 days from the date the request was processed simultaneously with the Development submitted. The City shall notify the applicant in Plan, Site Plan, or Minor Project Review to which writing not less than five days prior to the review it relates. The ART shall determine whether each meeting. requested Administrative Departure is approved, (c) The ART shall review the application and approved with conditions, or denied. Decisions approve, approve with conditions, or deny the on Administrative Departures shall be reported application based on the criteria of § 153.066(F) to the required reviewing body that approved the (3) applicable to Site Plan Reviews. A written Development Plan and/or Site Plan Review. summary of the ART decision shall be provided (c) Should the ART find that the request does not to the applicant not more than 10 days after the meet the criteria for an Administrative Departure, Minor Project Review meeting. the applicant may request a Waiver under the (d) Alternatively, the ART may forward any Minor provisions of §153.066(1) or submit a new application for Development Plan, Site Plan, or Project Review application to the Planning Minor Project Review. and Zoning Commission for a decision at their next available meeting if it concludes that the (3) Criteria for Administrative Departure Approval application raises complex issues, including but The ART shall make its decision on the requested not limited to, the need for public infrastructure Administrative Departure based on the following improvements and/or other neighborhood or criteria: community -wide effects that would benefit from a (a) The need for the Administrative Departure is Commission decision. These applications shall be caused by unique site conditions, conditions on reviewed under the provisions of §153.066(F)(2) surrounding properties, and/or otherwise complies (c) and shall not require a Basic Plan Review. with the spirit and intent of the Bridge Street (e) Following the decision, the applicant shall be District Plan, and is not being requested simply to given the opportunity to revise the application in reduce cost or as a matter of general convenience, response to the ART's comments if the application (b) The Administrative Departure does not have is not approved by the ART. The applicant may the effect of authorizing any use, sign, building request additional subsequent meetings with the type, open space type that is not otherwise ART, which shall also be subject to the 14 day permitted in that BSD zoning distract; tt time limit for a decision. (c) The Administrative Departure does not modify any numerical zoning standard related to building (H) ADMINISTRATIVE DEPARTURES dimensions, lot dimensions or coverage, open (1) Purpose and Applicability space, landscaping, parking, fencing, walls, The intent of §153.066(1) is to provide an screening, or exterior lighting by more than administrative process to allow minor deviations 10% of the requirement; and from the strict application of the BSD zoning district 122 § 153.066 EFFECTIVE DATE REVIEW & APPROVAL JANUARY 7, 2015 PROCEDURES & CRITERIA (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, (K) MINOR MODIFICATIONS (1) Purpose and Applicability (a) The Director may authorize Minor Modifications to approved Development Plans, Site Plans and Minor Projects that are required to correct any undetected errors or omissions, address conditions discovered during the permitting process or construction, or that are necessary to ensure BRIDGE STREET DISTRICT § 153.066 123 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA (d) The Administrative Departure, if approved, will (e) The requested modification would better be ensure that the development is of equal or greater addressed through the Waiver rather than an development quality with respect to design, amendment to the requirements of this Chapter, material, and other development features than (f) For Development Plans, the other Development without the Administrative Departure. Plan elements not affected by the Waiver will be generally consistent with §153.060(A) (I) WAIVER REVIEW and §153.061(A) and (1) Requests for Waivers shall be submitted for any (g) For Site Plan Reviews and Minor Project project elements that deviate from one or more of Reviews, the Waiver does not have the effect of the requirements of §§ 153.059 through 153.065, and authorizing any use or open space type that is not that do not qualify for an Administrative Departure otherwise permitted in that BSD zoning district. under the provisions of §153.066(H). The Waiver request may be submitted with any application for (,7) ARCHITECTURAL REVIEW BOARD (ARB) REVIEW Development Plan, Site Plan, or Minor Project Review. (1) Applications for Basic Plan (if conducted), Development Plan, Site Plan, Minor Project (2) The ART shall review the requested Waivers and make Reviews and Waiver Reviews for property within recommendations to the required reviewing body for the Architectural Review District shall be reviewed their approval, denial, or approval with conditions. by the ART within the timeframes specified in Should additional necessary Waivers be determined § §153.066(D)(2), 153.066(E)(2)(a), or 153.066(F) by the ART during its review, those Waivers may be (2)(a), as applicable and then forwarded to the ARB included for review by the required reviewing body. with a recommendation for approval, approval with (3) The required reviewing body shall review the conditions, or denial. requested Waivers using the criteria of §153.066(1)(6). (2) Applications for Basic Plan, Development Plan, Site Should other Waivers be necessary to resolve conflicts Plan, Minor Project Reviews and Waiver Reviews with other requirements of this Chapter resulting from for which the ARB is the required reviewing body the requested Waivers, those Waivers shall also be shall be reviewed in accordance with the standards of reviewed by the required reviewing body. § §153.066(E)(3), 153.066(F)(3), 153.066(G), and/or (5) The required reviewing body shall approve, approve 153.066(I), as applicable, as well as the provisions of with conditions, or deny the specific Waiver request(s) §153.170 through §153.180. not more than 28 days from the recommendation of (3) Public Review the ART. Apublic review of applications for Basic Plan (if (6) Criteria for Waiver Review conducted), Development Plan, Site Plan, Minor The required reviewing body shall make its Project Reviews and Waiver Reviews for which the recommendation/decision on an application for ARB is the required reviewing body shall be held in proposed Waivers based on all of the following criteria accordance with the provisions of §153.066(I)(1)(f). and with consideration to the recommendation of the (4) The ARB shall make a decision on the application ART: not more than 28 days from the date of the ART's (a) The need for the Waiver is caused by unique recommendation. site conditions, the use of or conditions on the (5) In the event of a conflict between the requirements property or surrounding properties, or other of §153.059 and § §153.062 through 153.065, and circumstance outside the control of the owner/ the provisions of §153.170 through §153.180, the lessee, including easements and rights -of -way, ARB shall determine the most appropriate provisions (b) The Waiver, if approved, will generally meet the to apply to the specific application based on the spirit and intent of the Bridge Street District Plan criteria of § I53.066(E)(3) for Development Plans and supports the commonly accepted principles of and §153.066(F)(3) for Site Plan and Minor Project walkable urbanism, Reviews. (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, (K) MINOR MODIFICATIONS (1) Purpose and Applicability (a) The Director may authorize Minor Modifications to approved Development Plans, Site Plans and Minor Projects that are required to correct any undetected errors or omissions, address conditions discovered during the permitting process or construction, or that are necessary to ensure BRIDGE STREET DISTRICT § 153.066 123 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA orderly and efficient development. Any approved Minor Modifications must be consistent with the approved Development Plan, Site Plan or Minor Project Review, as applicable. (b) The Director may also authorize Minor Modifications to Existing Structures and associated site improvements that are necessary to complete ordinary maintenance, refurbishment or Zoning Code compliance. (c) The following are considered Minor Modifications: 1. Adjustments to lot lines, provided no additional lots are created, required setbacks and/or RBZs are maintained, and the boundaries to any approved Development Plan are not altered, 2. Adjustments to the location and layout of parking lots provided the perimeter setbacks, yards and buffers, and required parking are maintained, 3. Adjustments for buildings up to 10% in total floor area of the originally approved building, building height(s) or floor plans, that do not alter the character of the use, 4. Substitution of landscaping materials specified in the landscape plan with comparable materials of an equal or greater size, 5. Redesigning and/or relocating stormwater management facilities provided that general character and stormwater capacities are maintained, 6. Relocating fencing, walls or screening (not including screening walls), provided that the same level and quality of materials and screening are maintained, 7. Modifications to sign location, sign face, landscaping and lighting, provided the general sign design, number of signs, and dimensional requirements are maintained, 8. Changes in building material or colors that are similar to and have the same general appearance comparable to or of a higher quality as the previously approved material, 9. Changes required by outside agencies such as the county, state, or federal departments, and/ or 10. 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. (2) Review Procedure (a) An application for a Minor Modification shall be made in accordance with the provisions of § I 53.066(N)(1) for Certificates of Zoning Plan Approval. (b) The Director shall review the request for a Minor Modification and make a decision on the request not more than 14 days after receiving a complete application for Certificate of Zoning Plan Approval. (c) 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. If a revised application for Certificate of Zoning Plan Approval is submitted, the 14 day review period shall start over on the day the revised request is received. (d) Requests not meeting the requirements for a Minor Modification shall require the filing and approval of a new application for a Development Plan Review, Site Plan Review, Minor Project Review, or other review, as applicable, in accordance with §153.066. (L) OTHER APPLICABLE REVIEWS (1) Open Space Fee in Lieu After a recommendation from the ART, the Planning and Zoning Commission shall determine whether a request for payment of a fee in lieu of open space dedication may be approved, as provided in §153.064(D) and (E). (2) Conditional Uses The conditional use approval procedures in §153.236 shall apply in the BSD zoning districts. For those projects requiring a development agreement, City Council shall determine the required reviewing body for any conditional use. A recommendation from the ART and the ARE, as applicable, shall be submitted for consideration by the Council or the Planning and Zoning Commission. (3) Zoning Map or Text Amendment The amendment procedures of §153.234 shall apply in the BSD zoning districts. In addition, a recommendation from the ART and the ARE, as applicable, shall be submitted for consideration by the Planning and Zoning Commission and City Council. (4) Preliminary and Final Plats Reviews of Preliminary and Final Plats shall be governed by Chapter 152 of the Dublin Code of Ordinances. (5) Special Permit The Special Permit procedures in §153.231(G) shall apply in the BSD zoning districts. (6) Zoning Variance The zoning variance procedures in §153.231(H) shall apply in the BSD zoning districts. In addition, a § 153.066 EFFECTIVE DATE REVIEW & APPROVAL JANUARY 7, 2015 PROCEDURES & CRITERIA recommendation from the ART shall be submitted for unnecessary by the Director based on the nature consideration by the Board of Zoning Appeals and for and scale of the proposed development. No City Council in the instance of a use variance. application shall be accepted by the City until (7) Public Tree Permit it is complete. Any applicable time limits noted in §153.066 shall not begin until a complete The tree perm itrequirements of §153.134(G) shall application is accepted by the City. If found to be apply in the BSD zoning districts. incomplete, the Director shall inform the applicant (8) Master Sign Plan of any additional materials required to complete (a) The Planning and Zoning Commission or the application. Architectural Review Board shall review all (c) After acceptance of a complete application, the master sign plans in the BSD zoning districts, Director and/or required reviewing body may as provided in §153.065(H). A recommendation request additional materials if deemed necessary from the ART shall be submitted to the required to evaluate the proposal. reviewing body for consideration. (d) Resubmission (b) For those projects requiring a development No application for a Development Plan or Site agreement, City Council may determine the Plan Review which has been denied by the required reviewing body for a master sign plan. required reviewing body shall be resubmitted for a period of one year from the date of the (M) APPEALS decision, unless permitted by the Director after (1) An appeal may be taken by any applicant where a demonstration by the applicant of a change of it is alleged by the applicant that there is error or circumstances from the previous application that misinterpretation in any order, requirement, decision, may reasonably result in a different decision. grant or refusal made by the required reviewing body (e) Simultaneous Processing or official for any decision required by this Chapter in 1. In cases where a Development Plan the BSD zoning districts. application is submitted, a Site Plan Review (2) Appeals shall be taken within 20 days after the and/or a Minor Project may be reviewed decision of the required reviewing body by filing simultaneously with that Development Plan, with the Clerk of City Council of a notice of appeal, if approved by the Director. specifying the grounds. The Clerk shall transmit to 2. The Site Plan Review or Minor Project City Council all the materials constituting the record approval shall not be effective until the upon which the action was taken. Development Plan has been approved. (3) City Council must determine whether or not to hear If appropriate, other required reviews as the appeal, in its sole discretion and by a motion provided in this section may be processed passed by a majority vote, no later than 21 days jointly with a Development Plan and/or Site following the Clerk of City Council's receipt of the Plan Review application. written notice of appeal, unless an extended time is (f) Public Reviews agreed upon by City Council and the applicant Where public reviews are required by this section, (4) City Council shall decide the appeal no later than a written notice of the public meeting shall be 28 days following the date of Council's decision to sent, not less than 10 days prior to the meeting, hear the appeal, unless an extended time is otherwise to the applicant, property owner, and owners of agreed upon by City Council and the applicant In parcels of land within 300 feet of the subject considering the appeal, City Council may consider any parcel(s), as listed on the County Auditor's current evidence and may affirm, reverse, or otherwise modify tax list. The notice shall, at a minimum, indicate the decision of the required reviewing body or any the property that is the subject of the request, other part of the application. describe the nature of the request, the time, date and location of the meeting at which the (N) GENERAL PROVISIONS application will be considered, and indicate when (1) Applications and where written comments will be received concerning the request. (a) Each application required by §153.066 shall be (2) Decisions made in writing on a form provided by the City and shall be accompanied by the fee as established (a) Any application required to be reviewed under by City Council. §153.066 shall be approved, approved with (b) Applications for approvals in the BSD zoning conditions, or denied by the required reviewing districts shall include all information required body based on the applicable review criteria by the City, unless some information is deemed as provided in §153.066 and other applicable provisions of this Chapter. The recommending BRIDGE STREET DISTRICT § 153.066 125 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA body and required reviewing body shall state the reasons for their decisions in the minutes and provide a written record of the decision to the applicant not more than 10 days after a recommendation or decision is made, unless otherwise provided in this section. (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 § 153.066 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. If the request for postponement is granted, a new review period shall begin on the date the applicant submits a complete application with revised materials. (c) Following the approval of a Site Plan Review or Minor Project application, the applicant may proceed with the process for obtaining a Certificate of Zoning Plan Approval and building permit, consistent with the approval as granted. All construction and development under any building permit shall comply with the approved Site Plan Review and Development Plan, and any other approval, as applicable. (3) Certificate of Zoning Plan Approval A Certificate of Zoning Plan Approval 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 BSD zoning districts. (4) Code Administration The Planning and Zoning Commission and the Architectural Review Board may evaluate and monitor the application of the requirements and standards of § §153.057 through 153.066 by the ART. The Commission and the Architectural Review Board may advise the ART as to whether it finds that the requirements or standards (including requests for Administrative Departures) are being applied correctly, and recommend to City Council any changes needed in the BSD zoning district standards and requirements to better implement the Bridge Street District Plan. (5) Time Extensions (a) Where the provisions of § 153.066 require that an action be taken by the City within a stated period of time, that time may be extended with the written consent of both the applicant and the Director prior to expiration of the required time period. (b) If the applicant submits a revised application during any required review period, and the Director determines that the revised application differs substantially from the previous application, a new review period shall begin and additional meetings of the required reviewing body may be scheduled if deemed necessary by the Director. (6) Duration of Approvals (a) An application shall be filed for a Development Plan and/or Site Plan Review within one year following the completion of the Basic Plan Review. If a Development Plan and/or Site Plan Review application is not filed within this period a new Basic Plan Review shall be required in accordance with the requirements of §153.066(D). (b) All Development Plan, Site Plan Review, and Minor Project approvals made pursuant to §153.066 shall be valid for a period of two years. If an initial building permit and/or Certificate of Zoning Plan Approval for the approved development has not been issued within that two year period, the applicant shall be required to apply for a new Development Plan, Site Plan Review, or Minor Project approval, as applicable, pursuant to §153.066 before obtaining a building permit. (c) Abandonment § 153.066 REVIEW & APPROVAL PROCEDURES & CRITERIA 1. Once a final approval is granted by the required reviewing body, if significant construction is not started within two years and meaningfully continued, or 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 intent to abandon the construction of the project. 3. Once the Director of Building Standards makes a determination of abandonment, if a new Bridge Street District 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 EFFECTIVE DATE JANUARY 7, 2015 any structures or other evidence of work on the site, within 180 days from the date of the determination of abandonment. 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. (7) Administrative Review Team (ART) (a) The purpose of the Administrative Review Team is to provide for review and approval authority for certain applications as defined by §153.066. The Administrative Review Team is responsible for the comprehensive review of each application, and making recommendations to City Council, the Planning and Zoning Commission, Architectural Review Board, or Board of Zoning Appeals where required. The ART is also responsible for making decisions in an efficient and timely manner based on evaluation of objective development standards and specific review criteria. While these objective standards and criteria must guide the decisions of the ART, it is recognized that some degree of subjectivity may be part of the ART's deliberations. (b) The Administrative Review Team shall consist of the Director (Chair), City Engineer, Fire Chief, Economic Development Manager, Parks and Open Space Director, Police Chief, and Chief Building Official, or their representatives, and any other members appointed by the City Manager as deemed necessary, either as permanent or temporary members. (c) The ART may use the services of other professionals, such as architectural, engineering, and other consultants as they deem necessary, to advise the ART on the application of the provisions of this Chapter. BRIDGE STREET DISTRICT § 153.066 127 DEVELOPMENT CODE REVIEW & APPROVAL PROCEDURES & CRITERIA y J F— I� i O � ' 8�1a1 � Q u w J Q O 1 r� ER� Z1Nb'a t t� O ui IV CD CD CD CD LO CD ° U) cu ° cu U U) U U O 0 a L �L m m m LL I O O L O Q L O a) L Z a Z Z z N a) (B U a� � o U) U) O U U) U) U) U m m m m m 1 N V N o N L z N i c� U O U U U O O O � 2 2 2 U) U) U) cm m m m m U C: U a) m E o a o cu U 0 0 aa) U) 0 Q 0) o O_ = a m U as i i CL �V = O � N � �V *1 N ,= _ Z4 L � N V Lm V1 CL N y w O � Q V L m Q W 8�1a1 � Q u w J Q O 1 r� ER� Z1Nb'a t t� O ui IV CD CD CD CD LO CD ° U) cu ° cu U U) U U O 0 a L �L m m m LL I O O L O Q L O a) L Z a Z Z z N a) (B U a� � o U) U) O U U) U) U) U m m m m m 1 N V N o N L z N i c� U O U U U O O O � 2 2 2 U) U) U) cm m m m m U C: U a) m E o a o cu U 0 0 aa) U) 0 Q 0) o O_ = a m U as i i EXHIBIT D PROPOSED COMMUNITY FACILITIES 1. Block `B" Parking Garage — approximately 850 parking spaces. 2. Block "C" Parking Garage — approximately 850 parking spaces. 3. West Side, Block "Z" Parking Garage — approximately 240 parking spaces. 4. Block "A" Parking Garage — approximately 500 parking spaces. 5. Block "D" Parking Garage — approximately 560 parking spaces. 6. Block "F "- Parking Garage — approximately 580 parking spaces. 7. Block "G" Parking Garage —approximately 350 spaces 8. Block "F" Performing Arts Center, located at the southwest corner of Dale Drive and Bridge Park Avenue will be approximately 20,000 square feet, and will contain approximately 500 seats. 9. Block "A" Events Center, located at the northeast corner of State Route 161 and Riverside Drive will be approximately 20,000 square feet and will seat approximately 500 patrons for an event. D -1 V 1 LL 1 J U Vl m � « 0 0 N _ m p S o f i O O PT ' �� f 1.. Oki i� c N � � a 00 /% a 1 a z O D 0 o J O O u N a r 0 l0 W Y A a a rn a m E R w Cie m D -2 'tip----_ - F s Ix s NORM STREET I 1 ° 'l eg �I ° xl d � I I 3 4E -i I 1 � � 1 I -- o o= s I 2 4 P , a Z O 2 D 0 LL 0 ME Ub ,/ , I /, a 0 th Q a r 3 3 Y A a a m a m oe ao `\ w z Do m D -3 [This Page Intentionally Left Blank] EXHIBIT E PRELIMINARY ECONOMIC FEASIBILITY ANALYSIS ovp, ip u The Developer seeks to utilize the Act to facilitate the creation of the Authority, in order to finance, construct, operate and maintain the Community Facilities, which will support approximately 625,000 square feet of commercial properties, 975,000 square feet of for -rent residential properties, and 400,000 square feet of for -sale residential properties (the "Private Development ") subject to final City development review and approval, market adjustments, and other normal development feasibility considerations. Over the past 2 years, the Developer has conducted extensive financial analysis of the Private Development, utilizing multiple sources, including a residential feasibility analysis conducted by Danter Company, the Developer's history with similar projects in other Central Ohio communities, local and national commercial real estate broker input and market data provided by the Developer's commercial mortgage banker. As a result of this analysis, the Developer has completed a development plan for the Private Development that is generating strong interest from both private equity and the construction lending community. This, coupled with the proposed public investment by the City of Dublin, has driven negotiations with various prospective tenants, including hotel, restaurant, office, and retail users. The Developer has obtained signed letters of intent from a hotel flag and many commercial tenants and for -sale residential buyers at the rates needed to support the development costs under the proposed financing structure. The project's proforma is utilizing for -rent residential rates which are based on the Danter Company Study. The market preferences that have informed the development plan are projected to remain strong for many years to come. In summary, the current and expected future market conditions influencing the District are likely to remain strong. Additional economic considerations are described below. Area Development Pattern and Demand The subject property is located in Dublin, Franklin County, Ohio. Franklin County is part of the Columbus Metropolitan Statistical Area (MSA). Dublin is a northwest suburb of Columbus, Ohio, and geographically includes portions of Franklin, Delaware, and Union Counties. More specifically the property is located with the Bridge Street District. The Bridge Street District encompasses 1,100 acres that stretches from I- 270/US33 to Sawmill Drive and I -270 to southern properties on Bridge Street. The Bridge Street District is an entertainment, dining and retail destination with civic spaces, riverside park amenities and appealing housing options. The current phase is situated primarily along the banks of the Scioto River. This urban, walkable district is poised to be our next economic development driver attracting new businesses, jobs and atalented, young workforce. The Bridge Street District is Dublin's response to the substantial demographic shifts that are shaping new development patterns. Specifically, there is a renewed interest in urbanism and E -1 more densely developed, walkable neighborhoods ( "New Urbanism') — driven by young professionals' desire for single - person households and empty nesters seeking an active lifestyle in vibrant environment. This dynamic vision will define and differentiate Dublin, provide more choices for our residents and corporate citizens and add value to our existing homes. Unlike past demographic and housing trends, over 80% of the region's projected growth in households will consist of singles and couples without children, and analysts project many of these households will seek to live in a dense, walkable mixed -use, urban environment. This type of development pattern provides less reliance on automobile and instead on other forms of transportation, including walking, biking, and public transit. Such a development would be unique to the current City area market place, and the District's location relative to the City's Historic Core and River, as well as the high visibility provided by the adjacent roadway system, further reinforce the expectations for extremely strong market demand for the proposed development. Present and Future Socio - Economic Conditions a. Employment Centers Major employment concentrations in the Dublin area include the areas in and around the I- 270/US 33 interchange and environs to the west. Major employers in the area include Cardinal Health, IGS Energy, Express Scripts, Dublin City Schools, Ohio Health, Fiserv, Careworks, OCLC, Ashland Chemical, and Wendy's International among others. New employment growth in Dublin is expected with the growing area to the west of the City near the West Innovation District, led by the expansion of Ohio University. Total employment throughout Dublin is nearly 70,000 jobs. Dublin residents also are employed throughout Central Ohio and Downtown, with other major employers such as the State of Ohio, The Ohio State University, Honda, Scotts, Nationwide Insurance, JP Morgan Chase, and Express Brands, and Huntington Bank among others. b. Area Amenities Located in the heart of the Bridge Street District, the residents of the Bridge Park New Community Authority will have easy access to activities and attractions through the Columbus Metropolitan Area. The District is in close proximity to the Columbus Zoo, Downtown Columbus, and The Ohio State University. Additionally, the District provides easy access to the significant park system within Dublin, in addition to the Glacier Ridge Metro Park. The District is adjacent to the City's Historic District, the Scioto River and the City's planned park improvements in the immediate area, which will provide an extraordinary array of amenities in the vicinity of the District. c. Economic Patterns Insight 2050, a study recently led by Calthorpe and Associates, and was sponsored by Columbus 2020, MORPC, and the Urban Land Institute, projects that total population growth in Central Ohio will total over 500,000 people and will create nearly 300,000 new jobs by E -2 2040. This study further projects that a significant portion of the individuals creating the demand for new housing and jobs associated with this Private Development will be seeking the types of mixed -use, walkable environments planned for the District. The current unemployment rate for Central Ohio was 4.6% at year end, the lowest rate since October 2001, compared to the rate of Ohio (5.0 %), and the United States (5.6 %). These trends are expected to continue in the near future. d. Economic Patterns Census data for the City, as of 2010, is also attached hereto. E -3 , pai ORAWFORD HOYING auggere as Riverside Dr, Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won Nno. 1 mile adws E4 x1i Zulu Population 6,035 6,272 Mosaic 2,774 2,760 Housing Uni 2914 2,924 Total 6,272 Population Reporting One Race 6 White 4,737 Black 302 Asian 839 Spoke Other Race 197 Population Reporting To A or More Races 183 Total Hispanic 42e ?�WZeon Male 3 123 Ferre 3,149 wn by high, Total 6,273 Age 0 4 487 Age 5 9 430 Age 10 14 387 Age 15 19 320 Age 20 24 380 Age 25 29 762 Age 30 34 616 Age 35 39 493 Age 40 44 419 Age 45 49 365 Age 50 54 279 Age 55 59 256 Age 60 64 318 Age 65 69 JAC Age 70 74 130 Age 75 79 100 Age 80 84 74 Age 85+ 94 Age 18+ 4,761 Ag 559 /xieanic organ M l highl Sand and xa® p Total Population 33 0 Male 32 2 Ferree 33 8 Able Alone 34 7 Black Alone 27 8 th,eacan Indian Alone 15 0 Asian Alone 30 9 Cache Islander Alone 12 5 Spoke Other Race Alone 27 3 To A or More Races 16 9 Hispanic Population 25 distributor . Sup.dong US ski Census And Summary His I Ask censored Census 2DOO do. Ho gold geography E4 pai as ORAWFORD HOYING , asperse Riverside DU Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won only, HJ dir Ring I mile radius Lutanist : - byrrre real 2,760 100 0% Households with 1 Person 937 33 9% Hi Dh 2+ People 1,823 66 1% Family Households 1,589 57 6% Husband I'D darrhad 11199 43 4% path Gain Ch,ldren 579 21 0% Other Donald (No Spouse presex) 290 14 1% path (par Ch,ldren 244 8 8% personals Households 234 8 5% Al H.upei on Chddren 859 31 1% Multingenerstional Households 49 1 8% Unmarried Partner oueeholae MaleHernale Ids 6 8% Household z n Family Ha.� xaua I see Toral i 100 0% * People 678 426% * People 383 24 1% * People 322 20 3% package zss mgry lanmhame by sea Toral 1,171 100 0% 1 Person 937 so 0% * People 200 17 1% Paaage q Raxeamship and xanwrvau rape Toral 6,272 100 0% In Hi 6,272 its 0% In Family Households 4,836 77 1% Spouse 11180 is 8% Other Usage iss 3 0% Penelope 130 2 1% In o lls Households In Group ce Institutionalized Population 0 0 0% games Ni Hdumzml with sudden include any households GO people under age Is related or not n parei regi Unmarried! Penney hommeal are usually dopopfied as Hong households unlessnem danodher member One household pentato He householder Mmigenerational aid unmarried parder households are reported only tothemoc: pool Em ectmated block soup dozen which is pope coding polygons or no, standard geography Jampapperallymonce edudesnompganoyes plamprom US Cdi seeks 2010 Summary His I Pu9u9]➢p➢14 5 August 20 2014 E6 as CRAWFORD HOYING n accure Riverside op Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won i. ..i r Ring L radius miry xo.mrvoue uy. agent xp.eehaH t mile Total 1,589 100 0% Householder Age 15 44 838 52 7% Householder Age 45 54 225 20 5% Householder Age 55 64 247 15 5% Householder Age 65 74 102 6 4% Householder n a.e� Hai W �n d Bangui Total 1,171 100 0% Householder Age 15 44 616 52 6% Householder Age 45 54 162 13 8% Householder Age 55 64 185 15 8% Householder Age 65 74 94 8 0% Householder Age 75+ 114 sai[ Hl By FIRM a Hi hakil Total 2,759 100 0% Householder a Wh,te phone S,247 81 4% Householder a Black Alone 103 3 7% Householder a America, India, Alone 1 0 0% Householder a Ad., Alone 311 11 3% Henri P.afiA Islander phone 1 0 0% Householder . Some Other Race Alone 53 1 9% Householder a T .. r More Reaps 43 1 6% Hispanic Householder Hoozehold w;eh Ras a.sib f1i by goes, of HaRA, Total 11199 100 0% Householder a Wh,te phone Sea 77 1% Householder a Black Alone 41 3 4% Householder . American Indian Alone Householder a Asian Alone IRS 15 7% Islander None Householder a Some Other Race Alone 28 2 3% Husband IHe Fai with Hispanic Householder 54 a. sib Cuban milim (Na spauw) by Raw of HRuwhall Total S90 100 0% Householder a Wh,te phone R06 78 5% Householder a Black Alone 31 7 9% Householder a American Indian Alone 0 0 0% Householder a Asian Alone 27 6 9% Householder a Some Other Race Alone 16 4 1% Householder a To A or More Races S 2 3% Cohen degrades w¢M1 Hispanic Householder as s.xw mIN Ha.mhaJe by RRw aF Ha.whakil Total 1,171 100 0% Householder a Wh,te phone 11016 86 8% Householder a Black Alone 31 2 6% Householder a American Indian Alone 1 0 1% Householder a Asian Alone 96 8 2% Householder a Some Other Race Alone 9 0 8% cadmagg US (Sears Break (dra. 2010 Summary His I August 20 2014 E6 Total 2,950 Occupied Housing Units 2,760 Vacant Housing Units For Reard 116 as ORAWFORD HOYING 5 For Sale Only 23 Sold, net Occupied For aRearealbllahQe9onal use Ad, 0 Ohei 21 Tortal V acancy Race 5.643 ll by Ta n n in and cartel ill Total Cray Riverside Dr, Dublin, Ohio, 430172 0, red Free and Clear 248 Agreed Household Size Cray Riverside Dr Dublin, Ohio, 43017 khou so Hi i- Total Nno. 1 mde adws 1,152 Householder a Black Alone 24 LcnoiW da 83 rind' Total 2,950 Occupied Housing Units 2,760 Vacant Housing Units For Reard 116 Contest, net Occupied 5 For Sale Only 23 Sold, net Occupied For aRearealbllahQe9onal use For picked Workers 0 Ohei 21 Tortal V acancy Race 5.643 ll by Ta n n in and cartel ill Total 2,760 We Her Occupied 1,276 We red art a ag LOan 0, red Free and Clear 248 Agreed Household Size 2 44 Center Occupied 1,494 Nrea xv2 Rai i xh nB unite by In al xauwM1elnr Total 1,276 Householder a White phone 1,152 Householder a Black Alone 24 Householder Is Arnervan Indian Alone 1 Householder Is Asian Alone 76 Householder . Cocoa Islander phone 0 Householder a Store Other Race Alone We Her occupied rousing unrtz wOn hispanic householder xx BRIther ¢upred ranemB unite by In al raveahakil Total 1,484 Householder a White phone 1,095 Householder . Black Alone 79 Householder Is Arnervan Indian None Householder Is Asian Alone 235 Householder a Cocoa Islander phone I Householder . Store Other Race Alone 46 Center occupied Housing 96 Assail h1makflihald a by Hin BuI argon af" Usuahi Householder a White phone 2 14 Householder a Black Alone 2 88 Householder Is Arnervan Indian Alone 1 00 Householder . Asian Alone 2 68 Householder a Cocoa Islander phone 4 00 Householder a Store Other Race Alone Me Householder a To . or More amez 3 07 Householder Is hispanic an E -7 as ORAWFORD HOYING sun Riverside Dr, Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won L - - radius Busy Zulu Alli Ful Population 73,909 811080 0 93% Henri 30,003 33,601 1 14% Housing 31,728 35,701 119% an W al all p"Zi real 81,081 100 0% Population Reporting One Race 79,052 97 5% White 64,399 79 4% Black 3,321 4 1% American Indian 108 0 1% Asian 9,637 11 9% baci Islander 32 0 0% Some Other Race 1,555 1 9% Population Reporting To A or More Races 2,029 2 5% Taal Hi spanic a.5% pai ?�weenn Male 40 101 49 5% Damage 40,979 snow W n high, Total 81,081 100 0% Age 2Z 29 8,421 10 4% Age 65 69 11961 2 4% Age 75 79 971 1 2% Age 80 84 813 1 0% Age 65+ 5,965 z4% an Agee Sage aind Ra ®/xiepanicorgin Total Population 33 7 Male 32 9 Ferree 34 6 Able Alone As 3 Black Alone 29 2 American Indian Alone SO 9 Asian Alone 32 2 cache Dander Alone 3010 Some Other Race Alone 25 9 To A or More Races 16 3 Hispanic Population 2518 Rare Ni UlTarapopulation conbe dairy race (en.g201 are c.rni operated do, z. Sompou US Cysgi Canous 2010 Summary His I Am spooned Cepus 2300 do. Ho si geography Ai 20 , 2014 E -8 pai as ORAWFORD HOYING , asperse Riverside DU Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won i. 1 1 ..i r Ring 3 mile radius re real 33,601 100 0% Households with 1 Person 9,905 29 5% Hi Dh 2+ People 23,696 70 5% Family Households 20,689 61 6% Husband I'D darrhad 16,644 49 5% path Gain Ch,ldren 8,427 25 1% Other Donald (No Spouse presex) path (par Ch,ldren 2,472 7 4% personals Households 3,007 8 9% Al H.upei on Chddren 11,297 33 6% Multingenerstional Households 558 1 7% Unmarried Partner oaeholas MaleHernale 2,033 6 1% package Household Size 2 4 Fm Family ua I s Toral 20,688 100 0% 7+ People 221 1 1% package a. os mgN lanmhame b stra Toral 12,912 100 0% 1 Person 9,905 16 7% Paaape q Raxeamship and xanwrvau rraa Toral 811080 100 0% In Hi S0,904 99 8% In Family Households 64,446 79 5% Hi 20,691 25 5% Spouse 16,649 20 5% (pulp 24,033 29 6% Other Usage 1,904 2 3% Penelope 11169 1 4% In o lly Households 16,457 20 3% In Group Quarters Institutionalized Population 158 0 2% N.Unittiocionalzed Peculator is 0 0% games Ni Hdumzml with sudden include any households GO people undo age Is Nmd or not n am OezxM Formers parei regi Unmarried! Penney hommeal are usually dopopfied as Hong households unlessnem danodher member One household pentato He householder Mmigenerational aid unmarried parder households are reported only tothemoc: pool Em ectmated block soup dozen which is pope coding polygons or no, standard geography Jampapperallymonce edudesnompganoyes plamprom US Cdi seeks 2010 Summary His I Pu9u9]➢p➢14 9 August 20 ,2014 X10 c I as CRAWFORD HOYING n accure Riverside op Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won i. ..i r Ring 3 radius mlry xo.mrvoue uy. age of xp.eehaH t mile Total 20,690 100 0% Householder Age 15 44 9,813 47 4% Householder Age 45 54 5,446 26 3% Householder Age 55 64 3,484 16 8% Householder Age 65 74 1,220 5 9% Householder 727 ass nwwrvamR W age d Bangu OUer Total 12,912 100 0% Householder Age 15 44 7RS4 57 2% Householder Age 45 54 1,833 14 2% Householder Age 55 64 1,789 13 9% Householder Age 65 74 789 6 1% Lan eai[ eebel By FIRM a H hakier Total 33,601 100 0% Householder a Wh,te phone 27,985 83 3% Householder a Black Alone 1,274 3 8% Householder a America, India, Alone 34 0 1% Householder a Ad., Alone 3,430 10 2% Henri P.afiA Islander phone 8 0 0% Householder . Some Other Race Alone 413 1 2% Householder a T .. r More Reaps 457 14% Hispanic Householder Hoozehold w;eh ses . x 9% f1i by goes, Ha RA, War Total 16,643 100 0% Householder a Wh,te phone 13,458 so 9% Householder a Black Alone 455 2 7% Householder . American Indian Alone Householder a Asian Alone 2,323 14 0% Islander None Householder a Some Other Race Alone 191 1 1% Husband IHe Famlie w¢6 Hispanic Householder axo msw Cuban miliex (Na spauw) by Raw of HRuwbRll Total 4,044 100 0% Householder a Wh,te phone asks 80 3% Householder a Black Alone 353 8 7% Householder a American Indian Alone 11 0 3% Householder a Asian Alone 236 5 8% Householder a Some Other Race Alone 115 2 8% Householder a To A or More Races so 2 0% Cohen degrades w¢M1 wroamc Householder an saw ngN HaumrvaJe by RRw aF Hauwhakil Total 12,912 100 0% Householder a Wh,te phone 11,280 87 4% Householder a Black Alone 465 3 6% Householder a American Indian Alone 11 0 1% Householder a Asian Alone 871 6 7% Householder a Some Other Race Alone 107 0 8% cadmagg US (Sears Break (dra. 2010 Summary His I August 20 ,2014 X10 c I ORAWFORD HOYING as Ad, Cray Riverside Dr, Dublin, Ohio, won 2 Cray Riverside Dp Dublin, Ohio, won 1, pro .3 mite adws I I a .I ,: Total 35,724 Occupied Housing Units 23,601 Vacant Housing Units For Reard 1,209 Contest, net Occupied 68 For Sale Only 355 Sold, net Occupied For aneerealblla/Qm9onal use For picked Workers 4 Ohei 191 Tortal V acancy Race ssw ll by Tan and cartel ill nm Total 33,601 We Her Occupied 19,185 We red art a 0, red Free and Clear 3,009 Agreed Household Size 2 64 Center Occupied 14,416 Agreed . x ao Rai i xh nB unite by In al Hsi Total 19,185 Householder a White phone 17,146 Householder a Black Alone 365 Householder Is Arnervan Indian Alone 10 Householder Is Asian Alone 1,423 Householder . Cocoa Islander phone 6 Householder a Store Other Race Alone We Her occupied Homing unrtz w On Hispanic Householder 241 BRIther ¢upred HanemB unite B In al Haveahakil Total 14,416 Householder a White phone 10,839 Householder . Black Alone 908 Householder Is Arnervan Indian None Householder Is Asian Alone 2,007 Householder a Cocoa Islander phone 2 Householder . Store Other Race Alone 246 occupied Housing 'w A ssn By Hin BuI of af" Usualhi Householder a White phone 2 33 Householder a Black Alone 2 65 Householder Is Arnervan Indian Alone 2 47 Householder . Asian Alone 2 79 Householder a Cocoa Islander phone 4 00 Householder a Store Other Race Alone 3 52 Householder a To . or More amez 2 71 Householder Is Hispanic 3 2 E-11 , pai ORAWFORD HOYING auggere as Riverside Dr, Dublin, Ohio, won 2 Riverside Dp Dublin, Ohio, won Nno. 5 mile Zeus - E 12 x1i Zulu Population 158,724 181,046 Mosaic 64,160 74,077 Housing Uni 67,257 78.635 Total 181,046 Population Reporting One Race 176,987 White 149,983 Black 6,471 Annercan Indian 229 Asian 17all baci Islander 59 Spoke Other Race 2,534 Population Reporting To A or More Races 4,059 Taal wzp Male 89,055 Ferree 91,991 Regulation, e9e Total 181,048 Age 0 4 11,645 Age 5 9 12,548 Age 10 14 12,838 Age 15 19 11,165 Age 20 24 10,679 Age 25 29 15,093 Age 30 34 13,268 Age 35 39 13,061 Age 40 44 13,222 Age 45 49 14,114 Age 50 54 13,897 Age 55 59 11,907 Age 60 64 9,422 Age 65 69 5,655 Age 70 74 3,980 Age 75 79 3,170 Age 80 84 2 Age 85+ 2,716 Age 18+ 136,278 Age 65+ 1 &187 M l ngeb Sand and flog® /hiepanic organ Total Population 36 3 Male 351 Ferree 37 4 Able Alone AS 3 Black Alone 29 2 th,eacan Indian Alone 26 9 Asian Alone 33 0 Cache Islander Alone 3010 Spoke Other Race Alone 25 6 To A or More Races 16 B Hispanic Population g Sup.dong US ski Census And Summary His I Ask censored Census 2DOO do. Ho gold geography E 12 pai as ORAWFORD HOYING , asperse Riverside op Dublin, Ohio, won 2 Riverside On Dublin, Ohio, won i. 1 1 ..i r Ring 5 mile radius Midnight byrrre Total 74,077 100 0% Households with 1 Person 20,564 27 8% Hi Dh 2+ People 53,513 72 2% Family Households 47,598 64 3% Husband I'D darrhad 39,798 53 7% path Gain Ch,ldren 19,084 25 8% Other Donald (No Spouse cresent) path (par Ch,ldren 4,556 6 2% Nomarmly Households 5,915 8 0% Al H.upei , on Chddren 24,499 33 1% Multingenerstional Households 11195 1 6% Unmarried Partner eaehelas MaleHernale 3,723 5 0% package Household Size 2 4 m Family ua I see Total 47,598 100 0% * People 2(hpin 42 7% * People 11,07p 23 3% * People 10,474 22 0% * People 11161 2 4% 7+ People 438 0 9% package F.m mlry l anmhame by sea Total 26,479 100 0% 1 Person 20,564 17 7% Paaape q Raxeamship and xanwrvau rape Total 181,046 100 0% In Hi DIDDS5 99 5% In Family Households 146,627 81 0% Hi 47,571 26 3% Spouse 39,767 22 0% (pulp 53,337 29 5% Other Usage 3,781 2 1% Penelope 2,170 1 2% In a lly Households 33,508 18 5% In Group Quarters Institutionalized Population 752 0 4% rvomnztwNonalzed peculator 159 0.1% games Ni Hdumzml with sudden include any households GO people unto age Id Nmd or not e amOuxM Formers parei regi Unmarried! Penney hommeal are usually dopopfied as Hong households unlessnem danoduar member One housetold pentato He householder Mmigenerational aid unmarried parder households are reported only tothetrac: pool Em ectmated block soup dozen which is pope ectmate polygons or no, standard geography Jampapperallymonce edudesnompganoyes Pu9u9]L 2014 1 August 20 2014 X14 as CRAWFORD HOYING , asoure Riverside op Dublin, Ohio, won 2 Riverside In Dublin, Ohio, won i. 1 1 ..i r Ring 5 mile radius miry xo.mrvoue By a"f xaiusur H Total 47,597 100 0% Householder Age 15 44 19,952 41 9% Householder Age 45 54 12,493 26 2% Householder Age 55 64 81901 IS 7% Householder Age 65 74 3,740 7 9% Householder 2,511 s.ats nwwrvame W<sed Bangui Total 26,480 100 0% Householder Age 15 44 13,334 50 4% Householder Age 45 54 3,790 14 3% Householder Age 55 64 3,978 15 0% Householder Age 65 74 2,177 8 2% Householder Age 75+ 3,201 12 1% Hl By Rl a Hi hakil Total 74,078 100 0% Householder I Wh,te phone 63,568 85 8% Householder I Black Alone 2,514 3 4% Householder I America, India, Alone so 0 1% Householder I Ad., Alone 6,295 8 5% Henri P.SfiA Islander phone is 0 0% Householder . Some Other Race Alone 678 0 9% Henri w Dh Hispanic Householder llxi maw mle f1i by Racy of HaRA, Wer Total 39,798 100 0% Householder I Wh,te phone 33,811 85 0% Householder I Black Alone 874 2 2% Householder . American Indian Alone Householder I Asian Alone 4,337 10 9% Islander None Householder I Some Other Race Alone 311 0 8% Husband IAs Famlie with Hispanic Householder exa x.aw Cuban milim (xe spauw) by Raw of Heuwhell Total 7,800 100 0% Householder I Wh,te phone tla Householder I Black Alone 620 7 9% Householder I American Indian Alone 21 0 3% Householder I Asian Alone 409 5 2% Householder I Some Other Race Alone 186 2 4% Householder I To A or More Races 157 2 0% abv Families w¢M1 Hispanic Householder aae saw nxN Ha.mhalJe by Raw aF Ha.whauer Total 26,479 100 0% Householder I Wh,te phone 23,353 88 2% Householder I Black Alone 11019 3 8% Householder I American Indian Alone 28 0 1% Householder I Asian Alone 1,548 5 8% Householder I Some Other Race Alone 181 0 7% cadmoss US (Agra Break (dra. 2010 Summary His I August 20 2014 X14 ORAWFORD HOYING as sun Cray Riverside or, Dublin, Cray Riverside Du Dublin, Ring 5 mile radius Ohio, won 2 Ohio, won 1, It ..i r Tatal newg unite by occupancy Total 78,653 100 0% Occupied Housing Units 74,077 94 2% Vacant Housing Units For Reard 2,168 2 8% Reented, net Occupied 125 0 2% For Sale Only 1,024 1 3% Sold, net Occupied For eVRearesainaVar3nainal Use Other Vacant 506 0 O Tortal V acancy Rare s.ew me uyr nnm suave and cartel Total 74,077 100 0% We Her Occupied 48,638 65 7% We red art a d 39,103 52 8% 0, red Free and Clear 9,535 12 9% Agreed Household Size 2 63 Center Occupied 25039 34 3% Awa zw Raman i none ng unneuy Roca as xaneervamar Total 48,638 100 0% H.uveh.lder a White phone 44,147 90 8% H.uveh.lder a Black Alone 793 1 6% H.uveh.lder a American Indian Alone C5 0 1% H.uveh.lder a Asian Alone VOWS 6 4% H.uveh.lder . Cook Islander phone 11 0 0% H.uveh.lder a Some Other Race Alone We ner occupied Housing Units am Hispanic Householder sza a.2% BRIther i xanewg unite by Ra® al Haneahakil Total 25,440 100 0% H.uveh.lder a White phone 19,421 76 3% H.uveh.lder . Black Alone 1,721 6 8% H.uveh.lder a American Indian Rene H.uveh.lder a Asian Alone 3,197 12 6% H.uveh.lder . Some Other Race Alone 528 2 1% Center pin Hai.n� z.zoo cow A H By Hin epanwaraw ah KUeahaWH[ H.uveh.lder a Black Alone 254 H.uveh.lder a American Indian Alone 2 50 H.uveh.lder a Cook Islander phone 3 17 H.uveh.lder a Some Other Race Alone 3 43 Retie: 2 72 eausnalder is Hispanic 3 17 cadmagg US Cei Break (ands gone Summary Big 1, Argue 202014 X15 [This Page Intentionally Left Blank] EXHIBIT F FINANCIAL PLAN The Developer seeks to create the Authority to promote and coordinate the financing, construction, operation and maintenance of Community Facilities that are estimated to cost $78 million to construct. These Community Facilities include approximately 3,930 parking spaces, a community events center, and a performing arts center. It is anticipated that the Finance Authority will issue approximately $90 million in Bonds to finance the Community Facilities. All Bonds will be subject to the approval of the City pursuant to the terms of development and cooperative agreements among the City, the Authority and the Developer. The Developer expects to construct 3 parking garages in the first phase of the project, one in Historic Dublin (approximately 240 parking spaces), and two on the east side of the Scioto River (approximately 1,700 parking spaces). Future garages will be developed as additional development is consummated and is available to provide financial support for the issuance of additional Bonds. The Bonds will be secured by the Community Development Charge as the primary source of repayment during the time that the Bridge Park Development will be 100% abated pursuant to the Tax Abatement. Once the Tax Abatement expires, TIF Service Payments will be the primary source of repayment for the Bonds. In the event the TIF Service Payments are not sufficient to pay the Bond Debt Service, the Community Development Charge will be levied and collected to cover the shortfall. Determination of Communitv Development Charges The Authority will impose a Community Development Charge on Chargeable Property (as defined hereinbelow), determined as generally described in this Exhibit F , which is intended to be a uniform fee. Alternatively, the Community Development Charge may be a dollar amount determined on the basis of the assessed valuation of real property or interests in real property in the District sold, leased, or otherwise conveyed by the Developer. In addition, there may be a component of the Community Development Charge that is determined on the basis of gross receipts of restaurants and other retail, excluding any use that is predominantly grocery, operating in the District, in an amount not greater than '/2 %, and a Community Development Charge that is determined on the basis of gross receipts of hotels operating in the District, in an amount not greater than 1 %. These funds would be collected by an independent collection agent engaged by the Authority and would be used to pay the Annual Amount. Calculation of Communitv Development Charge The Community Development Charge will be collected on Chargeable Property and will be calculated on a uniform basis with respect to four property types to be developed within the District, based on the square footage of such property type, and the effective real property tax millage rate for such property type (residential vs. commercial). It is anticipated that the four classifications will be as follows: Commercial — Properties classified as Commercial include restaurants, retail, fitness, hotels and all other development typically classified as commercial property for real F -1 property tax purposes (i.e., not classified as "residential /agricultural' use for real property tax purposes), except for -rent housing and property classifications described below as "Apartments," "Townhomes," or "Condos." Apartments — Properties classified as Apartments include for -rent residential property that is typically classified as commercial property for real property tax purposes and exclude property classifications described below as "Townhomes" or "Condos." Townhomes — Properties classified a Townhomes include owner - occupied residential property that is typically classified as "residential/agricultural' use for real property tax purposes and exclude the property classification described below as "Condos." Townhomes are typically accessed from the outside. Condos — Properties classified as Condos are owner - occupied residential property that is typically classified as "residential /agricultural' use for real property tax purposes that are located in a building with more than 3 stories. The entry to the individual units are from interior hallways. The formula for the Community Development Charge on each of the four classifications are expected to be determined as follows: Community Development Charge for that classification of use multiplied by the total square footage of the building on such tax parcel. It is expected that the Community Development Charge for each classification will be determined on the basis of comparable market data for each classification for similar properties in Franklin County. The final determination of the Community Development Charge per square foot for each classification will be included in the Declaration and Development Agreement to be entered into between the Developer and the City. The effective millage rate will never be less than the current effective tax rates for property within the District (87.783604 mills for residential property and 100.254 mills for non - residential commercial property). Allocation of Community Development Charges The Community Development Charges shall be allocated and applied in the following order (1) Bond Debt Service; (2) O &M; (3) City Contribution; (4) Supplemental Debt Service Reserve and a Supplemental Operating and Maintenance Reserve for maintenance and repair of Community Facilities; and (5) Optional redemption of Bonds. F -2 Supplemental Communitv Development Charge If the Community Development Charges as prescribed are not sufficient to pay Annual Amount in any year, an increased or supplemental Community Development Charge may be levied in the following manner: (a) The shortfall will be proportionately applied to all Chargeable Property (as defined hereinbelow). Proportionate application of the shortfall will be based on the valuation of each individual type of development divided by the summation of the valuation of all Chargeable Property in the District. (b) The proportionate allocation of the shortfall will result in an increased effective millage rate for Chargeable Property in an amount sufficient to pay the shortfall. Timing and Collection of the Communitv Development Charges The Community Development Charge will be imposed on Chargeable Property. "Chargeable Property" will be further defined in the Declaration but generally means all or any portion of a parcel in the District for which the Commencement Date has occurred. The "Commencement Date" means, with respect to a building located on a parcel, the earlier of (a) the date that a certificate of occupancy is issued for such building or (b) the date that the owner of such parcel requests, in writing, that the Authority impose the Community Development Charge at a level consistent with the development of such parcel. For the first year that the Community Development Charge is imposed on such parcel, a pro -rated Community Development Charge will be levied from the Commencement Date through the remainder of the calendar year. For example, if a certificate of occupancy is issued on March 31, nine - twelfths of the annual Community Development Charge will be levied on the property, due in the succeeding calendar year. Thereafter, the full Community Development Charge will be collected annually. As permitted by Section 349.07 of the Ohio Revised Code, the Authority is expected to certify the Community Development Charges to the Franklin County Auditor, who will enter the Community Development Charges on the tax list and duplicate of real property and certify the Community Development Charge to the Franklin County Treasurer for collection with the tax bills. In the event the Authority collects a Community Development Charge determined on the basis of gross receipts of restaurants and other retail, excluding any use that is predominantly grocery, and hotels operating in the District, these amounts would be collected by an independent collection agent engaged by the Authority and would be used to pay the Annual Amount. F -3 [This Page Intentionally Left Blank] EXHIBIT G THE DEVELOPER'S MANAGEMENT CAPABILITY Crawford Hoying Development Partners, Ltd. ( "Crawford Hoying "), is a regionally recognized developer whose track record already features a number of successful mixed -use projects across the State of Ohio, including The Lane in Upper Arlington, The Heights at Worthington Place in Worthington, and Water Street District in Dayton, Bridge Park will represent the next generation of quality and connected mixed -use development, as well as a vibrant and vital new investment in the future of their company's hometown. The principals of Crawford Hoying are as follows: Brent Crawford is a Principal and Founder in the full services real estate firm Crawford Hoying and family of companies. Brent has guided the vision of the company for the past 20 years, which he has grown from a single investment property in 1994 to one of the largest real estate firms in Columbus, Ohio. The residential and commercial real estate brokerages alone manage over 2,000,000 S.F. of commercial properties, and have closed over $2.4 billion in transactions. Brent is currently guiding the development of $500 million in new developments to be completed over the next three years, and manages the company's relationships with over 100 equity investors. He has spoken at many events as a guest speaker covering topics such as current real estate trends, multi - family markets, and development growth in central Ohio. In addition, Brent taught property management and real estate trends for two years at the Fisher College of Business at Ohio State University. Bob Hoying returned to central Ohio in 2002 after a seven -year career as a quarterback with the Philadelphia Eagles and Oakland Raiders in the National Football League. The former Ohio State Buckeye had earlier befriended Brent Crawford during a chance pairing on the golf course in 1998. Upon his return to the Columbus area, the two men partnered to purchase the 252 -unit apartment community Gateway Lakes in 2002. Within ten years the pair had grown their partnership into a full service real estate company, managing over 20 apartment communities, over 1 million S.F. in commercial real estate, and becoming major contributors in Central Ohio real estate development. Like Brent Crawford, Bob takes an active role in guiding the company's $500 million in new developments. His role includes several facets of the development process, including land acquisition, property due diligence, closing requirements, and the obtainment of city entitlements. Nelson Yoder has extensive and diverse experience in financial analysis, architecture and construction, which provide him with a uniquely broad understanding of all aspects of real estate development. He holds an MBA focused in Real Estate Development and Construction Management from the University of Cincinnati and a Bachelor's Degree of Architecture from Ball State University. Nelson worked with large Columbus, Ohio firm M +A Architects for over a decade, eventually rising to the position of Partner while overseeing the master planning, zoning, design, leasing coordination, and construction of over 7,500,000 S.F. of Mixed -Use, Retail, Office, Multifamily, Hospitality, Religious and Industrial projects. Nelson is a licensed architect, earning his certification from NCARB in 2004, and LEED Accreditation in 2008. In 2010, Nelson co- founded Real Estate Development Advisors where his responsibilities included financial modeling, procurement of public subsidies, market analysis and management of G -1 consultant teams. Nelson joined Crawford Hoying Development in 2012 to facilitate the firm's development of more Class A mixed -use projects. Matthew Starr is the Director of Development for Crawford Hoying, joining the team in April, 2014. In that role with Crawford Hoying, Starr has involvement in all aspects of development, including acquisitions /due diligence, deal structuring, planning/design, government negotiations, leasing, financing, and construction. Prior to joining Crawford Hoying, Starr was the Director of Real Estate Equities for Nationwide Realty Investors, Ltd., for nearly ten years. While at NRI, Starr was involved in all phases of the development of Grandview Yard, a 100 acre mixed -use project in Grandview Heights, OH. Starr began his career in Real Estate Finance for National City Bank (now PNC Bank), from 1995 -2004. Starr is a 1994 graduate of Saginaw Valley State University (BBA), and a 2002 graduate of The Weatherhead School of Management at Case Western University (MBA). Russ Hunter joined Crawford Hoying Development in 2013 as Design Director, overseeing both architectural vision and interior design for all of the new developments. After earning his degree from Miami University, Russ moved to Columbus where he eventually became Senior Designer at M +A Architects for more than 8 years. At M +A Architects he played a key role in the design of more than a dozen mixed -use projects, giving him a deep understanding of mixed -use neighborhood design and planning. At Crawford Hoying Development, he works with the entire project team to create a vision for the project site's future through site planning, building programming and architectural design and works with the team to create a beautiful and financially viable project. G -2 [This Page Intentionally Left Blank]