Boston Open Data · 311 Service Requests
Every 311 complaint about a vehicle in a Boston bike lane, cross-checked two independent ways — what people wrote, and where they stood — and compared against how the city handles everything else in the same queue.
Everything on this page is generated directly from Boston's Open311 API. SQL, source code, and methodology are open source.
Closure and on-time rates for Confirmed bike lane blocking, measured against everything else in the same queue.
Three mutually exclusive groups: Confirmed (the complaint's own text names a bike lane), Possible (no such text, but the location sits within 15m of a mapped bike lane), and Other (the rest of the same Illegal Parking / Abandoned Vehicle / Bicycle Issues / Abandoned Bicycle pool). Two independent detection methods, same result.
Confirmed + Possible bike lane blocking incidents, by week requested.
Top streets and neighborhoods by combined Confirmed + Possible incident count.
The full scope this dataset covers, before splitting out bike lane blocking specifically.
All Confirmed + Possible bike lane blocking requests. Click a column to sort; search filters street, neighborhood, and description.