<?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: METRO tracks down improved technology for trains</title>
	<atom:link href="http://lightrailblogger.com/2009/09/01/metro-tracks-down-improved-technology-for-trains/feed/" rel="self" type="application/rss+xml" />
	<link>http://lightrailblogger.com/2009/09/01/metro-tracks-down-improved-technology-for-trains/</link>
	<description>METRO light rail and the car-free experience in downtown Phoenix</description>
	<lastBuildDate>Tue, 09 Nov 2010 05:11:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: David SB</title>
		<link>http://lightrailblogger.com/2009/09/01/metro-tracks-down-improved-technology-for-trains/comment-page-1/#comment-545</link>
		<dc:creator>David SB</dc:creator>
		<pubDate>Wed, 02 Sep 2009 18:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://lightrailblogger.com/?p=1150#comment-545</guid>
		<description>A switch from the present system to Google Transit would be a welcome and long overdue development. The current trip planner on Valley Metro&#039;s site is extraordinarily clunky. It seems to want exact addresses and often fails to produce a route based on an approximate address or intersection. In addition, the current system is standalone, whereas Google Transit meshes with Google Maps and other tools that many are used to.</description>
		<content:encoded><![CDATA[<p>A switch from the present system to Google Transit would be a welcome and long overdue development. The current trip planner on Valley Metro&#8217;s site is extraordinarily clunky. It seems to want exact addresses and often fails to produce a route based on an approximate address or intersection. In addition, the current system is standalone, whereas Google Transit meshes with Google Maps and other tools that many are used to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michichan</title>
		<link>http://lightrailblogger.com/2009/09/01/metro-tracks-down-improved-technology-for-trains/comment-page-1/#comment-1079</link>
		<dc:creator>michichan</dc:creator>
		<pubDate>Wed, 02 Sep 2009 00:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://lightrailblogger.com/?p=1150#comment-1079</guid>
		<description>@lightrailblog will never happen as long as City of Phx owns the data.</description>
		<content:encoded><![CDATA[<p>@lightrailblog will never happen as long as City of Phx owns the data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David_SB</title>
		<link>http://lightrailblogger.com/2009/09/01/metro-tracks-down-improved-technology-for-trains/comment-page-1/#comment-1078</link>
		<dc:creator>David_SB</dc:creator>
		<pubDate>Wed, 02 Sep 2009 00:03:12 +0000</pubDate>
		<guid isPermaLink="false">http://lightrailblogger.com/?p=1150#comment-1078</guid>
		<description>@lightrailblog Long overdue. Will comment in more detail on the blog.</description>
		<content:encoded><![CDATA[<p>@lightrailblog Long overdue. Will comment in more detail on the blog.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

