SSAR Stub Outs

59 slides
4.01 MB
572 views

Similar Presentations

Presentation Transcript

1

VDOT Land Use RegulationsFebruary and March 2012

2

*VDOT Land Use RegulationsOutline of Presentation Overview Traffic Impact Analysis Secondary Street Acceptance Requirements Access Management Land Use Permits Changes in Limited Access

3

*VDOT Land Use RegulationsGoals for Today’s Training What’s changed? Regulatory changes in 2011 Refresher Theory and basic application Consistency Outcomes Processes

4

*VDOT Land Use RegulationsVDOT’s Land Use Regulations http://www.virginiadot.org/projects/landuse.asp Traffic Impact Analysis (Chapter 527) Provide traffic information on land use proposals Secondary Street Acceptance Requirements Requirements for streets to be accepted by VDOT Access Management Regulate entrances/connections to state highways Land Use Permits Regulate activities allowed to occur on highway R/W

5

*How VDOT Land Use Regulations Relate to Each Other

6

Highway Functional ClassificationHighway MaintenanceConstruction ProgramShort & Long Range Transportation PlanningCounty Comprehensive Plan*How VDOT Land Use Regulations Relate to Other Processes

7

*VDOT Land Use Involvement Authorized by Titles 15.2 and 33.1 of the Code of Virginia Comprehensive plans and amendments Provide assistance with transportation plan (at request of locality - § 15.2-2223) Review proposal (at request of locality or if Ch. 527 triggered - § 15.2-2222.1) Review “official map” (required - § 15.2-2237 for counties that have “official map”) Zoning Review proposals (at request of locality or if Ch. 527 triggered - § 15.2-2222.1) Site plans Review proposals (at request of locality - § 15.2-2258 and § 15.2-2286) Subdivisions Review of preliminary plats (at request of locality - § 15.2-2260) Review and approval (required for streets intended for state maintenance - § 33.1-70.3 or others at request of locality - § 15.2-2259) Entrances Review and approval (required - §§ 33.1-197 through 33.1-198.1)

8

* VDOT Land Use Involvement – Plan Review Plan or plat review for two purposes As locality’s transportation consultant For VDOT regulatory activity Subdivision street development (SSR / SSAR streets) Site access (Access Management / LUPR) Nature of comments depends upon purpose of review Should (recommended) Shall (required) Plat signing Acknowledge review (not approval of plat)

9

*Traffic Impact Analysis Regulations (Chapter 527) http://www.virginiadot.org/projects/chapter527/default.asp Contact: Paul Grasewicz

10

*Traffic Impact Analysis Legislative History 2006 General Assembly: Chapter 527 creates new § 15.2-2222.1 in the Code which directs the VDOT Commissioner to develop and implement traffic impact analysis regulations for development proposals that will have a substantial affect on state highways, as of July 1, 2007 2007 General Assembly: Chapter 792 allows VDOT to phase implementation, with full implementation by January 1, 2009 2011 General Assembly: Chapter 647 removes site plans, subdivision plats, and plans of development from TIA regulations; Chapter 870 requires VDOT and CTB to review and revise based upon public input; Chapter 888 requires a lesser level of review for zoning actions that are consistent with comprehensive plan change that was previously reviewed by VDOT.

11

*Traffic Impact AnalysisLand development proposals to be submitted “Substantially affect transportation on state controlled highways” based on traffic volume 5,000 trips per day (standard threshold) 400 trips per day and exceeds existing traffic on road (for residential development only, low volume road threshold) Dependent upon Submission type Comprehensive Plan or Plan Amendment (no TIA required) Rezoning or Special Use Permit Location Within 3,000 ft of connection to VDOT highway (for non-VDOT localities) Exception: Rezoning that does not increase allowable trips (daily and peak hour) over those allowed under existing zoning

12

*Traffic Impact AnalysisTIA submission thresholds for localities in which VDOT maintains local streets

13

*Traffic Impact Analysis

14

*Traffic Impact AnalysisComp plan submission not required to include TIA; rezoning is required to include a TIA Published local study standards can be used, if certified by District Locality must request VDOT review of standards Written and posted requirements Must provide information on current and future conditions Meet reasonable professional standards and practice Required elements Scope of study dependent upon amount of traffic generated but generally includes Existing and proposed land use Existing traffic and Level of Service (LOS) Expected future traffic and LOS (without proposed development) Expected future traffic and LOS (with proposed development) Recommendations for traffic impact mitigation measures

15

