Data and methods

The atlas is only as good as the record behind it. This page sets out where that record comes from, exactly what the atlas does to it and what it cannot tell you.

County roads only31,976 collisionsData through October 22, 2026

At a glance

The record at a glance
Item Value
Source layer Collisions, Clark County GIS
Original data Washington State Department of Transportation collision records
Release used November 13, 2026
Retrieved November 21, 2026
Period covered January 1, 2001 to October 22, 2026
Records in the source 31,981
Records in the atlas 31,976
Records with a map location 28,493
Roads covered Roads maintained by Clark County

Where the record comes from

When police investigate a collision in Washington they complete a police traffic collision report. Those reports go to the state, and the Washington State Department of Transportation keeps the statewide collision data. Clark County GIS publishes the part of that data that falls on county roads as a public map layer called Collisions, which the county describes as collision points from the State of Washington Department of Transportation.

The atlas uses the release the county published on November 13, 2026, retrieved on November 21, 2026. It holds 31,981 records dated from January 1, 2001 to October 22, 2026.

What it covers

The record covers collisions on county roads: the roads Clark County maintains. Under Washington law a county road is a public road outside the limits of cities and towns that has not been designated a state highway. In practice that means the unincorporated communities north and east of Vancouver, such as Hazel Dell, Salmon Creek, Felida, Orchards and Brush Prairie, and the rural roads beyond them.

That is a large part of the county. The Washington Office of Financial Management estimated that 249,320 of the county's 550,000 residents lived outside city limits on April 1, 2026.

It does not cover:

  • City streets in Vancouver, Camas, Washougal, Battle Ground, Ridgefield, La Center, Yacolt and Woodland, which each city maintains.
  • State highways and interstates, which the state maintains: Interstate 5, Interstate 205 and State Routes 14, 500, 501, 502 and 503.
  • Private roads and parking lots.
  • Collisions that were never reported.

Of the 28,493 mapped records, 27,022 lie outside every city as the limits stand today. The other 1,471 are inside present-day city limits, on roads that belonged to the county when the collision happened.

How the atlas prepares it

The atlas began as a script that converted the county's collision export into a file a web map could draw as a heat layer. The preparation now does more, but the principle is the same: change as little as possible and write down every change.

  1. Retrieve every record. All 31,981 records are read from the county layer with every field, with positions converted from the Washington State Plane South system to latitude and longitude.
  2. Remove duplicates. 5 report numbers appear twice in the source with the same date and time. The atlas keeps one copy of each, leaving 31,976 records.
  3. Keep records that have no location. 3,483 records have no coordinates. They cannot be mapped, but they are real collisions and are counted in every chart and total.
  4. Name the roads. The source gives a county road number and milepost, not a name. The atlas matches each record to the Clark County road log, an inventory of 8,835 road segments covering about 1,111 miles, and takes the name of the road at that milepost. 29,523 records receive a road name. 998 have a road number the current log does not contain and are shown by number. 1,455 have no road number at all.
  5. Find the cross street. Where the source names an intersecting county road, the atlas uses it (9,164 records). Otherwise it looks along the road log for the nearest junction: within about 100 feet the record is described as at that cross street (4,411 records) and within about 800 feet as near it (7,846 records).
  6. Assign a community. Each mapped record is tested against current city limits and then against the census designated places drawn by the U.S. Census Bureau.
  7. Group severity. The source uses eight severity codes and two generations of labels. The atlas merges them into six levels and treats the three fatal codes as one.
  8. Complete the collision type. 134 records have no generalized collision type in the source. The atlas assigns them from the detailed type: 119 to bicyclist, 12 to other and 1 to pedestrian. 2 have no type of either kind and are shown as not stated.
  9. Add road class and posted speed. These come from the road log segment each record matches (27,697 records). Where there is no match, the class recorded with the collision is used (2,797 records), except for freeway and interstate labels, which the source attaches to ordinary county roads in error. 1,482 records are left unclassified.
  10. Pack the result for the browser. The prepared records are stored in one compact file. Every filter, chart, ranking and statistic on the site is then computed in your browser from that file, so the map and the numbers cannot drift apart.

The field guide lists every field and value that results.

Known limits

  • Empty does not mean safe. Large parts of the map are empty because the roads there are not county roads.
  • The network changes. When a city annexes land, roads leave the county system and later collisions on them leave this record. A falling count in one area can be an annexation, not an improvement.
  • Counts are not rates. The record has no traffic volumes by year. The roads page estimates rates from current traffic counts and says how rough they are.
  • Minor collisions are under-recorded. A collision is in the record only if it was reported. Property-damage collisions below the legal reporting threshold may never be.
  • 11% of records cannot be mapped. 3,373 of the 3,483 unmapped records date from 2003 to 2009; in 2004 they are 29% of the year. Maps of those years show fewer collisions than occurred.
  • The newest months are incomplete. Reports take weeks to reach the record. For the last three months of 2026 in this release the counts are August 42, September 29, October 3, against about 67 in a typical month of 2025.
  • Fields describe the scene, not the cause. Weather, lighting and alcohol are what the officer observed. None of them is a finding of fault.
  • Road class and speed are current values. They describe each road as it is in the road log today.
  • Locations are approximate. Collisions at a junction are placed at its center, and positions depend on the milepost the officer recorded.

Changes in the record over time

  • Driveway collisions are coded as a separate type only from 2001 to 2008 (1,588 records).
  • Bicyclist collisions have a blank generalized type from 2018 onward. The atlas fills it in, as described above.
  • Alcohol status is blank in all 5,620 records from 2020 onward.
  • Severity labels changed wording during the period. Serious injury became suspected serious injury and evident injury became suspected minor injury. Both sets of labels appear side by side for many years under the same codes, so the atlas treats each pair as one level.
  • The reporting threshold rose. Washington raised the property-damage threshold for a required collision report from 700 dollars to 1,000 dollars at the start of 2015. Fewer low-damage collisions are required to be reported than before.

Checks

  • Totals. The number of records in each year matches the count the county's service reports for that year, less the 5 duplicates.
  • Severity. Every record with a fatal severity code has at least one death recorded, and no other record has any.
  • Positions. Coordinates were compared with an independent conversion of an earlier county export. Of 26,656 records present in both, all but 2 agree to within 16 feet.
  • Names. The twelve busiest locations were compared with the street names in OpenStreetMap at the same coordinates, and all twelve matched. Use the collision map to do the same for any road.

If the base map itself is wrong, OpenStreetMap accepts corrections from anyone at openstreetmap.org/fixthemap.

Federal law limits how some highway safety data can be used in court. Title 23, section 407 of the United States Code provides that reports, surveys, schedules, lists or data compiled or collected to identify, evaluate or plan the safety enhancement of potential accident sites or hazardous roadway conditions under certain federal programs shall not be subject to discovery or admitted into evidence in a federal or state court proceeding, or considered for other purposes, in any action for damages arising from an occurrence at a location the data addresses.

Whether that provision applies to a particular use of collision data is a legal question. The atlas offers general information and is not legal advice.

Updates

The county republishes its collisions layer from time to time, adding new reports and occasionally revising old ones. Every figure on this site reflects the release of November 13, 2026. When the atlas moves to a newer release, counts for recent years will rise as late reports arrive.

Citing the data

Credit the source as Clark County GIS, collisions layer, from Washington State Department of Transportation collision data, release of November 13, 2026, as prepared by the Clark County Collision Atlas. State the years and filters you used and that the figures cover county roads only.