Lopez Village committee pushes code changes to require pathway connectivity, tweak parking and bike rules

Lopez Village Planning Review Committee members spent the bulk of their Feb. 27 meeting debating a package of code changes aimed at improving pedestrian connectivity, clarifying setback exceptions and updating parking and bicycle-parking requirements.

Committee member Barbara, Lopez Village Planning Review Committee member, opened the discussion by pressing to “get the connectivity map in the code section,” saying developers should be required to connect to pedestrian pathways shown on the Lopez Village sub-area plan map (connectivity plan, Map 7, page 46). Committee members said failing to put the connectivity map into the land‑use code leaves planned pathways vulnerable to obstructions such as equipment, utility apparatus and water storage tanks.

The committee framed the proposed edits as three linked steps: identify parcels that need connection, require connectivity language in the code, and meet with public-works and project teams to ensure connections are implemented. Sofia, county planning staff, recommended inviting Public Works staff (and specifically suggested inviting Colin Hutchmer) to coordinate on crosswalks and pathway construction and said she could track and place permit submissions on committee agendas when they enter the county permit review system.

Members also proposed changes to specific code sections. They asked that Table 18.37.50 (setbacks) be revised so items that are currently exempt from setback rules—mailboxes, pump houses, utility apparatus and similar features—cannot be placed where they prevent construction or use of village pathways shown on the connectivity map. The committee suggested substituting the phrase “buildings” for the broader “development” in select provisions to avoid allowing single-purpose structures (for example, a water storage tank) to be treated as development that can be sited in a pathway.

On parking the committee reiterated a longtime objective: reduce paved area and eliminate or lower parking minimums where possible, and promote shared driveways and shared parking to limit unnecessary paving. Members said the code should explicitly require shared driveways when feasible and enforce the existing standard that “all parking areas must provide adequate space for turning and maneuvering without using public rights-of-way for internal circulation,” citing concerns about truck access and tight turning areas at new sites.

The members also proposed tightening bicycle-parking rules. The current code allows a bicycle to substitute for a car parking space when a developer meets a vehicle-parking minimum, but does not require that bicycle parking be an actual bicycle rack or area. Committee members proposed requiring a designated bicycle-parking installation (rack or enclosure) as a condition of any substitution.

Landscaping proposals included pollinator-friendly plantings, with at least three species that bloom across seasons and alignment of multifamily parking-lot landscaping standards with commercial standards when parking exceeds five spaces.

Members emphasized implementation tasks: committee walkthroughs of existing paths, a prioritized list of high-value connections, and direct outreach to Public Works and project leads to ensure pathway connections are addressed early in design. Sofia said she will add relevant permit applications to the committee agenda as they enter the county’s review process so members can comment early.

The committee did not adopt a formal code amendment at the meeting; members asked staff to compile their suggested edits for a future submittal to planning staff and the planning commission.