Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Lumberyard Parking topic
No spam. Unsubscribe anytime.
Council tables decision on Lumberyard parking and stormwater work after public debate
Summary
Council heard competing views on a developer‑funded proposal to pave and add stormwater swales to the city’s parking area near the boathouse tied to the Lumberyard project and voted to table the item to July 29 for further staff‑developer discussion.
Get email alerts on the Lumberyard Parking topic
No spam. Unsubscribe anytime.
The council heard extensive public comment and staff and developer presentations on a proposed developer-funded improvement to the city‑owned parking area beside the boathouse tied to the Lumberyard redevelopment project.
The developer’s representative said the project includes paving, new stormwater swales and grading to treat runoff generated by new public and private infrastructure (including roadway improvements and sidewalks). The developer said a substantial portion of treated runoff would come from public infrastructure the developer is required to build, not solely from private buildings. The developer also said staff and county/state agencies had reviewed and permitted stormwater plans.
Opponents — including nearby residents, longtime civic advocates and at least one councilmember — raised concerns that the project would reduce public waterfront open space, that approvals or amendments to the community‑benefit agreement were not properly noticed, and that the city could be ceding waterfront land or stormwater capacity for private development. One attorney for the developer said the project was approved consistent with documents adopted by council and that work had proceeded in reliance on those approvals and on water‑management permits, creating potential equitable‑estoppel concerns.
After extended discussion and requests for follow‑up on survey discrepancies, staff and the developer agreed to continue working toward a resolution. The council voted to table the item to the July 29 meeting to allow staff and the developer to meet and attempt to resolve outstanding issues.

