Skip to main content
Loading…
This section is included in your selections.

(1) Scoping Letter. The level of detail and scope of a Transportation Impact Analysis (TIA) will vary with the size, complexity, and location of the proposed application. Prior to any TIA, the applicant shall submit sufficient information to the City for the Public Works Department to issue a scoping letter. The scoping letter expires 180 days after the date the letter was issued. If stipulations to reduce transportation impacts are requested by an applicant, it must first be shown by means of an analysis that an unconditional approval is not possible without some form of mitigation to maintain an adequate LOS and level of safety. This will determine whether a stipulation is necessary.

(2) Extent of Study Area:

The study area shall be defined by the Public Works Department in the scoping letter and shall address at least the following areas:

(a) All proposed development site access points;

(b) Any intersection of a collector or arterial roadway with another collector or arterial roadway where the proposed development can be expected to contribute 25 or more trips during the analysis peak hour. Impacts of less than 25 peak hour trips are not substantial and will not be included in the study area. This volume may be adjusted, at the discretion of the Public Works Department, for safety or unusual situations; and

(c) Any intersections directly adjacent to the subject property.

The Public Works Department may, at its discretion, waive the study of certain intersections when it is concluded that the impacts are not substantial.

(3) When required:

A TIA shall be required if a proposed application has the potential of generating more than 250 net average daily trips (ADT) or the Public Works Department has concerns due to operations or accident history. A TIA will be required to evaluate development impacts to the transportation system. The Public Works Department may waive a TIA if it is concluded that the impacts are not substantial.

(4) Submittals:

Applicants shall provide two copies of the TIA for Public Works Department to review.

(5) Elements of Analysis:

A TIA shall be prepared by a Traffic Engineer or Civil Engineer licensed to practice in the State of Oregon with specific training and experience in traffic engineering. The TIA shall be a thorough review of the effects a proposed use and/or development will have on the transportation system. The study area shall include all streets and intersections in the analysis, as defined in subsection 10.461(2) above. Transportation impacts generated from a proposed site will be distributed throughout the transportation system using existing count data or the current transportation model used by the City; any alternate distribution method must be based on data acceptable to the Public Works Department. Incomplete reports shall be returned to the applicant for completion without review. The following checklist outlines what a TIA shall contain:

(a) The scoping letter as provided by the Public Works Department;

(b) The Final TIA shall be signed and stamped by a Professional Civil or Traffic Engineer registered in the State of Oregon;

(c) An executive summary, discussing the development and/or use, the major findings of the analysis, and the mitigation measures proposed;

(d) A vicinity map of the proposed site and study area;

(e) Project characteristics such as current zoning, proposed zoning, potential trip generations (unless stipulated to less than potential), proposed access(s), and other pertinent factors;

(f) Street characteristics within the study area including roadway functional classification (as established in the most recent Transportation System Plan (TSP)), number of travel lanes, lane width, shoulder treatment, bicycle path corridors, and traffic control at intersections;

(g) Description of existing transportation conditions including transit accessibility, pedestrian facilities, bicycle facilities, traffic signals, and overall traffic operations and circulation;

(h) Peak hour turning movement counts of at least two-hour minimums at study area intersections, less than two years old. These counts shall be adjusted to the study year(s) of the project as defined in the scoping letter and consider seasonal traffic adjustments when required by the scoping letter;

(i) Figures showing existing peak hour (AM, noon, or PM, whichever is largest) turning movement volumes at study area intersections. An appropriate adjustment factor shall be applied to existing count data if counts were taken during the off-peak season;

(j) Figures showing existing peak hour turning movement volumes at study area intersections for the project study year(s).

(k) Potential Project trip generation using either the potential trip generation rates kept on file by the Public Works Department for City zoning districts or the most current edition of the ITE Trip Generation Manual, as identified by the Public Works Department in the scoping letter. Variations of trip rates will require the approval of the Public Works Department; such approval will require submission of adequate supporting data prior to first submittal of the TIA;

(l) Figures illustrating project turning movement volumes at study area intersections for peak hours. Adjustments made for pass-by traffic volumes shall follow the methodology outlined in the latest edition of the ITE Trip Generation Manual;

(m) Figures illustrating the combined traffic of existing, background, and project turning movement volumes at study area intersections for peak hours;

(n) Level of Service (LOS) analysis at study area intersections under the following conditions:

(i) Background conditions

Background traffic (Existing traffic counts + traffic count growth rates) and project traffic in the project study year(s)

(ii) Proposed conditions

Background traffic (Existing traffic counts + traffic count growth rates) and project traffic in the project study year(s)

A table shall be prepared which illustrates all LOS results. The table shall show LOS conditions with corresponding vehicle delays for signalized intersections and the critical movement at unsignalized intersections.

(o) Tier 1 projects as identified in the Transportation System Plan, except for those listed below in 10.461(5)(o)(i), shall be considered reasonably likely to be provided by the end of the planning period. Tier 2 projects, as identified in the Transportation System Plan, shall not be considered to be reasonably likely to be provided by the end of the planning period.

(i) The following Tier 1 projects shall not be considered reasonably likely to be provided by the end of the planning period:

(A) Project #537b South Stage Road (South Pacific Highway to North Phoenix Road)

(B) Project #609 Foothill Road (McAndrews to Delta Waters Road)

