Boston Vision Zero crash and fatality records, 2015 to present

Provider
City of Boston (Vision Zero Boston, Boston Transportation Department)
License
Open Data Commons Public Domain Dedication and License (PDDL) 1.0
Size
2 files
Records
44,505 rows
Stored at
data.boston.gov
Access
Free and public. No account with the data provider is needed.
Category
Urban & Civic
Source
https://data.boston.gov/dataset/vision-zero-crash-records

About Boston Vision Zero crash and fatality records, 2015 to present

Traffic crashes in Boston that required a public safety response, published as part of the Vision Zero Boston programme: 44,344 crash records from 1 January 2015 to the present, plus a separate 161-record file of traffic fatalities over the same period. Records are compiled by the Department of Innovation and Technology from the city's Computer-Aided Dispatch (911) system and verified as having required a response. One row is one dispatch. Each carries the dispatch timestamp, a mode_type of ped, bike or mv identifying the mode of transport of the most vulnerable person involved (so a car striking a cyclist is coded bike, not mv), a location_type of Street, Intersection or Other, the street name and up to two cross streets, and coordinates in both Massachusetts State Plane (x_cord, y_cord) and WGS84 (lat, long). The dataset is deliberately privacy-limited: it does not indicate injury severity or whether medical transport occurred, which is why the fatality records are published as a separate, much smaller file rather than as a severity flag. Every field carries a per-column description in the DataStore metadata, which is unusual for this portal and is surfaced in the schema card. The 44,344 crash records against 161 fatalities is the ratio that makes this dataset useful: it supports exposure-adjusted risk by mode, corridor and intersection hot-spot identification, temporal patterns by hour and season, and before-and-after evaluation of street redesigns and speed limit changes. The schema card documents the two traps. The lat and long columns are not raw 911 coordinates: the city snaps the reported point to the nearest street centreline and then reprojects, so the coordinates are accurate to the street but not to the exact point of impact, and clustering on them recovers street segments rather than collision points. And when location_type is Intersection the street column is null and the location lives entirely in xstreet1 and xstreet2, so a groupby on street silently discards every intersection crash, which is the majority of the file. Published by Vision Zero Boston and the Boston Transportation Department under PDDL 1.0.

How to load Boston Vision Zero crash and fatality records, 2015 to present in Python

import io, json, urllib.error, urllib.parse, urllib.request
import pandas as pd

CKAN = "https://data.boston.gov/api/3/action"

def ckan(action, **params):
    """Any CKAN action endpoint. Plain urllib works; no auth, no headers."""
    url = f"{CKAN}/{action}?" + urllib.parse.urlencode(params)
    with urllib.request.urlopen(url, timeout=300) as r:
        return json.load(r)["result"]

def sql(query):
    """Server-side SQL over the DataStore. Warns when the 32,000-row cap clips."""
    res = ckan("datastore_search_sql", sql=query)
    if res.get("records_truncated"):
        print("WARNING: clipped at the 32,000-row cap; aggregate or page with OFFSET")
    return pd.DataFrame(res["records"])

CRASHES    = "e4bfe397-6bfc-49c5-9367-c879fac7401d"   # 44,344 rows
FATALITIES = "92f18923-d4ec-4c17-9405-4e0da63e1d6c"   # 161 rows

# Crashes by mode and year. mode_type is the MOST VULNERABLE party involved,
# so "ped" means a pedestrian was hit, whatever hit them.
crashes = sql(f'''
    SELECT date_part(\'year\', "dispatch_ts"::timestamp)::int AS yr,
           "mode_type", count(*) AS crashes
    FROM "{CRASHES}" GROUP BY 1, 2
''')
deaths = sql(f'''
    SELECT date_part(\'year\', "date_time"::timestamp)::int AS yr,
           "mode_type", count(*) AS fatalities
    FROM "{FATALITIES}" GROUP BY 1, 2
''')
both = crashes.merge(deaths, on=["yr", "mode_type"], how="left").fillna({"fatalities": 0})
print(both.pivot_table(index="yr", columns="mode_type",
                       values=["crashes", "fatalities"], aggfunc="sum").fillna(0).astype(int))

