My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
19-3118 Approving and Adopting City of Casselberry Healthy Community Complete Streets Policy and Design Guidelines
Laserfiche
>
City Clerk's Public Records
>
Resolutions
>
Resolutions Archives
>
2019 Resolutions
>
19-3118 Approving and Adopting City of Casselberry Healthy Community Complete Streets Policy and Design Guidelines
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/28/2019 3:56:41 PM
Creation date
8/28/2019 3:56:34 PM
Metadata
Fields
Template:
City Clerk
City Clerk - Doc Type
Resolutions
City Clerk - Date
8/26/2019
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
17
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Context Sensitivity <br />The City of Casselberry recognizes that complete streets solutions vary according to <br />each street's land use context (both existing and planned). Appropriate design <br />standards and input from community members should be considered within each <br />context that provide for a flexible, innovative, and balanced approach resulting in safety <br />for all users and supportive of the Goal of this Policy. <br />Key Local Standards and Design Guidance <br />Additional design standards and policy updates are recommended as a future task (see <br />Chapter 10; also note that this Policy was updated in 2019), but below is specific <br />guidance on certain key issues. This should not be construed as exhaustive guidance, <br />as the above design standards and guidance references should be employed. Rather, <br />these specific points serve as a quick reference tool for planners, engineers, and <br />developers in designing certain transportation components within the City of <br />Casselberry. In addition, certain guidance below purposefully sets more restrictive local <br />standards. It is important to note that feasibility and appropriateness in context should <br />be considered when applying these design standards and guidelines; not all will apply to <br />every project. In addition, human behavior should be considered as a factor in all <br />design. <br />1. "Design Speed = Posted Speed" Approach. Nearly all City -owned <br />streets have a posted speed limit of 25 mph (and none more than 30 <br />mph). In most City contexts, new public and private projects should be <br />designed for a target speed no higher than a 25 mph speed limit. All public <br />and private streets shall be designed with appropriate features such that <br />the "design speed" approaches the "posted speed", which should equal <br />the target speed (also known as the desired operating speed). This <br />represents an overarching approach to street design to encourage a more <br />walkable City. <br />a. Note the FDOT Design Manual (FDM) Table 202.3.1 provides a <br />listing of potential speed management strategies. Example speed <br />management techniques that may be employed (depending on <br />context) include but are not limited to roundabouts, lane narrowing, <br />horizontal deflection (e.g., chicanes), vertical deflection (e.g., raised <br />intersections, raised crosswalks, or speed tables), speed feedback <br />signs, Rectangular Rapid Flashing Beacons (RRFB's), Pedestrian <br />Hybrid Beacons (PHB's), on -street parking, street trees, terminated <br />vistas, short blocks, and curb extensions (bulb -outs). <br />b. Multiple speed management strategies will often need to be <br />employed to effectively achieve desired operating speed. <br />C. Context should be considered in all speed management <br />considerations, but particularly use of vertical deflection should <br />carefully consider context, emergency services, drainage issues, <br />and human behavior. Use of raised crosswalks at key logical <br />7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.