Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Automated Enforcement topic
No spam. Unsubscribe anytime.
Council directs staff to pursue ODOT application for automated enforcement amid debate over placement and speed limits
Summary
Council directed staff to move ahead with submitting an application to ODOT for automated traffic enforcement on Highway 26 at multiple intersections after an extended debate about crash data, speed‑limit ramping, signage, privacy safeguards and whether enforcement would prioritize safety or revenue.
City staff asked council for direction to submit an application to the Oregon Department of Transportation to allow automated traffic enforcement (photo‑based speed and red‑light enforcement) at selected Highway 26 intersections. After an extended discussion about data, placement and public messaging, council gave staff authority to proceed with the ODOT application and to gather supplemental traffic data for a targeted intersection.
Police and records staff described privacy protections: access would be limited to the Sandy Police Department and municipal court for violations and criminal investigations, handled under existing criminal‑justice information (CJIS) rules. “This data would be treated no differently than any other data that the police department or court currently handles,” the police representative explained. Staff said license‑plate‑reading technology was not part of this first stage and that contracts would explicitly limit vendor use and data resale.
Councilors pushed back on placement criteria and the program’s purpose. Several members argued the application should be data‑driven and target intersections with the highest crash and pedestrian‑safety risk; staff provided ODOT crash summaries showing higher incident counts at intersections including 26 & Bluff, 26 & Reuben, 26 & 362nd and 26 & Orient. Others argued for entry‑and‑exit camera placements to set a speed message for drivers entering Sandy. There was robust discussion of “ramping” the posted speed transition (for example, preventing a sudden drop from 40 to 25 mph) so enforcement would not become a perceived speed trap.
After debate, councilors agreed staff should submit the application and pursue additional targeted data collection (for the 211/Proctor/Pioneer area) so the application would reflect crash history and directional needs. Staff said vendor contracts and final camera placement would be determined later, and that applications to ODOT can cover multiple candidate intersections to avoid later delays when adding locations.
Next steps: staff will finalize the ODOT application (including supplemental traffic data) and continue public communications planning (signage and an awareness campaign) prior to installation if ODOT grants authority.
