June 11, 2026 City Planning Commission hearing

The hearing moved Riverwalk forward. It did not resolve the safety questions.

The Commission approved staff recommendations for Riverwalk, but the hearing record shows unresolved contradictions in the reasoning used to justify approval. This page summarizes those contradictions without posting the full machine transcript.

The full transcript is being reviewed. Because the transcript is machine-generated, direct quotes should be checked before publication. The points below are based on the hearing record and will be refined as the record is verified.

The core contradiction

One project when selling benefits. A narrower project when answering safety concerns.

The applicant presented Riverwalk as a major integrated mixed-use development: 814 residential units, 75,968 square feet of commercial or restaurant use, 1,806 parking spaces, new river access, a public plaza, landscaping, commercial activation, and traffic improvements.

But when public health and environmental findings were challenged, the applicant argued that the tract map only divided land and did not approve density, so some safety and density arguments should not control the tract map decision.

That is the central problem. The project is presented as one full community benefit package when seeking approval, but narrowed into a technical land division when safety findings are challenged.

Contradictions and unresolved gaps

Questions the approval did not resolve.

01

The applicant and staff appeared to take opposite positions on parking exemption eligibility.

The applicant stated that the staff report said the property was eligible for a state parking exemption, but argued the nearest qualifying major transit stop was more than half a mile away and that the project did not qualify. Later, City staff stated the project was eligible for the full parking exemption and that the City was legally barred from imposing minimum parking requirements.

Why it matters

Parking exemption eligibility affects the legal basis for parking conditions and the broader claim that this project is properly reviewed under state housing rules.

02

Evacuation was treated as unnecessary, but safety was still treated as addressed.

Residents and appellants raised evacuation capacity in a Very High Fire Hazard Severity Zone. Staff responded that the demand for corridor-level evacuation simulation exceeded statutory requirements and that project review relied on access, roadway, and department standards. When a commissioner asked whether evacuation was required as part of project review, staff indicated the exemption meant that level of analysis was not required.

Why it matters

Emergency vehicle access standards are not the same as an evacuation capacity analysis for thousands of civilians trying to leave while fire responders enter.

03

Fire compliance was described as complete, but also left for later clearance.

The applicant said fire compliance had been fully reviewed and was not being deferred. In the same explanation, the applicant described Fire Department checks, clearance, and building permit plan check as later steps that would confirm compliance.

Why it matters

If compliance still has to be confirmed later, the public record should clearly explain what has already been proven and what is still pending.

04

Calling the problem pre-existing does not answer whether Riverwalk worsens it.

The applicant acknowledged evacuation fears among hillside residents but characterized them as pre-existing conditions and stated that adopted city evacuation and hazard plans were already in place.

Why it matters

A pre-existing safety problem is not a reason to ignore added load. The relevant question is whether adding 814 residential units, commercial activity, rideshare activity, deliveries, and construction traffic worsens the known risk.

05

Traffic benefits were presented as safety improvements, while requirements remained unclear.

The applicant promoted traffic and safety infrastructure upgrades, including signals and circulation improvements. But when a commissioner asked about the difference between recommended and required signal improvements, staff explained that signalization requires warrant analysis and may be voluntary absent the warrant.

Why it matters

Public-facing improvements should not be treated as safety mitigation unless they are actually required, funded, and enforceable.

06

The project was framed as housing relief, but only 46 units are very low-income.

The project includes 814 units and 46 very low-income units. When asked how that number was reached, the applicant explained it as the density bonus calculation. Commissioners themselves asked whether the developer could consider more affordable units.

Why it matters

The project is defended as housing and affordability, but the affordable component appears to be close to the minimum needed to unlock the requested density bonus.

07

The project was described as green, while significant tree removal was discussed.

The applicant emphasized landscaping, sustainability, and new tree planting. The hearing also discussed substantial removal of existing trees and questions about whether replacement would actually meet or exceed the existing number.

Why it matters

Tree replacement counts, species, location, maturity, shade, and ecological function matter. A young replacement tree is not the same as existing canopy.

08

Questions were asked. The approval still moved forward.

Commissioners asked about evacuation, ingress and egress, transportation, tree replacement, affordable unit count, and parkway design. After those questions, the Commission still approved staff recommendations.

Why it matters

The record matters because it shows that major questions were live at the hearing, but approval moved forward without a clear public-facing resolution.

What happens now

The legal effort is moving forward.

After the June 11 hearing, the group is meeting with counsel to evaluate the strongest next steps and determine the most effective path forward. This is an active phase, not a pause. The immediate work is to preserve the record, identify the strongest issues, coordinate with affected neighborhood groups, and determine what is realistic to pursue.

A new public comment opportunity is expected soon. As soon as the City assigns a Council File Number to this case, residents will be able to submit comments to the City Council's Planning and Land Use Management (PLUM) Committee and to the full City Council. We are watching for that number and will post it here, with instructions, as soon as it appears.

Support the next phase Donate