-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
1026 lines (865 loc) · 52.1 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Bicycle Collision Analytics (Lincoln, NE)</title>
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">
<link rel="stylesheet" href="css/chartist.min.css">
<link rel="stylesheet" href="css/main.css" />
<script src="https://maps.googleapis.com/maps/api/js?v=3.exp&key=AIzaSyDpyFz8qiDpmPqe8BakGx6L8Gcwqb1DfJU&libraries=visualization"></script>
<script src="//code.jquery.com/jquery-1.12.0.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/js/bootstrap.min.js" integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS" crossorigin="anonymous"></script>
<script src="js/toc.min.js"></script>
<script src="js/chartist.min.js"></script>
<script src="js/chartist-plugin-axistitle.min.js"></script>
<script src="js/graphs.js"></script>
<script src="js/main.js"></script>
<script src="js/maps.js"></script>
<!--[if IE]>
<script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body id="index" class="home">
<header id="banner" class="body">
<h1><a href="http://stpierre.github.io/crashes/">Bicycle Collision Analytics (Lincoln, NE) </a></h1>
</header>
<div class="alert alert-success fade in">
<button type="button" class="close" data-dismiss="alert"
aria-label="Close">
<span aria-hidden="true">×</span>
</button>
Many of the graphs on this page are now clickable to get even
more data out of them. Try it out!
</div>
<div id="toc"></div>
<aside id="featured" class="body">
<article>
<footer class="post-info">
<abbr class="published">
Last updated: 2019-05-20 14:51
</abbr>
<address class="vcard author">By Chris St. Pierre</address>
</footer>
<p>In March 2015, I was hit by a car while on my bike in a
bike path crosswalk, and was ticketed for failure to yield
the right of way. I got interested in bicycle safety and, as
a software engineer by trade, I decided to download, parse,
and quantify as much collision data as possible from the
Lincoln Police Department.</p>
<div class="section">
<h2>Interpreting These Data</h2>
In the data below, bike-car collisions are categorized based
on where they happened. The following locations are tracked:
<ul class="simple">
<li><b>Bike Lane</b>: Collision happened while a person on a bicycle was riding in a bike lane, including in an intersection.
</li>
<li><b>Bike Trail</b>: Collision happened while a person on a bicycle was riding on a bike trail, not in an intersection.
</li>
<li><b>Bike Trail Crossing</b>: Collision happened while a person on a bicycle was using a crosswalk between two bike trail segments, or continuing past the end of a bike trail over a crosswalk to the start of a sidewalk. This does not include cyclists crossing perpendicularly to a bike trail, unless they are continuing on another bike trail on the other side.
</li>
<li><b>Crosswalk</b>: Collision happened while a person on a bicycle was using a crosswalk between two sidewalks; that is, attempting to cross a road or intersection either in a painted crosswalk that is not part of a bike trail, or crossing an intersection from one sidewalk to another. This does not include cyclists who are riding on the street and pass through the intersection without using a crosswalk, nor cyclists in a crosswalk that is part of a bike trail.
</li>
<li><b>Elsewhere</b>: Collision happened elsewhere (alleyways, parking lots, etc.). This also includes ride-outs at mid-block and other collisions that happened on the road, but where the cyclist was not riding on the road as such.
</li>
<li><b>Intersection</b>: Collision happened while a person on a bicycle was riding through an intersection on the road, not using a crosswalk. Does not include cyclists who entered the intersection from a bike lane.
</li>
<li><b>Road</b>: Collision happened while a person on a bicycle was riding on the road, excluding intersections.
</li>
<li><b>Sidewalk</b>: Collision happened while a person on a bicycle was riding on a sidewalk that is not a bike trail. For instance, a car entering or leaving a private driveway or, in rare situations, a car that jumps the curb.
</li>
<li><b>Unknown</b>: The police report contained insufficient information to determine where the collision happened; or the collision record came from NDOR and no police report could be located.
</li>
</ul>
<p>There is some inherent difficulty in categorizing certain
types of collisions; for instance, if a cyclist enters a
crosswalk from a sidewalk but, midway through the
intersection leaves the crosswalk, it's impossible to know
if the cyclist was intending to enter the roadway, avoid
an obstacle and continue in the crosswalk, or so on.</p>
</div>
<div class="section">
<h2>Quantitative Results</h2>
<p>The current dataset includes 62,161 reports, from January 15, 2008 to January 3, 2019. Since 2012, when LPD
started widespread use of computer-written accident
reports, the dataset includes 54,308 reports, 868 (1.6%) of which involved a person on a bicycle.</p>
<p>This number is almost certainly an underestimate, for
several reasons:</p>
<ul class="simple">
<li>Not every accident is reported. Non-injury accidents
in particular may not be; anecdotally, I was initially
advised not to file an accident report when I was hit,
since my injuries were very minor.</li>
<li>Accident reports are not written for bicycle-bicycle
or bicycle-pedestrian collisions.</li>
</ul>
<p>Nearly all of the post-2011 reports are from LPD, but
494 reports came from the Nebraska Department
of Roads <i>[sic]</i>
via <a href="http://www.arcgis.com/home/webmap/viewer.html?webmap=76d544b5646645dcaa8e9ba5c5543d0a">Lacey
Matney's 2014 study</a>. All of the data from 2008-2011
is from NDOR.</p>
<p>Because the first four years of data in this dataset is
from NDOR, and includes less data, some of the reports
below only include data from 2012 onward, while others
include data from 2008. I've noted this where it's
relevant.</p>
<p>7369 reports could not be parsed
automatically, largely because they were handwritten. The
years 2012-2014 have been cross-checked against the NDOR
data (which includes handwritten reports), and the handful
of handwritten reports from 2015 have been manually
parsed.</p>
</div>
<div class="section-a">
<h3>Collision locations</h3>
<div class="ct-chart ct-major-seventh left"
id="location-pie-chart"></div>
<div class="right">
<p>The majority of collisions involving a bicycle
(352/868) happened in a
crosswalk.</p>
<p>Large numbers of collisions also involve people riding
in the street, and people riding in sidewalks. (Most
sidewalk accidents involve cars turning into private
drives, but a few featured cars jumping the curb.) A
smattering involves people riding elsewhere, which
includes parking lots, or crossing streets in the middle
of blocks (i.e., away from crosswalks). Collisions in
bike lanes are very rare indeed, but that likely
reflects the rarity of bike lanes more than
anything.</p>
<p>Clearly, crosswalks are far and away the most dangerous
place for cyclists. No matter what other riding patterns
are, cyclists almost certainly spend orders of magnitude
more time out of crosswalks, so more than half the
accidents happening in crosswalks is pretty clearly
damning.</p>
<p>Unfortunately clear data on the number of miles ridden
on streets as compared to sidewalks are not available,
so it's not possible to extrapolate from the data shown
above to conclude whether it's more dangerous to ride in
the street or on the sidewalk. It is worth noting,
though, that 54.1% (470) of the collisions
indicate a pattern of riding on sidewalks, while merely
22.0%
(191) indicate a pattern of riding in the
street.</p>
<p>Unsurprisingly, no collisions were reported on
off-street bike paths. (Recall that these data only
include car-bike accidents; bike-bike and
bike-pedestrian accidents certainly do occur on the
off-street bike paths.)</p>
</div>
</div>
<div class="section-b">
<h3>Locations by age</h3>
<div class="ct-chart-container">
<div class="ct-chart ct-major-twelfth has-legend"
id="location-by-age-line-chart"></div>
<!-- TODO: autogenerate this legend -->
<div class="legend" id="location-by-age-legend">
<div class="ct-series-a">Road</div>
<div class="ct-series-b">Bike Trail Crossing</div>
<div class="ct-series-c">Intersection</div>
<div class="ct-series-d">Sidewalk</div>
<div class="ct-series-e">Bike Trail</div>
<div class="ct-series-f">Bike Lane</div>
<div class="ct-series-g">Unknown</div>
<div class="ct-series-h">Crosswalk</div>
<div class="ct-series-i">Elsewhere</div>
</div>
</div>
<div class="below">
<p>The location of collisions varies slightly by the age of
the cyclist.</p>
<p>Again, though, without data on the number of miles
ridden in various scenarios, it's hard to make much
sense of these data -- especially with such
variable-sized (and often small) data sets. The 51-to-60
set seems to be doing something interesting, though,
with relatively more collisions in intersections and
fewer in crosswalks than most other groups. Perhaps
these cyclists ride on the street more often than
cyclists of other ages.</p>
</div>
</div>
<div class="section-a">
<h3>Monthly collision rate</h3>
<div class="ct-chart-container">
<div class="ct-chart ct-major-twelfth has-legend"
id="monthly-rate-chart"></div>
<div class="legend" id="monthly-rates-legend">
<div class="ct-series-a">Collisions Per Month</div>
<div class="ct-series-c">Monthly Rock Island Riders</div>
<div class="ct-series-e">Collisions Per 1000 Monthly Rock Island Riders</div>
</div>
</div>
<div class="below">
<p>For this chart I've invented a couple of metrics. One
is Monthly Rock Island Riders, or MRIR. The city has had
a bike traffic counter installed on the Rock Island
Trail since July 2014, and it provides our best
estimates of how many people are out riding at any given
time. So while it's a slightly arbitrary number, we
expect that the number of riders on the Rock Island
Trail roughly mirrors the total number of riders in
Lincoln during each month.</p>
<p>Combining the MRIR with the average number of
collisions per month we can see a reasonable estimate of
the collision rate during any given month, measured in
Collisions Per Monthly Rock Island Rider
(CPMRIR). Although the line looks fairly flat, this is a
logarithmic scale so it's anything but -- you're 5.8 times more likely to be
hit in November as in March.</p>
<p>It's not immediately obvious why this tremendous
difference -- or why there's such a peak in November. One possibility might be more
darkness during the commute due to the end of Daylight
Savings Time.</p>
<p>Interestingly, the increase in ridership during the
spring months doesn't track CPMRIR, either. That is, it
doesn't appear that when more cyclists appear on the
streets they're more likely to be hit; instead there
seems to be a novelty effect, where March is quite safe
(relatively speaking) and then collisions go up in April
once drivers are more accustomed to seeing cyclists on
the streets.</p>
<p>Ultimately, for all the fluctuations of the CPMRIR,
collisions per month correlates quite closely with MRIR
(r=0.84), suggesting that
our transportation system is just plain designed to
bring cyclists into inevitable conflict with drivers, no
matter how many of us are on the roads or what time of
year it is.</p>
</div>
</div>
<div class="section-b">
<h3>Average monthly collisions</h3>
<div class="ct-chart ct-major-seventh left"
id="monthly-average-chart"></div>
<div class="right">
<p>Predictably, most accidents by sheer numbers happen
during the summer months, simply because so many people
are riding. January has the fewest collisions, making it
one of the safer months.</p>
</div>
</div>
<div class="section-a">
<h3>Collisions per year</h3>
<div class="left">
<p>It's hard to tell how much of the fluctuation here is
just randomness and how much is a trend; the changes are
rapid and fairly small. We had been on an upward trend
from 2012 through 2016, but we only have bike traffic
count data from 2014 onward so it's hard to tell if that
upward trend is due to increased ridership, or to other
factors. There appears to be a downward trend since 2016,
which could be due to projects like the N street bikeway,
or could just be pure chance.</p>
<p>Mean collisions per year is 122.40
and median collisions is 126.</p>
</div>
<div class="ct-chart ct-major-seventh right"
id="yearly-bar-chart"></div>
</div>
<div class="section-b">
<h3>Collisions per month</h3>
<div class="ct-chart ct-major-twelfth"
id="monthly-line-chart"></div>
<p>January 2010, February 2015, January 2017, January 2019, February 2019, March 2019, April 2019, May 2019 are the only months
without a recorded collision. The most dangerous months in
the data set, with 24, are September 2008, September 2011, September 2016.</p>
</div>
<div class="section-a">
<h3>Hourly collision rate</h3>
<div class="ct-chart-container">
<div class="ct-chart ct-major-twelfth has-legend"
id="hourly-chart"></div>
<div class="legend" id="hourly-rates-legend">
<div class="ct-series-a">Annual Collisions Per Hour</div>
<div class="ct-series-c">Hourly Rock Island Riders</div>
<div class="ct-series-e">Collisions Per Hourly Rock Island Rider</div>
</div>
</div>
<div class="below">
<p>Similar to
the <a href="#toc-monthly-collision-rate">Monthly
Collision Rate</a> graph above, I've invented a few
metrics. First is Hourly Rock Island Riders, which is an
average count of the number of cyclists on the Rock
Island Trail during any given one-hour period.</p>
<p>The other new metric is Annual Collisions Per Hour,
or ACPH. That's the average number of collisions in a
given one-hour time slot that have happened per year
since January 15, 2008.</p>
<p>From these two metrics, we can see that the most
dangerous times in terms of Annual Collisions Per Hourly
Rock Island Rider (ACPHRIR) are the dark hours, followed
distantly by the morning commute. In particular, the
hours between midnight and 4 am are incredibly
dangerous, possibly because the extremely low ridership
numbers then make even the small numbers of collisions
inflate the ACPHRIR.</p>
<p>Although the ACPHRIR rate is lower, most collisions (by
aggregate count) happen during commutes. It's
interesting that more people are hit during the evening
commute -- not the presumably darker morning commute.
There are fare more collisions during the evening
commute, but the morning commute is actually more
dangerous because so many more people are out riding in
the evening -- nearly twice as many as in the
morning.</p>
<p>It's also interesting that we see a steady stream of
cyclists all day long, but collisions drop off sharply
outside of commutes. It seems likely that this is due to
the number of drivers out (and possibly their perceived
urgency). Initial results (below) indicate that darkness
has a limited effect on the number of collisions.</p>
<p>Despite the spikiness of the ACPH, it correlates quite
well with HRIR (r=0.89), so
the number of cyclists out has a significant effect on
the number of collisions. This is a stronger correlation
than we see on
the <a href="#toc-monthly-collision-rate">Monthly
Collision Rate</a> graph, so time of day has even less
to do with the rate of collisions than time of year.</p>
<p>Note that this graph uses a logarithmic (base 2) Y
axis.</p>
</div>
</div>
<div class="section-b">
<h3>Collision rate by position of sun</h3>
<div class="ct-chart ct-major-tenth left"
id="daylight-rate-chart"></div>
<div class="right">
<p>Here we see that the collision rate is *much* higher
at night that during other times -- and that it's much
<i>lower</i> during times of dim light. This was pretty
unexpected, given how closely collision rates track
ridership in other cases; I didn't expect nighttime to
be that much more dangerous. It's probably a <i>bit</i>
misleading, due to the presence of the incredibly low
dusk and dawn bars; ultimately riding at night is only
1.8 times more dangerous than riding
during the day.</p>
<p>Dusk and dawn are also pretty interesting. It turns out
that dusk is safe because there are huge numbers of
cyclists out -- that evening commute is incredibly
busy. So even though it has a much higher number of
collisions than dawn, it's the safest phase of the
day.</p>
<p>Dusk and dawn may also be thrown off a bit by the
limited amounts of data available; they're each only
about 30 minutes long, while the other two phases of the
day make up the remainder, so we have much more data
about day and night.</p>
</div>
</div>
<div class="section-a">
<h3>Proportion of collisions by position of sun</h3>
<div class="ct-chart ct-major-tenth left"
id="daylight-pie-chart"></div>
<div class="right">
<p>The vast majority of collisions happen during the day,
simply because so many riders are out then.</p>
</div>
</div>
<div class="section-b">
<h3>Collisions by position of sun and by month</h3>
<div class="ct-chart-container">
<div class="ct-chart ct-major-twelfth has-legend"
id="daylight-line-chart"></div>
<!-- TODO: autogenerate this legend -->
<div class="legend" id="daylight-line-chart-legend">
<div class="ct-series-a">Night</div>
<div class="ct-series-b">Dawn</div>
<div class="ct-series-c">Dusk</div>
<div class="ct-series-d">Day</div>
<div class="ct-series-e">Hours of daylight</div>
</div>
</div>
<div class="below">
<p>More collisions happen at night during the winter
months, but that's probably because there's just more
night. The rate of daytime collisions correlates quite
strongly with the hours of daylight per day (r=0.88), but not as strongly
as with the number of cyclists out.</p>
<p>In other words, lack of visibility is a factor in the
collision rate, but a greater factor is the simple
presence of bikes. This aligns with
the <a href="#toc-collision-rate-by-position-of-sun">earlier
finding</a> that riding at night is more dangerous than
during the day, but not a whole lot. Drivers are almost
as good at not seeing people on bikes in the middle of
the day as they are in the darkest night. (Or maybe our
transportation systems are designed to make collisions
inevitable, regardless of whether it's day or
night.)</p>
</div>
</div>
<div class="section-a">
<h3>Collisions by age of cyclist</h3>
<div class="ct-chart ct-major-seventh left"
id="ages-bar-chart"></div>
<div class="right">
<p>Just so we're clear, that's about
8 children under 11 hit by
cars every year in Lincoln alone.</p>
<p>I suspect that this may just be a graph of ridership
numbers. There's a dropoff at 16, when kids get their
driver's license, but it goes back up for the college
age crowd; then a slow descent to 40, after which it
picks up again, presumably with the MAMIL crowd.</p>
<p>But seriously, over 31% of people hit on bikes in Lincoln
are <i>children</i>.</p>
<p>We only have age data for cyclists injured since 2011,
but given that 93.9% of cyclists in collisions are injured,
it's still a pretty broad sample.</p>
</div>
</div>
<div class="section-b">
<h3>Collisions by gender of cyclist</h3>
<div class="left">
<p>Men are apparently over-represented, but this again
might just be a graph of ridership numbers. These line
up with national figures on ridership; People For Bikes
reports that
<a href="http://www.peopleforbikes.org/statistics/category/participation-statistics">about
24% of bike trips nationally are taken by women</a>
(based on a 2009 study). Compared to other small cities,
though, if this <i>is</i> a chart of ridership numbers,
Lincoln seems to have a fairly high number of women
riding.</p>
<p>This uses LPD's reporting of the gender of injured
cyclists; the gender of uninjured cyclists is not
reliably recorded. The "Unknown" category represents
only those cyclists who were uninjured. LPD uses a
purely bivalent gendering system, so trans and nonbinary
people may be misgendered in this graph.</p>
</div>
<div class="ct-chart ct-major-seventh right"
id="gender-pie-chart"></div>
</div>
<div class="section-a">
<h3>Injuries by collision location</h3>
<div class="left">
<p>Interestingly, different locations have different
injury rates.</p>
<p>Sidewalks have one of the highest injury rates, but
also the most non-disabling injuries. Collisions
occurring in dedicated bike infrastructure -- bike lanes
and trail crossings -- are the least likely to lead to
injuries. Collisions on the road and in intersections
generally show more disabling injuries. (Collisions on
bike trails *away from* intersections also show a lot of
disabling injuries, but that's due to the extremely
small sample size.)</p>
<p>Note that these data are based entirely on accident
reports, and so do not take into account cyclists who
are hit and later killed; the "Killed" category only
represents cyclists who were dead at the scene.</p>
<p>Non-injury collisions are the most likely collisions to
not be reported, so all of the injury rates are
hopefully overestimates.</p>
</div>
<div class="ct-chart-container right">
<div class="ct-chart ct-major-sixth has-legend"
id="injury-rates-bar-chart"></div>
<div class="legend" id="injury-rates-legend">
<div class="ct-series-a">Killed</div>
<div class="ct-series-b">Disabling</div>
<div class="ct-series-c">Visible but not disabling</div>
<div class="ct-series-d">Possible but not visible</div>
</div>
</div>
</div>
<div class="section-b">
<h3>Injury severities</h3>
<div class="ct-chart ct-major-seventh left"
id="injury-severity-pie-chart"></div>
<div class="right">
<p>Overall, while disabling injuries are scary, they
represent a fairly small percentage of collisions. That
said, it's still worrisome that a cyclist is about as
likely to escape a collision unscathed as to suffer
disabling injury.</p>
</div>
</div>
<div class="section-a">
<h3>Body region of injuries</h3>
<div class="left">
<p>Predictably, injuries are most common to the
extremities, particularly the lower legs.</p>
</div>
<div class="ct-chart ct-major-seventh right"
id="injury-region-pie-chart"></div>
</div>
<div class="section-b">
<h3>Hit-and-runs</h3>
<div class="ct-chart ct-major-seventh left"
id="hit-and-run-pie-chart"></div>
<div class="right">
<p>Of the 868 collisions,
162 (18.7%) were categorized as
hit-and-runs by LPD. In 10 cases, either both the
driver and cyclist left the scene, or it couldn't be
easily determined who left the scene. In the remaining
152 cases, the driver fled the scene the vast
majority of times -- 128
times, or 84.2% of remaining cases.</p>
<p>Overall, in 14.7% of <i>all</i> bike-car
collisions the driver fled the scene. If you are hit,
make sure to immediately get license plate numbers!</p>
<p>I'm not sure what LPD counts as a "hit-and-run"; for
example, <a href="http://cjis.lincoln.ne.gov/~ACC/B611/B6118033.PDF" class="reference external">case
no. B6-118033</a> sure sounds like a hit-and-run to me,
but LPD didn't count it as such despite the fact that a
driver hit a cyclist, left the scene, wasn't contacted
by LPD until the following day, and the officer
"explained to [the driver] that if that happens again to
just stay at the scene."</p>
<p>Or, say, <a href="http://cjis.lincoln.ne.gov/~ACC/B803/B8038226.PDF" class="reference external">B8-038226</a>, in
which the "Driver of V1 did not exit the vehicle and
drove off without stopping," and at the time of the
report the vehicle (and, presumably, its driver) was
still "unknown" -- but somehow was also not a
hit-and-run.</p>
</div>
</div>
<div class="section-a">
<h2>Heatmap of Collisions</h2>
<div class="map-container">
<div class="map-canvas" id="heatmap-canvas"></div>
</div>
<p>Luckily, there's not <i>too much</i> red on this
map. While we're unlikely to avoid any particular
intersection based simply on the number of collisions
there, we can be more careful at the more dangerous
intersections. Some of the most dangerous intersections
are at or near bike path underpasses or overpasses, so you
can avoid crossing 27th at Vine, for instance, on the
Mopac Trail.</p>
<p>Some intersections may seem more dangerous solely because
they are more heavily trafficked, not because they are
actually more dangerous. That said, a few corridors seem
particularly dangerous, with 27th street from Vine to
Holdrege leading the pack. Capital Parkway/Normal Blvd. is
a close second; the intersections with 27th, 33rd, and
South are all among the most dangerous in the city.</p>
<p>As an aside, can you imagine what an on-street bike lane
would do to help out north 27th street and South street
between 13th and 27th? Both are struggling but viable
commercial districts that are already lined with local
businesses, and they have terrific numbers of car-bike
collisions.</p>
</div>
<div class="section-b">
<h2>Map of Collisions</h2>
<p>All locations should be considered approximations, and
there are almost certainly mistakes in places.</p>
<div class="map-container">
<div class="map-canvas" id="all-collisions-map-canvas"></div>
</div>
<button class="map-buttons current" map-layer="crosswalk">
<img src="http://www.googlemapsmarkers.com/v1/C/FF9900/"
alt="Crosswalk marker"> Crosswalk</button>
<button class="map-buttons current" map-layer="sidewalk">
<img src="http://www.googlemapsmarkers.com/v1/S/FFFF66/"
alt="Sidewalk marker"> Sidewalk</button>
<button class="map-buttons current" map-layer="road">
<img src="http://www.googlemapsmarkers.com/v1/R/009900/"
alt="Road marker"> Road</button>
<button class="map-buttons current" map-layer="intersection">
<img src="http://www.googlemapsmarkers.com/v1/I/0099FF/"
alt="Intersection marker"> Intersection</button>
<button class="map-buttons current" map-layer="bike_lane">
<img src="http://www.googlemapsmarkers.com/v1/L/990000/"
alt="Bike lane marker"> Bike Lane</button>
<button class="map-buttons current" map-layer="bike_trail_crossing">
<img src="http://www.googlemapsmarkers.com/v1/T/6600FF/"
alt="Bike trail crossing marker"> Bike Trail Crossing</button>
<button class="map-buttons current" map-layer="bike_lane">
<img src="http://www.googlemapsmarkers.com/v1/B/00FF66/"
alt="Bike trail marker"> Bike Trail</button>
<button class="map-buttons current" map-layer="elsewhere">
<img src="http://www.googlemapsmarkers.com/v1/E/CC33FF"
alt="Elsewhere marker"> Elsewhere</button>
<button class="map-buttons current" map-layer="unknown">
<img src="http://www.googlemapsmarkers.com/v1/U/33FFCC"
alt="Unknown marker"> Unknown</button>
<p>This gives us some granular detail to see where
collisions are happening around town. For instance, we
knew Capitol Parkway and 27th had lots collisions, but
here we can see that they were all in crosswalks.</p>
<p>In general, collisions increase towards downtown and
diminish as you get further out. There are two notable
exceptions: The entire length of 84th street (with nearly
twice as many crosswalk collisions as 70th and 56th
streets); and Pine Lake near 27th. These two areas have
something in common: Bike paths adjacent to streets, where
cyclists must still cross many side streets. Superior
street, which also has a street-adjacent bike path, has no
nearby analogue to compare it to, but it has as many
crosswalk collisions as Havelock, Fremont, and Holdrege
combined.</p>
<p>A significant number of crosswalk and sidewalk collisions
occur in the downtown exclusion area. Stop riding on the
sidewalks downtown already! It's not even safer! (It also
could <a href="http://cjis.lincoln.ne.gov/~ACC/B604/B6045945.PDF" class="reference external">get you a ticket</a>.)
Road collisions, predictably, are focused downtown. But at
least riding on the streets is legal.</p>
</div>
<div class="section">
<h2>Qualitative Results</h2>
<p>A number of interesting trends revealed themselves in
reading through the reports. Most disturbingly, at least
some members of LPD have a significant misunderstanding of
the law, claiming in the
<a href="http://cjis.lincoln.ne.gov/~ACC/B306/B3063805.PDF" class="reference external">accident</a>
<a href="http://cjis.lincoln.ne.gov/~ACC/B405/B4050934.PDF" class="reference external">report</a> that
<a href="http://cjis.lincoln.ne.gov/~ACC/B408/B4085278.PDF" class="reference external">cyclists are required</a> to
walk their bike across intersections, and
<a href="http://cjis.lincoln.ne.gov/~ACC/B410/B4107448.PDF" class="reference external">in some cases</a> specifically
<a href="http://cjis.lincoln.ne.gov/~ACC/B507/B5074595.PDF" class="reference external">noting</a> that they
"<a href="http://cjis.lincoln.ne.gov/~ACC/B310/B3104457.PDF" class="reference external">lectured</a>" the cyclist.</p>
<p>Even after LB716 took effect, cops were still
<a href="http://cjis.lincoln.ne.gov/~ACC/B607/B6073532.PDF" class="reference external">lecturing cyclists</a> about
<a href="http://cjis.lincoln.ne.gov/~ACC/B608/B6086968.PDF" class="reference external">walking</a> across
<a href="http://cjis.lincoln.ne.gov/~ACC/B609/B6093266.PDF" class="reference external">sidewalks</a>, and noting in
reports that the cyclist <a href="http://cjis.lincoln.ne.gov/~ACC/B804/B8043384.PDF" class="reference external">did
not "dismount from the bicycle"</a>. (In
<a href="http://cjis.lincoln.ne.gov/~ACC/B804/B8043384.PDF" class="reference external">that report</a>, the officer
also coded "No improper driving" for driver error and
"Improper crossing" for cyclist error.) One officer even
<a href="http://cjis.lincoln.ne.gov/~ACC/B808/B8087221.PDF" class="reference external">cited an unrelated state
statute</a> that he apparently believed prevented cyclists
from riding through an intersection.</p>
<p>In other (fewer) <a href="http://cjis.lincoln.ne.gov/~ACC/B309/B3096911.PDF" class="reference external">cases</a>,
the officer had a <a href="http://cjis.lincoln.ne.gov/~ACC/B406/B4063856.PDF" class="reference external">correct
understanding</a> of the law, and
"<a href="http://cjis.lincoln.ne.gov/~ACC/B511/B5112375.PDF" class="reference external">educate</a>" the cyclist; and
in some cases <a href="http://cjis.lincoln.ne.gov/~ACC/B304/B3042103.PDF" class="reference external">the driver of the
car was ticketed</a> for
<a href="http://cjis.lincoln.ne.gov/~ACC/B206/B2062920.PDF" class="reference external">failure to yield</a> to a
cyclist in a crosswalk.</p>
<p>In <a href="http://cjis.lincoln.ne.gov/~ACC/B805/B8059374.PDF" class="reference external">one case</a>, it's not
clear who knows the law and who doesn't. That case report
notes that "the bicyclist thought all bicycles had the
right of way [when] crossing in the non marked crosswalk
area," and she was correct. It seems that the only reason
the officer would mention that is if they disagreed, which
seems to be the case as there were "no citations
issued."</p>
<p>The law for crossing private drives is less clear, but
<a href="http://cjis.lincoln.ne.gov/~ACC/B210/B2106960.PDF" class="reference external">at least one cop</a> thinks
that bikes on sidewalks must yield to cars in driveways,
while <a href="http://cjis.lincoln.ne.gov/~ACC/B509/B5099464.PDF" class="reference external">another one
disagrees</a>. One cop <a href="http://cjis.lincoln.ne.gov/~ACC/B605/B6050106.PDF" class="reference external">lectured
a cyclist</a> who collided with a car in a private drive,
even though the accident report states that the view was
blocked. I guess you should leave the Oakleys at home and
wear your X-ray glasses.</p>
<p>Some officers may not really have a good understanding of
right of way at all;
in <a href="http://cjis.lincoln.ne.gov/~ACC/B703/B7033773.PDF"
class="reference external">one case</a>, a motorist was
cited for running a stop sign and hitting a child on a
bike, but the <i>cyclist</i> was "educated/lectured about
yielding right of way," which is apparently something that
all cyclists owe all drivers regardless of the actual
rules of the road.</p>
<p>Perhaps ironically, in <a href="http://cjis.lincoln.ne.gov/~ACC/B405/B4055506.PDF" class="reference external">one
case</a> a cyclist who had dismounted to walk his bike
across the intersection was hit while on foot.</p>
<p>If you get right-hooked by a driver who just can't wait
three seconds for a parking space, you might just
<a href="http://cjis.lincoln.ne.gov/~ACC/B209/B2092954.PDF" class="reference external">wind up with a ticket
yourself</a> for "violating general traffic laws." Which
laws? Well, general ones, of course.</p>
<p>In some cases, the accident report
<a href="http://cjis.lincoln.ne.gov/~ACC/B304/B3046597.PDF" class="reference external">mentions</a> that the cyclist
<a href="http://cjis.lincoln.ne.gov/~ACC/B403/B4032910.PDF" class="reference external">was not wearing</a> a
<a href="http://cjis.lincoln.ne.gov/~ACC/B702/B7025699.PDF" class="reference external">helmet</a>, despite the fact
that this has absolutely no legal bearing, nor does it
have any bearing on whether or not a cyclist is hit. It's
hard to see this as anything other than editorial
victim-blaming. In another case the fact that cyclists
*were* <a href="http://cjis.lincoln.ne.gov/~ACC/B510/B5102671.PDF" class="reference external">wearing helmets and
reflective clothing</a> is mentioned; although the
reflective clothing has a clear bearing on their
visibility, helmet use again seems to be mentioned simply
as part of a false correlation with "proper" cycling.</p>
<p>A <a href="http://cjis.lincoln.ne.gov/~ACC/B304/B3049103.PDF" class="reference external">number</a> of accident
reports reverse the agents, claiming that
<a href="http://cjis.lincoln.ne.gov/~ACC/B406/B4065578.PDF" class="reference external">a bike hit a car</a> in cases
where the car clearly hit the bike. In some cases, it's
described <a href="http://cjis.lincoln.ne.gov/~ACC/B403/B4034454.PDF" class="reference external">both ways</a>. It's
not clear why this inversion of causality occurs.</p>
<p>Some people, upon hitting a ten-year-old child, can think
of nothing better to do than
<a href="http://cjis.lincoln.ne.gov/~ACC/B604/B6043838.PDF" class="reference external">yell at the kid about
right-of-way</a> and drive away.</p>
<p>In some cases, bicyclists
"<a href="http://cjis.lincoln.ne.gov/~ACC/B201/B2019522.PDF" class="reference external">suddenly appear</a>". Stop
<a href="http://cjis.lincoln.ne.gov/~ACC/B306/B3063032.PDF" class="reference external">apparating</a> in public or the
muggles will catch on! (Strangely, the accident reports
where cyclists <a href="http://cjis.lincoln.ne.gov/~ACC/B508/B5081151.PDF" class="reference external">appear</a> show
the bike moving through space normally, not
teleporting.)</p>
<p>The only place <a href="http://cjis.lincoln.ne.gov/~ACC/B205/B2057557.PDF" class="reference external">two</a>
"elsewhere" <a href="http://cjis.lincoln.ne.gov/~ACC/B302/B3023161.PDF" class="reference external">collisions</a>
occurred is on 27th street, just south of Highway 2, where
there's a cutout of the median to let train tracks cross
27th street. People are crossing a busy arterial street
with no crosswalk along train tracks -- with a pedestrian
bridge overhead. Please don't be dumb.</p>
<p>Don't <a href="http://cjis.lincoln.ne.gov/~ACC/B511/B5114253.PDF" class="reference external">ride like a dingus</a>.</p>
<p><a href="http://cjis.lincoln.ne.gov/~ACC/B207/B2072693.PDF" class="reference external">Please</a>,
<a href="http://cjis.lincoln.ne.gov/~ACC/B404/B4049988.PDF" class="reference external">get information</a> from a
<a href="http://cjis.lincoln.ne.gov/~ACC/B207/B2072693.PDF" class="reference external">driver</a> who
<a href="http://cjis.lincoln.ne.gov/~ACC/B409/B4090913.PDF" class="reference external">hits
you</a>. <a href="http://cjis.lincoln.ne.gov/~ACC/B206/B2065976.PDF" class="reference external">Call the police.</a>
<a href="http://cjis.lincoln.ne.gov/~ACC/B304/B3047233.PDF" class="reference external">File a report.</a></p>
<p>If you <a href="http://cjis.lincoln.ne.gov/~ACC/B508/B5086728.PDF" class="reference external">don't have brakes on
your bike</a>, <b>get some</b>. If you can't afford them,
visit the
incredible <a href="http://www.lincolnbikekitchen.org/">Lincoln
Bike Kitchen</a>. If you can afford an extra pair,
please <a href="http://www.lincolnbikekitchen.org/donate.html">donate</a>
to the Bike Kitchen.</p>
</div>
<div class="section">
<h2>Methodology</h2>
<p>Accident reports are downloaded automatically from the
<a href="https://lincoln.ne.gov/city/police/stats/acc.htm"
class="reference external">Lincoln Police Department's
website</a>. The reports are parsed automatically and
selected data are extracted. The data are available as
CSV files at <a href="data/db_dump" class="reference
external">data/db_dump</a>.
<p>These reports are then curated by hand to determine where
the collision happened, as described above. This depends
on the accuracy of the accident report; anecdotally,
several cyclists have reported to me that their accident
reports were not completely accurate. I found one accident
report where the <a href="http://cjis.lincoln.ne.gov/~ACC/B307/B3074762.PDF" class="reference external">drawing does
not look like the actual intersection</a> where the
collision happened, so there are definitely at least some
inaccuracies. These inaccuracies are not expected to be
significant, but there's no obvious way to test this with
the given data set.</p>
<p>Much of the methodology is described in more detail in the
<a href="https://github.com/stpierre/crashes/blob/master/README.rst"
class="reference external">README</a>. All of the code
used to generate this report is free and open source
under the
<a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html"
class="reference external">GPLv2</a>.</p>
<p>I have made no effort at all to determine fault, as that
process would be fraught beyond any semblance of
reason.</p>
<p>The Lincoln Police Department deserves special thanks for
their open records. In the other two largest cities in
Nebraska, the Omaha and Grand Island Police Departments
both charge for accident reports ($5 and $6,
respectively), and the Omaha Police Department does not
allow listing accident reports. Lincoln's open records
made this project possible.</p>
</div>
<div class="section">
<h2>Further Study</h2>
<p>Classifying each collision according to the U.S. DOT
classification system would let us compare data with other
cities that have published their data, and see how Lincoln
stacks up.</p>
<p>It could be interesting to look at how tickets are
assigned during collisions and see how likely drivers
and/or cyclists are likely to be ticketed.</p>
<p>Current traffic data is based only on the Rock Island
Trail, but the city has other traffic counters and they've
generously shared the data with me. I need to find a way
to normalize it all to get a general traffic rate for the
city based on more than just the Rock Island Trail.</p>
</div>
<div class="section">
<h2>Links</h2>
<ul class="simple">
<li><a href="https://one.nhtsa.gov/nhtsa/stateCatalog/states/ne/docs/Nebraska_PAR_Instruction_Manual_2009_sub12_22_09.pdf">Comprehensive
guide to LPD Accident Reports</a>. There are lots of
little arcane notations all over the accident report;
this tells you what they all mean. Many of them are
demonstrably wrong on many accident reports.</a>
<li><a href="http://www.arcgis.com/home/webmap/viewer.html?webmap=76d544b5646645dcaa8e9ba5c5543d0a">GIS
maps of statewide data on collisions involving
cyclists and pedestrians, 2008-2014</a>. Part of a UNO
masters thesis. The data in this study came from the
Nebraska Department of Roads, and is incomplete
compared to the LPD accident reports, but it covers
the entire state. The NDOR data from this study has
been merged into the data used on this page.</li>
<li><a href="http://www.transportation.nebraska.gov/highway-safety/"
class="reference external">Official Nebraska
Department of Roads Crash Data</a>. Monthly and
yearly summaries with lots of aggregate crash data,
but little in the way of bicycle-specific
data.</li>
<li><a href="https://lincoln.ne.gov/city/plan/reports/GapAnalysis.pdf"
class="reference external">Lincoln Complete Streets
Gap Analysis</a>. Information about Lincoln's bike
trail network, including a collision heat map (page
14) of 1,655 bike-car collisions.</li>
<li><a href="http://www.nebike.org/laws/" class="reference
external">Nebraska Bike Laws</a>, courtesy of the
Nebraska Bicycling Alliance.</li>
<li><a href="http://www.citylab.com/navigator/2015/05/what-to-do-when-youre-hit-by-a-car/393809/"
class="reference external">What to do when you're
hit by a car</a> (and have the time, money, and
presence of mind to handle it the best way).</li>
<li><a href="http://grist.org/living/what-to-do-if-youre-hit-by-a-car-while-riding-your-bike/"
class="reference external">What to do if you're hit
by a car while riding your bike</a>. A little more
pragmatic.</li>
<li><a href="http://www.peopleforbikes.org/statistics/">People
for Bikes' Statistics Library</a></li>
<li><a href="http://www.bicyclinglife.com/Library/riskfactors.htm">Risk
Factors for Bicycle-Motor Vehicle Collisions at
Intersections</a>. A similar (but much larger and more
rigorous) study of police reports in Palo Alto.</li>
<li><a href="http://www.sharetheroad.ca/what-are-the-dangers-in-terms-of-cycling-safety--p128277">What
are the Dangers in Terms of Cycling Safety?</a>
Excellent international data on cycling risks.</li>
</ul>
</div>
<div class="section">
<h3>Media coverage of this report</h3>
<ul class="Simple">
<li><a href="http://journalstar.com/news/local/cindy-lange-kubick-cars-and-bikes-and-navigating-lincoln-from/article_3a705d1a-cc0c-5df4-b8d1-4b867d26acd0.html">Cars
and bikes navigating Lincoln from one computer nerd to
the rest of us</a>, Cindy Lange-Kubick, Lincoln
Journal-Star</li>
<li><a href="http://www.klkntv.com/story/29233856/lincoln-man-creates-website-to-advocate-bike-safety">Lincoln
man creates website to advocate bike safety</a>,
Marlenia Thornton, KLKN-TV</li>
<li><a href="http://www.dailynebraskan.com/news/injured-bicyclist-creates-webpage-on-bike-crash-data/article_ea4db40a-7782-11e5-ad4d-93738956dab0.html">Injured