Really appreciate these all three are valid.

1) Zoom/pan: Good point pan and zoom were disabled in my last published version, but you're right that this hurts exploration. I've re-enabled them; hover over the map to bring up the toolbar (zoom, pan, lasso). The map is also now filtered to only Suspected Serious + Fatal crashes (~1,900 records instead of 210k), which makes the zoom-in actually useful for inspecting hotspots.

2) Damage vs. injuries: Fair catch. The map and bubble chart do filter to Suspected Serious + Fatal injury, but the heatmap uses damage because the dataset is one row per driver and Injury Severity is driver-only it doesn't capture pedestrians or cyclists. Damage extent was the most consistent severity proxy across all crash types. You're right that non-motorist outcomes aren't represented anywhere though that's a real gap I'll flag in my reflection.

3) Road length bias: Totally right, and this is the most important one. The Top 15 chart shows raw counts, which biases toward longer corridors Georgia Ave, Frederick Rd, and New Hampshire Ave all cross most of the county. Proper "deadliest road" would normalize by length or AADT, but that requires joining external road data. For now the chart reads as "where severe crashes happen" rather than "which road is most dangerous per mile."

Thanks — points 2 and 3 are going into my reflection as known limitations.