CRD-01 · Public records

Reading the crash map before you ride

Georgia keeps the crash reports that police file and publishes what they add up to. Read as a record of where collisions concentrate rather than a prophecy of where you will be hit, the data is a route-planning tool.

Published 6 September 2026 · The Georgia Records Desk editorial team

A crash map is a register, not a forecast

Every marker on a crash map stands for a report an officer filed after the fact. What the state publishes is the register of those reports: where collisions were recorded, what the reporting officer noted, and which contributing factors were marked. The map says where crashes happened, not where they will.

That distinction is what makes the dataset useful instead of frightening. A rider planning a calmer route is doing the same thing this desk does with any register: reading a history to make a practical choice, in this case between two ways of reaching the same office.

Which datasets describe a commute route?

Three kinds of public data describe a ride. Crash data says where collisions involving cyclists or pedestrians were reported. Road inventory data says what the corridor is: lane counts, speed limits, whether a shoulder or a marked facility exists. Traffic counts say how many vehicles use it. Each is a different record kept by a different part of the transportation department.

A route that looks dangerous on the crash map but sits on a low-speed corridor with few vehicles is a different risk than the same marker count on an arterial. The three datasets are meant to be read together.

How do you read crash data without alarm?

Read for concentration, not for count. Ten markers scattered along three miles of road describe a different corridor than ten markers at one intersection, even though the totals match. Intersections dominate the record because that is where paths cross; long midblock stretches that feel exposed often show almost nothing.

Read for pattern, not for story. A cluster at one junction usually reflects a fixed feature: a missing signal phase, a turn lane that hides cyclists, a driveway density. What is fixed can be routed around, which is precisely what makes the record actionable.

What the record cannot tell you

Crash reports capture collisions serious enough to be reported. Close passes, near misses and the rides people declined to take leave no file at all. A corridor empty on the map may simply be one nobody rides; the absence of markers is not evidence of safety, only of unrecorded experience.

The record also ages. A repaving, a new signal or a development that changed turning traffic can make a five-year-old cluster obsolete. The data describes the road as it was when the reports were written.

What do you do with what the records show?

The record’s practical output is small and concrete: shift a route one street over to skip a bad junction, time a ride outside the peak the reports cluster in, or flag a corridor to the city with the crash record attached. A request to an office that carries its own evidence reads differently than a complaint.

Where a route problem sits inside a city’s limits rather than on a state route, the file to ask about is local, the same divide this guide draws on finding a city’s own rules.

Why records beat anecdotes here

Every cyclist knows an intersection by reputation, and reputations are unreliable registers: loud, current and wrong in both directions. The crash file is incomplete but consistent; it was not written to persuade anyone. That is the quality this desk looks for in any source, the same discipline behind the guide’s method of tracing a rule back to the document that carries it.

What dot.ga.gov is

The Georgia Department of Transportation publishes the state’s road data: traffic counts, road inventories, project files and the crash data compiled from police reports. Its pages and linked dashboards are where the datasets described here are published, alongside the engineering context that explains how the state reads its own numbers.