<?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: Feedback on iPhone&#8217;s transit directions &amp; maps</title>
	<atom:link href="http://www.trilliumtransit.com/blog/2008/12/05/feedback-on-iphone-transit-instructions-powered-by-google-transit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.trilliumtransit.com/blog/2008/12/05/feedback-on-iphone-transit-instructions-powered-by-google-transit/</link>
	<description>More riders and less hassle.</description>
	<lastBuildDate>Fri, 21 May 2010 16:17:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Aaron Antrim</title>
		<link>http://www.trilliumtransit.com/blog/2008/12/05/feedback-on-iphone-transit-instructions-powered-by-google-transit/comment-page-1/#comment-2328</link>
		<dc:creator>Aaron Antrim</dc:creator>
		<pubDate>Sat, 06 Dec 2008 02:37:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.trilliumtransit.com/blog/?p=76#comment-2328</guid>
		<description>You are very right Jehiah.  I hope you&#039;ve checked out my &lt;a href=&quot;http://www.trilliumtransit.com/blog/2008/09/11/trimet-innovations-in-transit-data-publishing/&quot; rel=&quot;nofollow&quot;&gt;interview with the great folks at TriMet&lt;/a&gt;.  Those kinds of examples really make a case for open data to other agencies well, I think.

The four agencies Trillium has helped join Google Transit — (three in Humboldt), and then Rio Vista Delta Breeze in the SF Bay Area — have all chosen to make their data feeds public.  I think that&#039;s great.

One other factor in making feeds public besides agency choice that is worth pointing out is that some software and service providers have license agreements that lock transit data from being freely shared (I guess because it would make it easy to switch to another vendor&#039;s product).  My clients own their own data.

I hope other vendors take this approach because it&#039;s the best thing for public transportation.  I say let&#039;s try to grow the whole public transportation pie (as a market for us, and with it&#039;s benefits for communities and riders) rather than jealously guard slices of it.</description>
		<content:encoded><![CDATA[<p>You are very right Jehiah.  I hope you&#8217;ve checked out my <a href="http://www.trilliumtransit.com/blog/2008/09/11/trimet-innovations-in-transit-data-publishing/" rel="nofollow">interview with the great folks at TriMet</a>.  Those kinds of examples really make a case for open data to other agencies well, I think.</p>
<p>The four agencies Trillium has helped join Google Transit — (three in Humboldt), and then Rio Vista Delta Breeze in the SF Bay Area — have all chosen to make their data feeds public.  I think that&#8217;s great.</p>
<p>One other factor in making feeds public besides agency choice that is worth pointing out is that some software and service providers have license agreements that lock transit data from being freely shared (I guess because it would make it easy to switch to another vendor&#8217;s product).  My clients own their own data.</p>
<p>I hope other vendors take this approach because it&#8217;s the best thing for public transportation.  I say let&#8217;s try to grow the whole public transportation pie (as a market for us, and with it&#8217;s benefits for communities and riders) rather than jealously guard slices of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jehiah</title>
		<link>http://www.trilliumtransit.com/blog/2008/12/05/feedback-on-iphone-transit-instructions-powered-by-google-transit/comment-page-1/#comment-2326</link>
		<dc:creator>Jehiah</dc:creator>
		<pubDate>Sat, 06 Dec 2008 02:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.trilliumtransit.com/blog/?p=76#comment-2326</guid>
		<description>Yes a pat on the back is in order, however the list of agencies making data &lt;a href=&quot;http://code.google.com/p/googletransitdatafeed/wiki/PublicFeeds&quot; rel=&quot;nofollow&quot;&gt;fully&lt;/a&gt; &lt;a href=&quot;http://www.gtfs-data-exchange.com/&quot; rel=&quot;nofollow&quot;&gt;public&lt;/a&gt; is still really small. Things like this would have happened sooner had that barrier been removed, and there are still good applications for riders that are unavailable simply because of agencies unwillingness to publish their schedule data. So even though this is a large step in the right direction, let us not forget that it is only a step.</description>
		<content:encoded><![CDATA[<p>Yes a pat on the back is in order, however the list of agencies making data <a href="http://code.google.com/p/googletransitdatafeed/wiki/PublicFeeds" rel="nofollow">fully</a> <a href="http://www.gtfs-data-exchange.com/" rel="nofollow">public</a> is still really small. Things like this would have happened sooner had that barrier been removed, and there are still good applications for riders that are unavailable simply because of agencies unwillingness to publish their schedule data. So even though this is a large step in the right direction, let us not forget that it is only a step.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
