The URL can be used to link to this page

Home My WebLink About05-04-09 Carmel Smart CodeCI OF CAR CARMEL, INDIANA z0 0 9 a r- a- �r A x T =•�P U D•=C A BQ'�i~. D RA F T FOR INTERNAL USE ONLY SMARTCODE GUIDE VERSION 05.04.09 THE CITY OF CARMEL City Patrons TOWN PLANNING URBAN DESIGN COLLABORATIVE City Planners CITY OF CARMEL SMARTCODE TABLE OF CONTENTS Carmel, Indiana ARTICLE 1. GENERAL TO ALL PLANS 1.1 AUTHORITY 1.2 APPLICABILITY 1.3 INTENT 1.4 PROCESS 1.5 WARRANTS AND VARIANCES 1.6 SUCCESSION ARTICLE 2. SECTOR PLANS 2.1 INSTRUCTIONS 2.2 SEQUENCE OF SECTOR DETERMINATION 2.3 (0 -1) PRESERVED OPEN SECTOR 2.4 (0 -2) RESERVED OPEN SECTOR 2.5 (G -1) RESTRICTED GROWTH SECTOR 2.6 (G -2) CONTROLLED GROWTH SECTOR 2.7 (G -3) INTENDED GROWTH SECTOR 2.8 (G -4) INFILL GROWTH SECTOR 2.9 (SD) SPECIAL DISTRICTS ARTICLE 3. P 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 JEW COMMUNITY REGULATING PLANS INSTRUCTIONS SEQUENCE OF COMMUNITY DESIGN COMMUNITY TYPES TRANSECTZONES CIVIC ZONES SPECIAL DISTRICTS THOROUGHFARE STANDARDS DENSITY CALCULATIONS SPECIAL REQUIREMENTS ARTICLE 4. INFILL COMMUNITY REGULATING PLANS 4.1 INSTRUCTIONS 4.2 COMMUNITY TYPES 4.3 TRANSECT ZONES 4.4 CIVIC ZONES 4.5 SPECIAL DISTRICTS 4.6 PRE EXISTING CONDITIONS 4.7 SPECIAL REQUIREMENTS www.tpudc.com 0 2009 Town Planning Urban Design Collaborative LLC ARTICLE 5. BUILDING LOT REGULATING PLANS 5.1 INSTRUCTIONS 5.2 PRE EXISTING CONDITIONS 5.3 SPECIAL REQUIREMENTS 5.4 CIVIC ZONES 5.5 SPECIFIC TO T1 NATURAL ZONE 5.6 BUILDING DISPOSITION 5.7 BUILDING CONFIGURATION 5.8 BUILDING FUNCTION 5.9 PARKING AND DENSITY CALCULATIONS 5.10 PARKING LOCATION STANDARDS 5.11 LANDSCAPE STANDARDS 5.12 SIGNAGE STANDARDS ARTICLE 6. STANDARDS AND TABLES TABLE 1 TRANSECT ZONE DESCRIPTIONS TABLE 2 SECTOR /COMMUNITY ALLOCATION TABLE 3A VEHICULAR LANE DIMENSIONS TABLE 3B VEHICULAR LANE& PARKING ASSEMBLIES TABLE 4A PUBLIC FRONTAGES GENERAL TABLE 4B PUBLIC FRONTAGES SPECIFIC TABLE 4C THOROUGH FARE ASSEMBLIES TABLE 5 PUBLIC LIGHTING TABLE 6 PUBLIC PLANTING TABLE 7 PRIVATE FRONTAGES TABLE 8A BUILDING CONFIGURATION TABLE 8B BUILDING TYPES SPECIFIC TABLE 9 BUILDING DISPOSITION TABLE 10 BUILDING FUNCTION PARKING TABLE 11 PARKING CALCULATIONS TABLE 12 SPECIFIC FUNCTION USE TABLE 13 CIVIC SPACE TABLE 14 SMARTCODE SUMMARY TABLE 15A FORM -BASED CODE GRAPHICS T3 TABLE 15B FORM -BASED CODE GRAPHICS T4 TABLE 15C FORM -BASED CODE GRAPHICS T5 TABLE 15D FORM -BASED CODE GRAPHICS T6 TABLE 16 SPECIAL DISTRICT STANDARDS TABLE 17 DEFINITIONS ILLUSTRATED ARTICLE 7. DEFINITIONS OF TERMS SC3 CITY OF CARMEL SMARTCODE ARTICLE 1. GENERAL TO ALL PLANS Carmel, Indiana 1.1 AUTHORITY 1.1.1 The action of the City of Carmel, Indiana (the "City in the adoption of this Code is authorized under the Code of the State of Indiana (the "State Code (the "State Code Sections 36 -7 -4, et seq. 1.1.2 This Code was adopted as one of the instruments of implementation of the public purposes and objectives of the Carmel Clay Comprehensive Plan (the "Compre- hensive Plan This Code was adopted upon and may be amended only by recom- mendation by the City of Carmel Plan Commission the "Plan Commission to and approval by the City of Carmel City Council (the "City Council) in accordance with applicable ordinances, rules and regulations of the City relating to amendments to the City's zoning ordinances and /or maps, as applicable. In the adoption hereof, the Plan Commission and City Council have determined that this Code is in accordance with the existing Comprehensive Plan, as required by the State Code and by its adoption hereof, the City Council certifies and declares such determination. Any application forapproval of any Plan under this Code shall demonstrate conformance of such Plan to the Comprehensive Plan and this Code hereby is declared to be in accord with the Comprehensive Plan. 1.1.3 This Code was adopted to promote the health, safety and general welfare of the City and its citizens, including protection of the environment, conservation of land, energy and natural resources, reduction in vehicular traffic congestion, more efficient use of public funds, health benefits of a pedestrian environment, historic preservation, education and recreation, reduction in sprawl development, and improvement of the built environment, preservation of open space and provision of growth areas. 1.1.4 Each Plan approved pursuant to this Code may be amended only in accordance with applicable ordinances, rules and regulations of the City relating to amendments to the City's zoning maps and ordinances, as applicable. 1.1.5 This entire Code shall constitute a portion of and an amendment to, and is incorporated by reference into, the Comprehensive Plan and zoning, planning, development, and subdivision codes, ordinances and regulations. 1.2 APPLICABILITY 1.2.1 a. This Code shall be the exclusive and mandatory land use zoning, planning, sub- division and development ordinance in the Downtown SmartCode Area depicted on Table_ hereof and in any other parts of the City forwhich a Community Regulating Plan is approved underArticle 3 or 4 hereof. In all other cases, this Code shall be an option that may be elected by an owner in lieu of proceeding under the Existing Local Codes. In any area of the City covered by an approved Community Regulat- ing Plan, this Code, the applicable Community Regulating Plan and any approved Building and Lot Plan shall comprise the sole land planning, zoning, subdivision, and development regulation for such area, which shall supersede and replace in all respects any other zoning ordinance, zoning map, subdivision ordinance, plan- ning ordinance, development ordinance or overlay district ordinance previously applicable thereto. Without limitation to the foregoing, no additional architectural or design approval shall be required for any Plans, development, project, building, renovation or redevelopment approval under this Code. [CITY TO CONFIRM] b. The existing City Zoning and Subdivision Ordinances (the "Existing City Codes shall continue to be applicable to issues not covered by this Code except where www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC5 ARTICLE 1. GENERAL TO ALL PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 1.2.2 1.2.3 1.2.4 1.2.5 1.2.6 a the Existing City Codes would be in conflict with Section 1.3 Intent. The provisions of this Code, when in conflict, shall take precedence over those of other codes, ordinances, regulations and standards except City and State Health and Safety Codes. Capitalized terms used throughout this Code may be defined in the text of Articles 1 -6 or in Article 7 Definitions of Terms. Article 7 contains regulatory language that is integral to this Code. Those terms not defined in Article 7 shall be accorded their commonly accepted meanings. In the event of conflicts between these definitions and those of the Existing City Codes, those of this Code shall take precedence. The metrics of Article 6 Standards and Tables are an integral part of this Code. However, the diagrams and illustrations in any acompanying annotation or appendix shall be considered explanatory only. Provisions of this Code are activated by "shall' when required; "should" when recom- mended; and "may" when optional. Where in conflict, numerical metrics shall take precedence over graphic metrics. Uses of existing building(s) that legally do not conform to this Code with respect to Function may continue as non conforming uses, as contemplated in Chapter 28 of the Existing City Codes. At such time as any such uses may no longer continue as non conforming uses or improvements under Chapter 28, such uses shall be required to conform to the requirements of this Code without regard to the first sentence of this section 1.2.6a. b. Any building, appurtenance, or other improvement which legally existed immediately prior to the adoption of this Code that does not comply with the provisions of this Code in any way other than with respect to Function may continue in existence as a non conforming building, appurtenance or other improvement until a Substantial Modification occurs or is requested with respect thereto, at which time such building, appurtenance, development, lot or other improvement shall be required to comply to all applicable provisions of this Code without regard to the first sentence of this Section 1.2.6b. c. Any property that has been granted approvals under the Existing City Codes to such extent as is necessary for such approvals to have created Vested Rights, as defined in the Existing City Codes, may proceed in accordance with such approvals. The owner of any such property, however shall be entitled to elect to make application under this Code in lieu of proceeding under such approvals. In that case, the application under this Code shall be given priority processing by placing the same ahead of prior filed applications to the extent possible while still complying with applicable procedures related to such prior filed applications, and all additional application fees for application under this Code shall be waived for application under this Code. d. Provided that all requirements of Article 5 of this Code for the applicable Transect Zone in which a Lot is situated are complied with other than lot dimensions and setbacks, which shall continue to be governed by the Existing City Codes in effect on the date immediately proceeding the adoption of this Code, any subdivided lot that legally existed pursuant to an approved final subdivision plat immediately prior to the adoption of this Code shall continue to legally exist from and after the date of such adoption unless and until such time as a Community Regulating Plan covering such lot is approved subsequent to the approval of the Initial Community Regulating Plan. www.tpudc.com SC6 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 1. GENERAL TO ALL PLANS Carmel, Indiana 1.3 INTENT The intent and purpose of this Code is to enable, encourage and qualify the imple- mentation of the following policies: 1.3.1 THE REGION a. Thatthe region should retain its natural infrastructure and visual character derived from topography, woodlands, farmlands and riparian corridors. b. That growth strategies should encourage Infill and redevelopment in parity with New Communities. c. That development non contiguous to urban areas should be organized in the pattern of Clustered Land Development "CLD Traditional Neighborhood Development "TND or Regional Center Development "RCD d. That development contiguous to urban areas should be structured in the pattern of Infill TND or Infill RCD and be integrated with the existing urban pattern. e. That transportation Corridors should be planned and reserved in 000rdination with land use. f. That green corridors should be used to define and connect the urbanized areas. g. That the region should include a framework of transit, pedestrian, and bicycle systems that provide alternatives to the automobile. 1.3.2 THE COMMUNITY a. That neighborhoods and Regional Center Development should be compact, pedestrian- oriented and Mixed Use. b. That neighborhoods and Regional Center Development should be the preferred pattern of development and that Districts specializing in a single use should be the exception. c. That ordinary activities of daily living should occur within walking distance of most dwellings, allowing independence to those who do not drive and promoting a healthy lifestyle. d. That interconnected networks of Thoroughfares should be designed to disperse traffic and reduce the length of automobile trips. e. That within neighborhoods, a range of housing types and price levels should be provided to accommodate diverse ages and incomes. f. That appropriate building Densities and land uses should be provided within walking distance of transit stops. g. That Civic, institutional, and Commercial activity should be embedded in down- towns, not isolated in remote single -use complexes. h. That schools should be sized and located to enable children to walk or bicycle to them. i. That a range of Open Space including Parks, Squares, and playgrounds should be distributed within neighborhoods and downtowns. 1.3.3 THE BLOCK AND THE BUILDING a. That buildings and landscaping should contribute to the physical definition of Thoroughfares as Civic places. b. That development should adequately accommodate automobiles while respecting the pedestrian and the spatial form of public areas. c. That the design of streets and buildings should reinforce safe environments, but not at the expense of accessibility. d. That architecture and landscape design should grow from local climate, topog- raphy, history, and building practice. e. That buildings should provide their inhabitants with a clear sense of geography and climate through energy efficient methods. www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC7 ARTICLE 1. GENERAL TO ALL PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana f. That Civic Buildings and public gathering places should be provided as locations that reinforce community identity and support self government. g. That Civic Buildings should be distinctive and appropriate to a role more important than the other buildings that constitute the fabric of the city. h. That the preservation and renewal of historic buildings should be facilitated, to affirm the continuity and evolution of society. i. That the harmonious and orderly evolution of urban areas should be secured through form -based codes. 1.3.4 THE TRANSECT a. That Communties should provide meaningful choices in living arrangements as manifested by distinct physical environments. b. That the Transect Zone descriptions on Table 1 shall constitute the Intent of this Code with regard to the general character of each of these environments. 1.4 PROCESS 1.4.1 The City hereby confirms the [Chairman of the City Technical Advisory Committee, the Zoning Administrator, the Chairman of the Plan Commission, the Chairman of the Carmel Redevelopment Commission and the Chairman of the City Architecture, Design, Development and Landscape Committee as] the Plan Review Committee "PRC under this Code to process applications and plans for proposed projects and approve or deny certain administrative matters to the extent authorized in this Code. 1.4.2 The geographic locations of the Sectors, the standards for theTransect Zones and the Initial Community Regulating Plan for the Downtown SmartCode Area shall be determined as setforth in Article 2, Article 3, Article 4, and Article 5 through a process of public consultation with approval by the City Council. Proof of compliance with the Sectors so determined shall be required as a condition to the approval of any Community Regulating Plan or other Plan. The standards for the Transect Zones and the Community Types permitted in each Sector shall be applicable to each development, building or Plan under this Code. 1.4.3 An owner may appeal a decision on any Plan as set forth under the Existing City Codes. 1.4.4 Should a violation of an approved Community Regulating Plan occurduring construc- tion, or should any construction, site work, or development be commenced without an approved Community Regulating Plan or Building and Lot Regulating Plan, the the Zoning Administrator has the right to require the owner to stop, remove, and /or mitigate the violation, or to secure a Variance to cover the violation. 1.5 WARRANTS AND VARIANCES 1.5.1 There shall be two types of deviation from the requirements of this Code: Warrants and Variances. Whether a deviation requires a Warrant or Variance shall be deter- mined by the Zoning Administrator. [consider deferring Warrants to existing Zoning Waiver Process.] 1.5.2 A Warrant is a ruling that would permit a practice that is not consistent with a specific provision of this Code but is justified by the provisions of Section 1.3 Intent. The Zoning Administrator shall have the authority to approve or disapprove administra- tively a request for a Warrant. [John to advise as to whether a Warrant is ok under state law]. 1.5.3 AVariance is any ruling on a deviation other than a Warrant. There are two types of p www.tpudc.com SC8 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 1. GENERAL TO ALL PLANS Carmel, Indiana Variance, a Function Variance and a Development Standards Variance. A Function Variance shall be required for a non Warrant Deviation from the Function require- ments under this Code and shall be granted only in accordance with the procedures of Chapter of the Existing City Codes applicable to Use Variances. A Develop- ment Standards Variance shall be required for all other non Warrant Deviations from the requirements of this Code and shall be granted only in accordance with the procedures of Chapter of the Existing City Codes applicable to Development Standards Variances.. 1.5.4 The request for a Variance shall not subject the entire application to approval in the Variance proceedings, but only that portion necessary to rule on the specific issue requiring the relief. 1.6 SUCCESSION 1.6.1 Twenty years after the approval of a Community Regulating Plan, each Transect Zone, except the T1 Natural and T2 Rural Zones, shall be considered for rezoning to the successional (next higher) Transect Zone, in accordance with the Existing Local Codes. ARTICLE 1. SMARTCODE MODULES 1.7 FOR INCENTIVES 1.8 FOR AFFORDABLE HOUSING INCENTIVES 1.9 FOR HAZARD MITIGATION STANDARDS 1.10 FOR HAZARD MITIGATION STANDARDS 1.11 APPEALS Any decision on a Plan, Warrant or Variance application may be appealed by the applicant to the City Board of Zoning Adjustment "BZA in accordance with the Existing City Codes. www. tp udc. com ?009 Town Planning c& Urban Design Collaborative LLC SC9 ARTICLE 2. SECTOR PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 2.1 DIRECTIONS 2. 1.1 a. This Article governs the preparation of Sector Plans and amendments thereto "Sector Plans that allocate Sectors for the purpose of identifying open preserved areas, open reserve areas that may be preserved in the future, and growth areas. Sections 2.5, 2.6, 2.7 and 2.8 prescribe the Community Types permitted in each Growth Sector. Articles 3 and 4 regulate the standards of those Community Types. b. The provisions of this Article shall constitute a portion of the Comprehensive Plan and Zoning and Subdivision Ordinances, including without limitation Articles 3 and 4 hereof. c. A Sector Plan or any amendment thereto shall be prepared by the Department of Community Services (the "Department and /or consultants under its supervision. The process shall involve citizen participation and shall require the recommendation of the Plan Commission to and approval by the City Council. d. The Initial Sector Plan (or any amendment thereof) shall be prepared by or on behalf of the Plan Department and shall be subject to recommendation by the Planning Commission to, and approval of the City Council in the same manner as an amendment to the City's Zoning Map. e. Once the Initial Sector Plan (or any amendment thereof) has been adopted, such Sector Plan (as may have been amended) may be amended: (i) upon application of an owner with respect to such portion of area covered thereby as is owned by such owner, (ii) at the request of the Department or Zoning Administrator or (iii) at the request of the Planning Commission or City Council. 2.1.2 Sector Plans shall integrate the largest practical geographic area, overlapping property lines as necessary and municipal boundaries if possible. 2.1.3 Sectors are defined in Article 2 and are comprised of Open Space and growth areas. Growth areas are intended for the development of Communities, defined in Article 3 and Article 4, which in turn are comprised of Transect Zones, defined by the elements appropriate to them in Article 5 and Article 6. 2.1.4 Sector Plans shall be prepared by the Department and /or consultants under its supervision. The process shall involve citizen participation, Planning Commission recommendation to, and the approval of the City Council. 2.1.5 a. The directions and provisions of this Article 2 shall be considered to be among the essential components of this Code and each of the otherArticles hereof. Any Plan submitted under this Code, whether at the scale of the Sector, the Community or the Building and Lot, shall be reviewed for and shall be subject to compliance with this Article as well as each of the other Articles hereof. b. The provisions of this Article and the Sector Plan adopted pursuant hereto shall constitute an integral portion of the City's zoning, planning, subdivision and devel- opment ordinances. c. Any amendment to the Sector Plan shall be subject to compliance with all provi- sions of the Existing City Codes relating to amendments to the City zoning map. Without limitation, this Article shall be deemed to be an integral part of Articles 3, 4 and 5 hereof and an adopted Sector Plan, as may be amended, shall be deemed to be an integral part of each New Community Regulating Plan, Infill Community Regulating Plan or Building and Lot Plan submitted or approved under Article 3, 4 or 5 hereof. www.tpudc.com SC 1 Q 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 2. SECTOR PLANS Carmel, Indiana 2.2 SEQUENCE OF SECTOR DETERMINATION In preparing a Sector Plan, the determination of Sector designations shall be made in the following sequence: 2.2.1 Preserved Open Sectors (0 -1) shall be designated and mapped using the criteria listed in Section 2.3. 2.2.2 Reserved Open Sectors (0 -2) shall be mapped using the criteria listed under Section 2.4. 2.2.3 Infill Growth Sectors (G -4) shall be mapped as described in Section 2.8. These areas may be redeveloped pursuant to Infill Community Regulating Plans according to Article 4 of this Code. 2.2.4 After mapping of the Sectors specified in paragraphs 2.2.1, 2.2.2. and 2.2.3, all remaining areas shall be mapped as either Restricted Growth Sectors (G -1), Controlled Growth Sectors (G -2) or Intended Growth Sectors (G -3) using the criteria set forth in Sections 2.5, 2.6 and 2.7, respectively. Those three Growth Sectors shall be available for new development pursuant to New Community Regulating Plans submitted and approved in accordance with, and to the extent prescribed in Article 3 of this Code. Within such Growth Sectors, the Community Types of Clustered Land Development (CLD), Traditional Neighborhood Development (TND), and Regional Center Development, shall be permitted to the extent set forth in Sections 2.5, 2.6 and 2.7. 2.2.5 Those areas that cannot or should not conform to one of the Community Types shall be allocated to one or more Special Districts. See Section 2.9. 2.2.6 Except in the Downtown SmartCode Area, in which the requirements of this Code are exclusive and mandatory, within the four Growth Sectors, development in accordance with the Existing City Codes remains as an option. 2.3 (0 -1) PRESERVED OPEN SECTOR 2.3.1 The Preserved Open Sector shall consist of Open Space that is protected from development in perpetuity. The Preserved Open Sector includes areas under envi- ronmental protection by law or regulation, as well as land acquired for conservation through purchase or by easement. 2.3.2 The Preserved Open Sector shall consist of the aggregate of the following categories: a. surface waterbodies b. protected wetlands c. protected habitat d. riparian Corridors e. purchased Open Space f. conservation easements g. transportation Corridors h. areas residual to Clustered Land Development (CLD) 2.3.3 Any development or construction within the Preserved Open Sector and the speci- fications required to do so subject to recommendation by the Plan Commission to, and approval of, the City Council. 2.3.4 To encourage the preservation of woodlands, farmlands, wetlands and other open spaces, the owner of a parcel in the Reserved Open Sector, the Restricted Growth Sector (G -1) or the Intended Growth Sector (G -2) may donate or sell land to the City, or may donate or sell land or grant a perpetual conservation easement with respect to land to a land trust or nature conservancy such that all development www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC 11 ARTICLE 2. SECTOR PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana rights with respect to such parcel in the Reserved Open Sector Growth (0 -2) or Restricted Growth Sector (G -1) shall terminate and such parcel shall be redesignated as Preserved Open Sector (0 -1). 2.4 (0 -2) RESERVED OPEN SECTOR 2.4.1 The Reserved Open Sector shall consist of land that has intrinsic value as Open Space but is subject to being developed because it is not within any of the catego- ries of permanently protected areas described in Section 2.3.2 and therefore is not protected by any binding method. 2.4.2 The Reserved Open Sector shall consist of the aggregate of the following categories: a. flood plain and flood hazard mitigation areas, including Special Flood Hazard Areas in which development is not prohibited, conditional or restricted b. steep slopes c. Open Space to be acquired d. Corridors to be acquired e. buffers to be acquired f. legacy woodland, farmland and viewsheds identified by the Department as being worthy of permanent protection by sale, gift or easement to the City or by sale, gift or easement to a nature or land conservancy or trust g. riparian corridors and drainage canals and ditches 2.4.3 (For HAZARD MITIGATION STANDARDS) 2.5 (G -1) RESTRICTED GROWTH SECTOR 2.5.1 The Restricted Growth Sector shall be assigned to areas that have value as Open Space but nevertheless are subject to development, either because the zoning already has been granted, it is not comprised of one of the categories set forth in paragraph 2.4.2, or because there is no legally defensible reason, in the long term, to deny the right to develop such areas. 2.5.2 Within the Restricted Growth Sector, development shall be in the pattern of Clustered Land Development (CLD). 2.6 (G -2) CONTROLLED GROWTH SECTOR 2.6.1 The Controlled Growth Sector shall be assigned to those locations that can support Mixed Use by virtue of proximity to an existing or planned Thoroughfare. 2.6.2 Within the Controlled Growth Sector, development shall be in the pattern of Clustered Land Development (CLD )and Traditional Neighborhood Development (TND). 2.6.3 Any Traditional Neighborhood Development (TND) on an existing or projected rail or Bus Rapid Transit (BRT) network may be redesignated in whole or in part as Transit Oriented Development (TOD) and permitted the higher Density represented by the Effective Parking allowance in Section 5.9.24. The use of a TOD overlay requires approval by Warrant. 2.7 (G -3) INTENDED GROWTH SECTOR 2.7.1 The Intended Growth Sector shall be assigned to those locations that can support substantial Mixed Use by virtue of proximity to an existing or planned regional Thoroughfare and /or transit. www.tpudc.com SC 12 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 2. SECTOR PLANS Carmel, Indiana 2.7.2 Within the Intended Growth Sector, development shall be in the pattern of Regional Center Developments (RCDs) and Traditional Neighborhood Developments (TNDs). 2.7.3 Any TND or RCD on an existing or projected rail or Bus Rapid Transit (BRT) network may be redesignated in whole or in part as TOD and permitted the higher Density represented by the Effective Parking allowance in Section 5.9.24. The use of a TOD overlay requires approval by Warrant. 2.8 (G -4) INFILL GROWTH SECTOR 2.8.1 The Infill Growth Sectorshall be assigned to areas already developed, having the potential to be modified, confirmed or completed in the pattern of Infill TNDs or Infill RCDs. 2.9 (SD) SPECIAL DISTRICTS 2.9.1 Special District designations shall be assigned to areas that, by their intrinsic size, Function, or Configuration, cannot conform to the requirements of a CLD, a TND, or an RCD as set forth in Article 3. 2.9.2 Conditions and Standards for development of Special Districts shall be subject to recommendation by the Plan Commission to, and approval by the City Council and shall be determined in public hearing of the City Council and recorded on Table 16. 2.9.3 Without limitation to the foregoing, no Special District shall be used to avoid compli- ance with the provisions of this Code. ARTICLE 2. SMARTCODE MODULES 2.4 FOR HAZARD MITIGATION STANDARDS www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC 1 3 ARTICLE 3. NEW COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 3.1 DIRECTIONS 3.1.1 An Initial Community Regulating Plan shall be prepared on behalf of the City for the Downtown SmartCode Area and submitted to the Planning Commission for recommendation to and approval by the City Council. Within any part of the City with respect to which an owner elects to develop in accordance with this Code, and within the Downtown SmartCode Area, development in the Reserved Open Sector (0 -2), the Restricted Growth Sector (G -1), Controlled Growth Sector (G -2), the Intended Growth Sector (G -3) and to the extent set out in Secton 3.1.6(c) below, the Infill Growth Sector (G -4), as shown on the Sector Plan, shall be subject to approval of a Community Regulating Plan conforming to the provisions of Article 3 and this Code. A development that complies with the Initial Community Regulating Plan shall be eligible for administrative approval by [the Zoning Administrator /the CRCJ. 3.1.2 New Community Regulating Plans may contain more than one Community and /or more than one Community Type. 3.1.3 Once the City Council approves the Initial Community Regulating Plan or any New Community Regulating Plan, the Plan area shall be marked on all zoning and other land use and land classification maps of the City as a SmartCode Community Plan- ning Area with all applicable Transect Zones, Thoroughfares and other elements indicated. 3.1.4 This Code shall be the exclusive and mandatory zoning regulation for the Down- town SmartCode Area and for any other area within the City which is a SmartCode Planning Area, and the provisions of this Code shall be applied in their entirety to such areas. 3.1.5 Any development within an area for which a Community Regulating Plan has been approved shall comply with such approved Community Regulating Plan unless and until another Community Regulating Plan is submitted and approved for such development pursuant to section 3.1.2 above. 3.1.6 Afterapproval of the Initial Community Regulating Plan under paragraph 3.1.1, New Community Regulating Plans may be submitted and approved under this Article for areas within the 0 -2 Reserved Open Sector, the G -1 Restricted Growth Sector, the G -2 Controlled Growth Sector and the G -3 Intended Growth Sector effective at such time as an amendment, or in addition to, the Community Regulating Plan in effect at such time. Any such amendatory or additional New Community Regulating Plan shall be: a. prepared by or on behalf of the City, upon request of the Planning Commission; b. prepared by or on behalf of the owner of the property; or c. prepared by or on behalf of one or more owners of property within the G -4 Infill Growth Sector comprising one or more adjoining parcels of at least 40 acres of contiguous property pursuant to Section 4.1.13 hereof, in which case such plan shall be subject to this Article 3 and treated in all respects as a New Community Regulating Plan submission. 3.1.7 Any New Community Regulating Plan application fora development that utilizes the Transect Zone assignments, Thoroughfares and all other elements of the then existing Community Regulating Plan applicable to such development and is otherwise in accordance with the pro visions of this Code, for the appropriate Sector within which the subject property is situated and requiring no Variances, shall be approved administratively by the [Zoning Administrator /CRCJ. Any www.tpudc.com SC 14 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 3. NEW COMMUNITY SCALE PLANS Carmel, Indiana other development shall require submission of a New Community Regulating Plan and shall be subject to approval by the CRC, recommendation by the Planning Commission to and approval of the City Council. [JOHN TOADVISE ON WHETHERADMINISTRATIVEAPPROVAL WILL WORK.] 3.1.8 A New Community Regulating Plan shall be prepared in accordance with Section 3.2 hereof and shall consist of the following: a. the applicant's demonstration of the consistency of such New Community Regulating Plan with the Intent provisions of this Code and the applicable Sector Plan; and b. one or more maps showing the following for each Community Unit in the plan area, in compliance with the standards described in this Article: i. the Outline of the Pedestrian Shed(s) and boundaries of the Community Unit(s) ii. Allocation and Location of Transect Zones iii. Assignment of Civic Zones according to an analysis of existing conditions and future needs iv. Densities v. Thoroughfare network vi. Assignment of Special Districts, if any vii. Special Requirements, if any viii. Itemization of requested Warrants or Variances, if any ix. Form -Based Chart and Graphics for each applicable Transect Zone in the form of Tables 15A -15F hereof. 3.1.9 ANewCommunity Regulating Plan (otherthan the Initial New Community Regulating Plan) shall include a preliminary site plan conforming to the requirements of Table 15 and Section 5.1.3a hereof. 3.1.10 The Sector Plan applicable to the New Community Regulating Plan site shall be deemed to be an integral part of each New Community Regulating Plan submitted or approved under this Code. 3.1.11 If a portion of a single parcel of land lies within more than one Growth Sector, then a New Community Regulating Plan applicable to such parcel may conform to any one of such applicable Sectors. 3.2 SEQUENCE OF COMMUNITY DESIGN 3.2.1 With respect to each New Community Regulating Plan, the site shall be structured using one or several Pedestrian Sheds, which shall be located according to exist- ing conditions and existing Common Destinations, such as Thoroughfares, traffic intersections, adjacent developments, natural features, Civic Space, a Civic Building, Commercial Center, transit center or natural features. The site may be larger than a single Pedestrian Shed and a Community Unit within the site may be smaller than its Pedestrian Shed. 3.2.2 The Pedestrian Sheds may be adjusted to include land falling between or outside them (an "Adjusted Pedestrian Shed but the extent of each shall not exceed the acreage limit specified in Section 3.3 for the applicable Community Type. Any Adjusted Pedestrian Shed becomes the boundary of the Community. 3.2.3 Areas of Transect Zones (Section 3.4) shall be allocated within the boundaries of each Community as appropriate to its type. See Section 3.3 and Table 14, Item a. 3.2.4 Civic Zones shall be assigned according to Section 3.5. www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC 1 5 ARTICLE 3. NEW COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 3.2.5 Special Districts, if any, shall be assigned according to Section 3.6. 3.2.6 The Thoroughfare network shall be laid out according to Section 3.7. 3.2.7 Density shall be calculated according to Section 3.8. 3.2.8 Notwithstanding adjustments pursuant to Section 3.2.2, any remnants of the site outside of the Adjusted Pedestrian Shed(s) shall be assigned to Transect Zones or Civic Space subject to approval by Warrant or Special District subject to approval by Variance. 3.3 COMMUNITY TYPES 3.3.1 New Community Regulating Plans shall provide for one or more Communities in the pattern of one of the following Community Types: 3.3.2 CLUSTERED LAND DEVELOPMENT (CLD) a. In addition to any otherCommunity Type permitted foreach such Sector, develop- ment within the 0 -2 Reserved Open Sector, the G -1 Restricted Growth Sector and the G -2 Controlled Growth Area shall be one or more Communities in the pattern of Clustered Land Development (CLD). b. A CLD shall be structured by one Standard Pedestrian Shed and shall consist of no fewer than 15 acres and no more than 80 acres. c. A CLD shall include Transect Zones as allocated on Table 2 and Table 14, Item a. A minimum of 50% of the Community shall be permanently allocated to a T1 Natural Zone and /or T2 Rural Zone. 3.3.3 TRADITIONAL NEIGHBORHOOD DEVELOPMENT (TND) a. In addition to any otherCommunity Type permitted foreach such Sector, develop- ment within the G -2 Controlled Growth Sector and G -3 Intended Growth Sector shall be one or more Communities in the pattern of Traditional Neighborhood Development (TND). b. A TND shall be structured by one Standard or Linear Pedestrian Shed and shall be no fewer than 80 acres and no more than 160 acres. See Article 4 for Infill TND acreage requirements in the G -4 Infill Growth Sector. c. A TND shall include Transect Zones as allocated on Table 2 and Table 14, Item a. d. Sites larger than 160 acres shall be designed and developed as multiple Com- munities, each subject to the individual Transect Zone requirements for its type as allocated on Table 2 and Table 14, Item a. The simultaneous planning of adjacent parcels is encouraged. e. In the T -4 General Urban Zone, a minimum Residential mix of three Building Disposition types (none less than 20 shall be required, selected from Table 9. 3.3.4 REGIONAL CENTER DEVELOPMENT (RCD) a. In addition to any other Community Type permitted for each such Sector, devel- opment Within the G -3 Sector Intended Growth Sector, or in the case of a New Community Regulating Plan prepared under Sections 4.1.6 and 3.1.4 (iii) hereof, G -4 Infill Growth Sector, shall be one or more Communities in the pattern of RCD. b. An RCD shall be structured on the basis of one Long Pedestrian Shed or Linear Pedestrian Shed and shall consist of no fewer than 80 acres and no more than 640 acres. See Article 4 for Infill RCD acreage requirements in the G -4 Infill Growth Sector. c. An RCD shall include Transect Zones as allocated on Table 2 and Table 14, Item a. www.tpudc.com SC 1 6 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 3. NEW COMMUNITY SCALE PLANS Carmel, Indiana d. For sites larger than 640 acres, an RCD may be adjoined without buffer by one or more TNDs, each subject to the individual Transect Zone requirements for TND as allocated on Table 2 and Table 14, Item a. The simultaneous planning of adjacent parcels is encouraged. 3.3.5 TRANSIT ORIENTED DEVELOPMENT (TOD) a. Any TND or RCD on an existing or projected rail or Bus Rapid Transit (BRT) network may be redesignated in whole or in part as TOD and permitted the higher Density represented by the Effective Parking allowance in Section 5.9.24. b. The use of a TOD overlay requires approval by Variance. 3.4 TRANSECT ZONES 3.4.1 Transect Zones shall be assigned and mapped on each New Community Regulating Plan according to the percentages allocated on Tables 2 and 14, Item a. 3.4.2 A Transect Zone may include any of the elements indicated for its T -Zone number throughout this Code, in accordance with Intent described in Table 1 and the metric standards summarized in Table 14. 3.4.3 There shall be a Residential Function within each New Community Regulating Plan providing for a minimum average number of dwelling units per acre of Net Acreage equal to 75% of the maximum Density permitted for the applicable Transect Zone. 3.5 CIVIC ZONES 3.5.1 GENERAL a. Civic Zones dedicated for public use shall be required for each Community and designated on the New Community Regulating Plan as Civic Space (CS) and Civic Building (CB). b. Civic Space Zones are public sites permanently dedicated to Open Space. c. Civic Building Zones are sites dedicated for buildings generally operated by not for profit organizations dedicated to culture, education, religion, government, transit and municipal parking, or for a use approved by the City Council. d. A Civic Zone may be permitted by Warrant if it does not occupy more than 20% of a Pedestrian Shed, otherwise it is subject to the creation of a Special District. See Section 3.6. e. Parking for Civic Zones shall be determined by Warrant. Civic parking lots may remain unpaved if graded, compacted and landscaped. 3.5.2 CIVIC ZONES SPECIFIC TO T1 T2 ZONES a. Civic Buildings and Civic Spaces within T1 Natural and T2 Rural Zones shall be permitted only by Variance. 3.5.3 CIVIC SPACE (CS) SPECIFIC TO T3, T3E, T3L, T4, T5 AND T6 ZONES The following shall be applicable to T -Zones T3, T3E, T3L, T4, T5 and T6: a. Each Pedestrian Shed shall assign at least 5% of its Urbanized area to Civic Space. b. Civic Spaces shall be designed as generally described in Table 13, approved by Warrant, and distributed throughout Transect Zones as described in Table 14, Item e. c. Those portions of the T1 Natural Zone that occur within a development parcel shall be part of the Civic Space allocation and shall conform to the Civic Space types specified in Table 13a or 13b. d. Each Pedestrian Shed shall contain at least one Main Civic Space. The Main www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC 1 7 ARTICLE 3. NEW COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana Civic Space shall be within 800 feet of the geographic center of each Pedestrian Shed, unless topographic conditions, pre- existing Thoroughfare alignments or other circumstances prevent such location. A Main Civic Space shall conform to one of the types specified in Table 13, Items b, c or d. e. Within 800 feet of every Lot in which a Residential use is allowed, a Civic Space designed and equipped as a playground shall be provided. A playground shall conform to Table 13, Item e. f. Each Civic Space shall have a minimum of 50% of its perimeter enfronting a Thoroughfare, except for playgrounds. g. Civic Spaces may be permitted within Special Districts by Warrant. 3.5.4 CIVIC BUILDINGS (CB) SPECIFIC To T3-T6 ZONES a. The owner shall covenant to construct a Meeting Hall or a Third Place in proxim- ity to the Main Civic Space of each Pedestrian Shed. Its corresponding Public Frontage shall be equipped with a shelter and bench for a transit stop. b. If the Plan Area has been designated as a proposed elementary school site by the Board of Education, one Civic Building Lot shall be reserved for an elementary school. The school site may be within any Transect Zone. Any playing fields should be outside the Pedestrian Shed. c. One Civic Building Lot suitable for a childcare building shall be reserved within each Pedestrian Shed. The owner or a homeowners' association or other com- munity council may organize, fund and construct an appropriate building as the need arises. d. Civic Building sites shall not occupy more than 20% of the area of each Pedestrian Shed. e. Civic Building sites should be located within or adjacent to a Civic Space, or at the axial termination of a significant Thoroughfare. f. Civic Buildings shall not be subject to the standards of Article 5. The particulars of their design shall be determined by Warrant. g. Civic Buildings may be permitted within Special Districts by Warrant. 3.6 SPECIAL DISTRICTS 3.6.1 Special District designations shall be assigned to areas that, by their intrinsic size, Function, or Configuration, cannot conform to the requirements of any Transect Zone or combination of zones. Conditions of development for Special Districts shall be determined based on public hearing of the approval by the Plan Commission and recommendation to and approval by the City Council and recorded on Table 16. 3.6.2 Special Districts shall be governed by any standards therefor contained on Table 16 hereof. Special Districts for which standards are not included in Table 16 hereof shall comply with the applicable standards of the Existing City Codes. 3.6.3 Without limitation to the foregoing, no Special District shall be used to avoid compliance with the provisions of this Code. 3.7 THOROUGHFARE STANDARDS 3.7.1 GENERAL a. Thoroughfares are intended for use by vehicular and pedestrian traffic and to p www.tpudc.com SC 18 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 3. NEW COMMUNITY SCALE PLANS Carmel, Indiana provide access to Lots and Open Spaces. b. Thoroughfares shall consist generally of vehicular lanes and Public Frontages. c. Thoroughfares shall be designed in contextwith the urban form and desired design speed of the Transect Zones through which they pass. The Public Frontages of Thoroughfares that pass from one Transect Zone to another shall be adjusted accordingly or, alternatively, the Transect Zone may follow the alignment of the Thoroughfare to the depth of one Lot, retaining a single Public Frontage throughout its trajectory. d. Within the most rural Transect Zones (T1 and T2) pedestrian comfort shall be a secondary consideration of the Thoroughfare. Design conflict between vehicular and pedestrian generally shall be decided in favor of the vehicle. Within the more urban Transect Zones (T3 through T6) pedestrian comfort shall be a primary consideration of the Thoroughfare. Design conflict between vehicular and pedestrian movement generally shall be decided in favor of the pedestrian. e. The Thoroughfare network shall be designed to define Blocks not exceeding the size prescribed in Table 14, Item c. The perimeter shall be measured as the sum of Lot Frontage Lines. Block perimeter at the edge of the development parcel shall be subject to approval by Warrant. f. All Thoroughfares shall terminate at other Thoroughfares, forming a network. Internal Thoroughfares shall connect wherever possible to those on adjacent sites. Cul -de -sacs shall be subject to approval by Warrant to accommodate specific site conditions only. g. Each Lot shall Enfront a vehicular Thoroughfare, except that 20% of the Lots within each Transect Zone may Enfront a Passage. h. Thoroughfares along a designated B -Grid may be exempted by Warrant from one or more of the specified Public Frontage or Private Frontage requirements. See Table 7. i. Standards for Bicycle Trails and Paths shall be as shown in Tables 3A and 4C, respectively. j. The standards for Thoroughfares within Special Districts shall be determined by Variance. 3.7.2 VEHICULAR LANES a. Thoroughfares may include vehicular lanes in a variety of widths for parked and for moving vehicles, including bicycles. The standards for vehicular lanes shall be as shown in Table 3A. b. A bicycle network consisting of Bicycle Trails, Bicycle Routes and Bicycle Lanes should be provided throughout as defined in Article 7 Definitions of Terms and allocated as specified in Table 14, Item d. Bicycle Routes should be marked with Sharrows. The Community bicycle network shall be connected to existing or proposed networks wherever possible. 3.7.3 PUBLIC FRONTAGES a. GENERAL TO ALL ZONES T1, T2, T3, T4, T5, T6 i. The Public Frontage contributes to the character of the Transect Zone, and includes the types of Sidewalk, Curb, planter, bicycle facilities, street signs, and street trees. ii. Public Frontages shall be designed as shown in Table 4A and Table 4B and allocated within Transect Zones as specified in Table 14, Item d. www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC 1 9 ARTICLE 3. NEW COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana iii. Within the Public Frontages, the prescribed types of Public Planting and Public Lighting shall be as shown in Table 4A, Table 4B, Table 5 and Table 6. The spacing may be adjusted by Warrant to accommodate specific site conditions. b. SPECIFIC TO ZONES T1, T2, T3, T3E AND T3L The following shall be applicable in T -Zones T1, T2, T3, T3E and T3L: i. The Public Frontage shall include trees of various species, naturalistically clustered, as well as understory. ii. The introduced landscape shall consist primarily of native species requiring minimal irrigation, fertilization and maintenance. C. SPECIFIC TO ZONE T4, T5, T6 The following shall be applicable in T -Zones T4, T5 and T6: i. The introduced landscape shall consist primarily of durable species requir- ing minimal irrigation, fertilizer and maintenance and being tolerant of soil compaction. d. SPECIFIC TO ZONE T4 The following shall be applicable in T -Zones T4: i. The Public Frontage shall include trees planted in a regularly- spaced Allee pattern of single or alternated species with shade canopies of a height that, at maturity, clears at least one Story. e. SPECIFIC TO ZONES T5, T6 The following shall be applicable in T -Zones T5 and T6: i. The Public Frontage shall include trees planted in a regularly- spaced Allee pattern of single species with shade canopies of a height that, at maturity, clears at least one Story. At Retail Frontages, the spacing of the trees may be irregular, to avoid visually obscuring the shopfronts. ii. Streets with a Right -of -Way width of 40 feet or less shall be exempt from the tree requirement. 3.8 DENSITY CALCULATIONS 3.8.1 All areas of the New Community Regulating Plan site that are not part of the 0 -1 Pre- served Sector shall be considered cumulatively the Net Site Area. The Net Site Area shall be allocated to the various Transect Zones according to the parameters specified in Table 14, Item a. 3.8.2 Density shall be expressed in terms of housing units per acre as specified for the area of each Transect Zone by Table 14, Item b. For purposes of Density calcula- tion, the Transect Zones include the Thoroughfares but not land assigned to Civic Zones. 3.8.3 Within the percentage range shown on Table 14, Item b for Other Functions, the housing units specified on Table 14, Item b shall be exchanged at the following rates: a. For Lodging: 2 bedrooms for each unit of Net Site Area Density. b. For Office or Retail: 1000 square feet for each unit of Net Site Area Density. c. The number of units exchanged shall be subject to approval by Warrant. 3.8.4 The housing and other Functions for each Transect Zone shall be subject to further adjustment at the building scale as limited by Table 10, Table 11 and Section 5.9. 3.9 SPECIAL REQUIREMENTS 3.9.1 A New Community Regulating Plan may designate any of the following Special www.tpudc.com SC20 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 3. NEW COMMUNITY SCALE PLANS Carmel, Indiana Requirements: a. A differentiation of the Thoroughfares as A -Grid and B -Grid. Buildings along the A -Grid shall be held to the highest standard of this Code in support of pedestrian activity. Buildings along the B -Grid may be more readily considered for Warrants allowing automobile- oriented standards. The Frontages assigned to the B -Grid shall not exceed 30% of the total length of Frontages within a Pedestrian Shed. b. Designations for Mandatory and /or Recommended Retail Frontage requiring or advising that a building provide a Shopfront at Sidewalk level along the entire length of its Private Frontage. The Shopfront shall be no less than 70% glazed in clear glass and shaded by an awning overlapping the Sidewalk as generally illustrated in Table 7 and specified in Article 5. The first floor shall be confined to Retail use through the depth of the second Layer. (Table 17, Item d) c. Designations for Mandatory and /or Recommended Gallery Frontage, requiring or advising that a building provide a permanent cover over the Sidewalk, either cantilevered or supported by columns. The Gallery Frontage designation may be combined with a Retail Frontage designation. d. Designations for Mandatory and /or Recommended Arcade Frontage, requiring or advising that a building overlap the Sidewalk such that the first floor Facade is a colonnade. The Arcade Frontage designation may be combined with a Retail Frontage designation. e. A designation for Coordinated Frontage, requiring that the Public Frontage (Table 4A) and Private Frontage (Table 7) be coordinated as a single, coherent landscape and paving design. f. Designations for Mandatory and /or Recommended Terminated Vista locations, requiring or advising that the building be provided with architectural articulation of a type and character that responds visually to the location, as approved by the CRC. g. A designation for Cross Block Passages, requiring that a minimum 8- foot -wide pedestrian access be reserved between buildings. h. A designation for Buildings of Value, requiring that such buildings and structures may be altered or demolished only in accordance with Municipal Preservation Standards and Protocols. [STAFF TO PROVIDE LIST OF ALL CONTRIBUTING BUILDINGS, HISTORICAL BUILDINGS AND ANY OTHER WORTHY BUILD- INGS] ARTICLE 3. SMARTCODE MODULES 3.5.2 b. FOR HAZARD MITIGATION STANDARDS 3.7 FOR ENVIRONMENTAL STANDARDS 3.7.3 a. FOR NATURAL DRAINAGE STANDARDS 3.7.3 c. FOR NATURAL DRAINAGE STANDARDS www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC21 ARTICLE 4. INFILL COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 4.1 DIRECTIONS 4.1.1 Within the G -4 Infill Growth Sector, the provisions of this Article 4 and this Code in general shall be mandatory, subject to an owner's election under Section 1.2.6c or 4.1.4 hereof. 4.1.2 The Initial Community Regulating Plans for all parts of the Downtown SmartCode Area within the G -4 Infill Growth Sector shall be prepared by or on behalf of the City and shall be subject to recommendation by the Planning Commission to, and approval by the City Council. 4.1.3 Once the Initial Community Regulating Plan has been approved, the areas covered by such Plan shall be marked on all zoning and other land use maps of the City as part of the Downtown SmartCode Area. 4.1.4 After approval of the Initial Community Regulating Plan under paragraph 4.1.2, Infill Community Regulating Plans or amendments thereto may be submitted and approved under this Article for areas within the G -4 Infill Growth Sector effective at such time as an amendment, or in addition to the Infill Community Regulating Plan in effect at such time. Any such amendatory or additional Infill Community Regulating Plan shall be: a. prepared by or on behalf of the Department, upon its own initiative or upon request of the Planning Commission; b. prepared as a Special Area Plan under Section 4.1.5 hereof by or on behalf of the Department: (i) upon its own initiative or upon request of the Planning Commission, or (ii) at the request and at the expense of, and in consultation with, one or more owners of property within the G -4 Infill Growth Sector comprising one or more adjoining Parcels of at least 10 acres of contiguous property having at least 400 linear feet of frontage. 4.1.5 A Special Area Plan prepared pursuant to Section 4.1.4b may assign new Transect Zones, Civic Zones, Thoroughfares, Special Districts and /or Special Requirements as provided in this Article 4, with appropriate transitions to abutting areas. 4.1.6 All Infill Community Regulating Plans, including without limitation, any Special Area Plan prepared under paragraph 4.1.4(b) but not including a Plan submitted as a New Community Regulating Plan or amendment pursuant to Section 4.1.12 and 3.1.6 hereof, shall be subject to recommendation by the Planning Commission to, and approval by, the City Council. 4.1.7 Each Infill Community Regulating Plan, including without limitation a Special Area Plan but excluding a New Community Regulating Plan submitted pursuant to Section 4.1.12 shall regulate, either alone or together with another Infill Community Regulating Plan, a minimum area the size of the Pedestrian Shed commensurate with its Community Type as listed in Section 4.2. The Plan Office shall determine a Community Type based on existing conditions and intended evolution in the plan area. An Infill Community Regulating Plan also may be prepared along a public Thoroughfare. 4.1.8 An Infill Community Regulating Plan shall consist of the following: a. the applicant's demonstration of the consistency of such Infill Community Regulating Plan with the Intent provisions of this Code and the applicable Sector Plan; and b. one or more maps showing the following for each Community Unit in the plan area, in compliance with the standards described in this Article: www.tpudc.com SC22 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 4. INFILL COMMUNITY SCALE PLANS Carmel, Indiana (i) The outline(s) of the Pedestrian Shed(s) and the boundaries of the Community Unit(s). (ii) Location of Transect Zones; (iii) Assignment of Civic Zones; (iv) Densities according to an analysis of existing conditions and future needs; (v) Thoroughfare network, existing and planned; (vi) Any Special Districts (Section 4.5); (vii) Any Special Requirements (Section 4.7); (viii) An itemization of requested Warrants or Variances, if any. 4.1.10 All areas for which an Infill Community Regulating Plan has been approved shall be marked on all zoning and other land use maps of the City as a SmartCode Area with all applicable Transect Zones indicated thereon. 4.1.11 Within the Downtown SmartCode Area and any other area subject to an approved Infill Community Regulating Plan, the provisions of this Code and the applicable Community Regulating Plan becomes the exclusive and mandatory regulation. Property owners within the plan area may submit Building and Lot Regulating Plans under Article 5 in accordance with the provisions of this Code. Building and Lot Regulating Plans requiring no Variances shall be approved administratively by the Zoning Administrator. 4.1.12 One or more owners of a parcel, or abutting parcels, consisting of 40 acres or more of contiguous lots, whether inside or outside an area already subject to an Infill Community Regulating Plan, may initiate the preparation of a New Community Regulating Plan under Article 3 in the pattern of TND or RCD. New Community Regulating Plans for the G -4 Infill Growth Sector, or other areas designated as Infill by the Department, shall regulate, at minimum, an area the size of the Pedestrian Shed commensurate with its Community Type as listed in Section 4.2, even if it overlaps adjacent parcels. Both the site and plan area shall connect and blend with surrounding development. 4.2 COMMUNITY TYPES 4.2.1 Infill Community Regulating Plans shall encompass one or more of the following Community Types specified in Sections 4.2.2, 4.2.3 and 4.2.4. The allocation percentages of Table 14, Item a do not apply. 4.2.2 INFILL TND (TRADITIONAL NEIGHBORHOOD DEVELOPMENT) a. An Infill TND shall be assigned to neighborhood areas that are predominantly residential with one or more Mixed Use Corridors or centers. An Infill TND shall be mapped as at least one complete Standard Pedestrian Shed, which may be adjusted as a Network Pedestrian Shed, oriented around one or more existing or planned Common Destinations. b. The edges of an Infill TND should blend into adjacent neighborhoods and /or a downtown without buffers. 4.2.3 INFILL RCD REGIONAL CENTER DEVELOPMENT) a. An Infill RCD shall be assigned to downtown areas that include significant Office and Retail uses as well as government and other Civic institutions of regional importance. An Infill RCD shall be mapped as at least one complete Long or Linear Pedestrian Shed, which may be adjusted as a Network Pedestrian Shed, oriented around an important Mixed Use Corridor or center. b. The edges of an Infill RCD should blend into adjacent neighborhoods without buffers. www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC23 ARTICLE 4. INFILL COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 4.2.4 INFILL TOD TRANSIT ORIENTED DEVELOPMENT) a. Any Infill TND or Infill RCD on an existing or projected rail or Bus Rapid Transit (BRT) network may be redesignated in whole or in part as TOD and permitted the higher Density represented by the Effective Parking allowance in Section 5.9.24. b. The use of a TOD overlay shall be approved by Variance. 4.3 TRANSECT ZONES 4.3.1 Transect Zone standards for Infill Community Regulating Plans shall be as set forth on Table 14. Transect Zones shall be assigned and mapped on each Infill Community Regulating Plan. 4.3.2 Transect Zones shall include elements indicated by Article 3, Article 5, and Article 6. 4.4 CIVIC ZONES 4.4.1 GENERAL a. Infill Community Regulating Plans shall designate Civic Space Zones (CS) and Civic Building Zones (CB). b. A Civic Zone may be permitted by Warrant if it does not occupy more than 20% of a Pedestrian Shed, otherwise it is subject to the creation of a Special District. See Section 4.5. c. Parking provisions for Civic Zones shall be determined by Warrant. 4.4.2 CIVIC SPACE ZONES (CS) a. Civic Spaces shall be designed generally as described in Table 13, with their type determined by the surrounding or adjacent Transect Zone in a process of public consultation subject to recommendation by the Planning Commission to and the approval of the City Council. 4.4.3 CIVIC BUILDING ZONES (CB) a. Civic Buildings shall be permitted by Variance in any Transect Zone or by War- rant on Civic Zones reserved in the Infill Community Regulating Plan. b. Civic Buildings shall not be subject to the Requirements of Article 5. The particulars of their design shall be determined by Warrant. 4.5 SPECIAL DISTRICTS 4.5.1 Any area that, by its intrinsic size, Function, or Configuration, cannot conform to the requirements of any Transect Zone or combination of zones shall be designated as Special Districts on an Infill Community Regulating Plan. Any applicatoin for establishment of a Special District shall be subject to recommendation by the Plan- ning Commission to and approval by the City Council. Conditions of development for Special Districts shall be determined in public hearing of the City Council and recorded on Table 16. 4.5.2 Special Districts that are not submitted for approval underthis Code shall be governed by the standards of the Existing City Codes. 4.5.3 Without limitation to the foregoing, no Special District shall be used to avoid compliance with the provisions of this Code. 4.6 PRE EXISTING CONDITIONS 4.6.1 Existing buildings, lots and appurtenances that do not conform to the provisions of this Code may continue in the same use and form until a Substantial Modification www.tpudc.com SC24 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 4. INFILL COMMUNITY SCALE PLANS Carmel, Indiana occurs or is requested, at which time the Zoning Administrator shall determine the provisions of this Section that shall apply. 4.6.2 Existing buildings that have at any time received a certificate of occupancy shall not require upgrade to the current Building Code and when renovated may meet the standards of the code under which they were originally permitted. [JOHN MOLI- TOR TO ADVISE ON THIS] 4.6.3 The modification of existing buildings is permitted By Right if such changes result in greater conformance with the specifications of this Code. 4.6.4 Where buildings exist on adjacent Lots, the Zoning Administrator may require that a proposed building match one or the other of the adjacent Setbacks and heights rather than the provisions of this Code. 4.6.5 Any demolition of, addition to or modification of a Building of Value that has been designated as such by the Department or to a building actually or potentially eligible for inclusion on a state, local or national historic register, shall be subject to approval by the Department. 4.6.6 The restoration or rehabilitation of an existing building shall not require the provision of (a) parking in addition to that existing or (b) on -site stormwater retention /detention in addition to that existing. Existing parking requirements that exceed those for this Code may be reduced as provided by Tables 10 and 11. 4.7 SPECIAL REQUIREMENTS 4.7.1 An Infill Community Plan may designate any of the following Special Requirements: a. A differentiation of the Thoroughfares as A -Grid and B -Grid. Buildings along the A -Grid shall be held to the highest standard of this Code in support of pedestrian activity. Buildings along the B -Grid may be more readily considered for Warrants allowing automobile- oriented standards. The Frontages assigned to the B -Grid shall not exceed 30% of the total length of Frontages within a Pedestrian Shed. b. Designations for Mandatory and /or Recommended Retail Frontage requiring or advising that a building provide a Shopfront at Sidewalk level along the entire length of its Private Frontage. The Shopfront shall be no less than 70% glazed in clear glass and shaded by an awning overlapping the Sidewalk as generally illustrated in Table 7 and specified in Article 5. The first floor shall be confined to Retail use through the depth of the second Layer. (Table 17., Item d.) c. Designations for Mandatory and /or Recommended Gallery Frontage, requiring or advising that a building provide a permanent cover over the Sidewalk, either cantilevered or supported by columns. The Gallery Frontage designation may be combined with a Retail Frontage designation. d. Designations for Mandatory and /or Recommended Arcade Frontage, requiring or advising that a building overlap the Sidewalk such that the first floor Facade is a colonnade. The Arcade Frontage designation may be combined with a Retail Frontage designation. e. A designation for Coordinated Frontage, requiring that the Public Frontage (Table 4A) and Private Frontage (Table 7) be coordinated as a single, coherent landscape and paving design. f. Designations for Mandatory and /or Recommended Terminated Vista locations, requiring or advising that the building be provided with architectural articulation of a type and character that responds visually to the location, as approved by the CRC. www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC25 ARTICLE 4. INFILL COMMUNITY SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana g. A designation for Cross Block Passages, requiring that a minimum 8- foot -wide pedestrian access be reserved between buildings. h. A designation for Buildings of Value, requiring that such buildings and structures may be altered or demolished only in accordance with Municipal Preservation Standards and Protocols. 4.8 DENSITY CALCULATIONS 4.8.1 All areas of an Infill Community Regulating Plan site that are not part of the 0 -1 Preserved Open Sector or a protected wetland shall be considered cumulatively the Net Site Area. 4.8.2 Density shall be expressed in terms of dwelling units per acre of Net Site Area as specified for each Transect Zone by Table 14, Item b. 4.8.3 Within the percentage range shown on Table 14, Item b for Other Functions, the housing units specified on Table 14, Item b may be exchanged for other uses at the following rates, subject to approval by Warrant: a. For Lodging: 2 bedrooms for each unit of Net Site Area Density. b. For Office or Retail: 1000 square feet for each unit of Net Site Area Density. 4.8.4 The Residential and Other Functions foreach Transect Zone shall be subject to further adjustment at the building scale as provided by Table 10, Table 11 and Section 5.9. www.tpudc.com SC26 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 5. BUILDING SCALE PLANS Carmel, Indiana 5.1 DIRECTIONS 5.1.1 Lots and buildings located within an area covered by a Community Regulating Plan governed by this Code and previously approved by the City Council shall be subject to the requirements of this Article. 5.1.2 Any building, restoration, redevelopment, development or improvement in any area of the City covered by a Community Regulating Plan shall be subject to the approved Sector Plan and the applicable Community Regulating Plan and shall also require submission of Building and Site Plans under this Article. Building and Site Plans required under this Article shall be prepared by or on behalf of the owner or developer of the subject property. Building and Site Plans shall be subject to review and administrative approval by the Zoning Administrator and any other applicable authorities having jurisdiction over any part of the Plan. 5.1.3 Building and site plans submitted under this Article shall show the following, in compliance with the standards described in this Article: The applicable portion of the Community Regulating Plan Building Disposition Building Configuration Building Function Parking Location Standards Bicycle Facility Standards Landscape Standards Signage Standards Special Requirements, if any Hazard Mitigation Standards Natural Drainage Standards Architectural Standards Lighting Standards Sound Standards Visitability Standards 5.1.4 Special Districts that do not have provisions within this Code shall be governed by the standards of the pre- existing zoning. 5.2 PRE EXISTING CONDITIONS 5.2.1 Legal non conforming uses existing as of the date this Code is adopted shall be allowed to continue in accordance with the Existing Local Codes. Any Building, appurtenance, development, improvement or lot which legally existed immediately prior to adoption of this Code that does not conform to the provisions of this Code in any way other than Function may continue in existence as a non conforming Build- ing, appurtenance development, improvement or lot until a Substantial Modification occurs or is requested, at which time the Zoning Administrator shall determine the provisions of this Article that shall apply. 5.2.2 Existing buildings that have at any time received a certificate of occupancy shall not require upgrade to the current Building Code and when renovated may meet the standards of the code under which they were originally permitted. 5.2.3 The modification of existing buildings is permitted By Right if such changes result in greater conformance with the specifications of this Code. 5.2.4 Where buildings exist on adjacent Lots, the CRC may require that a proposed building match one or the other of the adjacent Setbacks and heights rather than www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC27 ARTICLE 5. BUILDING SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana the provisions of this Code. 5.2.5 Any addition to or modification of a Building of Value that has been designated as such by the Department, or to a building actually or potentially eligible for inclusion on a state, local or national historic register, shall be subject to approval by the Department. 5.2.6 The restoration or rehabilitation of an existing building shall not require the provi- sion of (a) parking in addition to that existing nor (b) on -site stormwater retention/ detention in addition to that existing. Existing parking requirements that exceed those for this Code may be reduced as provided by Table 10 and Table 11. 5.3 COMPLIANCE WITH CODE 5.3.1 Buildings and sites governed by this Code shall comply in all respects to all applicable provisions of this Code, including any Special Requirements standards which are applicable thereto, as shown on the applicable Community Regulating Plan. 5.4 CIVIC ZONES 5.4.1 GENERAL a. Civic Zones are designated on Community Regulating Plans as Civic Space (CS) or Civic Building (CB). b. Parking provisions for Civic Zones shall be determined by Warrant. 5.4.2 CIVIC SPACES (CS) a. Civic Spaces shall be generally designed as described in Table 13. 5.4.3 CIVIC BUILDINGS (CB) a. Civic Buildings shall not be subject to the requirements of this Article. The par- ticulars of their design shall be determined by Warrant. 5.5 SPECIFIC TO T1 NATURAL ZONE 5.5.1 Buildings in the T1 Natural Zone are permitted only by Variance. Permission to build in T1 and the standards for Article 5 shall be determined concurrently upon recommendation of the Department to the Plan Commission, and recommendation of the Plan Commission to and approval by the City Council. 5.6 BUILDING DISPOSITION 5.6.1 SPECIFIC TO ZONE T2 a. Within T -Zone T2, Building Disposition shall be determined by Warrant. 5.6.2 SPECIFIC TO ZONES T3, T3 -E, T3 -L, T4, T5, AND T6 Within T -Zones T3, T3- E,T3 -L, T4, T5 and T6: a. Newly platted Lots shall be dimensioned according to Table 14, Item f and Table 15. b. Building Disposition types shall be as shown in Table 9 and Table 14, Item i. c. Buildings shall be disposed in relation to the boundaries of their Lots according to Table 14, Item g, Table 14, Item h, and Table 15. d. One Principal Building at the Frontage, and one Outbuilding to the rear of the Principal Building, may be built on each Lot as shown in Table 17, Item c. e. Lot coverage by building shall not exceed that recorded in Table 14, Item f and Table 15. f. Facades shall be built parallel to a rectilinear Principal Frontage Line or to the tangent of a curved Principal Frontage Line, and along a minimum percentage of the Frontage width at the Setback, as specified as Frontage Buildout on Table 14, Item g and Table 15. p www.tpudc.com SC28 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 5. BUILDING SCALE PLANS Carmel, Indiana g. Setbacks for Principal Buildings shall be as shown in Table 14, Item g and Table 15. In the case of an Infill Lot, the Zoning Administrator may require that Setbacks be adjusted to one of the existing adjacent Setbacks or the average of the Block. Setbacks may be adjusted by Warrant. h. Rear Setbacks for Outbuildings shall be a minimum of 12 feet measured from the centerline of the Rear Alley or Rear Lane easement. In the absence of Rear Alley or Rear Lane, the rear Setback shall be as shown in Table 14, Item h and Table 15. i. To accommodate slopes over ten percent, relief from front Setback requirements is available by Warrant. 5.6.3 SPECIFIC TO ZONE T6 a. Within T -Zone T6, the Principal Entrance of Buildings shall be on a Frontage Line. 5.7 BUILDING CONFIGURATION 5.7.1 GENERAL TO ZONES T2, T3, T3 -E, T3 -L,T4, T5 AND T6 The following shall be applicable to Buildings and Lots in T -Zones T2, T3, T3 -E, T3 -L, T4, T5 and T6: a. The Private Frontage of buildings shall conform to and be allocated in accordance with Table 7 and Table 14, Item j. b. Buildings on corner Lots shall have two Principal Frontages as shown in Table 17. Prescriptions for the second and third Layers pertain only to the Principal Frontage. Prescriptions for the first Layer pertain to both Principal Frontages of a corner Lot. c. All Facades shall be glazed with clear glass no less than 30% of the first Story. d. Building Heights, Stepbacks, and Extension Lines shall conform to Table 8 and Table 14, Item j. e. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a first floor space eligible for a Commercial Function, which shall be a minimum of 11 feet with a maximum of 25 feet. A single floor level exceed- ing the maximum permitted height at ground level, shall be counted as two (2) stories. Mezzanines extending beyond 33% of the floor area shall be counted as an additional Story. f. In a Parking Structure or garage, each above ground level counts as a single Story regardless of its relationship to habitable Stories. g. Height limits do not apply to Attics or raised basements, masts, belfries, clock towers, chimney flues, water tanks, or elevator bulkheads. 5.7.2 SPECIFIC TO ZONES T2, T3, T3 -E, T3 -L, T4 ANDT5 The following shall be applicable to T -Zones T3, T3 -E, T3 -L, T4 and T5: a. The habitable area of an Accessory Unit within a Principal Building or an Out- building shall not exceed 600 square feet, excluding the parking area. b. Garages shall not be permitted in the First or Second Lot Layers. 5.7.3 SPECIFIC TO ZONE T3, T3 -E AND T3 -L The following shall be applicable to T -Zones T3, T3 -E and T3 -L: a. No portion of the Private Frontage may Encroach upon the Sidewalk. b. Open porches may Encroach upon the First Lot Layer by 50% of the depth of the Lot Layer provided that they do not encroach upon any existing easement. (Table 17, Item d) www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC29 ARTICLE 5. BUILDING SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana c. Balconies and bay windows may Encroach upon the First Lot Layerby25% of the depth of the Lot Layer, except that balconies on porch roofs may Encroach as does the porch. d. All specified Building Heights may be increased by the difference between the actual lot elevation and the base elevations required by applicable FEMA stan- dards, provided that any first level space shall be designed for use as (i) garage or other parking or storage space set into the structure into the Second and deeper Layers, provided no front facing garage shall be permitted in the Second Lot Layer; (ii) an open market, a loggia, building entrance or porch or combination thereof, or other open -air area for recreation, relaxation or gathering, to the extent permitted by applicable FEMA requirements, or other use specifically permitted by Variance. [ADRIENNE TO PROVIDE CITY'S FEMA/FLOOD HAZARD REGULATIONS] 5.7.4 SPECIFIC TO ZONE T4 The following shall be applicable to T -Zone T4: a. Balconies, open porches and bay windows may Encroach upon the First Lot Layer by 50% of the depth of the Lot Layer provided that they do not encorach upon any existing easement. (fable 17, Item d) 5.7.5 SPECIFIC TO ZONES T5, T6 The following shall be applicable to T -Zones T5 and T6: a. Awnings, Arcades, and Galleries may Encroach upon the Sidewalk to within 2 feet of the Curb but must clear the Sidewalk vertically by at least 8 feet. b. Maximum Encroachment heights (Extension Lines) forArcades shall be as shown on Table 8. c. Stoops, Lightwells, balconies, bay windows, and terraces may Encroach upon the First Lot Layer by 100% of its depth. (Table 17, Item d). d. Loading docks and service areas shall be permitted on Frontages only by Warrant. e. In the absence of a Building Facade along any part of a Frontage Line, a Streetscreen shall be built co- planar with the Facade. f. Streetscreens shall be between 3.5 and 8 feet in height provided that they shall be between 5 and 8 feet in height at the rear of a Lot. The Streetscreen may be replaced by a hedge or fence by Warrant. Streetscreens shall have openings no larger than necessary to allow automobile and pedestrian access. g. Space at the first level of a Building which is eligible for Residential or Lodging Function shall be raised a minimum of 2 feet from average Sidewalk grade. h. All specified Building Heights may be increased by the difference between the actual lot elevation and the base elevations required by applicable FEMA stan- dards, provided that any first level space shall be designed for use as (i) parking or storage space set into the structure into the Second and deeper Layers,provided no front facing garage shall be permitted in the Second Layer, (ii) an open market, a loggia, building entrance or porch or combination thereof, or other open -air area for recreation, relaxation or gathering, or (iii) enclosed Commercial or Retail space, to the extent permitted by applicable FEMA requirements, or other use specifically permitted by Variance. www.tpudc.com SC30 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 5. BUILDING SCALE PLANS Carmel, Indiana 5.8 BUILDING FUNCTION 5.8.1 GENERAL To ZONES T2, T3, T3 -E, T3 -L, T4, T5 ANDT6 The following shall be applicable to T -Zones T2, T3, T3 -E, T3 -L, T4, T5 and T6: a. Buildings in each Transect Zone shall conform to the Functions on Table 10, Table 12 and Table 14, Item I. Functions that do not conform shall require ap- proval by Warrant or Variance as specified on Table 12. 5.8.2 SPECIFIC To ZONES T2, T3, T3 -E AND T3 -L The following shall be applicable to T -Zones T3, T3 -E and T3 -L: a. Accessory Functions of Restricted Lodging or Restricted Office shall be permitted within an Accesory Building. See Table 10. 5.8.3 SPECIFIC To ZONES T4 ANDT5 The following shall be applicable to T -Zones T4 and T5: a. Accessory Functions of Limited Lodging or Limited Office shall be permitted within an Accesory Building. See Table 10. 5.8.4 SPECIFIC To ZONES T5 ANDT6 The following shall be applicable to T -Zones T5 and T6: a. First Story Commercial and Artisan Light Industrial Functions shall be permitted. 5.9 PARKING AND DENSITY CALCULATIONS 5.9.1 SPECIFIC To ZONES T2, T3, T3 -E AND T3 -L The following shall be applicable to T -Zones T2, T3, T3 -E and T3 -L: a. Buildable Density on a Lot shall be determined by the actual parking provided within the Lot as applied to the Functions permitted in Table 10 and Table 11. 5.9.2 SPECIFIC To ZONES T4, T5 ANDT6 The following shall be applicable to T -Zones T4, T5 and T6: a. Buildable Density on a Lot shall be determined by reference to the sum of the actual parking calculated as that provided (1) within the Lot (2) along the parking lane corresponding to the Lot Frontage, and (3) by purchase or ten (10) -year or longer lease from a Civic Parking Reserve within the Pedestrian Shed, if available, adjusted pursuant to paragraph 5.9.2b to the extent applicable to determine the Effective Parking. b. The actual available parking attributable to a Lot shall be adjusted upward accord- ing to the Shared Parking Factor of Table 11 to determine the Effective Parking. The Shared Parking Factor is available for any two Functions within any pair of adjacent Blocks. c. Based on the actual parking or, if applicable, the Effective Parking available, the Density of the projected Function may be determined according to Table 10. d. Within the overlay area of a Transit Oriented Development (TOD) the Effective Parking may be further adjusted upward by 30 e. The total Density within each Transect Zone shall not exceed that specified by the approved Community Regulating Plan based on Article 3 or Article 4. f. Accessory Units that are not required to have separate parking available to them do not count toward Density calculations. g. Liner Buildings less than 30 feet deep and no more than two Stories shall be exempt from parking requirements. 5.10 VEHICLE BICYCLE PARKING LOCATION STANDARDS 5.10.1 GENERAL To ZONES T2, T3, T3 -E, T3 -L, T4, T5 AND T6 www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC31 ARTICLE 5. BUILDING SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana The following shall be applicable to T -Zones T2, T3, T3 -E, T3 -L, T4, T5 and T6: a. Vehicle parking shall be accessed by Rear Alleys or Rear Lanes, when such are avail- able on the applicable Community Regulating Plan. b. Open vehicle parking areas shall be masked from the Frontage by a Building or Streetscreen. c. Bicycle Parking and storage shall be within the Public Frontage or Private Front- age. 5.10.2 SPECIFIC TO ZONES T2, T3, T3 -E AND T3 -L The following shall be applicable to T -Zones T2, T3, T3 -E and T3 -L: a. Open parking areas shall be located at the Second and Third Lot Layers, except that Driveways, drop -offs and unpaved parking areas may be located at the first Lot Layer. (Table 17, Item d) b. Garages shall be located at the Third Lot Layer. 5.10.3 SPECIFIC TO ZONES T3, T3 -E, T3 -L AND T4 The following shall be applicable to T -Zones T3, T3 -E, T3 -L and T4: a. Driveways at Frontages shall be no wider than 10 feet in the First Lot Layer. (Table 3B.f) 5.10.4 SPECIFIC TO ZONE T4 The following shall be applicable to T -Zone T4: a. All parking areas and garages shall be located at the Second or Third Lot Layer. (Table 17, Item d) 5.10.5 SPECIFIC TO ZONES T5 AND T6 The following shall be applicable to T -Zones T5 and T6: a. All parking lots, garages, and Parking Structures shall be located at the Second or Third Lot Layer. (Table 17, Item d) b. Vehicular entrances to parking lots, garages, and Parking Structures shall be no wider than 24 feet at the Frontage. (Table 3B.f) c. Pedestrian exits from all parking lots, garages, and Parking Structures shall be directly to a Frontage Line (i.e., not directly into a building) except underground levels which may be exited by pedestrians directly into a building. d. Parking Structures shall have Liner Buildings lining all Stories and lighting from within any Parking Structure shall be concealed from view of any adjacent Thor- oughfares. e. A minimum of one bicycle rack place shall be provided within the Public or Private Frontage for every ten (10) vehicular parking spaces. 5.11 LANDSCAPE STANDARDS 5.11.1 GENERAL TO ZONES T2, T3, T3 -E, T3 -L, T4, T5 AND T6 The following shall be applicable to T -Zones T2, T3, T3- E,T3 -L, T4,T5 and T6: a. Impervous surface shall be confined to the ratio of Lot coverage specified in Table 14, Item f. b. All landscaping shall conform to the City's landscape, urban forestry, tree mitiga- tion and tree canopy ordinances and regulations. 5.11.2 SPECIFIC TO ZONES T2, T3, T3 -E, T3 -L ANDT4 The following shall be applicable to T -Zones T2, T3, T3 -E, T3 -L and T4: a. The First Lot Layer shall not be paved, with the exception of Driveways as speci- fied in Section 5.10.2 and Section 5.10.3. (Table 17, Item d) 5.11.3 SPECIFIC TO ZONE T3, T3 -E AND T3 -L The following shall be applicable to T -Zones T3, T3 -E and T3 -L: www.tpudc.com SC32 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 5. BUILDING SCALE PLANS Carmel, Indiana a. A minimum of two trees shall be planted within the First Lot Layer for each 30 feet of Frontage Line or portion thereof. (Table 17, Item d) b. Trees may be of single or multiple species as shown on Table 6. c. Trees shall be naturalistically clustered. d. Lawn shall be permitted by Right. 5.11.4 SPECIFIC TO ZONE T4 The following shall be applicable to T -Zone T4: a. A minimum of one tree shall be planted within the First Lot Layer for each 30 feet of Frontage Line or portion thereof. (Table 17, Item d) b. Lawn shall be permitted By Right. 5.11.5 SPECIFIC TO ZONES T5 AND T6 The following shall be applicable to T -Zones T5 and T6: a. Trees shall not be required in the First Lot Layer. b. The First Lot Layer may be paved to match the pavement of the Public Frontage. 5.12 SIGNAGE STANDARDS 5.12.1 GENERAL TO ZONES T2, T3, T3 -E, T3 -L, T4, T5 AND T6 The following shall be applicable to T -Zones T2, T3, T3 -E, T3 -L, T4, T5 and T6: a. There shall be no signage permitted additional to that specified in this section. b. The address number, no more than 6 inches measured vertically, shall be attached to the building in proximity to the Principal Entrance or at a mailbox. Notwithstand- ing anything to the contrary contained or implied in this Code, and irrespective whether the same does or does not constitute a Substantial Modification, any signage installed or replaced after the date this Code is adopted shall comply with the provisions of this Section 5.12. 5.12.2 SPECIFIC TO ZONES T2, T3, T3E AND T3L The following shall be applicable to T -Zones T2, T3, T3 -E and T3 -L: a. Signage shall not be illuminated. 5.12.3 SPECIFIC TO ZONES T4, T5 AND T6 The following shall be applicable to T -Zones T4, 5 and T6: a. Signage shall be externally illuminated, except that signage within the Shopfront glazing may be neon lit. 5.12.4 SPECIFIC TO ZONES T2, T3, T3E, T3L AND T4 The following shall be applicable to T -Zones T2, T3, T3 -E, T3 -L, and T4: a. One blade sign for each business may be permanently installed perpendicular to the Facade within the First Lot Layer. Such a sign shall not exceed a total of 4 square feet and shall clear 8 feet above the Sidewalk. 5.12.5 SPECIFIC TO ZONES T5 ANDT6 The following shall be applicable to T -Zones T5 and T6: a. Blade signs, not to exceed 6 square feet for each separate business entrance, may be attached to and should be perpendicular to the Facade, and shall clear 8 feet above the Sidewalk. b. A single external permanent sign band may be applied to the Facade of each building, providing that such sign not exceed 3 feet in height by any length. ARTICLE 5. SMARTCODE MODULES 5.7.34 FOR HAZARD MITIGATION STANDARDS www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC33 ARTICLE 5. BUILDING SCALE PLANS CITY OF CARMEL SMARTCODE Carmel, Indiana 5.7.6 FOR HAZARD MITIGATION STANDARDS 5.13 FOR NATURAL DRAINAGE STANDARDS 5.14 FOR ARCHITECTURAL STANDARDS 5.15 FOR LIGHTING STANDARDS 5.16 FOR SOUND STANDARDS 5.17 FOR VISITABILITY STANDARDS 5.18 FOR HAZARD MITIGATION STANDARDS 5.19 FOR HAZARD MITIGATION STANDARDS www.tpudc.com SC34 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 1. TRANSECT ZONE DESCRIPTIONS Carmel, Indiana TABLE 1: Transect Zone Descriptions. This table provides descriptions of the character of each T -zone. T -1 NATURAL Primarily agricultural with woodland wetland and scattered buildings Building Placement: T -1 Natural Zone consists of lands General Character: Natural landscape with some agricultural use approximating or reverting to a wilder- Building Placement: Not applicable ness condition, including lands unsuit- Frontage Types: Not applicable able for settlement due to topography, Typical Building Height: Not applicable hydrology or vegetation. Type of Civic Space: Parks, Greenways T -2 RURAL TO Rural Zone consists of sparsely settled lands in open orcultivated states. These include woodland, agricultural land, grassland, and irrigable desert. Typical buildings are farmhouses, agri- cultural buildings, cabins, and villas. c: General Character: Primarily agricultural with woodland wetland and scattered buildings Building Placement: Variable Setbacks Frontage Types: Not applicable Typical Building Height: 1- to 2 -Story Type of Civic Space: Parks, Greenways T -3 SUB -URBAN higher density mixed use building that T -4 GENERAL URBAN T -3E SUB -URBAN EDGE General Character: Lawns, and landscaped yards surrounding detached single family T -3L SUB -URBAN LARGE LOT T -4 General Urban Zone consists of houses; pedestrians occasionally Mix of Houses, Townhouses small Apartment buildings, with scat These Zones consists of low density Building Placement: Large and variable front and side yard Setbacks tered Commercial activity, balance between landscape and buildings residential areas, adjacent to higher Frontage Types: Porches, fences, naturalistic tree planting presence of pedestrians zones that include some mixed use. Home Typical Building Height: 1 -tot -Story with some 3-Story Shallow to medium front and side yard Setbacks occupations and Outbuildings are allowed. Planting is naturalistic and setbacks are Type of Civic Space: Parks, Greenways Porches, fences, Dooryards relatively deep. Blocks may be large and are variable. Streets with curbsand side- Typical Building Height: 2 -to3 -Story with a few taller Mixed Use buildings the roads irregulartoaccommodate natural walks define medium -sized blocks. Type of Civic Space: Squares, Greens conditions. The primary difference among T -5 URBAN CENTER these zones is lot size. T -5 Urban Center Zone consists of higher density mixed use building that T -4 GENERAL URBAN workplace, and Civic buildings, predominantly attached buildings; ■i� T -4 General Urban Zone consists of General Character: Mix of Houses, Townhouses small Apartment buildings, with scat Building Placement: mixed use but primarily residential VW tered Commercial activity, balance between landscape and buildings urban fabric. It may have a wide range IT presence of pedestrians is a of building types: single, sideyard, and Building Placement: Shallow to medium front and side yard Setbacks Typical Building Height: of Civic Space: rowhouses. Setbacks and landscaping Frontage Types: Porches, fences, Dooryards are variable. Streets with curbsand side- Typical Building Height: 2 -to3 -Story with a few taller Mixed Use buildings walks define medium -sized blocks. Type of Civic Space: Squares, Greens General Character: T -5 URBAN CENTER highest density and height, with the T -5 Urban Center Zone consists of General Character: Shops mixed with Townhouses, IargerApartment houses, Offices, higher density mixed use building that workplace, and Civic buildings, predominantly attached buildings; accommodate etail, offices, rowhouses trees within the public right -of -way; substantial pedestrian activit and apartments. It has a tight network Building Placement: Shallow Setbacks or none, buildings oriented to street defining a VW of streets, with wide sidewalks, steady street wall IT street tree planting and buildings set Frontage Types: Stoops, Shopfronts, Galleries M IR Type close to the sidewalks. Typical Building Height: of Civic Space: 3- to 5 -Story with some variation Parks, Plazas and Squares, median landscaping T -6 URBAN CORE T -6 Urban Core Zone consists of the General Character: Medium to high- Density Mixed Use buildings, entertainment, Civic highest density and height, with the and cultural uses. Attached buildings forming a continuous street greatest variety of uses, and civic build- wall, trees within the public right -of -way; highest pedestrian and ings of regional importance. It may have transit activity largerblocks, streets have steadystreet Building Placement: Shallow Setbacks or none, buildings oriented to street, defining a tree planting and buildings are set close street wall to wide sidewalks. Typically only large Frontage Types: Stoops, Dooryards, Forecourts, Shopfronts, Galleries, and Arcades towns and cities have an Urban Core Typical Building Height: 4 -plus Story with a few shorter buildings Zone. Type of Civic Space: Parks, Plazas and Squares, median landscaping www. tp UC�C. `Cl�11�*s Transect Zones T3, T3 -E and T3 -L. 2009 Town Planning Urban Design Collaborative LLC SC35 TABLE 2. SECTOR/COMMUNITY ALLOCATION CITY OF CARMEL SMARTCODE Carmel, Indiana TABLE 2: Sector /Community Allocation. Table 2 defines the geography, including both natural and infrastructure elements, determining areas that are or are not suitable for development. Specific Community Types of various intensities are allowable in specific Sectors. This table also allocates the proportions of Transect Zones within each Community Type. ALREADY DEVELOPED AREAS PROXIMITY TO MAJOR THOROUGHFARES AND TRANSIT PROXIMITY TO THOROUGHFARES MEDIUM SLOPES WOODLANDS FLOOD PLAIN OPEN SPACE TO BEACQUIRED CORRIDORS TO BEACQUIRED BUFFERS TO BEACQUIRED LEGACY WOODLAND LEGACY FARMLAND LEGACY VIEWSHEDS CLD RESIDUAL OPEN SPACE z z SURFACE WATERBODIES c c PROTECTED WETLANDS o 0 m m PROTECTED HABITAT RIPARIAN CORRIDORS z z PURCHASED OPEN SPACE z CONSERV. EASEMENTS LANDTRUST TRANSPORT. CORRIDORS CLD OPEN SPACE (PRIMARILY OPEN SPACE) (PRIMARILY NEW COMMUNITIES) (SUCCESSIONAL COMMUNITIES) PRESERVED RESERVED RESTRICTED CONTROLLED INTENDED INFILL OPEN SECTOR OPEN SECTOR 0 0 0 0 0 0 0 0 0 0 0 e e e e e e GROWTH SECTOR GROWTH SECTOR 0 0 0 0 0 0 0 0 0 0 0 e e e e e e e e GROWTH SECTOR GROWTH SECTOR I I UM NO MINIMUM 50% MIN 7NOMIN 7 VNOMINIMUIM NO MINIMUM NO MIN 10 -30% 10 -30% 10 -30% 10 -30% 20 -40% 20 -40% 30 -60% 30 -60% 10 -30% VARIABLE VARIABLE 10 -30% 10 -30% 10 -30% VARIABLE VARIABLE 40 -80% VARIABLE VARIABLE Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com SC36 C 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 3A. VEHICULAR LANE DIMENSIONS Carmel, Indiana TABLE 3A: Vehicular Lane Dimensions. This table assigns lane widths to Transect Zones. The Design ADT (Average Daily Traffic) is the determinant for each of these sections. The most typical assemblies are shown in Table 313. Specific requirements for truck and transit bus routes and truck loading shall be decided by Warrant. DESIGN SPEED TRAVEL LANE WIDTH W 90 0 W W 9 0 Below 20 mph 8 feet 20 -25 mph 9 feet 25 -35 mph 10 feet 25 -35 mph 11 feet Above 35 mph 12 feet DESIGN SPEED PARKING LANE WIDTH 20 -25 mph (Angle 18 feet 20 -25 mph (Parallel) 7 feet 25 -35 mph (Parallel) 8 feet Above 35 mph DESIGN SPEED (Parallel) 9 feet EFFECTIVE TURNING RADIUS (See Table 17b) Below 20 mph 5 -10 feet I 20 -25 mph 10 -15 feet 25 -35 mph 15 -20 feet Above 35 mph 20 -30 feet Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC BY RIGHT BY WARRANT SC37 TABLE 3B. VEHICULAR LANE PARKING ASSEMBLIES CITY OF CARMEL SMARTCODE Carmel, Indiana TABLE 3B: Vehicular Lane /Parking Assemblies. The projected design speeds determine the dimensions of the vehicular lanes and Turn- ing Radii assembled for Thoroughfares_ ONE WAY MOVEMENT 10 TWO WAY MOVEMENT a. NO Mo PARKING 12 11 22' t 10 J0 Design ADT 300 VPD 600 VPD 2,500 VPD 22,000 VPD 36,000 VPD Pedestrian Crossing 3 Seconds 5 Seconds 5 Seconds 9 Seconds 13 Seconds Design Speed 20 30 MPH Below 20 MPH 2O -25 MPH 35 MPH and above b. YIELD PARKING 1 1 4 b4 �1 1 Design ADT 1,000 "PE 1,000 VPD Pedestrian Crossing 5 Seconds 7 Seconds Design Speed C. PARKING ONE SIDE PARALLEL x191 1. e'' °1 1. a 'r 9 ,zy ,zr -Irt9y I4 I4;4 Ib�4 Ib 4I I bib 4;4I 1� 1' I' Design ADT 5,000 VPD 18,000 VPD 16,000 VPD 15,000 VPD 32,000 VPD Pedestrian Crossing 5 Seconds 8 Seconds 8 Seconds 11 Seconds 13 Seconds Design Speed 20 -30 MPH 25 -30 MPH 25 -30 MPH d. PARKING BOTH SIDES PARALLEL Yt '''Hfi B ''ry y'rtl g u 1t11 s 12 Y I�� I4I I Ib� Ib;8;4I Ib;b;4;4I Design ADT 8,000 VPD 20,000 VPD 15,000 VPD 22,000 VPD 32,000 VPD Pedestrian Crossing 7 Seconds 10 Seconds 10 Seconds 13 Seconds 15 Seconds Design Speed I Below 20 MPH 25 -30 MPH 25 -30 MPH 25 -30 MPH 35 MPH and above e. PARKING BOTH SIDES DIAGONAL 8j- -r3' rS' aa sy s ,r sy 16 ,r Design ADT 18,000 VPD 20,000 VPD 7 tl 15,000 VPD 17 Seconds 2O -25 MPH 22,000 VPD 20 Seconds 25 -30 MPH 111 31,000 VPD 23 Seconds 25 -30 MPH Pedestrian Crossing 15 Seconds 17 Seconds Design Speed Below 20 MPH 2O -25 MPH f. PARKING ACCESS Design ADT Pedestrian Crossing Design Speed b 3 Seconds b4 6 Seconds *Includes Transect Zones T3, T3 -E and T3 -L. SC38 www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 4A. PUBLIC FRONTAGES GENERAL Carmel, Indiana TABLE 4A: Public Frontages General. The Public Frontage is the area between the private Lot line and the edge of the vehicular lanes. Dimen- sions are given in Table 4B. PLAN a. (HM For Highway: This Frontage has open Swales drained by percolation, Bicycle Trails and no parking. The landscaping consists of the natural condition or multiple species arrayed in naturalistic clusters. Build- ings are buffered by distance or berms. b. (RD) For Road: This Frontage has open Swales drained by percolation and a walking Path or Bicycle Trail along one or both sides and Yield parking. The landscaping consists of multiple species arrayed in naturalistic clusters. c. (ST) For Street: This Frontage has raised Curbsdrained byinletsand Sidewalks separated from the vehicular lanes by individual or continuous Planters, with parking on one or both sides. The landscaping consists of street trees of a single or alternating species aligned in a regularly spaced Allee, with the exception that Streets with a right -of -way (R.O.W.) width of 40 feet or less are exempt from tree requirements. d. (DR) For Drive: This Frontage has raised Curbs drained by inlets and a wide Sidewalk or paved Path along one side, related to a Greenway or waterfront. It is separated from the vehicular lanes by individual or continuous Planters. The landscaping consists of street trees of a single or alternating species aligned in a regularly spaced AIIee. e. (AV) For Avenue: This Frontage has raised Curbs drained by inlets and wide Sidewalks separated from the vehicular lanes by a narrow continuous Planter with parking on both sides. The landscaping consists of a single tree species aligned in a regularly spaced AIIee. f. (CS) (AV) For Commercial Street or Avenue: This Frontage has raised Curbs drained by inlets and very wide Sidewalks along both sides separated from the vehicular lanes by separate tree wells with grates and parking on both sides. The landscaping consists of a single tree species aligned with regular spacing where possible, but clears the storefront entrances. g. (BV) For Boulevard: This Frontage has Slip Roads on both sides. It consists of raised Curbs drained by inlets and Sidewalks along both sides, separated from the vehicular lanes by Planters. The landscaping consists of double rows of a single tree species aligned in a regularly spaced AIIee. Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC39 A PUBLIC FRONTAGE T1 rz i6 T4 1! T5 Lill, M�l TIS i6 SC39 TABLE 4B. PUBLIC FRONTAGES SPECIFIC CITY OF CARMEL SMARTCODE Carmel, Indiana Table 413: Public Frontages Specific. This table assembles prescriptions and dimensions for the Public Frontage elements Curbs, walkways and Planters relative to specific Thoroughfare types within Transect Zones. Table 413-a assembles all of the elements for the various street types. Locally appropriate planting species should be filled in to the calibrated Code. R U R A L I I I I I I I I I I I I I I I IT R AN S E C T I I I I I I I I I I I I I I I U R B AN TRANSECT ZONE Public Frontage Type HW RD RD ST ST -DR -AV ST- DR -AV -BV CS- DR -AV -BV CS- DR -AV -BV a.Assembly: The princi- I I pal variables are the type I I and dimension of Curbs, I� I walkways, Planters and landscape. O Total Width 16 -24 feet 12 -24 feet 12 -18 feet 12 -18 feet 18 -24 feet 18 -30 feet b.Curb: The detailing of I the edge of the vehicular j pavement, incorporating j drainage. _-j JlIII __4.7 _M" :1 1i T Open Swale Open Swale Raised Curb Raised Curb Raised Curb Raised Curb Radius 10 -30 feet 10 -30 feet 5 -20 feet 5 -20 feet 5 -20 feet 5 -20 feet c. Walkway: The pavement j I I dedicated exclusively to pedestrian activity. j I I Type Path Optional Path Sidewalk Sidewalk Sidewalk Sidewalk Width n/a 5-8 feet 5-8 feet 5-8 feet 12 -20 feet 12 -30 feet d. Planter: The layer which j accommodates street trees j I I and other landscape. i j° j D J i l l Clustered Clustered Regular Regular Regular Opportunistic Specie Multiple Multiple Alternating Single Single Single Planter Typ Continuous Swale Continuous Swale Continuous Planter Continuous Planter Continuous Planter Tree Well Planter Width 8 feet -16 feet 8 feet -16 feet 8 feet -12 feet 8 feet -12 feet 4 feet -6 feet 4 feet -6 feet e. Landscape: The recom- mended plant species. (See Table 6) f. Lighting: The recom- mended Public Lighting. (See Table 5) Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com SC40 C 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 4C. THOROUGHFARE ASSEMBLIES Carmel, Indiana TABLE 4C: Thoroughfare Assemblies. These Thoroughfares are assembled from the elements that appear in Tables 3A and 3B and incorpo- rate the Public Frontages of Table 4A. The key gives the Thoroughfare type followed by the right -of -way width, followed by the pavement width, and in some instances followed by specialized transportation capabiliity. KEY ST- 57 -20 -BL Thoroughfare Type 24' 24' Right of Way Width Pavement Width Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP Thoroughfare Type Transect Zone Assignment Right -of -Way Width Pavement Width Movement Design Speed Pedestrian Crossing Time Traffic Lanes Parking Lanes Curb Radius Walkway Type Planter Type Curb Type Landscape Type Transportation Provision RL -24 -12 Rear Lane T3 -E, T34_, T3 24 feet 12 feet Yield Movement 10 MPH 3.5 seconds n/a None Taper None None Inverted Crown None None RA -24 -24 Rear Alley T4, T5, T6 24 feet 24 feet Slow Movement 10 MPH 7 seconds n/a None Taper None None Inverted Crown None None www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC41 TABLE 4C. THOROUGHFARE ASSEMBLIES CITY OF CARMEL SMARTCODE Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type 50' 50' Right of Way Width Pavement Width 18 T T 18 16' 9' 9' 16' Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP Thoroughfare Type Transect Zone Assignment Right -of -Way Width Pavement Width Movement Design Speed Pedestrian Crossing Time Traffic Lanes Parking Lanes Curb Radius Walkway Type Planter Type Curb Type Landscape Type Transportation Provision RD -50 -14 Road T1, T2, T3 -E, T34_, T3 50 feet 14 feet Yield Movement 15 MPH 4 seconds 2 lanes None 25 feet Path optional Continuous Swale Swale Trees clustered BT RD -50 -18 Road T1, T2, T3 -E, T34_, T3 50 feet 18 feet Slow Movement 15 MPH 5.1 seconds 2 lanes None 25 feet Path optional Continuous Swale Swale Trees clustered BT www.tpudc.com SC42 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 4C. THOROUGHFARE ASSEMBLIES Carmel, Indiana I ypc 50' Right of Way Width Pavement Width 13' 12' 12' 13' Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST `r Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL r Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC ST -40 -19 Street T5, T6 40 feet 19 feet Slow Movement 20 MPH 5.4 seconds 1 lane One side 7 feet marked 15 feet 13/8 foot Sidewalk 4x4" tree well Curb Trees at 30' o.c. Avg. SC43 40' RD -50 -24 Thoroughfare Type Road Transect Zone Assignment T1, T2, T3 -E, T31, T3 Right -of -Way Width 50 feet Pavement Width 24 feet Movement Slow Movement Design Speed 20 MPH Pedestrian Crossing Time 6.8 seconds Traffic Lanes 2lanes Parking Lanes None Curb Radius 25 feet Walkway Type Path optional Planter Type Continuous Swale Curb Type Swale Landscape Type Trees clustered Transportation Provision BT www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC ST -40 -19 Street T5, T6 40 feet 19 feet Slow Movement 20 MPH 5.4 seconds 1 lane One side 7 feet marked 15 feet 13/8 foot Sidewalk 4x4" tree well Curb Trees at 30' o.c. Avg. SC43 40' TABLE 4C. THOROUGHFARE ASSEMBLIES CITY OF CARMEL SMARTCODE Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type 50' 50 Right of Way Width Pavement Width 5' T 8' 18' T5 5' 6' 8' 12' 8' 6' 5' Transportation THOROUGHFARE TYPES Street Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP ST -50 -26 ST -50 -28 Thoroughfare Type Street Street Transect Zone Assignment T4, T5, T6 T4, T5, T6 Right -of -Way Width 50 feet 50 feet Pavement Width 26 feet 28 feet Movement Free Movement Yield Movement Design Speed 20 MPH 20 MPH Pedestrian Crossing Time 7.4 seconds 7.6 seconds Traffic Lanes 2lanes 2 lane Parking Lanes One side 8 feet marked Both sides 8 feet unmarked Curb Radius 10 feet 10 feet Walkway Type 5 foot Sidewalk 5 foot Sidewalk Planter Type 7 foot continuous Planter 6 foot continuous Planter Curb Type Curb Curb Landscape Type Trees at 30' o.c. Avg. Trees at 30' o.c. Avg. Transportation Provision www.tpudc.com SC44 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 4C. THOROUGHFARE ASSEMBLIES Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type Right of Way Width Pavement Width Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP Thoroughfare Type Transect Zone Assignment Right -of -Way Width Pavement Width Movement Design Speed Pedestrian Crossing Time Traffic Lanes Parking Lanes Curb Radius Walkway Type Planter Type Curb Type Landscape Type Transportation Provision ST -50 -30 Street T3-E, T3 -L, T3, T4 50 feet 30 feet Slow Movement 20 MPH 8.5 seconds 2 lanes Both sides 7 feet unmarked 10 feet 5 foot Sidewalk 5 foot continuous Planter Curb Trees at 30' o.c. Avg. ST -60 -34 Street T3 -E, T34_, T3, T4, T5 60 feet 34 feet Slow Movement 20 MPH 9.7 seconds 2 lanes Both Sides 7 feet marked 15 feet 6 foot Sidewalk 7 foot continuous Planter Curb Trees at 30' o.c. Avg. BR www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC45 5D' 10' 7' 16' 7' 10' 60' 13' T 10' 10' 7' 13' TABLE 4C. THOROUGHFARE ASSEMBLIES CITY OF CARMEL SMARTCODE Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type 50' 55' Right of Way Width Pavement Width Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP Thoroughfare Type Transect Zone Assignment Right -of -Way Width Pavement Width Movement Design Speed Pedestrian Crossing Time Traffic Lanes Parking Lanes Curb Radius Walkway Type Planter Type Curb Type Landscape Type Transportation Provision CS -50 -22 Commercial Street T5, T6 50 feet 22 feet Slow Movement 20 MPH 6.2 seconds 1 lane One side 8 feet marked 15 feet 18/10 foot Sidewalk 4x4" tree well Curb Trees at 30' o.c. Avg. CS -55 -29 Commercial Street T5, T6 55 feet 29 feet Slow Movement 20 MPH 8.2 seconds 1 lane Both sides 7 feet marked 15 feet 13 foot Sidewalk 4x4" tree well Curb Trees at 30' o.c. Avg. www.tpudc.com SC46 C 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 4C. THOROUGHFARE ASSEMBLIES Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type Right of Way Width Pavement Width Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP Thoroughfare Type Transect Zone Assignment Right -of -Way Width Pavement Width Movement Design Speed Pedestrian Crossing Time Traffic Lanes Parking Lanes Curb Radius Walkway Type Planter Type Curb Type Landscape Type Transportation Provision CS -60 -34 Commercial Street T5, T6 60 feet 34 feet Slow Movement 20 MPH 9.7 seconds 2 lanes Both sides 7 feet marked 10 feet 13 foot Sidewalk 4x4" tree well Curb Trees at 30' o.c. Avg. 80' 18' 8' 14' 14' 8' 18' CE it I i i i CE CS -80 -44 Commercial Street T5, T6 80 feet 44 feet Free Movement 25 MPH 8 seconds at corners 2 lanes Both sides 8 feet marked 10 feet 18 foot Sidewalk 4x4" tree well Curb Trees at 30' o.c. Avg. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC47 60' 13' 7' 10' 10' 7' 13' TABLE 4C. THOROUGHFARE ASSEMBLIES CITY OF CARMEL SMARTCODE Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type Right of Way Width Pavement Width Transportation THOROUGHFARE TYPES Commercial Street C Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP I CS -80 -54 100' 18' 17' 15' 15' 17' 18' I CS- 100 -64 Thoroughfare Type C Commercial Street C Commercial Street Transect Zone Assignment T T5, T6 T T5, T6 Right -of -Way Width 8 80 feet 1 100 feet Pavement Width 5 54 feet 6 64 feet Movement S Slow Movement S Slow Movement Design Speed 2 25 MPH 2 25 MPH Pedestrian Crossing Time 5 5.7 seconds at corners 8 8.5 seconds at corners Traffic Lanes 2 2lanes 2 2lanes Parking Lanes B Both sides angled 17 feet marked B Both sides angled 17 feet marked Curb Radius 1 10 feet 1 10 feet Walkway Type 1 13 foot Sidewalk 1 18 foot Sidewalk Planter Type 4 4X4' tree well 4 4X4' tree well Curb Type C Curb C Curb Landscape Type T Trees at 30' o.c. Avg. T Trees at 30' o.c. Avg. Transportation Provision www.tpudc.com SC48 C 2009 Town Planning Urban Design Collaborative LLC 80' 13' 17' 10' 10' 17 13' CITY OF CARMEL SMARTCODE TABLE 4C. THOROUGHFARE ASSEMBLIES Carmel, Indiana KEY ST- 57 -20 -BL Thoroughfare Type Right of Way Width Pavement Width Transportation THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP Thoroughfare Type Transect Zone Assignment Right -of -Way Width Pavement Width Movement Design Speed Pedestrian Crossing Time Traffic Lanes Parking Lanes Curb Radius Walkway Type Planter Type Curb Type Landscape Type Transportation Provision AV -75 -40 Avenue T3 -E, T34_, T3, T4, T5 75 feet 40 feet total Slow Movement 25 MPH 5.7 seconds 5.7 seconds 2 lanes Both sides 8 feet marked 10 feet 6 foot Sidewalk 7 foot continuous Planter Curb or Swale Trees at 30' o.c. Avg. BR, TR AV -90 -56 Avenue T3 -E, T34_, T3, T4, T5 90 feet 56 feet total Slow Movement 25 MPH 5.7 seconds 5.7 seconds at corners 4 lanes Both sides 8 feet marked 10 feet 6 foot Sidewalk 7 foot continuous Planter Curb or Swale Trees at 30' o.c. Avg. BR, TR www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC49 75' 13' 8' 12' 9' 12' 8' 13 90' 13' 8' 20' 8' 20' 8' 13' TABLE 4C. THOROUGHFARE ASSEMBLIES CITY OF CARMEL SMARTCODE Carmel, Indiana „1- eye l ype 15' 125' Right of Way Width Pavement Width 13' 20' 8' 33' 8' 20' 13' 13' 20' 8' 43' 8' 20' 13' Transportation THOROUGHFARE TYPES Boulevard Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP BV- 115 -33 BV- 125 -43 Thoroughfare Type Boulevard Boulevard Transect Zone Assignment T5, T6 T5, T6 Right -of -Way Width 115 feet 125 feet Pavement Width 20 feet 33 feet 20 feet 20 feet 43 feet 20 feet Movement Free Movement (inner lanes) Free Movement (inner lanes) Design Speed 35 MPH 35 MPH Pedestrian Crossing Time 5.7 seconds 9.4 seconds 5.7 seconds 5.7 seconds -12.2 seconds 5.7 seconds Traffic Lanes 3 lanes, one turning lane two one -way slip roads 4 lanes two one -way slip roads Parking Lanes 8 feet 8 feet Curb Radius 10 feet 10 feet Walkway Type 6 foot Sidewalk 6 foot Sidewalk Planter Type 7 foot continuous Planter 7 foot continuous Planter Curb Type Curb Curb Landscape Type Trees at 30' o.c. Avg. Trees at 30' o.c. Avg. Transportation Provision BR, TR BR, TR www.tpudc.com SC50 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 4C. THOROUGHFARE ASSEMBLIES Carmel, Indiana 135' 135' Right of Way Width Pavement Width 13' 30' 8' 33' 8' 30' 13' 53' Transportation THOROUGHFARE TYPES Boulevard Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP BV- 135 -33 BV- 135 -53 Thoroughfare Type Boulevard Boulevard Transect Zone Assignment T5, T6 T5, T6 Right -of -Way Width 135 feet 135 feet Pavement Width 30 feet 33 feet 30 feet 20 feet 53 feet 20 feet Movement Free Movement Free Movement Design Speed 35 MPH 35 MPH Pedestrian Crossing Time 8.5 seconds 9.4 seconds 8.5 seconds 5.7 seconds -15.1 seconds 5.7 seconds Traffic Lanes 3 lanes, one turning lane two one -way slip roads 5 Lanes, one turning lane two one -way slip roads Parking Lanes 8 feet 8 feet Curb Radius 10 feet 10 feet Walkway Type 6 foot Sidewalk 6 foot Sidewalk Planter Type 7 foot continuous Planter 7 foot continuous Planter Curb Type Curb Curb Landscape Type Trees at 30' o.c. Avg. Trees at 30' o.c. Avg. Transportation Provision BR, TR BR, TR www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC51 TABLE 4C. THOROUGHFARE ASSEMBLIES CITY OF CARMEL SMARTCODE Highway: HW Carmel, Indiana KEY ST- 57 -20 -BL Avenue: AV Thoroughfare Type Drive: DR Right of Way Width Vanes Y Pavement Width Vanes Rear Alley: RA Transportation Rear Lane: RL THOROUGHFARE TYPES Highway: HW Boulevard: BV Avenue: AV Commercial Street: CS Drive: DR Street: ST Y Road: RD Rear Alley: RA Rear Lane: RL Bicycle Trail: BT Bicycle Lane: BL Bicycle Route: BR Path: PT Passage: PS Transit Route: TR Multi -Way/ Multi -Modal Path MP W- Varies Varies Thoroughfare Type Multi -Way Multi -Modal Path (Monon Trail) Transect Zone Assignment T2, T3', T4, T5, T6 Right -of -Way Width 50 feet Pavement Width 10 feet -18 feet Movement N/A Design Speed N/A Pedestrian Crossing Time N/A Traffic Lanes N/A Parking Lanes N/A Curb Radius N/A Walkway Type 10 20 foot Multi -Way/ Multi -Modal Path Planter Type Continuous Planter Curb Type N/A Landscape Type Naturalistic, Opportunistic and Allee depending on Transect Zone Transportation Provision BR, TR www.tpudc.com SC52 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 5. PUBLIC LIGHTING Carmel, Indiana TABLE 5: Public Lighting. Lighting varies in brightness and also in the character of the fixture according to the Transect. The table shows five common types. A listed set of streetlights corresponding to these types would be approved by the utility company and listed on the page. Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC53 Specifications Cobra Head LED fixtures are required. Pipe LED fixtures are required. Post LED fixtures are required. Column LED fixtures are required. Double Column LED fixtures are required. Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC53 TABLE 6. PUBLIC PLANTING CITY OF CARMEL SMARTCODE Carmel, Indiana TABLE 6: Public Planting. This table shows six common types of street tree shapes and their appropriateness within the Transect Zones. The local planning office shall select species appropriate for the bioregion. See Local City Codes for species types. If Specific Species Oval Ball Pyramid Umbrella Vase Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com SC54 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 7. PRIVATE FRONTAGES Carmel, Indiana TABLE 7: Private Frontages. The Private Frontage is the area between the building Facades and the Lot lines. SECTION PLAN a. Common Yard: a planted Frontage wherein the Facade is set back substantially from the Frontage Line. The front yard created remains unfenced and is visually continuous with adjacent yards, supporting a common landscape. The deep Setback provides a buffer from the higher speed Thoroughfares. b. Porch Fence: a planted Frontage wherein the Facade is set back from the Frontage Line with an attached porch permitted to Encroach. A fence at the Frontage Line maintains street spatial definition. Porches shall be no less than 8 feet deep. c. Terrace or Lightwell: a Frontage wherein the Facade is set back from the Frontage line by an elevated terrace or a sunken Lightwell. This type buffers Residential use from urban Sidewalks and removes the private yard from public Encroachment. Terraces are suitable for conversion to outdoor cafes. Syn: Dooryard. d. Forecourt: a Frontage wherein a portion of the Facade is close to the Frontage Line and the central portion is set back. The Forecourt created is suitable for vehicular d rop-offs. This type should be allocated in conjunction with other Frontage types. Large trees within the Forecourts may overhang the Sidewalks. e. Stoop: a Frontagewherein the Facade isaligned close to the Frontage Line with the first Story elevated from the Sidewalk sufficientlyto secure privacy for the windows. The entrance is usually an exterior stair and landing. This type is recommended for ground -floor Residential use. f. Shopfront: a Frontage wherein the Facade is aligned close to the Frontage Line with the building entrance at Sidewalk grade. This type is conventional for Retail use. It has a substantial glazing on the Sidewalk level and an awning that should overlap the Sidewalk to within 2 feet of the Curb. Syn: Retail Frontage. g. Gallery: a Frontage wherein the Facade is aligned close to the Frontage line with an attached cantilevered shed or a lightweight colonnade overlapping the Sidewalk. This type is conventional for Retail use. The Gallery shall be no less than 10 feet wide and should overlap the Sidewalk to within 2 feet of the Curb but shall not encroach upon any existing easement. h. Arcade: a colonnade supporting habitable space that overlaps the Sidewalk, while the Facade at Sidewalk level remains at or behind the Frontage Line. This type is conventional for Retail use. The Arcade shall be no less than 12 feet wide and should overlap the Sidewalk to within 2 feet of the Curb but shall not encroach upon any existing easement.. See Table 8. LOT 0. PRIVATE 0. FRONTAGE .4 R.O.W. LOT R.O.W. .4 PUBLIC PRIVATE PUBLIC FRONTAGE FRONTAGE FRONTAGE I I I I I I I I I I m I I I I I m I I I m I m I i I I, jl I I I m I I I m m I I I I I 1 I m I I I *Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC55 TABLE 8A. BUILDING CONFIGURATION CITY OF CARMEL SMARTCODE Carmel, Indiana TABLE 8: Building Configuration. This table shows the Configurations for different building heights for each Transect Zone. It must be modified to show actual calibrated heights for local conditions. Recess Lines and Expression Lines shall occur on higher buildings as shown. N maximum height as specified in Table 14k. See Section 5.7.1e regarding floor -to- ceiling height. Stepbacks /Arcade Heights. The diagrams below show Arcade Frontages. Diagrams above apply to all other Frontages. SC56 CITY OF CARMEL SMARTCODE TABLE 8B. BUILDING TYPES SPECIFIC Carmel, Indiana a m 0 ai r a a rc T y o r o r r o 1 w r� =o; a rc w w a rc a m RURAL SUB -URBAN m GENERAL URBAN m URBAN CENTER m URBAN CORE .11111 1 ;1111 1 1111 11111 1 1111 1 m II111 E E E= o� a�a 1111 1 1 11111 1 X 1111 1 11111 1 A A 3 E I E o 1 1 1 1 �EE o� jKj E 1 1 1 1 1 1 1 1 r °a E ES 0 r �nL s c Q E Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC57 TABLE 9. BUILDING DISPOSITION CITY OF CARMEL SMARTCODE Carmel, Indiana TABLE 9: Building Disposition. This table approximates the location of the structure relative to the boundaries of each individual Lot, establishing suitable basic building types for each Transect Zone. a. Edgeyard: Specific Types -single family House, cottage, villa, estate house, urban villa. A building that occupies the center of its Lot with Setbacks on all sides. This is the least urban of types as the front yard sets it back from the Frontage, while the side yards weaken the spatial definition of the public Thoroughfare space. The front yard is intended to be visually continuous with the yards of adjacent buildings. The rear yard can be secured for privacy by fences and a well placed Backbuilding and/or Outbuilding. b. Sideyard: Specific Types Charleston single house, double house, zero lot line house, twin. A building that occupies one side of the Lot with the Setback to the other side. A shallow Frontage Setback defines a more urban condition. If the adjacent building is similar with a blank side wall, the yard can be quite private. This type permits systematic climatic orientation in response to the sun or the breeze. If a Sideyard House abuts a neighboring Sideyard House, the type is known as a twin or double House. Energy costs, and sometimes noise, are reduced by sharing a party wall in this Disposition. c. Rearyard: Specific Types Townhouse, Rowhouse, Live -Work unit, loft building, Apartment House, Mixed Use Block, Flex Building, perimeter Block.A building thatoccupies the full Frontage, leaving the rear of the Lot as the sole yard. This is a very urban type as the continuous Facade steadily defines the public Thoroughfare. The rear Elevations may be articulated for functional purposes. In its Residential form, this type is the Rowhouse. For its Commercial form, the rear yard can accommodate substantial parking. d. Courtyard: Specific Types- patio House. Abuilding that occupies the boundaries of its Lotwhile internally defining one or more private patios. This is the most urban of types, as it is able to shield the private realm from all sides while strongly defining the public Thoroughfare. Because of its ability to accommodate incompatible activities, masking them from all sides, it is recommended for workshops, Lodging and schools. The high security provided by the continuous enclosure is useful for crime -prone areas. e. Specialized: A building that is not subject to categorization. Buildings dedicated to manufacturing and transportation are often distorted by the trajectories of machinery. Civic buildings, which may express the aspirations of institutions, may be included. Includes Transect Zones T3, T3 -E and T3 -L. SC58 I I I I m O I I O www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLES 10 11. BUILDING FUNCTION Carmel, Indiana PARKING CALCULATIONS TABLE 10: Building Function. This table categorizes Building Functions within Transect Zones. Parking requirements are correlated to functional intensity. For Specific Function and Use permitted By Right or by Warrant, see Table 12. TABLE 11: Parking Calculations. The Shared Parking Factor for two Functions, when divided into the sum of the two amounts as listed on the Required Parking table below, produces the Effective Parking needed for each site involved in sharing. Conversely, if the Sharing Factor is used as a multiplier, it indicates the amount of building allowed on each site given the parking available. REQUIRED PARKING (See Table 10) MM_ Vj RESIDENTIAL 2.0 dwelling 1.51 dwelling 1.0 /dwelling LODGING 1.01 bedroom 1.01 bedroom 1.01 bedroom OFFICE 3.011000 sq. ft. 3.011000 sq. ft. 2.011000 sq. ft. RETAIL 4.0 1000 sq. ft. 4.0 1000 sq. ft. 3.0 1000 sq. ft. CIVIC To be determined by Warrant OTHER I To be determined by Warrant Includes Transect Zones T3, T3 -E and T3 -L. SHARED PARKING FACTOR Function with Function RESIDENTIAL RESIDENTIAL LODGING LODGING OFFICE a. RESIDENTIAL Restricted Residential: The number of Limited Residential:The numberof dwell- Open Residential: The number ofdwelIings 1.4 1 1.4 RETAIL dwellings on each Lot is restricted to one ings on each Lot is limited bythe requirement on each Lot is limited by the requirement within a Principal Building and one within of 1.5 parking places for each dwelling, a of 1.0 parking places for each dwelling, a an Accessory Building, with 2.0 parking ratio which maybe reduced accord i ng to the ratio which maybe reduced accord i ng to the places for each. Both dwellings shall be shared parking standards (See Table 11). shared parking standards (See Table 11). under single ownership. The habitable area oftheAccessory Unit shall not exceed 440 sf, excluding the parking area. b. LODGING Restricted Lodging: The number of bed- Limited Lodging: The numberof bedrooms Open Lodging: The number of bedrooms rooms available on each Lot for lodging is available on each Lot for lodging is limited available on each Lot for lodging is limited limited by the requirement of 1.0 assigned by the requirement of 1.0 assigned parking by the requirement of 1.0 assigned parking parking place for each bedroom, up to five, places for each bedroom, up to twelve, placesforeach bedroom. Food service may in addition to the parking requirement for in addition to the parking requirement for be provided at all times. The area allocated the dwelling. The Lodging must be owner the dwelling. The Lodging must be owner for food service shall be calculated and occupied. Food service may be provided in occupied.Food service may be provided in provided with parking according to Retail the a.m. The maximum length of stay shall the a.m. The maximum length of stay shall Function. not exceed ten days. not exceed ten days. c. OFFICE Restricted Office: The building area avail- Limited Office: The building areaavailable Open Office: The building area available ableforoffice useon each Lot is restrictedto forofficeuseon each Lotis limited tothefrst for office use on each Lot is limited by the the first Story of the Principal ortheAcces- Story of the principal building and /or to the requirement of 2.0 assigned parking places sory Building and bythe requirement of 3.0 Accessory building, and bythe requirement per 1000 square feet of net office space. assigned parking places per 1000 square of 3.0 assigned parking places per 1000 feet of net office space in addition to the squarefeet of net office space in addition to parking requirement for each dwelling. the parking requirement for each dwelling. d. RETAIL Restricted Retail: The building area avail- Limited Retail: The building area available Open Retail: The building area available ablefor Retail use is restricted to one Block for Retail use is limited to the first Story of forRetail use is limited bythe requirementof corner location at the first Story for each buildings at corner locations, not more than 3.Oassigned parking places per 1000square 300 dwelling units and by the requirement one per Block, and by the requirement of feetof net Retail space. Retail spaces under of 4.0 assigned parking places per 1000 4.0 assigned parking places per 1000 1500 square feet are exempt from parking square feet of net Retail space in addition square feet of net Retail space in addition requirements. tothe parking requirement of each dwelling. tothe parking requirement of each dwelling. The specific use shall be further limited to The specific use shall be further limited to neighborhood store, orfood service seating neighborhood store, orfood service seating no more than 20. no more than 40. e. CIVIC See Table 12 See Table 12 See Table 12 f. OTHER See Table 12 See Table 12 See Table 12 TABLE 11: Parking Calculations. The Shared Parking Factor for two Functions, when divided into the sum of the two amounts as listed on the Required Parking table below, produces the Effective Parking needed for each site involved in sharing. Conversely, if the Sharing Factor is used as a multiplier, it indicates the amount of building allowed on each site given the parking available. REQUIRED PARKING (See Table 10) MM_ Vj RESIDENTIAL 2.0 dwelling 1.51 dwelling 1.0 /dwelling LODGING 1.01 bedroom 1.01 bedroom 1.01 bedroom OFFICE 3.011000 sq. ft. 3.011000 sq. ft. 2.011000 sq. ft. RETAIL 4.0 1000 sq. ft. 4.0 1000 sq. ft. 3.0 1000 sq. ft. CIVIC To be determined by Warrant OTHER I To be determined by Warrant Includes Transect Zones T3, T3 -E and T3 -L. SHARED PARKING FACTOR Function with Function RESIDENTIAL RESIDENTIAL LODGING LODGING OFFICE OFFICE 1.1 1.1 RETAIL 1.4 1 1.4 RETAIL www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC59 TABLE 12. SPECIFIC FUNCTION USE CITY OF CARMEL SMARTCODE Carmel, Indiana TABLE 12: Specific Function Use. This table expands the categories of Table 10 to delegate specific Functions and uses within Transect Zones. Table 12 should be customized for local character and requirements. a. RESIDENTIAL f. OTHER: AGRICULTURE Mixed Use Block Grain Storage Flex Building Livestock Pen Apartment Building Greenhouse Live/Work Unit Stable Row House Kennel Duplex House f. OTHER: AUTO- ORIENTED Courtyard House Sideyard House Cottage House Villa Accessory Unit b. LODGING Hotel (no room limit) Inn (u to 12 rooms) Gasoline Automobile Service Truck Maintenance Drive Through Facility Rest Stopi I Roadside Stand I I Billboard x x x x x x x Shopping Center Shopping Mall p f. OTHER: CIVIL SUPPORT Bed Breakfast (up to 5 rooms) Fire Station S.R.O. hostel Police Station School Dormitory c. OFFICE Cemetery Office Building Cremation/ Funeral Home Live -Work Unit Hospital ri RFT011 I CFR1 11CFC Medical Clinic 177 Open- Market Building Retail Building Display Gallery Restaurant Kiosk Push Cart Personal Services Professional Services Tavern/ Bar/ Liquor Sales Adult Entertainment x x x x x X e. CIVIC Bus Shelter Convention Center Conference Center Exhibition Center Fountain or Public Art Library Live Theater Movie Theater Museum Outdoor Auditorium Parking Structure Passenger Terminal Playground Sports Stadium Surface Parking Lot f. OTHER: EDUCATION College High School Trade School Elementary School Other- Childcare Center f. OTHER: INDUSTRIAL Heavy Industrial Facility Light Industrial Facility Truck Depot Laboratory Facility Water Supply Facility Sewer and Waste Facility Electric Substation Wireless Transmitter Warehousel I I I I I Produce Storage Mini Storage BY RIGHT BY WARRANT X PROHIBITED Includes Transect Zones T3, T3 -E and T3 -L. Religious Assembly www.tpudc.com SC60 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 13. CIVIC SPACE Carmel, Indiana a. Park: A natural preserve available for unstructured recreation. A park may be independent of surrounding building Frontages. Its landscape shall consist of Paths and trails, meadows, waterbodies, woodland and open shelters, all naturalistically disposed. Parks may be lineal, following the trajectories of natural corridors. The minimum size shall be 8 acres. Larger parks may be approved by Warrant as Special Districts in all zones. b. Green: An Open Space, available for unstructured recreation. A Green may be spatially defined by landscaping ratherthan building Frontages. Its landscape shall consistof lawn and trees, natu- ralistically disposed. The minimum size shall be 112 acre and the maximum shall be 8 acres. c. Square: An Open Space available for unstructured recreation and Civic purposes. A Square is spatially defined by building Frontages. Its landscape shall consist of paths, lawns and trees, formally disposed. Squares shall be located at the intersection of important Thoroughfares. The minimum size shall be 112 acre and the maximum shall be 5 acres. d. Plaza: An Open Space available for Civic purposes and Commercial activities. A Plaza shall be spatially defined by building Frontages. Its landscape shall consist primarily of pavement. Trees are optional. Plazas should be located at the intersection of important streets. The minimum size shall be 112 acre and the maximum shall be 2 acres. e. Playground: An Open Space designed and equipped forthe recreation of children. Aplayground should be fenced and may include an open shelter. Playgrounds shall be interspersed within Residential areas and may be placed within a Block. Playgrounds may be included within parks and greens. There shall be no minimum or maximum size. Includes Transect Zones T3, T3 -E and T3 -L. www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC A SC61 T4 T5 T6 T6 11147IT5 T2 LJ SC61 TABLE 14. SMARTCODE SUMMARY CITY OF CARMEL SMARTCODE Carmel, Indiana a. ALLOCATION OF ZONES per Pedestrian Shed (applicable to Article 3 only) 200 fl. min. 100 fl. min.- 72 fl. min 120 fl. max M (see Table 16) CLD requires no minimum 50% min 10 -30 1 20 -40% 1 notpermined not permitted TND requires permitted 10 -30 1 30 -60% 1 10 -30% not permitted RCD requires no minimum no minimum notpermined notpermined not permitted 1 10 -30% 1 10 -30% 40 -80% b. BASE RESIDENTIAL DENSITY (sce Section 3.4) permitted AV not permitted not permitted permitted By Right notapplicable 1unit120acaq 1unit I acgross 2units -gross 4units I gross 12 units I ac. gross 24 units I ac. gross 96 units I an, gross Other Fu notions by Varbnce by Varbnce 10 -20% 10 -20% 10 -20% not permitted not permitted 1 50 -70% d.THOROUGHFARES (sce Table3and Table4) by Warrant 200 fl. min. 100 fl. min.- 72 fl. min 120 fl. max M 18 fl. min 96 fl. max 18 fl. min 180 fl. max 3000 ft. max with parking structures HW permitted permitted permitted permitted permitted not permitted not permitted not permitted BV not permitted not permitted permitted permitted permitted permitted permitted permitted AV not permitted not permitted permitted permitted permitted permitted permitted permitted CS not permitted not permitted not permitted not permitted not permitted not permitted permitted permitted DR not permitted not permitted Permitted permitted permitted permitted Permitted permitted ST not Permitted not Permitted Permitted permitted permitted permitted permitted not permitted RD permitted permitted Permitted permitted permitted not Permitted not permitted not permitted Rear lane permitted Permitted Permitted permitted Permitted Permitted not permitted not permitted Rear Alley not Permitted not Permitted Permitted permitted Permitted required required required Path permitted Permitted Permitted permitted Permitted Permitted not permitted not permitted Passage not Permitted not Permitted permitted permitted Permitted Permitted permitted permitted Bicycle Trail Permitted Permitted Permitted Permitted Permitted notpermined not permitted not permitted Bicycle lane Permitted Permitted Permitted Permitted Permitted Permitted not permitted not permitted Bicycle Route e. CIVIC SPACES (sce Table 13) permitted Permitted Permitted Permitted Permitted permitted except in Open Spaces Permitted permitted Park Permitted Permitted Permitted Permitted Permitted by Warrant by Warrant by Warrant Green not Permitted not Permitted Permitted permitted permitted permitted permitted not permitted Square not Permitted not Permitted not Permitted not permitted not permitted permitted permitted permitted Plana not Permitted not permitted not permitted not permitted not permitted not Permitted permitted permitted Playground permitted permitted permitted permitted permitted permitted Permitted permitted Lot Width notapplifable by Warrant 200 fl. min. 100 fl. min.- 72 fl. min 120 fl. max M 18 fl. min 96 fl. max 18 fl. min 180 fl. max 18 fl. min 700 fl. max La Coverage notapplifable g. SETBACKS PRINCIPAL BUILDING (see Table 15) by Warrant 10 %max 20 %max 50% ma 60 %max 80 %max 90% (Ol) Front Setback (Principal) not applicable 48 fl. min. 10011. min. 30 fl. min. 48 fl max. 24 fl. min. 30 fl. max. Oft. min. 18 fl. max. 0 fl. min. 12 fl. max. Oft. min. 12 fl. max. (g.2)Front Setback (Secondary) not applicable 48 fl. min. 100 fl. min. 30 fl. min. 48 fl. max. 24 fl. min. 30 fl. max. Oft. min. 18 fl. max. 0 fl. min. 12 fl. max. Oft. min. 12 fl. max. (03) Side Setback not applicable 96 fl. min. 24 fl. min. 12 fl. min. 18 fl. max. 12 fl. min. Oft. min. 0 fl. min. 24 fl. max. 0 fl. min. 24 fl. max. (g.4) Rear Setback not applicable 96 fl. min. 100 fl. min. 60 fl. min. 60 fl. min. 3 ft. min. 3 fl. min. 0 fl. min. Frontage Buildout notapplifable h. SETBACKS OUTBUILDING (sce Table 15) notapplifable 30% min. 40% min. 5)% min. 60% min. 80% min. 80% min. (h.1) Front Setback Fmtaplpicab. 20 fl. min +bldg seback 20 fl. min +bldg setback 20 fl. min +bldg setback 20 fl. min +bldg setback 20 ft. min +rag setback 40 ft max from mar prop notapplirable (h2) Sid. Setback notapplifable 3 ft. or 6 ft. at corner 3 ft. or 6 ft. at corner 3 ft. or 6 ft. at corner 3 ft. or 6 ft. at corner O ft. min or 3 ft. at corner Oft min notapplirable (h.3) Rear Setback notapplifable i. BUILDING DISPOSITION (sce Table 9) 3ft. min 3ft. min 3ft. min 3ft. min 3ft. min 3ft. min notapplicable Edgeyard permitted permitted permitted permitted permitted Permitted not permitted not permitted Sideyard notpermined not Permitted not permitted not permitted not Permitted Permitted permitted not permitted Rearyard notpermined not Permitted not Permitted not permitted not Permitted Permitted permitted permitted Courtyard notpermined not Permitted not Permitted not permitted not Permitted Permitted permitted permitted j. PRIVATE FRONTAGES (see Table 7) Common Yard notapplifable Permitted Permitted Permitted Permitted not Permitted not permitted not permitted Perth &Fence notapplifable notpermined Permitted permitted permitted Permitted not permitted not permitted Terrace or DOOryard notapplifable notpermitled not Permitted not Permitted not permitted Permitted permitted not permitted Forecourt notapplifable not permitted not Permitted not Permitted not permitted Permitted permitted permitted Stoop notapplifable not permitted not permitted not Permitted not permitted Permitted permitted permitted Shopfront &Awning notapplifable not permitted not permitted not Permitted not permitted Permitted permitted permitted Gallery notapplifable not permitted not permitted not Permitted not permitted permitted permitted permitted Arcade notapplifable not permitted not permitted not Permitted not permitted not Permitted permitted permitted Residential I notapplifable I restricted use I restricted use I restricted use I restricted use I limited use I open use I open use Lodging notapplifable restricted use restricted use restricted use restricted use limited use open use open use ORce notapplifable restricted use restricted use restricted use restricted use limited use open use open use Retail notapplifable restricted use restricted use restricted use restricted use limited use open use open use ARTICLE 5 Aggregate for T3, T3 -E and T3 -L www.tpudc.com SC62 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 15A. FORM -BASED CODE GRAPHICS T2 Carmel, Indiana (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I restricted use Lodging restricted use Office restricted use Retail restricted use k. BUILDING CONFIGURATION (see Table 8) Principal Building 12 stories max. Outbuilding 12 stories max. f. LOT OCCUPATION (see Table 14f) Lot Width I by Warrant Lot Coverage I by Warrant I. BUILDING DISPOSITION (see Table 9) Edgeyard permitted Sideyard not permitted Rearyard not permitted Courtyard not permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback 148 ft. min (g.2) Side Setback 148 ft min. (g.3) Rear Setback 196 ft min. Frontage Buildout I not applicable h. SETBACKS OUTBUILDING (see Table 14h) (h.1) Front Setback 120 ft. min. bldg setback (h.2) Side Setback 13 ft. or 6 ft at corner (h.3) Rear Setback 3 ft. min* j. PRIVATE FRONTAGES (see Table 7) Common Lawn permitted Porch Fence not permitted Terrace or L.C. not permitted Forecourt not permitted Stoop not permitted Shopiront Awning not permitted Gallery not permitted Arcade not permitted Refer to Summary Table 14 PARKING PROVISIONS See Table 10 Table 11 or 15 ft. from center line of alley/ lane ForTown Districts and CountrySegments, see also Sections 3.10 3.12 and Tables 6A, 613-1, 613-2 and 613-3 BUILDING CONFIGURATION 1. Building height shall be mea- sured in number of Stories, excluding Attics and raised basements. 2. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a Max.haght 1� first floor Commercial Function 2 Max. height which must be a minimum of 11 2 feet and may exceed 14 feet. A fi first floor Commercial function 1 that exceeds 14 feet shall be treated as 2 stories. 3. Height shall be measured to the eave or roof deck as specified on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. 2. Facades shall be built along the Principal Frontage to the minimum specified width in the table. I i (g- I I h (g•1) i I I It Layer I i Corner Lot g,3) Condition I I g'3) Mid -Block I Condition SETBACKS OUTBUILDING 1. The Elevation of the Outbuilding shall be distanced from the Lot lines as shown. I i i N (h. i (h. r .i (h.2) I h.3) I I N h.3) 1st 2nd Layer Layer 20 ft Corner Lot Condition Mid -Block Condition PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the Second and Third Lot Layers as shown in the diagram (see Table 17d). 2. Covered parking shall be provided within the Third Lot Layeras shown in the diagram (see Table 17d). Side- or rear -entry garages may be allowed in the First or Second Lot Layers by Warrant. Seoonda Frontage 1st 2nd 3rd Layer Layer 20 ft Layer i i i of s °1 al I i I Corner Lot Condition Mid -Block Condition www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC63 TABLE 15B. FORM -BASED CODE GRAPHICS T3 -E CITY OF CARMEL SMARTCODE Carmel, Indiana (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I restricted use Lodging restricted use Office restricted use Retail restricted use k. BUILDING CONFIGURATION (see Table 8) Principal Building 12.5 stories max. Outbuilding 12 stories max. f. LOT OCCUPATION (see Table 14f) Lot Width 1100 ft. min 200 ft. max Lot Coverage 20% max L BUILDING DISPOSITION (see Table 9) Edgeyard permitted Sideyard not permitted Rearyard not permitted Courtyard not permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback 1100 ft. min (g.2) Side Setback 124 ft min. (g.3) Rear Setback I 100 ft min. h. SETBACKS OUTBUILDING (see Table 14h) (h.1) Front Setback 120 ft. min. bldg setback (h.2) Side Setback 13 ft. or 6 ft. at corner (h.3) Rear Setback 13 ft. min. j. PRIVATE FRONTAGES (see Table 7) Common Lawn permitted Porch Fence permitted Terrace or L.C. not permitted Forecourt not permitted Stoop not permitted Shopiront Awning not permitted Gallery not permitted Arcade not permitted Refer to Summary Table 14 PARKING PROVISIONS See Table 10 Table 11 Corner lot minimum must be 12 ft. wider "N" stands for any Stories above those shown, up to the maximum. RefertoTable 14 metricsforexactminimums and maximums BUILDING CONFIGURATION 1. Building height shall be mea- sured in number of Stories, excluding Attics and raised basements. 2. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a Max.haght N first floor Commercial Function Max. height which must be a minimum of 11 feet and may exceed 14 feet. A fi 1 first floor Commercial function that exceeds 14 feet shall be treated as 2 stories. 3. Height shall be measured to the eave or roof deck as specified on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. 2. Facades shall be built along the Principal Frontage to the minimum specified width in the table. I I Corner Lot g -3) Condition I i 9'3) N Mid -Block Condition 4 I Layer I I (g I t------- i ti (g•1) i SETBACKS OUTBUILDING 1. The Elevation of the Outbuilding shall be distanced from the Lot lines as shown. (g1)________ (h.2) I h.3) I I N h.2 L 1st 2nd Layer Layer 20 ft I i i N I I J I Corner Lot Condition Mid -Block Condition PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the Second and Third Lot Layers as shown in the diagram (see Table 17d). 2. Covered parking shall be provided within the Third Lot Layeras shown in the diagram (see Table 17d). Side- or rear -entry garages may be allowed in the First or Second Lot Layers by Warrant. Secondary Frontage i I 1 st Layer L_._- 2nd 3rd Layer 20 ft Layer i i Corner Lot Condition I i i Mid -Block I Condition I i www.tpudc.com SC64 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 15C. FORM -BASED CODE GRAPHICS T3 -L Carmel, Indiana (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I restricted use Lodging restricted use Office restricted use Retail I restricted use k. BUILDING CONFIGURATION (see Table 8) Principal Building 12.5 stories max. Outbuilding 12 stories max. f. LOT OCCUPATION (see Table 14f) Lot Width 172 ft. min 100 ft. max Lot Coverage 40% max I. BUILDING DISPOSITION (see Table 9) Edgeyard permitted Sideyard not permitted Rearyard not permitted Courtyard not permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback 130 ft. min 48 ft. max (g.2) Side Setback 12 ft min 18 ft. max. (g.3) Rear Setback 60 ft min. h. SETBACKS OUTBUILDING (see Table 14h) (h.1) Front Setback 120 ft. min. bldg setback (h.2) Side Setback 13 ft. or 6 ft. at corner (h.3) Rear Setback 3 ft. min* j. PRIVATE FRONTAGES (see Table 7) Common Lawn permitted Porch Fence permitted (fence 36" max. ht) Terrace or L.C. not permitted Forecourt not permitted Stoop not permitted Shopiront Awning not permitted Gallery not permitted Arcade not permitted Refer to Summary Table 14 PARKING PROVISIONS See Table 10 Table 11 72 ft. min. w/ rear alley or 15 ft. from center line of alley Corner lot minimum must be 12 ft. wider "N" stands for any Stories above those shown, up to the maximum. RefertoTable 14 metricsforexactminimums and maximums BUILDING CONFIGURATION 1. Building height shall be mea- sured in number of Stories, excluding Attics and raised basements. 2. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a Max.haght 1� first floor Commercial Function N Max. height which must be a minimum of 11 2 feet and may exceed 14 feet. A fi first floor Commercial function 1 that exceeds 14 feet shall be treated as 2 stories. 3. Height shall be measured to the eave or roof deck as specified on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. 2. Facades shall be built along the Principal Frontage to the minimum specified width in the table. i (g,1) I t I h (g -1) i i i st Layer 4 g r I i g -3) i I I g -3) H I i i Corner Lot Condition Mid -Block Condition SETBACKS OUTBUILDING 1. The Elevation of the Outbuilding shall be distanced from the Lot lines as shown. I i i (I I i J (I I I I h.3] I I .1) N i h.3] 1st 0 2nd Layer Layer 20 ft Corner Lot Condition Mid -Block Condition PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the Second and Third Lot Layers as shown in the diagram (see Table 17d). 2. Covered parking shall be provided within the Third Lot Layeras shown in the diagram (see Table 17d). Side- or rear -entry garages may be allowed in the First or Second Lot Layers by Warrant. 1 r 1st 2nd 3rd Layer Layer 20 ft Layer I i I 1 I 1 i I i I Corner Lot Condition Mid -Block Condition www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC65 TABLE 15D. FORM -BASED CODE GRAPHICS T3 CITY OF CARMEL SMARTCODE Carmel, Indiana (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I restricted use Lodging restricted use Office restricted use Retail restricted use BUILDING CONFIGURATION 1. Building height shall be mea- sured in number of Stories, excluding Attics and raised basements. 2. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a Max. height first floor Commercial Function N 11ax1e9't which must be a minimum of 11 2 feet and may exceed 14 feet. A fi first floor Commercial function that exceeds 14 feet shall be treated as 2 stories. 3. Height shall be measured to the eave or roof deck as specified on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. 2. Facades shall be built along the Principal Frontage to the minimum specified width in the table. (9. i (9.3) Corner Lot Condition k. BUILDING CONFIGURATION (see Table 8) Principal Building 12.5 stories max. Outbuilding 12 stories max. f. LOT OCCUPATION (see Table 14f) Lot Width 160 ft. min 72 ft. max Lot Coverage 60% max I. BUILDING DISPOSITION (see Table 9) Edgeyard permitted Sideyard not permitted Rearyard not permitted Courtyard not permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback 24 ft. min 30 ft. max (g.2) Side Setback 112 ft min (g.3) Rear Setback 160 ft min. Frontage Buildout 50% min at setback h. SETBACKS OUTBUILDING (see Table 14h) (h.1) Front Setback 120 ft. min. bldg setback (h.2) Side Setback 13 ft. or(6 ft. or24 ft. atcorner) (h.3) Rear Setback 13 ft. min` j. PRIVATE FRONTAGES (see Table 7) Common Lawn permitted Porch Fence permitted (fence 36" max. ht) Terrace or L.C. not permitted Forecourt not permitted Stoop not permitted Shopfront Awning not permitted Gallery not permitted Arcade not permitted Refer to Summary Table 14 PARKING PROVISIONS 1st 2nd See Table 10 Table 11 60 ft. min. w/ rear alley or 15 ft. from center line of alley Corner lot minimum must be 12 ft. wider "N" stands for any Stories above those shown, up to the maximum. Refer to Table 14 metrics far exact minimums and maximums 1 (9'3) 14 Mid -Block 1 V Condition I St 0 Layer SETBACKS OUTBUILDING 1. The Elevation of the Outbuilding shall be distanced from the Lot lines as shown. PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the Second and Third Lot Layers as shown in the diagram (see Table 17d). 2. Covered parking shall be provided within the Third Lot Layeras shown in the diagram (see Table 17d). Side- or rear -entry garages may be allowed in the First or Second Lot Layers by Warrant. s r -i —(h.2) I 1 h.3) Corner Lot P4 (h• I '1 14 II Condition --I -r i 1 1 I J (h• 1 N I h.3) 1 Mid -Block h.2 Condition L 1----- —J 1st 2nd Layer Layer 20 ft Secondary Frontage Corner Lot Condition Mid -Block Condition L............ 1st 2nd 3rd Layer Layer 20 ft Layer I i i M .I 'i i i 1 www.tpudc.com SC66 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 15E. FORM -BASED CODE GRAPHICS T4 Carmel, Indiana (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I limited use Lodging limited use Office limited use Retail limited use k. BUILDING CONFIGURATION (see Table 8) Principal Building 3 stories max, 2 min Outbuilding 2 stories max. f. LOT OCCUPATION (see Table 14f) Lot Width 118 ft min 96 ft max Lot Coverage 70% max 1. BUILDING DISPOSITION (see Table 9) Edgeyard permitted Sideyard permitted Rearyard permitted Courtyard not permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback Principal 0 ft. min. 18 ft. max. (g.2) Side Setback 0 ft. min. (g.3) Rear Setback l3ft.min Frontage Buildout 60% min at setback h. SETBACKS OUTBUILDING (see Table 14h) (h.1) Front Setback 20 ft. min. bldg. setback (h.2) Side Setback 0 ft. min. or 3 ft. at corner (h.3) Rear Setback 3 ft. min j. PRIVATE FRONTAGES (see Table 7) Common Lawn not permitted Porch &Fence permitted (fence 36"max.ht) Terrace or L.C. permitted Forecourt permitted Stoop permitted Shopfront &Awning permitted Gallery permitted Arcade not permitted floor Commercial Function which Refer to Summary Table 14 PARKING PROVISIONS See Table 10 Table 11 or 15 ft. from center line of alley Single story buildings may be included provided that in the aggregate they do not exceed 15% of the total Frontage of a Block along any Thoroughfare. A Corner lot side setbacks shall match corresponding front setback Corner lot minimum must be 8 ft. wider "N" stands for any Stories above those shown, up to the maximum. Refer to Table 14 metrics for exact minimums and maximums BUILDINGCONFIGURATION F 1. Building height shall be mea- I I h sured in number of Stories, I L_ excluding Attics and raised basements. 2. Stories may not exceed 14 feet Maz.height in height from finished floor to N finished ceiling, except for a first floor Commercial Function which Min. height 0- must be a minimum of 11 feet 2 min. Maz. height 2 and may exceed 14 feet. A first floor Commercial function that fi 1 exceeds 14 feet shall be treated 1 as 2 stories. 3. Height shall be measured to the eave or roof deck as specified on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. F (9. 2. Facades shall be built along I Comer Lot the Principal Frontage to the 1 (g 1 (g.3) Condition minimum specified width in the table. I I I Mid Block 0- 1 (g- 4 (g• 1, Condition I (g.2) L_ —1 V J Ist Layer SETBACKS OUTBUILDING 1. The Elevations of the Out- building shall be distanced f th L t1i h (h.2) V rom e o mes ass own. F I I I I h I L_ Comer Lot Condition I I Mid -Block Condition I J is f 2nd Layer Layer 20 ft PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the Third Lot Layer as shown in the diagram (see Table 17d). 2. Covered parking shall be provided within the Third Lot Layeras shown in the diagram (see Table 17d). Secondary Frontage F I I rT i 1 i I I I i I i i I i I I I I I L_ J 1st 2nd 3rd Layer Layer 20 ft Layer Comer Lot Condition Mid -Block Condition www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC67 TABLE 15F. FORM -BASED CODE GRAPHICS T5 CITY OF CARMEL SMARTCODE Carmel, Indiana (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I open use Lodging open use Office I open use Retail I open use k. BUILDING CONFIGURATION (see Table 8) Principal Building 15 stories max. 2 min A Outbuilding 12 stories max. f. LOT OCCUPATION (see Table 14f) Lot Width 118 ft min 180 ft max Lot Coverage 80% max I. BUILDING DISPOSITION (see Table 9) Edgeyard not permitted Sideyard permitted Rearyard permitted Courtyard permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback Principal 10 ft. min. 12 ft. max. (g.2) Side Setback 10 ft. min. 24 ft. max. (g.4) Rear Setback 13 ft. min.` Frontage Buildout 80% min at setback h. SETBACKS OUTBUILDING (see Table 14h) (h.1) Front Setback 140 ft. max. from rear prop. (h.2) Side Setback 10 ft. min. (h.3) Rear Setback 13 ft. max. j. PRIVATE FRONTAGES (see Table 7) Common Lawn not permitted Porch Fence not permitted Terrace or L.C. permitted Forecourt permitted Stoop permitted Shopfront Awning I permitted Gallery I permitted Arcade I permitted Refer to Summary Table 14 PARKING PROVISIONS See Table 10 Table 11 BUILDING CONFIGURATION 1. Building height shall be measured in number of Stories, excluding Attics and Max heig5t raised basements. N 2. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a Min he9rt_,� 3 first floor Commercial Function 2 min.§ Max. height which must be a minimum of 11 feet and may exceed 14 feet. A 11 2 first floor Commercial function 11 1 1 that exceeds 14 feet shall be treated as 2 stories. 3. Height shall be measured to the eave or roof deck as specified on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. 2. Facades shall be built along the Principal Frontage to the minimum specified width in the table. Corner Lot Condition Mid -Block Condition ist Layer SETBACKS OUTBUILDING 1. The Elevationsof the Outbuilding shall be distanced from the Lot lines as shown. I (h.3) r Corner Lot j (h.1) 114 Condition I (h'1) Mid -Block I I 3) Condition L. 1 0. 1 J (h.2) PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the Third Lot Layer as shown in the diagram (see Table 17d). Li L1 2. Covered parking shall be S Frontage provided within the Third Lot I Layeras shown in the diagram (see Table 17d). i corner Lot Condition II Mid -Block a l I I Condition L J 1st 2nd 3rd Layer Layer20ft Layer For Town Districts and Country Segments, see also Sections 3.10 3.12 and Tables 6A, 613-1, 613-2 and 613-3 or 15 ft. from center line of alley Single story buildings may be included provided that in the aggregate they do not exceed 15% of the total Corner lot side setbacks shall match corresponding front Frontage of a Block along any Thoroughfare. setback "N" stands for any Stories above those shown, up to the Corner lot minimum must be 8 ft. wider maximum. RefertoTable 14 metricsforexactminimums and maximums p www.tpudc.com S C68 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 15G. FORM -BASED CODE GRAPHICS T6 Carmel, Indiana I dE U (see Table 1) I. BUILDING FUNCTION (see Table 10 Table 12) Residential I open use Lodging open use Office open use Retail open use k. BUILDING CONFIGURATION (see Table 8) Principal Building 8 stories max. 2 min. Outbuilding N/A f. LOT OCCUPATION (see Table 14f) Lot Width 118 ft. min 700 ft. max Lot Coverage F90% max i. BUILDING DISPOSITION (see Table 9) Edgeyard not permitted Sideyard not permitted Rearyard permitted Courtyard permitted g. SETBACKS PRINCIPAL BUILDING (see Table 14g) (g.1) Front Setback Puncipal 10 ft. min. 12 ft. max. (g.2) Front Setback Seoondaryl 0 ft. min. 12 ft. max. (g.3) Side Setback 10 ft. min. 24 ft. max. (g.4) Rear Setback 10 ft. min. Frontage Buildout 80% min. at setback h. SETBACKS OUTBUILDING (see Table 14h) Front Setback N/A Side Setback N/A Rear Setback N/A j. PRIVATE FRONTAGES (see Table 7) Common Lawn not permitted Porch Fence not permitted Terrace or L.C. not permitted Forecourt permitted Stoop permitted Shopfront Awning permitted Gallery permitted Arcade permitted Refer to Summary Table 14 PARKING PROVISIONS See Table 10 Table 11 *or 15 ft. from center line of alley "N" stands far any Stories above those shown, up to the maximum. RefertoTable 14 metrics for exact minimums and maximums BUILDING CONFIGURATION 1. Building height shall be mea- sured in number of Stories, excluding Attics and raised basements. 2. Stories may not exceed 14 feet in height from finished floor to finished ceiling, except for a first floor Commercial Function which must be a minu mu m of 11 ft with with a maximum of 25 ft. 3. Heightshall be measured to the eave or roof deck as specified on Table 8. 4. Stepbacks, Recess Lines, and Extension Lines shall be as shown on Table 8. SETBACKS PRINCIPAL BLDG 1. The Facades and Elevations of Principal Buildings shall be distanced from the Lot lines as shown. 2. Facades shall be built along the Principal Frontage to the minimum specified width in the table. (g• s Comer Lot Condition o (g• (g• o Mid -Block n (g.l) (g.4) P. Condition (g•3) o L. PARKING PLACEMENT 1. Uncovered parking spaces may be provided within the third Layer as shown in the diagram (see Table 17d). 2. Covered parking shall be provided within the third Layer as shown in the diagram (see Table 17d). 3. Trash containers shall be stared within the third Layer. F I I @I I a I I I I dam. 1,t 2nd 3 Layer Layer Layer Comer Lot Condition Mid -Block Condition www.tpudc.com 2009 Town Planning Urban Design Collaborative LLC SC69 TABLE 16. SPECIAL DISTRICT STANDARDS CITY OF CARMEL SMARTCODE Carmel, Indiana The metrics for each column of this table (SDI, SD2, etc.) are to be filled in for each Special District as they currently exist, or as they are permitted. More pages can be added. Special Districts that do not have provisions within this Code shall be governed by the standards of the pre- existing zoning. SD1 SD2 SD3 SD4 SD5 SD6 SD7 a. ALLOCATION OF ZONES GILD X TIMID X TOD X b. BASE RESIDENTIAL DENSITY By Right X By TOR X Other Functions X c. BLOCK SIZE X Block Perimeter X d. THOROUGHFARES HW X BBV AV X CS DR X ST F X RD X Rear Lan Rear Alley Path Passages Bicycle Tram La Bicycle Route e. CIVIC SPACES Park X Green Squares Plaza Playground Lot Width I X Lot Coverage I X g. SETBACKS PRINCIPAL BUILDING Front Setback X Side Setback X Rear Setback X h. BUILDING Disposition Edgeyard X Sideyard X Rea and X i. PRIVATE FRONTAGES Common Yard X Porch Fence X Terrace, Dooryard X Forecourt X Stoop X Shopfront X Gallery X Arcade X Parking Lot X j. BUILDING CONFIGURATION Principal Building I X Outbuilding X k. BUILDING FUNCTION Residential X Lodging X Office X Retail X 0 F 0 v z 0 c� z 0 U z 0 F z www.tpudc.com S C70 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE TABLE 17. DEFINITIONS ILLUSTRATED Carmel, Indiana a. THOROUGHFARE FRONTAGES Building Private Public Vehicular Public Private Building Frontage I Frontage Lanes Frontage I Frontage Private Lot b. TURNING RADIUS I i I� i i J J m JE C Y 0 O Thoroughfare (R.O.W.) I Private Lot c. BUILDING DISPOSITION I I I I I I I I I 1- Radius at the Curb 2- Effective Turning Radius 8 ft) d. LOT LAYERS I I I I di I Ri i of I I j PnncipalVrontage _._._._._._.l._._._._._._.J s R M N f. SETBACK DESIGNATIONS V 3 3 i I N2 i �i 2i4 i i I j 1 I 1 i _._._._._._.l._._._._._._.J e. FRONTAGE LOT LINES I I I 3rd layer i 2 !1 4 4 4 3 j 2nd layer j cN I cN 1stlayer 3 I 3 i ._._._.l._._._,....... 1 -Front Setback 2 -Side Setback 3 -Rear Setback 2009 Town Planning Urban Design Collaborative LLC 1- Principal Building 2- Backbuilding 3- Outbuilding 1- Frontage Line 2 -Lot Line 3- Facades 4- Elevations SC71 g. NETWORK -BASED PEDESTRIAN SHED ARTICLE 7. DEFINITIONS OF TERMS CITY OF CARMEL SMARTCODE Carmel, Indiana DEFINITIONS This Article provides definitions for terms in this Code that are technical in nature or that otherwise may not reflect a common usage of the term. If a term is not defined in this Article, then the PRC shall determine the correct definition. Items in italics refer to Articles, Sections, or Tables in the SmartCode. A -Grid: cumulatively, those Thoroughfares that by virtue of their pre- existing pedestrian- supportive qualities, or their future importance to pedestrian connectiv- ity, are held to the highest standards prescribed by this Code. See B -Grid. (Syn: primary grid.) Accessory Building: an Outbuilding with an Accessory Unit. Accessory Unit: an Apartment not greater than 440 square feet sharing owner- ship and utility connections with a Principal Building; it may or may not be within an Outbuilding. See Table 70 and Table 77 (Syn: ancillary unit) Adjusted Pedestrian Shed: a Pedestrian Shed that has been adjusted according to Section 3.2, creating the regulatory boundary of a Community. Affordable Housing: dwellings consisting of rental or for -sale units that have a rent (including utilities) or mortgage payment typically no more than 30% of the income of families earning no more than 80% of median incomes by family size for the county. Allee: a regularly spaced and aligned row of trees usually planted along a Thor- oughfare or Path. Apartment: a Residential unit sharing a building and a Lot with other units and /or uses; may be for rent, or for sale as a condominium. Arcade: a Private Frontage conventional for Retail use wherein the Facade is a colonnade supporting habitable space that overlaps the Sidewalk, while the Facade at Sidewalk level remains at the Frontage Line. Artisan Light Industrial: a Function that is non noxious, generates moderate noise in the creation, in a workshop or studio setting, assemblage and repair of artisan goods and crafts, including retail sales thereof, including without limitation, woodworking, metalworking, glass blowing, and other creative endeavors. Attic: the interior part of a building contained within a pitched roof structure. Avenue (A1): a Thoroughfare of high vehicular capacity and low to moderate speed, acting as a short distance connector between urban centers, and usually equipped with a landscaped median. B -Grid: cumulatively, those Thoroughfares that by virtue of their use, location, or absence of pre- existing pedestrian supportive qualities, may meet a standard lower than that of the A -Grid. See A -Grid. (Syn: secondary grid.) BRT: see Bus Rapid Transit. Backbuilding: a single -Story structure connecting a Principal Building to an Out- building. See Table 77 Base Density: the number of dwelling units per acre before adjustment for other Functions and /or TDR. See Density. Bed and Breakfast: an owner occupied Lodging type offering 1 to 5 bedrooms, permitted to serve breakfast in the mornings to guests. www.tpudc.com SC72 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 7. DEFINITIONS OF TERMS Carmel, Indiana Bicycle Lane (BL): a dedicated lane for cycling within a moderate -speed vehicular Thoroughfare, demarcated by striping. Bicycle Route (BR): a Thoroughfare suitable for the shared use of bicycles and automobiles moving at low speeds. Bicycle Trail (BT): a bicycle way running independently of a vehicular Thoroughfare. Block: the aggregate of private Lots, Passages, Rear Alleys and Rear Lanes, circumscribed by Thoroughfares. Block Face: the aggregate of all the building Facades on one side of a Block. Boulevard (BV): a Thoroughfare designed for high vehicular capacity and moderate speed, traversing an Urbanized area. Boulevards are usually equipped with Slip Roads buffering Sidewalks and buildings. Building of Value: any building designated as such by the Department and identi- fied on an itemization prepared by the Dapartment and made available to the public upon request. Brownfield: an area previously used primarily as an industrial site. Bus Rapid Transit: a rubber tire system with its own right -of -way or dedicated lane along at least 70% of its route, providing transit service that is faster than a regular bus. By Right: characterizing a proposal or component of a proposal for a Community Regulating Plan or Building and Lot Regulating Plan (Article 3, Article 4, orArticle 5) that complies with the SmartCode and is permitted and processed administratively, without public hearing. See Warrant and Variance. CLD or Clustered Land Development: a Community Type structured by a Standard Pedestrian Shed oriented toward a Common Destination such as a general store, Meeting Hall, schoolhouse, or church. CLD takes the form of a small settlement standing free in the countryside. See Table 2 and Table 74 Item a. (Syn: Hamlet, Conservation Land Development, cluster) CRC: Consolidated Review Committee. Civic: the term defining not for profit organizations dedicated to arts, culture, educa- tion, recreation, government, transit, and municipal parking. Civic Building: a building operated by not for profit organizations dedicated to arts, culture, education, recreation, government, transit, and municipal parking, or for use approved by the legislative body. Civic Parking Reserve: Parking Structure or parking lot within a quarter -mile of the site that it serves. See Section 5.9.2. Civic Space: an outdoor area dedicated for public use. Civic Space types are defined by the combination of certain physical constants including the relationships among their intended use, their size, their landscaping and their Enfronting buildings. See Table 73 Civic Zone: designation for public sites dedicated for Civic Buildings and Civic Space. Commercial: the term collectively defining workplace, Office, Retail, and Lodging Functions. Common Destination: An area of focused community activity, usually defining the approximate center of a Pedestrian Shed. It may include without limitation one or more of the following: a Civic Space, a Civic Building, a Commercial center, or a www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC73 ARTICLE 7. DEFINITIONS OF TERMS CITY OF CARMEL SMARTCODE Carmel, Indiana transit station, and may act as the social center of a neighborhood. Common Yard: a planted Private Frontage wherein the Facade is set back from the Frontage line. It is visually continuous with adjacent yards. See Table 7 Community: a regulatory category defining the physical form, Density, and extent of a settlement. See Community Type. Community Type: One of the categories of Community addressed in this Code, being CLD, TND, RCD and TOD. Variants of TND and RCD for Infill (Article 4) are called Infill TND and Infill RCD. The TOD may be created by an overlay on TND or RCD. Configuration: the form of a building, based on its massing, Private Frontage, and height; one element of Building Type.. Corridor: a lineal geographic system incorporating transportation and /or Greenway trajectories. A transportation Corridor may be a lineal Transect Zone. Cottage: an Edgeyard building type, typically built initially for single family dwelling with successional use as Retail, Commercial, or Office Function, on a regular Lot, often shared with an Accessory Building in the back yard. Courtyard Building: a building that occupies the boundaries of its Lotwhile internally defining one or more private patios. See Table 9. Curb: the edge of the vehicular pavement that may be raised or flush to a Swale. It usually incorporates the drainage system. See Table 4A and Table 4B. Density: the number of dwelling units within a standard measure of land area. Design Speed: is the velocity at which a Thoroughfare tends to be driven without the constraints of signage or enforcement. There are four ranges of speed: Very Low: (below 20 MPH); Low: (20 -25 MPH); Moderate: (25 -35 MPH); High: (above 35 MPH). Lane width is determined by desired Design Speed. See Table 3A. Developable Areas: lands other than those in the 0 -1 Preserved Open Sector. Disposition: the placement of a building on its Lot. See Table 9 and Table 77 Dooryard: a Private Frontage type with a shallow Setback and front garden or patio, usually with a low wall at the Frontage Line. See Table 7 (Variant: Lightwell, light court.) Drive: a Thoroughfare along the boundary between an Urbanized and a natural condition, usually along a waterfront, Park, or promontory. One side has the urban character of a Thoroughfare, with Sidewalk and building, while the other has the qualities of a Road or parkway, with naturalistic planting and rural details. Driveway: a vehicular lane within a Lot, often leading to a garage. See Section 5.70 and Table 3B -f. Edgeyard Building: a building that occupies the center of its Lot with Setbacks on all sides. See Table 9. Effective Parking: the amount of parking required for Mixed Use after adjustment by the Shared Parking Factor. See Table 77. Effective Turning Radius: the measurement of the inside Turning Radius taking parked cars into account. See Table 77 Elevation: an exterior wall of a building. See Table 77 See: Facade. Encroach: to break the plane of a vertical or horizontal regulatory limit with a structural element, so that it extends into a Setback, into the Public Frontage, or www.tpudc.com SC74 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 7. DEFINITIONS OF TERMS Carmel, Indiana above a height limit. Encroachment: any structural element that breaks the plane of a vertical or hori- zontal regulatory limit, extending into a Setback, into the Public Frontage, or above a height limit. Enfront: to place an element along a Frontage, as in "porches Enfront the street." Estate House: an Edgeyard building type. Asingle- family dwelling on a very large Lot of rural character, often shared by one or more Accessory Buildings. (Syn: country house, villa) Expression Line: a line prescribed at a certain level of a building for the major part of the width of a Facade, expressed by a variation in material or by a limited projection such as a molding or balcony. See Table 8. (Syn: transition line.) Extension Line: a line prescribed at a certain level of a building for the major part of the width of a Facade, regulating the maximum height for an Encroachment by an Arcade Frontage. See Table 8. Facade: the exterior wall of a building that is set along a Frontage Line. See Elevation. Forecourt: a Private Frontage wherein a portion of the Facade is close to the Frontage Line and the central portion is set back. See Table 7 Frontage: the area between a building Facade and the vehicular lanes, inclusive of its built and planted components. Frontage is divided into Private Frontage and Public Frontage. See Table 4A and Table 7 Frontage Buildout: the percentage of (a) the total number of linear feet measured across the Frontage Line of a Lot or parcel along which there are any of the follow- ing elements of Buildings: a wall, a porch, a balcony or a stoop; as it relates to (b) the total number of linear feet of the Private Frontage of the Lot or parcel. Frontage Line: a Lot line bordering a Public Frontage. Facades facing Frontage Lines define the public realm and are therefore more regulated than the Elevations facing other Lot Lines. See Table 77 Function: the use or uses accommodated by a building and its Lot, categorized as Restricted, Limited, or Open, according to the intensity of the use. See Table 70 and Table 72. Gallery: a Private Frontage conventional for Retail use wherein the Facade is aligned close to the Frontage Line with an attached cantilevered shed or lightweight colonnade overlapping the Sidewalk. See Table 7 GIS (Geographic Information System): a computerized program in widespread municipal use that organizes data on maps.The protocol for preparing a Sector Plan should be based on GIS information. See Section 2.7. Green: a Civic Space type for unstructured recreation, spatially defined by landscap- ing rather than building Frontages. See Table 73. Greenfield: an area that consists of open or wooded land or farmland that has not been previously developed. Greenway: an Open Space Corridor in largely natural conditions which may include trails for bicycles and pedestrians. Greyfield: an area previously used primarily as a parking lot. Shopping centers and shopping malls are typical Greyfield sites. (Variant: Grayfield.) Growth Sector: one of four Sectors where development is permitted By Right in www. t udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC75 ARTICLE 7. DEFINITIONS OF TERMS CITY OF CARMEL SMARTCODE Carmel, Indiana the SmartCode, three for New Communities and one for Infill. See Article 2. Hamlet: See CLD. (Syn: cluster, settlement.) Highway: a rural and suburban Thoroughfare of high vehicular speed and capacity. This type is allocated to the more rural Transect Zones (T -1, T -2, and T -3). Home Occupation: non Retail Commercial enterprises. The work quarters should be invisible from the Frontage, located either within the house or in an Outbuilding. Permitted activities are defined by the Restricted Office category. See Table 70. House: an Edgeyard building type, typically built initially for a single family Residential Function, with successional use to Commercial, Retail or Office Function, on a large Lot, often shared with an Accessory Building in the back yard. (Syn: single.) Incubator Retail: a Function that is established for the inexpensive operation of start -up and boutique businesses. This can be in the form of temporary free standing structures, contained within larger permanent structures or pedestrian Passages. Infill: noun -new development on land that had been previously developed, includ- ing most Greyfield and Brownfield sites and cleared land within Urbanized areas. verb- to develop such areas. Infill RCD: a Community Type within an Urbanized, Greyfield, or Brownfield area based on a Long or Linear Pedestrian Shed and consisting of T -Zones T3, T3E, T3L, T-4, T -5, and /or T -6. Infill RCDs are prescribed in the G -4 Infill Growth Sector and are regulated by Article 4. See Section 4.2.3. (Var: downtown.) Infill TND: a Community Type within an Urbanized, Greyfield, or Brownfield area based on a Standard Pedestrian Shed and consisting of T -Zones T -3, T3L, T3E, T-4, T -5 and /or T6. Infill TNDs are prescribed in the G -4 Infill Growth Sector and are regulated by Article 4. See Section 4.2.2. (Var: neighborhood.) Initial Community Regulating Plan: a Community Regulating Plan for the Down- town SmartCodeArea recommended by the Planning Commission to, and approved by, the City Council pursuant to Sections 3.1.2 and 4.1.2 hereof. Initial Sector Plan: the Sector Plan for the Downtown SmartCode Area recom- mended by the Planning Commission to, and approved by, the City Council pursuant to Section 2.1.1(d)hereof. Inn: a Lodging type offering 6 to 12 bedrooms, permitted to serve breakfast in the mornings to guests. See Table 70. Layer: a range of depth of a Lot within which certain elements are permitted. See Table 77. Lightwell: A Private Frontage type that is a below -grade entrance or recess designed to allow light into basements. See Table 7 (Syn: light court.) Linear Pedestrian Shed: A Pedestrian Shed that is elongated along an important Mixed Use Corridor such as a main street. A Linear Pedestrian Shed extends approximately 1/4 mile from each side of the Corridorfor the length of its Mixed Use portion. The resulting area is shaped like a lozenge. It may be used to structure a TND, RCD, Infill TND, or Infill RCD. (Syn: elongated pedestrian shed.) Liner Building: a building specifically designed to mask a parking lot or a Parking Structure from a Frontage. Live -Work: a Mixed Use unit consisting of a Commercial and Residential Function. The Commercial Function may be anywhere in the unit. It is intended to be occupied by a business operatorwho lives in the same structure that contains the Commercial www.tpudc.com SC76 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 7. DEFINITIONS OF TERMS Carmel, Indiana activity or industry. See Work -Live. (Syn.: flexhouse.) Lodging: premises available for daily and weekly renting of bedrooms. See Table 70 and Table 72. Long Pedestrian Shed: a Pedestrian Shed that is an average 1/2 mile radius or 2640 feet, used when a transit stop (bus or rail) is present or proposed as the Common Destination. A Long Pedestrian Shed represents approximately a ten minute walk at a leisurely pace. It is applied to structure an RCD Community Type. See Pedestrian Shed. Lot: a parcel of land accommodating a building or buildings of unified design. The size of a Lot is controlled by its width in order to determine the grain (i.e., fine grain or coarse grain) of the urban fabric. Lot Line: the boundary that legally and geometrically demarcates a Lot. Lot Width: the length of the Principal Frontage Line of a Lot. Main Civic Space: the primary outdoor gathering place for a community.The Main Civic Space is often, but not always, associated with an important Civic Building. Manufacturing: premises available for the creation, assemblage and /or repair of artifacts, using table- mounted electrical machinery or artisanal equipment, and including their Retail sale. Meeting Hall: a building available for gatherings, including conferences, that accom- modates at least one room equivalent to a minimum of 10 square feet per projected dwelling unit within the Pedestrian Shed in which it is located. Mixed Use: multiple Functions within the same building through superimposition or adjacency, or in multiple buildings by adjacency, or at a proximity determined by Warrant. Municipality: the City of Carmel, Indiana. Net Site Area: all developable land within a site including Thoroughfares but exclud- ing land allocated as Civic Zones. Network Pedestrian Shed: a Pedestrian Shed adjusted for average walk times along Thoroughfares. This type may be used to structure Infill Community Regulat- ing Plans. See Table 77 Office: premises available for the transaction of general business but excluding Retail, artisanal and Manufacturing uses. See Table 70. Open Space: land intended to remain undeveloped; it may be for Civic Space. Outbuilding: an Accessory Building, usually located toward the rear of the same Lot as a Principal Building, and sometimes connected to the Principal Building by a Backbuilding. See Table 77 Park: a Civic Space type that is a natural preserve available for unstructured rec- reation. See Table 73. Parking Court: a mid -block parking lot surrounded by buildings or Streetscreens. Parking Courts should be designed to also serve as internal plazas or public gather- ing places. Parking Structure: a garage or other building containing one or more Stories of parking above grade. Passage (PS): a pedestrian connector, open or roofed, that passes between build- ings to provide shortcuts through long Blocks and connect rear parking areas to www. tp udc. com ?009 Town Planning c& Urban Design Collaborative LLC SC77 ARTICLE 7. DEFINITIONS OF TERMS CITY OF CARMEL SMARTCODE Carmel, Indiana Frontages. Path (PT): a pedestrian way traversing a Park or rural area, with landscape match- ing the contiguous Open Space, ideally connecting directly with the urban Sidewalk network. Pedestrian Shed: An area that is centered on a Common Destination. Its size is related to average walking distances for the applicable Community Type. Pedes- trian Sheds are applied to structure Communities. See Standard, Long, Linear or Network Pedestrian Shed. (Syn: walkshed, walkable catchment.) Plan Commission: the City of Carmel, Indiana Plan Commission. Plan Review Committee (PRC): See Section 7.4.3. Planter: the element of the Public Frontage which accommodates street trees, whether continuous or individual. Plaza: a Civic Space type designed for Civic purposes and Commercial activities in the more urban Transect Zones, generally paved and spatially defined by building Frontages. Principal Building: the main building on a Lot, usually located toward the Frontage. See Table 77 Principal Entrance: the main point of access for pedestrians into a building. Principal Frontage: the primary Private Frontage of a building which includes its Principal Entrance; or with respect to corner Lots, the Private Frontage designated to bear the address and Principal Entrance to the building. Prescriptions for the First Lot Layer pertain to both Frontages of a corner Lot. See Frontage. Private Frontage: the privately held Layer between the Frontage Line and the Principal Building Facade. See Table land Table 77 Public Frontage: the area between the Curb of the vehicular lanes and the Front- age Line. See Table 4A and Table 4B. RCD: see Regional Center Development. Rear Alley (RA): a vehicular way located to the rear of Lots providing access to service areas, parking, and Outbuildings and containing utility easements. Rear Alleys should be paved from building face to building face, with drainage by inverted crown at the center or with roll Curbs at the edges. Rear Lane (RL): a vehicular way located to the rear of Lots providing access to service areas, parking, and Outbuildings and containing utility easements. Rear Lanes may be paved lightly to Driveway standards. The streetscape consists of gravel or landscaped edges, has no raised Curb, and is drained by percolation. Rearyard Building: a building that occupies the full Frontage Line, leaving the rear of the Lot as the sole yard. See Table 9. (Var: Rowhouse, Townhouse, Apartment House) Recess Line: a line prescribed for the full width of a Facade, above which there is a Stepback of a minimum distance, such that the height to this line (not the overall building height) effectively defines the enclosure of the Enfronting public space. Var: Extension Line. See Table 8. Regional Center: Regional Center Development or RCD. Regional Center Development (RCD): a Community Type structured by a Long Pedestrian Shed or Linear Pedestrian Shed, which may be adjoined without buffers p www.tpudc.com SC78 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 7. DEFINITIONS OF TERMS Carmel, Indiana by one or several Standard Pedestrian Sheds, each with the individual Transect Zone requirements of a TND. RCD takes the form of a high- Density Mixed Use center connected to other centers by transit. See Infill RCD, Table land Table 74a. (Var: town center, downtown. Syn: Regional Center) Residential: characterizing premises available for long -term human dwelling. Retail: characterizing premises available for the sale of merchandise and food service. See Table 70 and Table 72. Retail Frontage: Frontage designated on a Regulating Plan that requires or recom- mends the provision of a Shopfront, encouraging the ground level to be available for Retail use. See Special Requirements. Road (RD): a local, rural and suburban Thoroughfare of low -to- moderate vehicular speed and capacity. This type is allocated to the more rural Transect Zones (T1 -T3). See Table 3A. Rowhouse: a single family dwelling that shares a party wall with another of the same type and occupies the full Frontage Line. See Rearyard Building. (Syn: Townhouse) Sector: a neutral term for a geographic area. In the SmartCode there are six specific Sectors for Sector Planning that establish the legal boundaries for Open Space and development. Secondary Frontage: on corner Lots, the Private Frontage that is not the Principal Frontage. As it affects the public realm, its First Layer is regulated. See Table 17. Setback: the area of a Lot measured from the Lot line to a building Facade or Elevation that is maintained clear of permanent structures, with the exception of Encroachments listed in Section 5.7. See Table 74g. (Var: build -to- line.) Shared Parking Factor: an accounting for parking spaces that are available to more than one Function. See Table 77. Sharrows: a symbol on a vehicular lane indicating that its use is to be shared by motor vehicles and bicycles. Shopfront: a Private Frontage conventional for Retail use, with substantial glazing and an awning, wherein the Facade is aligned close to the Frontage Line with the building entrance at Sidewalk grade. See Table 7 Sidewalk: the paved section of the Public Frontage dedicated exclusively to pedes- trian activity. Sideyard Building: a building that occupies one side of the Lot with a Setback on the other side. This type can be a Single or Twin depending on whether it abuts the neighboring house. See Table 9. Slip Road: an outer vehicular lane or lanes of a Thoroughfare, designed for slow speeds while inner lanes carry higher speed traffic, and separated from them by a planted median. (Syn: access lane, service lane) Specialized Building: a building that is not subject to Residential, Commercial, or Lodging classification. See Table 9. Special District (SD): an area that, by its intrinsic Function, Disposition, or Configu- ration, cannot or should not conform to one or more of the normative Community Types or Transect Zones specified by the SmartCode. Special Districts may be mapped and regulated at the regional scale or the community scale. www. tp udc. corn ?009 Town Planning c& Urban Design Collaborative LLC SC79 ARTICLE 7. DEFINITIONS OF TERMS CITY OF CARMEL SMARTCODE Carmel, Indiana Special Flood Hazard Area: a designation by the Federal Emergency Management Agency (FEMA) that may include the V (Velocity) Zones and Coastal A Zones where building construction is forbidden, restricted, or contingent upon raising to the Base Flood Elevation. Special Requirements: provisions of Section 3.9, Section 4.7, and Section 5.3 of this Code and /or the associated designations on a Regulating Plan or other map for those provisions. Special Plan Area: an area already subject to an Infill Community Regulating Plan with respect to which a subsequent Infill Community Regulating Plan is approved in accordance with Section 4. Square: a Civic Space type designed for unstructured recreation and Civic purposes, spatially defined by building Frontages and consisting of Paths, lawns and trees, formally disposed. See Table 73. Standard Pedestrian Shed: a Pedestrian Shed that is an average 1/4 mile radius or 1320 feet, about the distance of a five minute walk at a leisurely pace. See Pedestrian Shed. State Code: the State of Indiana Code. Stepback: a building Setback of a specified distance that occurs at a prescribed number of Stories above the ground. See Table 8. Stoop: a Private Frontage wherein the Facade is aligned close to the Frontage Line with the first Story elevated from the Sidewalk for privacy, with an exterior stair and landing at the entrance. See Table 7 Story: a habitable level within a building, excluding an Attic or raised basement. See Table 8. Street (ST): a local urban Thoroughfare of low speed and capacity. See Table 3B and Table 4B. Streetscreen: a freestanding wall built along the Frontage Line, or coplanar with the Facade. It may mask a parking lot from the Thoroughfare, provide privacy to a side yard, and /or strengthen the spatial definition of the public realm. (Syn: streetwall.) See Section 5.7.5f. Substantial Modification: alteration to a building that is valued at more than 50% of the replacement cost of the entire building, if new. Swale: a low or slightly depressed natural area for drainage. T -Zone: Transect Zone. Terminated Vista: a location at the axial conclusion of a Thoroughfare. A build- ing located at a Terminated Vista designated on a Regulating Plan is required or recommended to be designed in response to the axis. Third Place: Thoroughfare: a way for use by vehicular and pedestrian traffic and to provide access to Lots and Open Spaces, consisting of Vehicular Lanes and the Public Frontage. See Table 3A, Table 3B and Table 77a. TND: Traditional Neighborhood Development, a Community Type structured by a Standard Pedestrian Shed oriented toward a Common Destination consisting of a Mixed Use center or Corridor, and in the form of a medium -sized settlement near a transportation route. See Table 2 and Table 74a. (Syn: village. Variant: Infill TND, neighborhood.) p www.tpudc.com SC80 2009 Town Planning Urban Design Collaborative LLC CITY OF CARMEL SMARTCODE ARTICLE 7. DEFINITIONS OF TERMS Carmel, Indiana TOD: Transit Oriented Development. TOD is created by an overlay on all or part of a TND or RCD, or by designation on a Sector Plan, permitting increased Density to support rail or Bus Rapid Transit (BRT) as set forth in Section 5.9.2d. Townhouse: See Rearyard Building. (Syn: Rowhouse) Traditional Neighborhood Development: TND Transect: a cross section of the environment showing a range of different habitats. The rural -urban Transect of the human environment used in the SmartCode tem- plate is divided into six Transect Zones. These zones describe the physical form and character of a place, according to the Density and intensity of its land use and Urbanism. Transect Zone (T- zone): One of several areas on a Zoning Map regulated by the SmartCode. Transect Zones are administratively similar to the land use zones in conventional codes, except that in addition to the usual building use, Density, height, and Setback requirements, other elements of the intended habitat are integrated, including those of the private Lot and building and Public Frontage. See Table 7. Turning Radius: the curved edge of a Thoroughfare at an intersection, measured at the inside edge of the vehicular tracking. The smaller the Turning Radius, the smaller the pedestrian crossing distance and the more slowly the vehicle is forced to make the turn. See Table 3B and Table 77. Urbanism: collective term for the condition of a compact, Mixed Use settlement, including the physical form of its development and its environmental, functional, economic, and sociocultural aspects. Urbanized: generally, developed. Specific to the SmartCode, developed at T -3 (Sub- Urban) Density or higher. Variance: a ruling that would permit a practice that is not consistent with either a specific provision or the Intent of this Code (Section 7.3). An application for a Variance is submitted to the Board of Zoning Adjustment and granted or denied after public hearing before the Board of Zoning Adjustment in accordance with the Existing City Codes. See Section 7.5. Villa: an Edgeyard building type, typically built initially for a single family Residential Function with succession to Multi Family Residential, Commercial, Office or Retail Function. On a very large lot of rural character and often shared by one or more ancillary buildings. Syn.: Estate House, Mansion Warrant: a ruling that would permit a practice that is not consistent with a specific provision of this Code, but that is justified by its Intent (Section 7.3). Warrants are usually granted administratively by the CRC. See Section 7.5. Work -Live: a Mixed Use unit consisting of a Commercial and Residential Func- tion. It typically has a substantial Commercial component that may accommodate employees and walk -in trade. The unit is intended to function predominantly as work space with incidental Residential accommodations that meet basic habitability requirements. See Live -Work. (Syn: Live With.) Yield: characterizing a Thoroughfare that has two -way traffic but only one effec- tive travel lane because of parked cars, necessitating slow movement and driver negotiation. Also, characterizing parking on such a Thoroughfare. Zoning Map: the official map or maps that are part of the zoning ordinance and delineate the boundaries of individual zones and districts. See Regulating Plan. www.tpudc.coni p ?009 Town Planning c& Urban Design Collaborative LLC SC81