Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transportation Data Platform topic
No spam. Unsubscribe anytime.
Select Board hears Urban SDK demo on speed-data platform; questions about data sources and costs
Summary
Representatives from Urban SDK demonstrated a traffic-speed analytics platform that uses aggregated vehicle telemetry to show daily-updated speed metrics and 13 months of history; the board asked about data provenance, privacy safeguards, penetration rates, pricing estimates of $5,000–$15,000 annually, and requested a sandbox for hands-on review.
Urban SDK representatives presented their traffic‑speed analytics platform to the Jericho Select Board and answered detailed questions about data sources, privacy, accuracy and pricing.
At the start of the presentation, an Urban SDK representative told the board the platform offers ‘13 months of historical speeds on your roadways’ and daily updates on a seven‑day delay, allowing staff to generate PDF reports and target enforcement or capital improvements. The presenter said the company buys anonymized telemetry from Here Technologies and processes it for jurisdiction‑level analysis.
Board members probed how the data are collected and anonymized. The presenter said the vendor ‘cannot give make, model, year, color or VIN’ and described the feed as aggregated and cleaned, adding their conservative penetration estimate is roughly 35% of vehicles on a roadway. The board asked whether that level of sampling is reliable in a rural town; the presenter cited a small‑town reference customer in Maine and said crosschecks with speed‑trailer data were within about 1 mile per hour.
On cost, the presenter offered a broad annual pricing range for Jericho ($5,000–$15,000), explaining fees scale with centerline miles and population and that the minimum contract term is one year. Staff and board members requested a sandbox/demo account and a partner reference; Urban SDK agreed to provide a sandbox link and contact information for a town that uses the system.
The board did not take any procurement action at the meeting. Members asked staff to circulate the sandbox link and arrange a follow‑up discussion to evaluate operational fit and data expectations before any purchase decision.
