Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Traffic Safety topic
No spam. Unsubscribe anytime.
Council approves first reading of school‑zone speed camera ordinance after extended debate over data, privacy and procurement
Summary
Council advanced on first reading an ordinance to allow automated speed detection in five school zones (phased implementation), after debate over vendor piggybacking, data retention, appeal process and whether cameras are a 'money grab'; the measure passed 4–1.
Get email alerts on the Traffic Safety topic
No spam. Unsubscribe anytime.
The council moved July 7 to advance a school‑zone speed detection ordinance on first reading after lengthy public comment and council discussion about safety, procurement and data safeguards.
Deputy City Attorney Nicole Donnell cited Florida Statute 316.1895 as authorizing local governments to adopt speed detection systems in school zones and explained a traffic study from February identified five school zones with elevated safety risk: Greco Middle School, Woodmont Charter School, Temple Terrace Elementary School, Lewis Elementary School and River Hills Elementary Magnet School. Captain Malave of the Temple Terrace Police Department outlined a phased rollout, starting with Greco Middle and Lewis Elementary and adding the remaining zones in later phases.
A Genoptic representative, Katie Nash, asked the city to include side‑by‑side demonstrations and to consider data integrity, third‑party audits, community reporting and customer service in vendor selection. Council members pressed staff on several points: whether cameras would operate on side streets (Captain Malave said cameras would be placed on side streets, not major thoroughfares such as Fowler or 56th), data retention periods (nontriggering footage: 30 days; violation evidence: destroyed 90 days after disposition), the appeals/hearing process (a local hearing officer will adjudicate appeals), and whether the contract would cost the city. Staff said the business model for the vendors is revenue‑sharing and that the city expects no direct vendor charges; some contracts allocate roughly 39% to the city or 65% share to the vendor depending on terms.
Council debated procurement approach: staff proposed piggybacking on another jurisdiction's contract (no direct cost to the city, and certified‑mail costs covered under the piggyback) while some council members urged broader vendor solicitation and clear contract language on data privacy and performance metrics. Council member Fernandez said she would not support remote automated enforcement; several others expressed conditional support if contract language addresses data use and effectiveness reporting.
A motion to approve the ordinance for first reading (with second reading set for Aug. 4) passed by recorded voice vote at the end of the discussion: ordinances approved on first reading 4–1. Council instructed staff to include time‑of‑operation and data safeguards in contract documents and to return with the contract for council approval.

