Laserfiche WebLink
tiY : _ 4 <br /> /f~ pp ~."•i <br /> "`+3 •r t,.Y~±t+c4_ 'S. , t.~7"~al ~ i ` -ors ~4 <br /> ' 't G ~Jrt F . <br /> E ~ <br /> ~-~~T. ' <br /> r h~ =l'..~, "s <br /> Internal Boundaries. Once the needed model data have been assembled, the next step is <br /> to evaluate and possibly update the internal boundaries. If the data do not support a single <br /> zone structure, the internal boundary lines should be drawn #o combine areas with similar trip <br /> con#ributlon characteristics so that the differing fee levels will be justifiable, equitable, and <br /> defensible basod on the model data. <br /> In preparing this analysis, we have found that it simplifies the process (and makes the results <br /> more understandable) to convert land use in each subarea into equivalent single family dwelling <br /> units, based on relative trip generation between the land use categories. This way, the study <br /> participants can more readily understand the relative growth in each subarea, and are better able <br /> to relate the results to the magnitude of fee level implied in the calculations. When the final fee level <br /> recommendation is developed, it also makes it easier to convert the per-trip fee into an appropriate <br /> 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 <br /> be challenging for staff to determine what is a fair and equitable level to recommend to the City <br /> Council. The nexus analysis usually Justifies a fee that is not only much higher than the currentiy- <br /> adopted fee but also seems to be well above a level that might be considered "reasonable". On <br /> ' ~ the other hand, the needed improvements may be costlier than those funded by programs of <br /> nearby peer Cities, so adopting a fee level that Is comparable to other programs may not generate <br /> ~ sufficient revenue to implement the needed Improvements. In past projects we have found that our <br /> experience in balancing these issues and recommending a zone structure and fee level can help <br /> staff reach a consensus on a program to recommend to the Council. In a case like this involving <br /> multiple agencies, it will be essential to have a staff consensus before going to the JPA Board and <br /> City Councils. So we will develop a recommendation based on the nexus analysis, a survey of peer <br /> Cities' fee levels, and input from the technical staff and development community participants in the <br /> study. <br /> Ta reach consensus between both Cities' staff on the recommended program, we will conduct <br /> a joint meeting/workshop of the technical team to review the zone alternatives, the nexus data, <br /> the peer Cities' survey results, and the recommended fee program. The earlier reviews and <br /> concurrence on land use assumptions and improvement cost estimates will make it possible to <br /> focus this discussion on the rationale behind the consultant recommendations, so #hat the meeting <br /> outcome can be a consensus fee program recommendation to take to elected offlclafs. <br /> Once we have developed consensus among the technical team, we will prepare the technical <br /> inputs required for the two Cities' ordinances. As explained in the pre-proposal meeting, the City <br /> d~ Attorneys' offices will take the lead in preparing the ordinances, and the traffic consultant will <br /> S5~ provide the needed technical input. <br /> <br /> _ z"" 13 I TL7701 S3 .09 <br /> ®S~ KimleyHom <br /> ~ and Associates, inc. <br /> 25C-23 <br /> <br />