CIRCULATION GUIDELINES AND STANDARDS

Orlando City Code ch. 68, pt. 4

in effect

Orlando City Code § 68.400 Purpose.

Sec. 68.400. - Purpose. This Part gives direction to the detailed planning of circulation networks within individual developments and shall ensure an interconnected system of arterial, collector and local streets; bicycle lanes; multi-use trails; transit; traffic calming; and parking standards. The intent of the Southeast Orlando Sector Plan's Transportation Design Standards are to assist in creating a sustainable community with a more balanced transportation system. These standards integrate the mobility of each mode of travel into Southeast Orlando's community design process. (Ord. of 5-10-1999, § 10, Doc. #32070)

Orlando City Code § 68.401 Street Sections.

Sec. 68.401. - Street Sections. Typical cross-sections have been developed for each type of street within Southeast Orlando. These cross-sections shall only be used where Traditional Design land use and building standards are utilized. Each cross section details lane width, medians, bicycle lanes, parking, sidewalks, landscape areas, drainage (rural roadways), and required right-of-way. Not all contingencies have been covered because the list would be far too large. However, cross sections may be modified to accommodate special circumstances. For example, it may not be desirable to have a sidewalk on the side of a roadway fronting a wetland; the appropriate cross section can be developed by deleting the sidewalk from the cross section designed for the particular type of roadway. Such modifications shall be reviewed by all pertinent City departments (Planning, Fire, Police, Solid Waste, Public Works) and must be approved by the City Planning Official and City Engineer. (a) Cross Section Types. Cross sections have been developed for arterials (urban and rural), mixed-use center streets (arterial and local), residential neighborhood streets, residential and connector streets, and airport support district streets. Arterials are defined as major high-volume roadways such as Narcoossee Road and Alafaya Trail. Town and Village Center streets should be composed of arterial and local streets. Neighborhood Center streets should be local in nature. Residential Neighborhoods should be comprised of connector and local streets. Residential and commercial connector streets shall provide vehicular connections between residential neighborhoods and commercial centers. Airport Support Districts streets are typically local in nature, but with a lane width and intersection radius sufficient to handle large trucks. (b) Specific Requirements for Residential Neighborhoods. Residential neighborhood local streets reflect the options available for three levels of on-street parking. Whether there is no on-street parking, limited on-street parking or unlimited on-street parking shall be determined by presence or absence of one- or two-car garages and the resulting driveway width. The specific roadway cross-section shall be determined at the time of site plan review based on the proposed unit types fronting the roadway. The core cross sections referenced above are summarized in the following table. In addition, the City has developed illustratives of these road cross-sections, which can be found in the Southeast Orlando Sector Plan-Development Guidelines and Standards illustrated guidebook. This guidebook is available for review/purchase in the City Planning Department. Figure 68-L Typical Roadway Cross Sections Roadway Type | Cross Section | Parking | Bicycle Lanes | Sidewalks | ROW (feet) | Lane Widths (feet) Major Urban Arterial Four-Lane Divided: Narcoossee Road | A | No | Yes | Yes | 138 | 11 Alafaya Trail | B | No | Yes | Yes | 104 | 11 Town Center: One-Way Arterial | C | Yes | Yes | Yes | 69 | 11 Two-Way Arterial | D | Yes | Yes | Yes | 67 | 10 Local | E | Yes | No | Yes | 57 | 10 Village Center: One-Way Arterial | C | Yes | Yes | Yes | 69 | 11 Two-Way Arterial | D | Yes | Yes | Yes | 67 | 10 Local | E | Yes | No | Yes | 57 | 10 Neighborhood and Residential Centers: Local | E | Yes | No | Yes | 57 | 10 Residential Neighborhood: Connector | F | No | Yes | Yes | 74 | 11 Connector | G | No | Yes | Yes | 64 | 11 Local | H | Limited | No | Yes | 53 | 12 Local | I | Yes | No | Yes | 58 | 8 Local* | J | 1 side only | No | Yes | 47 | 9 Estate Residential: Connector | F | Yes | Yes | Yes | 74 | 11 Connector | G | No | Yes | Yes | 64 | 11 Local | H | Limited | No | Yes | 53 | 12 Local | I | Yes | No | Yes | 58 | 8 Local* | J | 1 side only | No | Yes | 47 | 9 Airport Support District: Local | K | No | Yes | Yes | 66 | 12 Source: Glatting Jackson Kercher Anglin Lopez Rinehart, Inc. * Cross Section J to be used as deemed appropriate by the Development Review Committee, and only in conjunction with Estate Residential and/or where alleys are utilized. (Ord. of 5-10-1999, § 10, Doc. #32070; Ord. of 8-6-2001, § 1, Doc. #33983; Ord. No. 2022-56, § 6, 9-26-2022, Doc. #2209261204)

Orlando City Code § 68.402 Bicycle Accommodation.

Sec. 68.402. - Bicycle Accommodation. Bicycle lanes are a portion of the roadway which has been designed for the preferential or exclusive use of the bicycle. Sidewalks are not encouraged as substitutes for bicycle lanes. As stated in GMP Future Land Use Policy LU.4.2.6, bicycle lanes should be designed for all connector and arterial streets as indicated in the previous section. Bicycle lanes are typically 4 feet in width, and 5 feet in width when adjacent to on-street parking. Consult the "State of Florida Department of Transportation's Bicycle Facilities Planning and Design Manual" and the "City of Orlando Bicycle Plan" when designing bicycle lanes. The Southeast Orlando Sector Plan-Development Guidelines and Standards illustrated guidebook provides a conceptual Bicycle Master Plan for the Southeast Plan area. Developers shall utilize this document, as well as the above-mentioned documents, when designing roadways, bicycle/pedestrian lanes, trails, and paths. (Ord. of 5-10-1999, § 10, Doc. #32070; Ord. No. 2026-5, § 1(Exh. A), 4-6-2026, Doc. #26040612c)

Orlando City Code § 68.403 Transit Accommodation.

Sec. 68.403. - Transit Accommodation. Creating an environment conducive to the development of a balanced transportation system requires that the circulation system be engineered to functionally accommodate all modes. Designing for the functional requirements of LYNX (local transit provider) vehicles means creating sustainable facilities in which LYNX vehicles can operate properly and passengers can wait in comfort. The Southeast Orlando Sector Plan-Development Guidelines and Standards illustrated guidebook describes typical LYNX requirements in detail, and provides a conceptual Transit Master Plan for the Southeast Plan area. Developers shall utilize this document, as well as the City's Transportation Element when designing roadways to accommodate transit. In general, the City advocates utilizing smaller lane widths than recommended by LYNX in order to create a more urban environment. (Ord. of 5-10-1999, § 10, Doc. #32070)

Orlando City Code § 68.404 Connectivity Index.

Sec. 68.404. - Connectivity Index. In accordance with GMP Future Land Use Policy LU.4.2.5, and consistent with the GMP Transportation Element, the City shall combine the mobility of the traditional interconnected street pattern with the safety, security, and topographic sensitivity of the conventional or contemporary network. Such a hybrid network features short, curved stretches that follow the lay of the land or contribute to good urban design, as well as short loops and cul-de-sacs, so long as the higher-order street network is left intact. "Higher-order" means arterials, collectors, and sub-collectors that carry through traffic. An acceptable individual project master plan may feature interrupted grids of short street ending at T or Y intersections, traffic circles or squares/parks. By design, local streets may carry some through traffic, but the truncated nature of local streets means that traffic moves more slowly and the heaviest volumes are diverted to higher-order streets. A simple measure of connectivity is the number of street links divided by the number of nodes or link ends (including cul-de-sac heads). The more links relative to nodes, the more connectivity. A connectivity index of 1.4 to 1.8 represents an acceptable street network in the Southeast Plan area. The optimal connectivity index for a perfect grid network is 2.5. This is the procedure for calculating the connectivity index: (a) Count the number of nodes. Nodes are any point of intersection of two or more roads or any cul-de-sac ends. (b) Count the number of links. Links are the segments of road connecting nodes. To properly calculate the connectivity index, you must first include the first link beyond the last nodes. (c) Use the following formula to calculate the connectivity index: links/nodes = connectivity index. Simple changes in design, such as removing cul-de-sacs and connecting the street-ends to other streets, can bring about significant changes in connectivity index scoring. The City shall utilize the connectivity index mechanism, in addition to other qualitative measures, to determine whether transportation impact fees can be reduced within the Southeast Orlando Sector Plan area. (Ord. of 5-10-1999, § 10, Doc. #32070; Ord. No. 2026-5, § 1(Exh. A), 4-6-2026, Doc. #26040612c)

Orlando City Code § 68.405 Traffic Calming.

Sec. 68.405. - Traffic Calming. Traffic calming devices have potential use in both the design of new road segments in Southeast Orlando, as well as the modification of existing roads, or the future modification of roads initially built without traffic calming features. Five groups of traffic calming devices are appropriate for use in Southeast Orlando: (a) Street narrowing; (b) Vehicle deflection (traffic diversion); (c) Pavement sharing; (d) Rerouting; and, (e) Pavement surface treatments. The Southeast Orlando Sector Plan-Development Guidelines and Standards illustrated guidebook, available for review at the City Planning Department, graphically depicts these traffic calming techniques. (Ord. of 5-10-1999, § 10, Doc. #32070)

Orlando City Code § 68.406 Parking Standards and Design.

Sec. 68.406. - Parking Standards and Design. The following standards shall apply in Town, Village, Neighborhood and Residential Centers and may be used as design guidelines in other districts. (a) Joint Access. Cross access easements or similar mechanisms shall be used to provide joint access between the parking areas of adjacent properties. This shall preclude drivers from having to use the street network to access a neighboring parcel. (b) Shared Parking. Shared parking may be provided for multiple uses where it can be demonstrated that due to different use time frames the minimum amount of required parking will be available for each use. For example, land uses such as movie theatres and restaurants can share office parking space during the evening hours. (c) Off-Site Parking. Off-site parking, including on-street parking may be utilized to meet minimum parking requirements as long as reasonable pedestrian access is provided from the parking space to the use. (d) Parking Access. Parking areas shall be accessed from side and back streets and from adjacent properties. Access from the front street shall be avoided unless no other reasonable access is available. Block standards for Town, Village (except for Village Center anchor stores), and Residential Centers require a minimum of 65% street frontage therefore, forcing parking to the sides and rear of buildings. (e) Pedestrian Access. A direct pedestrian access shall be provided from the public sidewalk network to the primary building entrance without having to cross a vehicular travelway. (f) Landscaping/Screening. Parking areas shall be landscaped consistent with Chapter 60 of the Land Development Code. Connecting walkways should be landscaped with either shade trees or climbing vines on trellises. (g) On-Street Parking. On-street parking shall be utilized in mixed-use centers whenever and wherever possible. On-street parking areas shall be differentiated from road travel lanes through the use of texture paving or textured paving strips. (Ord. of 5-10-1999, § 10, Doc. #32070)

Source: City of Orlando, Florida, City Code and City Charter (Municode Library, library.municode.com)URL: https://library.municode.com/fl/orlando/codes/code_of_ordinances?nodeId=TITIICICO_CH68SOORSEPLDEGUST_PT4CIGUSTFetched: 11/1/2026