Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Environmental Review topic
No spam. Unsubscribe anytime.
Northfield Council denies citizen petition for environmental worksheet on Harvest Hills Phase 2
Summary
The council voted to deny a petition requesting an Environmental Assessment Worksheet for the Harvest Hills Phase 2 development, concluding the project does not meet state or MnDOT thresholds that would mandate an EAW; staff will proceed with targeted traffic counts and recommend mitigation at final plat.
The Northfield City Council voted on June 16 to deny a citizen petition that asked the city to prepare an Environmental Assessment Worksheet (EAW) for the proposed Harvest Hills Phase 2 development, a 71‑unit residential project adjacent to Northfield Middle School and Bridgewater Elementary.
The petition, presented by Jason Hill, argued the development would add motor traffic equal to roughly a 60% increase on nearby neighborhood streets and asserted a central planning error: the petition said Fillmore Street is incorrectly classified as a collector in city materials and should be treated as a local street, increasing concern for pedestrian safety. “This is a nearly 60% increase in neighborhood traffic along pedestrian roads, which is a significant increase by any reasonable definition,” Hill said during his presentation.
City staff and the council framed the decision around the narrow statutory question for a petitioned EAW: whether the project, based on the material evidence in the petition, has the potential for significant environmental effects. Staff and the resolution drafted for council noted that the project’s 71 units fall below the mandatory EAW unit thresholds commonly used in Minnesota (the mandatory range is roughly 100 to 150 units for residential projects) and that MnDOT guidance for when a traffic impact study is advised (250 peak‑hour trips or 2,500 daily trips) also was not triggered by the project’s projected trips.
Community Development Director Mr. Wapoda told the council that staff had collected pedestrian and vehicle counts in May on school days and non‑school days and was preparing recommendations based on observed data. “We are assessing that data, and when we get to final plat we’ll be suggesting, based on that data, what type of interventions—whether traffic calming measures or other pedestrian improvements—would be required or suggested,” he said.
Multiple councilors praised the petitioner’s community engagement while saying the petition did not present material evidence that would change staff’s technical finding. Councilor Peterson White said the concerns named in the petition are legitimate to study, but that the necessary information can be produced through the focused traffic and pedestrian counts staff is already collecting: “All of those things can be quantified … we know the number of units that will be built,” she said.
Councilors who opposed the petition argued the EAW is not the right tool for this scale of project and cited time and cost impacts of a full EAW. Councilor Beamer emphasized the financial cost to the city and developers for a full EAW and questioned whether the petition reflected substantive environmental criteria or other neighborhood objections.
The council approved the staff‑draft resolution to deny the EAW petition (Resolution 2026‑062). Staff said the denial will not stop the city from requiring targeted mitigation where data indicates it is warranted; staff expects to return in July with a summary of the traffic and pedestrian counts and any recommended crossing or intersection improvements.
What’s next: staff will complete the traffic and pedestrian analysis collected in May and present recommendations at a future meeting; no final plat or developer approvals will occur while the EAW petition decision process is open, consistent with the petition timeline.