(C) Project #610 Foothill Road (Delta Waters Road to North UGB)

(D) Project #611 N Phoenix Road (Barnett Road to Juanipero Way)

(E) Project #721 N Phoenix Road (Juanipero Way to South UGB)

(ii) Projects listed in 10.461(5)(o)(i) shall be considered reasonably likely to be funded when either they are:

(A) constructed;

(B) in progress of construction; or

(C) identified for funding within the City’s Capital Improvement Plan (CIP), System Development Charge (SDC) fiscally constrained project list, the federally approved local Regional Transportation Plan (RTP) Financially Constrained Project List, and/or programmed in the State’s current State Transportation Improvement Plan (STIP).

(p) A queuing and blocking report, based on a microsimulation software such as SimTraffic, which lists the 95th-percentile queues and any blocked facilities or exceeded storage lengths for the existing and proposed conditions described in subsection 10.461(5)(n) above;

(q) A left and right turn lane assessment where they do not currently exist for proposed conditions described in subsection 10.461(5)(n) above;

(r) Safety review of study area intersections based on the most recent available data from the Oregon Department of Transportation (ODOT) or the City of Medford;

(s) A mitigation plan if:

(i) Level of service (LOS) is determined to be below the mobility target identified in Section 10.462, per the analysis required of Section 10.461(5)(n);

(ii) The proposed development trips will affect an identified crash pattern or safety concern:

(iii) The turn lane assessment identifies a need; and/or

(iv) Impacts are identified that are otherwise considered a “significant effect” in accordance with Oregon Administrative Rule 660-012-060.

Mitigation measures may include stipulations and/or construction of necessary transportation improvements. Mitigation measures shall be required to the extent that the transportation facilities, under City jurisdiction, operate at an acceptable level of service (LOS)/mobility target with the addition of project traffic; and

(t) Intersections under jurisdiction of another agency, but still within the City limits, shall be evaluated by either the City’s criteria or the other jurisdiction’s criteria, or both, whichever is considered applicable by the Public Works Department. If any peak hour trips leave the City limits it shall be the responsibility of the applicant to coordinate with the applicable jurisdictions.

(u) If the TIA is not consistent with the scoping letter (including any amendments) then the TIA will be returned to the applicant without review.

(6) Analysis criteria:

(a) All trip distributions into and out of the transportation system must reflect existing traffic count data for consistency or follow the current transportation model used by the City. If alternate splits are used to distribute traffic then justification must be provided and approved by the Public Works Department prior to first submittal of the TIA.

(b) The peak hour used in the analysis must be the same for every intersection along the street and reflect that of the most critical intersection being evaluated.

(c) Counts performed must be a minimum of two hours and include the peak hour for analysis purposes. All documentation shall be included in the TIA.

(d) Any assumptions used in the TIA, including but not limited to, all supporting count data, LOS analyses, pass-by deductions, growth rates, traffic distributions, or other engineering assumptions must be clearly defined and attached to the TIA when submitted in report form to the City for review.

(e) All LOS analyses shall follow operational procedures per the current Highway Capacity Manual. Ideal saturation flow rates greater than 1800 vehicles per hour per lane should not be used unless otherwise measured in the project vicinity. Queue lengths shall be calculated at the 95th percentile where feasible. The peak hour factor shall be 1.0.

(f) Signal timing used in capacity or progression analysis shall follow City timing plans and account for pedestrian crossing times, unless otherwise noted in the scoping letter.

(g) Arrival Type 3 (random arrivals) shall be used unless a coordinated plan is in place during the peak hour.

(h) The safety review (per 10.461(5)(r)) shall include:

(i) Total number of crashes

(ii) The calculated crash rate compared to the Critical Crash Rate

(iii) Discussion of crash patterns

(iv) Discussion of whether the location is included within a published safety study such as, but not limited to, ODOT Safety Priority Index System (SPIS). Other published safety studies may be used, at the City’s discretion, for all study intersections.

(i) When mitigation is needed at an intersection, roundabouts shall be evaluated as an alternative to traffic signals according to the current procedures of the Public Works department.

(j) Residential dwelling units when within a vertically, mixed-use building, shall not be considered in trip generation calculations.

(7) Other Enhancements Required

If through the TIA analysis it is determined that improvements which increase transportation capacity will not be sufficient to meet the mobility targets, then the approving authority may require that the applicant implement other performance improvement actions sufficient to meet the mobility target. Potential performance improvement actions may include, but are not limited to:

(a) Transportation system connectivity improvements for vehicles, bicycles, and pedestrians.

(b) Transportation demand management (TDM) methods to reduce the need for additional capacity, such as mandatory car-sharing programs, alternative work schedules, employer provided transit passes, or other measures that incentivize transportation options other than single-occupancy vehicles.

(c) Multi-modal (bicycle, pedestrian, transit) improvements to reduce vehicle demand.

(d) Operational improvements to maximize use of the existing system.

(e) Land use techniques (e.g. restricted zones, trip caps/budgets to manage trip generation).

[Amd. Sec. 3, Ord. No. 2001-155, Aug. 16, 2001; Amd. Sec. 5, Ord. No. 2014-161, Dec. 22, 2014; Amd. Sec. 5, Ord. No. 2019-108, Oct. 3, 2019.]