*Traffic Impact AnalysisRequired elements (cont’d) Default assumptions and methodology Are conservative, but may be modified based upon results of scoping meeting Data collection (avoid holidays, inclement weather) Trip generation (rates vs. equations based upon ITE methodology) Internal capture rates (residential with others, hotel with office, office with retail) Pass-by trip rates (per ITE Trip Generation Handbook) Allow alternate trip generation for “Small Area Plans” (EPA-MXD methodology) Level of service calculation (HCM methodology for vehicles, Transit Capacity and Quality of Service Manual for transit) Modal split (bike/ped facilities, proximity to transit service)

16

*Traffic Impact Analysis - TimeframesComprehensive Plans and Plan Amendments Request for meeting to be made within 30 days of receipt of package Official response to locality within 90 days of receipt of package Rezonings Request for meeting to be made within 45 days of receipt of package Official response to locality within 45 receipt of package (no meeting) Official response to locality within 120 days receipt of package (meeting requested) Other Events Locality to submit package within 10 business days of locality’s receipt VDOT reply to scoping meeting request within 30 days, hold meeting within 60 days

17

*Traffic Impact Analysis Other RequirementsRezoning submissions made that are consistent with previous comprehensive plan submission: If technical analysis of traffic included in comp plan submission, rezoning submission may be of lowest scope (less than 500 VPH) If for small area plan element, and small area plan included TIA, small area plan TIA serves as TIA for rezoning Before rejecting incomplete study or requiring resubmission: Hold meeting and allow 30 days to make changes If study still deficient (not in accordance with best professional practice, fails to document impacts, or incomplete), may require resubmission All submissions must be made with a paper copy and an electronic copy (via CD, DVD, or file transfer) VDOT must post submission and official response on website (via LandTrack)

18

*Secondary Street Acceptance Requirements http://www.virginiadot.org/projects/ssar/ Contact: Lynne Wasz

19

*SSAR – The ProblemCurrent development patterns often rely on isolated street networks. Increased congestion Wider streets Discourages other modes of transportation Impacts on neighborhoods Unsustainable burden on major roadways

20

*SSAR - BackgroundSecondary Street Acceptance Requirements (SSAR) govern the acceptance of streets into the secondary system of state highways (does not cover VDOT-funded construction) In the past, streets have been accepted into the state system without consideration to the overall public benefit they provided §33.1-70.3 of the Code of Virginia, enacted in 2007, directed the Commonwealth Transportation Board to develop requirements that: Improve connectivity of road and pedestrian networks Minimize stormwater runoff and impervious surfaces (reduce local street widths) Update performance bonding and cost recovery fees Chapter 870, 2011 Acts of Assembly, directed the CTB to solicit public comments and revise regulation accordingly

21

*SSAR – Grandfathering & Applicable Former Requirements2011 SSAR supersedes the 2005 SSR and the 2009 SSAR Developments submitted prior to July 2009: 2005 SSR Developments submitted between July 2009 and January 31, 2012: 2009 SSAR Plans submitted after January 2012: 2011 SSAR Grandfathered developments may choose to be designed using the 2011 SSAR requirements Subdivision Street Design Guide: Appendix B – SSR Appendix B(1) – 2009 and 2011 SSAR

22

*SSAR - 2009 to 2011 ChangesEliminated “connectivity index” requirement Eliminated of “area types” Reduced median lot size for required pedestrian accommodations and combined with average daily traffic Required additional external connection when dwelling unit or vehicle per day thresholds are met per network addition

23

*SSAR Adding Streets as a Network In the past, streets have been considered for acceptance individually Phases of developments or an entire development will be accepted as a group or a network addition. Allows for more flexible connectivity requirements Focus on overall network and public benefit

24

*SSAR - Connectivity Basic connectivity requirements Network addition must be connected to a publically maintained street Connect to existing state-maintained stub outs Two connections in multiple directions Additional required connections based upon units or trips Second (and additional) connections can be stub outs Determined by network addition

25

*SSAR Stub Outs – Required Connection Connections to adjacent state-maintained stub outs are required District Administrator can waive requirement if connection to stub out is “unsafe” Network addition may not be accepted for maintenance at the discretion of the District Administrator: SSAR Section 100

26

*SSAR Multiple Connections Requirements Two connections in multiple directions At least one connection to existing publicly maintained street Other connections can be stub outs to adjacent property or the next network addition for the development Stub outs MUST have expectation that they can be extended/connected

Browse More Presentations

Last Updated: 8th March 2018

Recommended PPTs