My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
KIMLEY-HORN & ASSOCIATES 4 -2009
Clerk
>
Contracts / Agreements
>
K
>
KIMLEY-HORN & ASSOCIATES 4 -2009
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2019 12:18:42 PM
Creation date
2/2/2011 12:30:12 PM
Metadata
Fields
Template:
Contracts
Company Name
KIMLEY-HORN & ASSOCIATES
Contract #
A-2009-212
Agency
PUBLIC WORKS
Council Approval Date
12/21/2009
Insurance Exp Date
4/1/2020
Destruction Year
0
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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).
View images
View plain text
Internal Boundaries. Once the needed model data have been assembled, the next step is to evaluate and <br />possibly update the internal boundaries_ The internal boundary lines should be drawn to combine areas with <br />similar trip contribution characteristics so that the differing fee levels will be justifiable, equitable, and <br />defensible based on the model data. <br />In preparing this analysis, we have found that it simplifies the process (and makes the results more <br />understandable) to convert land use in each subarea into equivalent single family dwelling units, based on <br />relative trip generation between the land use categories. This way, the study participants can more readily <br />understand the relative growth in each subarea, and are better able to relate the results to the magnitude of <br />fee level implied In the calculations. When the final fee level recommendation is developed, it also makes it <br />easier to convert the per -trip fee into an appropriate fee rate for each land use category. <br />Fee Level Recommendation. When a traffic impact fee has not been updated for 16 years, it can be <br />challenging for staff to determine what is a fair and equitable level to recommend to the City Council. The <br />nexus analysis usually justifies a fee that is not only much higher than the currently -adopted fee but also <br />seems to be well above a level that might be considered "reasonable". On the other hand, the needed <br />improvements may be costlier than those funded by programs of nearby peer Cities, so adopting a fee level <br />that Is comparable to other programs may not generate sufficient revenue to implement the needed <br />improvements. In past projects we have found that our experience in balancing these issues and <br />recommending a zone structure and fee level can help staff reach a consensus on a program to recommend <br />to the Council. We will develop a recommendation based on the nexus analysis, a survey of peer Cities' fee <br />levels, and input from the technical staff and development community participants in the study. <br />We will conduct a meeting/workshop of the technical team to review the zone alternatives, the nexus data, <br />the peer City's survey results, and the recommended fee program. The earlier reviews and concurrence on <br />land use assumptions and improvement cost estimates will make it possible to focus this discussion on the <br />rationale behind the consultant recommendations, so that the meeting outcome can be a consensus fee <br />program recommendation to take to elected officials. <br />Once we have developed consensus among the technical team, we will prepare the technical inputs <br />required for the City's ordinance. As explained in the pre -proposal meeting, the City Attorney's office will take <br />the lead in preparing the ordinance, and the traffic consultant will provide the needed technical input. <br />Subtask CA: Prepare Model Data for Nexus Analysis <br />Review the current internal boundaries for traffic fee levels, and consider adjustments to the <br />boundaries if a clearer connection between land use and improvements could be established. <br />• For each subarea, calculate the percentage of trips generated in the overall study area, as well as <br />the percentage of improvement costs. <br />• Evaluate optional approaches for establishing the nexus between trips and improvement costs, and <br />identify the specific model data needed. For budgeting purposes, we have assumed that select link <br />model runs will be used to determine each geographic area's fair share of each improvement's cost. <br />Prepare select link model runs using the 2035 model to identify origins/destinations of trips using <br />streets being improved. For budgeting purposes, we have assumed that select link model data will <br />be developed for up to 30 improvement projects. <br />Prepare select link model runs using the base year model to identify origins/destinations of existing <br />trips using streets where improvements in the 2035 scenario are located. <br />
The URL can be used to link to this page
Your browser does not support the video tag.