<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Understanding Collision Summaries</title>
	<atom:link href="http://azbikelaw.org/blog/understanding-collision-summaries/feed/" rel="self" type="application/rss+xml" />
	<link>http://azbikelaw.org/blog/understanding-collision-summaries/</link>
	<description>Cycling, traffic safety and legal topics; energy, transit and transportion economics</description>
	<lastBuildDate>Tue, 22 May 2012 22:26:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: ADOT&#8217;s Bicycle Safety Action Plan Study @ Arizona Bike Law Blog</title>
		<link>http://azbikelaw.org/blog/understanding-collision-summaries/comment-page-1/#comment-10045</link>
		<dc:creator>ADOT&#8217;s Bicycle Safety Action Plan Study @ Arizona Bike Law Blog</dc:creator>
		<pubDate>Sat, 17 Sep 2011 21:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://azbikelaw.org/blog/understanding-collision-summaries/#comment-10045</guid>
		<description>[...] crash investigations that tends to wrongly faults cyclists who are doing nothing illegal (see Understanding Collision Summaries) &#8212; this is statistical proof of poor-quality investigations are a statewide problem for [...]</description>
		<content:encoded><![CDATA[<p>[...] crash investigations that tends to wrongly faults cyclists who are doing nothing illegal (see Understanding Collision Summaries) &#8212; this is statistical proof of poor-quality investigations are a statewide problem for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Listening to Phoenix&#8217;s Bicycle Collision Summary @ Arizona Bike Law Blog</title>
		<link>http://azbikelaw.org/blog/understanding-collision-summaries/comment-page-1/#comment-7828</link>
		<dc:creator>Listening to Phoenix&#8217;s Bicycle Collision Summary @ Arizona Bike Law Blog</dc:creator>
		<pubDate>Sun, 24 Apr 2011 21:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://azbikelaw.org/blog/understanding-collision-summaries/#comment-7828</guid>
		<description>[...] Phoenix, and many other entities issue a report, usually called something like a Bicyclist Collision Summary. For some background, complaints, and links to others, see Understanding Collision Summaries. [...]</description>
		<content:encoded><![CDATA[<p>[...] Phoenix, and many other entities issue a report, usually called something like a Bicyclist Collision Summary. For some background, complaints, and links to others, see Understanding Collision Summaries. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phoenix marks first year of light rail @ Arizona Bike Law Blog</title>
		<link>http://azbikelaw.org/blog/understanding-collision-summaries/comment-page-1/#comment-2357</link>
		<dc:creator>Phoenix marks first year of light rail @ Arizona Bike Law Blog</dc:creator>
		<pubDate>Sun, 27 Dec 2009 18:02:47 +0000</pubDate>
		<guid isPermaLink="false">http://azbikelaw.org/blog/understanding-collision-summaries/#comment-2357</guid>
		<description>[...] fault, is ~ 50 collisions significant? Nobody says. Keep in mind that Phoenix PD investigates ~ twenty thousand motor vehicle collisions per year.   [...]</description>
		<content:encoded><![CDATA[<p>[...] fault, is ~ 50 collisions significant? Nobody says. Keep in mind that Phoenix PD investigates ~ twenty thousand motor vehicle collisions per year.   [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Crash Forms / ALISS database @ Arizona Bike Law Blog</title>
		<link>http://azbikelaw.org/blog/understanding-collision-summaries/comment-page-1/#comment-2218</link>
		<dc:creator>New Crash Forms / ALISS database @ Arizona Bike Law Blog</dc:creator>
		<pubDate>Mon, 23 Nov 2009 22:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://azbikelaw.org/blog/understanding-collision-summaries/#comment-2218</guid>
		<description>[...] see also, Understanding Collision Summaries. [...]</description>
		<content:encoded><![CDATA[<p>[...] see also, Understanding Collision Summaries. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pre-preliminary 2009 Fatality Report @ Arizona Bike Law Blog</title>
		<link>http://azbikelaw.org/blog/understanding-collision-summaries/comment-page-1/#comment-2200</link>
		<dc:creator>Pre-preliminary 2009 Fatality Report @ Arizona Bike Law Blog</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://azbikelaw.org/blog/understanding-collision-summaries/#comment-2200</guid>
		<description>[...] I have become increasingly frustrated by what seems to me to be short-shrift paid to analysis of serious injury/fatality, as opposed to simply tallying every collision together. For example, in the Phoenix Collision summary, there are only two breakdowns in this regard: by time of day, and helmet usage. ( The Phoenix and ADOT reports are linked here). [...]</description>
		<content:encoded><![CDATA[<p>[...] I have become increasingly frustrated by what seems to me to be short-shrift paid to analysis of serious injury/fatality, as opposed to simply tallying every collision together. For example, in the Phoenix Collision summary, there are only two breakdowns in this regard: by time of day, and helmet usage. ( The Phoenix and ADOT reports are linked here). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Who&#8217;s Responsible? @ Arizona Bike Law Blog</title>
		<link>http://azbikelaw.org/blog/understanding-collision-summaries/comment-page-1/#comment-1863</link>
		<dc:creator>Who&#8217;s Responsible? @ Arizona Bike Law Blog</dc:creator>
		<pubDate>Thu, 03 Sep 2009 17:16:41 +0000</pubDate>
		<guid isPermaLink="false">http://azbikelaw.org/blog/understanding-collision-summaries/#comment-1863</guid>
		<description>[...] be a lot higher than is generally appreciated. I&#8217;ve grappled with this a little bit before in Understanding Collision Summaries, where I pointed out an inexplicably high proportion of  &#8220;other&#8221; violations assigned [...]</description>
		<content:encoded><![CDATA[<p>[...] be a lot higher than is generally appreciated. I&#8217;ve grappled with this a little bit before in Understanding Collision Summaries, where I pointed out an inexplicably high proportion of  &#8220;other&#8221; violations assigned [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