Data structure

Fields

_idint
dispatch_tstext. Date and time of 911 emergency services dispatch
mode_typetext. Type of incident (ped = pedestrian; mv = motor vehicle; bike = bicyclist). Refers to the mode of transport for…
location_typetext. Locations are coded as "street" if the reported location was on a City-owned street; "intersection" if the…
streettext. (if location_type = "Street") Name of city-owned street as reported in 911 system
xstreet1text. (if location_type = "Street" or "Intersection") Name of 1st cross-street
xstreet2text. (if location_type = "Street" or "Intersection") Name of 2nd cross-street
x_cordtext. X coordinate value of location in Massachusetts State Plane projection.
y_cordtext. Y coordinate value of location in Massachusetts State Plane projection.
lattext. Latitude of location. This field represents a transformation of snapping the Y coordinate to the closest street…
longtext. Longitude of location. This field represents a transformation of snapping the X coordinate to the closest street…

Files

One row is one 911 dispatch to a traffic crash. Two resources with the SAME 11-column shape apart from the timestamp column name: crash records (44,344 rows, dispatch_ts, verified 2015-01-01 to 2026-07-01) and fatality records (161 rows, date_time, verified 2015-01-22 to 2026-05-15).
COLUMNS, and unusually for this portal EVERY ONE CARRIES AN OFFICIAL DESCRIPTION in the DataStore metadata, reproduced here:
  dispatch_ts / date_time  date and time of 911 emergency services dispatch
  mode_type      ped, bike or mv. "Refers to the mode of transport for the most vulnerable
                 individual involved", so a car striking a cyclist is coded bike, not mv.
                 This is the single most misread column in the dataset.
  location_type  "street" if on a City-owned street, "intersection" if at a convergence of
                 two or more, otherwise other
  street         name of the city-owned street, only when location_type is Street
  xstreet1       first cross street
  xstreet2       second cross street
  x_cord/y_cord  Massachusetts State Plane coordinates
  lat/long       "a transformation of snapping the [X/Y] coordinate to the closest street as
                 well as converting it into WGS84 projection"
THE PRIVACY DESIGN IS DELIBERATE AND SHAPES WHAT YOU CAN ASK. The city states it does not indicate crash severity or whether medical transport occurred, in order to protect the individuals involved. That is why fatalities are a separate 161-row file rather than a flag: there is no severity column to filter on, and injury counts are not derivable.
RESOURCES:
  Vision Zero Crash Records (data.boston.gov/dataset/vision-zero-crash-records): 1 DataStore resources of 1 total
    e4bfe397-6bfc-49c5-9367-c879fac7401d      44344 rows  Vision Zero Crash Records
  Vision Zero Fatality Records (data.boston.gov/dataset/vision-zero-fatality-records): 1 DataStore resources of 1 total
    92f18923-d4ec-4c17-9405-4e0da63e1d6c        161 rows  Vision Zero Fatality Records

Example file: Crashes by mode and year, the base rate every Vision Zero question starts from: SELECT date_part('year', "dispatch_ts"::timestamp)::int AS yr, "mode_type", count(*) n FROM "e4bfe397-6bfc-49c5-9367-c879fac7401d" GROUP BY 1, 2 ORDER BY 1, 2

Sample notebook

Sample notebook for Boston Vision Zero crash and fatality records, 2015 to present: worked code with the output it printed.

Analyze this dataset without downloading it

On Scigantic, Boston Vision Zero crash and fatality records, 2015 to present opens in a hosted JupyterLab notebook with the data already mounted, so you can read files where they are stored instead of copying them first. Each notebook includes an AI assistant that can see the mounted files and write and run analysis code. Open the dataset page to launch a notebook, or browse the full catalog.

This page is also available as Markdown and as JSON.

Related Urban & Civic datasets