<?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"
	>
<channel>
	<title>Comments on: Google Transit, Meet Muni &#8212; Muni, Meet Google Transit</title>
	<atom:link href="http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/feed/" rel="self" type="application/rss+xml" />
	<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/</link>
	<description></description>
	<pubDate>Sat, 19 Jul 2008 13:19:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: AC Transit Joins the Google Transit Roster &#171; Transbay Blog</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5198</link>
		<dc:creator>AC Transit Joins the Google Transit Roster &#171; Transbay Blog</dc:creator>
		<pubDate>Wed, 21 May 2008 05:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5198</guid>
		<description>[...] Transit&#160;Roster  AC Transit joins the Google Transit roster. A few weeks ago, we reported that Muni was finally integrated into the Google Maps transit planner, and we are very happy to report that AC Transit has also been [...]</description>
		<content:encoded><![CDATA[<p>[...] Transit&nbsp;Roster  AC Transit joins the Google Transit roster. A few weeks ago, we reported that Muni was finally integrated into the Google Maps transit planner, and we are very happy to report that AC Transit has also been [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5150</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 02 May 2008 22:33:32 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5150</guid>
		<description>Google is interested in working on it, but their vision is larger than NextBus -- and it will have to be, as more and more systems make real time data available to passengers. As you said, having the option between real-time data and timetables for future planning would be the best option.</description>
		<content:encoded><![CDATA[<p>Google is interested in working on it, but their vision is larger than NextBus &#8212; and it will have to be, as more and more systems make real time data available to passengers. As you said, having the option between real-time data and timetables for future planning would be the best option.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Chow</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5149</link>
		<dc:creator>Andy Chow</dc:creator>
		<pubDate>Fri, 02 May 2008 22:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5149</guid>
		<description>Real time data requires coordination between different vendors. I think NextBus and Google may be interested to work together on this.

I don't have a problem with offering real time data as an option, but real time is not useful to plan trips way ahead of time.

I do like to see lines. I think it is even better if it is released as KML files.</description>
		<content:encoded><![CDATA[<p>Real time data requires coordination between different vendors. I think NextBus and Google may be interested to work together on this.</p>
<p>I don&#8217;t have a problem with offering real time data as an option, but real time is not useful to plan trips way ahead of time.</p>
<p>I do like to see lines. I think it is even better if it is released as KML files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rescue Muni &#187; Blog Archive &#187; May Day Muni miscellany</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5139</link>
		<dc:creator>Rescue Muni &#187; Blog Archive &#187; May Day Muni miscellany</dc:creator>
		<pubDate>Thu, 01 May 2008 21:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5139</guid>
		<description>[...] Muni data now available on Google Transit. Try it, let us know what you think. [...]</description>
		<content:encoded><![CDATA[<p>[...] Muni data now available on Google Transit. Try it, let us know what you think. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5125</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Tue, 29 Apr 2008 04:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5125</guid>
		<description>^^^ And because of that, I do think there is value in presenting the sort of information that was being provided in the maps on this site, like transfers. But there doesn't seem to be much point in duplicating every stop location. And right now, they're providing timetable schedules, so if the choice is between timetables and real-time data, the latter is more useful. It would basically put the NextMuni map out of business, but then again, that isn't exactly the epitome of clarity, or even error-free, for that matter.

I'd be interested in hearing opinions as to the potential value in seeing the configuration of stops on just one or a few lines at once -- rather than just seeing a grid of bus stops as you'd get on a Google map. They would certainly integrate easier into the transit wiki project that you're working on, Andy.

Incidentally, I have many line maps that were partially started or largely complete prior to the official announcement about the Google transit information, so I will likely be posting more line maps in any case. People might find them be cool to play around with.</description>
		<content:encoded><![CDATA[<p>^^^ And because of that, I do think there is value in presenting the sort of information that was being provided in the maps on this site, like transfers. But there doesn&#8217;t seem to be much point in duplicating every stop location. And right now, they&#8217;re providing timetable schedules, so if the choice is between timetables and real-time data, the latter is more useful. It would basically put the NextMuni map out of business, but then again, that isn&#8217;t exactly the epitome of clarity, or even error-free, for that matter.</p>
<p>I&#8217;d be interested in hearing opinions as to the potential value in seeing the configuration of stops on just one or a few lines at once &#8212; rather than just seeing a grid of bus stops as you&#8217;d get on a Google map. They would certainly integrate easier into the transit wiki project that you&#8217;re working on, Andy.</p>
<p>Incidentally, I have many line maps that were partially started or largely complete prior to the official announcement about the Google transit information, so I will likely be posting more line maps in any case. People might find them be cool to play around with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Chow</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5124</link>
		<dc:creator>Andy Chow</dc:creator>
		<pubDate>Tue, 29 Apr 2008 03:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5124</guid>
		<description>I don't know how much value by linking to real time information. A lot of people use trip planning tools to plan trips way ahead of time, not everyone has iphones and wireless internet connections.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know how much value by linking to real time information. A lot of people use trip planning tools to plan trips way ahead of time, not everyone has iphones and wireless internet connections.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: countZ</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5123</link>
		<dc:creator>countZ</dc:creator>
		<pubDate>Mon, 28 Apr 2008 05:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5123</guid>
		<description>Now, if only they could get TransLink working, then the Bay's mass transit network would start to make sense!</description>
		<content:encoded><![CDATA[<p>Now, if only they could get TransLink working, then the Bay&#8217;s mass transit network would start to make sense!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5122</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Sat, 26 Apr 2008 00:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5122</guid>
		<description>These maps haven't been implemented more quickly because Google partners with the individual agencies. The technology itself isn't hard to apply, once they get the necessary data from the agency. If we could add just AC Transit, SamTrans, and GGT, we'd have most of our bases covered in terms of buses and regional rail across the region.

Syncing with NextBus is a natural extension, but the goal there, just like with the transit stops, is to implement something that could be easily applied across the board, rather than coding a scheme specific to NextBus. But once Google gets around to replacing the timetable schedules with real-time data, it will basically be unstoppable.</description>
		<content:encoded><![CDATA[<p>These maps haven&#8217;t been implemented more quickly because Google partners with the individual agencies. The technology itself isn&#8217;t hard to apply, once they get the necessary data from the agency. If we could add just AC Transit, SamTrans, and GGT, we&#8217;d have most of our bases covered in terms of buses and regional rail across the region.</p>
<p>Syncing with NextBus is a natural extension, but the goal there, just like with the transit stops, is to implement something that could be easily applied across the board, rather than coding a scheme specific to NextBus. But once Google gets around to replacing the timetable schedules with real-time data, it will basically be unstoppable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Becks</title>
		<link>http://transbayblog.com/2008/04/25/google-transit-meet-muni-muni-meet-google-transit/#comment-5121</link>
		<dc:creator>Becks</dc:creator>
		<pubDate>Fri, 25 Apr 2008 23:54:22 +0000</pubDate>
		<guid isPermaLink="false">http://transbay.wordpress.com/?p=393#comment-5121</guid>
		<description>This is great news. I first heard about Google Transit a couple months ago and was horrified when I did my first searches to find out that it didn't include Muni or AC Transit info. So it sent me on absurd routes using BART that honestly would have been quicker to just walk.

Hopefully AC Transit will be the next to be included. Also, it seems like they should just be able to sync with NextBus, since NextBus covers hundreds of bus systems and thousands of bus lines across the country and is constantly expanding. It seems silly and redundant to come up with a separate real-time tracking system. If Google wants more coverage, they should partner with NextBus to make this happen.</description>
		<content:encoded><![CDATA[<p>This is great news. I first heard about Google Transit a couple months ago and was horrified when I did my first searches to find out that it didn&#8217;t include Muni or AC Transit info. So it sent me on absurd routes using BART that honestly would have been quicker to just walk.</p>
<p>Hopefully AC Transit will be the next to be included. Also, it seems like they should just be able to sync with NextBus, since NextBus covers hundreds of bus systems and thousands of bus lines across the country and is constantly expanding. It seems silly and redundant to come up with a separate real-time tracking system. If Google wants more coverage, they should partner with NextBus to make this happen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
