The Zoning Hearing Traffic Dispute
A city of 90,000 is considering a 400-unit apartment complex near a major intersection. The developer's traffic study, paid for by the developer, predicts 2,100 additional daily vehicle trips and rates the intersection at level of service C, which is generally acceptable. A neighborhood group submits a petition with 1,200 signatures, 60% from households within half a mile, claiming the project will add 4,000 trips and push the intersection to level of service F, which is failing. The city's own 2019 count recorded 18,000 daily vehicles at that intersection; the intersection's estimated capacity is 20,000 daily vehicles. The developer's study uses 2023 counts and assumes 35% of residents will commute by bus, based on a nearby development that opened before bus service was cut. The neighborhood group's estimate uses a national average of 10 daily trips per apartment unit. The city planning department has not independently verified either trip estimate. A council member asks how to weigh the two claims, what the petition actually shows, and what conditions, if any, should be attached to approval.
1. Compare the two trip estimates with the intersection's capacity. What does the arithmetic suggest, and why is neither estimate by itself decisive?
Read the worked answer
Baseline 2019 count: 18,000 daily vehicles. Capacity: 20,000. Headroom = 2,000 before any new trips.
Developer estimate: 18,000 + 2,100 = 20,100, slightly over capacity. Residents' estimate: 18,000 + 4,000 = 22,000, 2,000 over capacity. On arithmetic alone, both estimates imply the intersection is at or beyond capacity, but the developer's estimate is only barely over and depends on an old baseline.
Neither is decisive. The developer's 35% bus assumption is questionable because it relies on a nearby development from before bus service was cut; if bus ridership is lower, trips are higher. The residents' 10 trips per unit is a national average and may not fit this site's size, income, or transit access. The developer has an incentive to minimize impacts, but the residents' group has an incentive to maximize them. The city needs an independent count and local trip-generation data before choosing.
2. What does the petition show and not show? Explain how the signature distribution affects its evidentiary value.
Read the worked answer
The petition shows organized, concentrated concern: 1,200 signatures, with 60% from within half a mile. That is meaningful because nearby households would experience traffic, parking, and noise most directly; it is evidence of intensity, not of citywide prevalence. 1,200 is about 1.3% of 90,000 residents, and signatures can be gathered by active opponents without representing a random sample.
It does not prove that the project will add 4,000 trips or cause level of service F. Those are technical claims requiring traffic data, not petition counts. It also does not show that all signers oppose the project outright; some may support it with conditions. The council should treat the petition as a signal to investigate nearby impacts and to weigh distributional concerns, not as a substitute for an independent traffic analysis.
3. Recommend two conditions the council could attach if it approves the project, tied to the uncertainties in the evidence.
Read the worked answer
Conditions tied to the uncertainties:
Require an independent, developer-funded traffic count and trip-generation study before construction, using current counts and local transit data. If the study predicts the intersection exceeding capacity, require mitigation-such as a signal upgrade, turn lanes, or a bus shuttle-before occupancy.
Phase occupancy and set a trigger: after each phase, monitor the intersection; if level of service drops below D or queuing exceeds a set threshold, the developer must fund specified improvements before the next phase.
Require a travel-demand management plan with actual bus service, not just an assumption: subsidized transit passes, secure bike parking, and a shuttle if service is limited. This matters because the developer's estimate assumes 35% bus use; without service, that assumption fails. These conditions do not resolve whether to approve, but they make approval conditional on verifiable performance.