
ONTARIO PEDESTRIAN COLLISION DATA
https://pedestrians.ca

Generated date: 2026-09-24


1. OVERVIEW

This dataset contains spatial and tabular information about pedestrian
collisions in Ontario, Canada, compiled from May 1 2026 onwards.

The core dataset is a spatial vector point layer in which each record
represents a pedestrian collision. Additional information about individual
pedestrians involved in each collision is provided in a related, non-spatial
CSV table.

This dataset is distributed in the following formats:

1. Collisions Shapefile + Pedestrians CSV
2. Collisions GeoJSON + Pedestrians CSV
3. Collisions CSV + Pedestrians CSV

The spatial component contains the location and collision-level information.
The accompanying pedestrian CSV contains information about individual
pedestrians associated with each collision. Any number of pedestrians can
be associated with one collision.

2. FILES

Depending on the distribution format, the ZIP file contains the following:

SHAPEFILE FORMAT
collisions.shp
collisions.shx
collisions.dbf
collisions.prj
collisions_pedestrians.csv
README.txt

GEOJSON FORMAT
collisions.geojson
collisions_pedestrians.csv
README.txt

CSV FORMAT
collisions.csv
collisions_pedestrians.csv
README.txt

3. DATA STRUCTURE

The dataset consists of two related data components:

A. COLLISION DATA
Spatial point layer containing one record per pedestrian collision.

B. PEDESTRIAN DATA
Non-spatial CSV table containing records for individual pedestrians
associated with collisions.

A single collision may have zero, one, or multiple pedestrian records.

The two datasets are related by mapping the "id" field in the collision 
dataset to the "collision_id" field in the pedestrian dataset.

4. COLLISION DATA FIELDS

The collision dataset contains the following fields:

* id

Unique identifier for the collision.

Data type: PostgreSQL UUID
Valid values / format: Unique 36-character string
Example: 4e7fd7ca-1534-413f-b9b8-e75bad10ac0e

* collision_date

Date on which the collision occurred.

Data type: Date
Valid values / format: YYYY-MM-DD
Example: 2026-07-12

* collision_timeofday

Approximate time-of-day information associated with the collision.

Data type: String
Valid values:
- Unknown Time
- Before Sunrise
- Morning
- Afternoon
- Evening
- After Sunset

* title

Title of the source news article describing the collision.

Data type: String
Example: 28-year-old pedestrian dead after being hit by truck in Ajax: police

* url

URL of the source news article describing the collision.

Data type: String
Valid values / format: Fully qualified website URL
Example: https://www.cbc.ca/news/canada/toronto/pedestrian-fatal-truck-crash-durham-police-ajax-9.7312158

* latitude

Approximate latitude of the collision based on reported location.

Data type: Decimal Degrees
Valid values / format: Floating point number to 6 decimal places
Example: 43.859581

* longitude

Approximate longitude of the collision based on reported location.

Data type: Decimal Degrees
Valid values / format: Floating point number to 6 decimal places
Example: -79.014198

* location

Location or address of the collision as reported.

Data type: String
Valid values / format: Full intersection or street address
Example: Sherbourne Street and Dundas Street East, Toronto, ON, Canada

* city

City where the collision was reported to have occurred.

Data type: String
Example: Toronto

* pedestrians_injured

Number of pedestrians reported injured in the collision.

Data type: Integer
Valid values / format: 0 or positive 

* pedestrians_fatal

Number of pedestrians reported killed in the collision.

Data type: Integer
Valid values / format: 0 or positive 

* hit_and_run_reported

Indicates whether a hit-and-run was reported for the collision.

Data type: String
Valid values: 
- YES
- NO

* under_influence_reported

Indicates whether a driver being under the influence was reported
for the collision.

Data type: String
Valid values: 
- YES
- NO

5. PEDESTRIAN DATA FIELDS

The pedestrian CSV contains the following fields:

* id

Unique identifier for the pedestrian record.

Data type: PostgreSQL UUID
Valid values / format: Unique 36-character string
Example: 02513a23-69f1-4ffa-a0d7-5c9d43f9d8df

* collision_id

Identifier of the collision associated with the pedestrian.

This field corresponds to the "id" field in the collision dataset.

Data type: PostgreSQL UUID
Valid values / format: Unique 36-character string
Example: 4e7fd7ca-1534-413f-b9b8-e75bad10ac0e

* outcome

Outcome for the pedestrian associated with the collision as reported.

Data type: String
Valid values:
- injured
- fatal

* age

Approximate age of the pedestrian as reported.

Data type: String
Valid values:
- unknown
- infant
- child
- teenager
- adult
- senior
- 20s
- 30s
- 40s
- 50s
- 60s
- 70s
- 80s
- 90s
- 100+

* gender

Gender of the pedestrian as reported.

Data type: String
Valid values:
- unknown
- male
- female

6. RELATIONSHIP BETWEEN DATASETS

The collision dataset and pedestrian dataset can be joined using:

Collision dataset:
id

Pedestrian dataset:
collision_id

For example, if a collision has:

id = 12345

then all records in the pedestrian dataset where:

collision_id = 12345

represent pedestrians associated with that collision.

Because a collision may involve multiple pedestrians, the collision
identifier may occur multiple times in the pedestrian CSV.

7. SPATIAL INFORMATION

Geometry type: Point

Coordinate reference system: WGS 84 

The latitude and longitude fields in the collision dataset represent
the geographic location of each collision.


9. LIMITATIONS, COVERAGE & LIABILTY

THIS DATA IS PROVIDED ON AN AS-IS BASIS AND THE CREATORS OF THIS DATASET ARE 
NOT LIABLE FOR ANY ERRORS, INNACCURIES, OR OMISSIONS THEREIN. 

USE AT YOUR OWN RISK. 

THE CREATORS OF THIS DATASET DO NOT CLAIM ANY OWNERSHIP OF ANY SOURCE 
ARTICLES REFERENCED WITHIN. ALL DATA WAS OBTAINED FROM PUBLICLY 
AVAILABLE SOURCES.

Users should be aware:

- Data collection began on May 1, 2026.

- All data was summarized from online news reports published at or near the 
date of each collision. 

- URLs referencing original news sources may become inoperable at any time 
due to changes on the original news source websites.

- This dataset is not guaranteed to be exhaustive; that is, not all 
pedestrian-involved collisions that occured in Ontario during the 
timeframe indicated are guaranteed to be included in this dataset.

- Human or technical error may have occured during the reporting of any 
collision, or during the transcribing of any collision details from the 
original source material into this data.

- Any changes related to collisions described in this data (such as pedestrian 
health status) after initial reports will not be reflected in this data.

- Pedestrian collision reporting varies considerably in detail, terminology,
and accuracy, and any generalizations may be reflected in this data.

10. SOURCE

Pedestrians.ca
https://pedestrians.ca

11. DATA LICENSE / TERMS OF USE

This dataset is released under the Creative Commons CC0 1.0
Universal Public Domain Dedication.

To the extent possible under law, the creator(s) have waived all
copyright and related rights in this dataset.

The dataset may be copied, modified, distributed, published, and
used for any purpose, including commercial purposes, without
permission or attribution requirements.

CC0 1.0:
https://creativecommons.org/publicdomain/zero/1.0/

News articles referenced within the data remain the property of
their original creators and are not impacted by this license.

12. DATA VERSION

Data version: 1.0

Last updated: 2026-09-24

13. CONTACT

Questions or issues regarding this dataset can be directed to:

https://pedestrians.ca/about
