<?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: 2009 bike count numbers released</title>
	<atom:link href="http://tucsonvelo.com/news/2009-bike-count/feed" rel="self" type="application/rss+xml" />
	<link>http://tucsonvelo.com/news/2009-bike-count/272</link>
	<description>Covering Tucson&#039;s bike community</description>
	<lastBuildDate>Sat, 04 Feb 2012 02:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Red Star</title>
		<link>http://tucsonvelo.com/news/2009-bike-count/272/comment-page-1#comment-111</link>
		<dc:creator>Red Star</dc:creator>
		<pubDate>Fri, 05 Feb 2010 21:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://tucsonvelo.com/?p=272#comment-111</guid>
		<description>Anyway, it seems &quot;hard&quot; (hard as in fairly costly and disruptive activities that involve building things) infrastructure improvements such as those described here:

http://dot.ci.tucson.az.us/traffic3/tspedestrian.php

should be placed in 85705 and 85719 zip codes or something matching up with &quot;Top15 Cyclist Locations.&quot;

Perhaps future studies will put less emphasis on duh macro things that transpo planners have long known and focus instead on where, precisely, to put them...

Yes, of course, there is the adverse economic and fiscal environment at play.</description>
		<content:encoded><![CDATA[<p>Anyway, it seems &#8220;hard&#8221; (hard as in fairly costly and disruptive activities that involve building things) infrastructure improvements such as those described here:</p>
<p><a href="http://dot.ci.tucson.az.us/traffic3/tspedestrian.php" rel="nofollow">http://dot.ci.tucson.az.us/traffic3/tspedestrian.php</a></p>
<p>should be placed in 85705 and 85719 zip codes or something matching up with &#8220;Top15 Cyclist Locations.&#8221;</p>
<p>Perhaps future studies will put less emphasis on duh macro things that transpo planners have long known and focus instead on where, precisely, to put them&#8230;</p>
<p>Yes, of course, there is the adverse economic and fiscal environment at play.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Star</title>
		<link>http://tucsonvelo.com/news/2009-bike-count/272/comment-page-1#comment-106</link>
		<dc:creator>Red Star</dc:creator>
		<pubDate>Thu, 04 Feb 2010 21:43:27 +0000</pubDate>
		<guid isPermaLink="false">http://tucsonvelo.com/?p=272#comment-106</guid>
		<description>The study has value in that it confirms what is intuitive and generally accepted by planners:  when it comes to cycling, usage is highest in densely populated areas that have relatively low incomes and rate relatively high on resident turnover. This finding pretty much holds true when it comes to mass transit/public transit (the bus, light rail).  It&#039;s a pretty robust and stable conclusion. Citing the study, the zip codes 85719 and 85705 would seem to be where the demand is,  in the context of getting the most bang for the public buck,  so to speak. One could parse the data further by census block, but there&#039;s really no point.</description>
		<content:encoded><![CDATA[<p>The study has value in that it confirms what is intuitive and generally accepted by planners:  when it comes to cycling, usage is highest in densely populated areas that have relatively low incomes and rate relatively high on resident turnover. This finding pretty much holds true when it comes to mass transit/public transit (the bus, light rail).  It&#8217;s a pretty robust and stable conclusion. Citing the study, the zip codes 85719 and 85705 would seem to be where the demand is,  in the context of getting the most bang for the public buck,  so to speak. One could parse the data further by census block, but there&#8217;s really no point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

