<?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: Follow-up: Timetables for posting at stop poles (&#8220;Quick: When is the next bus scheduled to arrive?&#8221;)</title>
	<atom:link href="http://www.trilliumtransit.com/blog/2009/11/28/follow-up-timetables-for-posting-at-stop-poles-quick-when-is-the-next-bus-scheduled-to-arrive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.trilliumtransit.com/blog/2009/11/28/follow-up-timetables-for-posting-at-stop-poles-quick-when-is-the-next-bus-scheduled-to-arrive/</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: Wojtek</title>
		<link>http://www.trilliumtransit.com/blog/2009/11/28/follow-up-timetables-for-posting-at-stop-poles-quick-when-is-the-next-bus-scheduled-to-arrive/comment-page-1/#comment-5855</link>
		<dc:creator>Wojtek</dc:creator>
		<pubDate>Mon, 30 Nov 2009 12:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.trilliumtransit.com/blog/?p=447#comment-5855</guid>
		<description>Hi,
just wanted to throw my 2 cents worth into discussion here.
it&#039;s and interesting article, that compares different approaches to display timetables in an user-friendly format.
imho, the berlin approach seems the most suitable one as it meets requirements of two groups of riders mentioned in article.
we have been developing webapps for passengers in poznan,poland and in the area, and used a similar approach.
with the only difference, that we list the next stops in an extra column (and not above the timetable).
we are actually thinking however to revert to this idea.

take a look here for an example:
http://www.ztm.poznan.pl/rozklad/#/showTimetable/2874/19/byLine

timetable is in similar format to the german one, allows you to see:
- all departure times for weekdays, saturdays and sundays,
- list of previous and next stops on this route (with time-to-next-stop information)
- info on other routes on that stop.

hope this could be useful in further exploration of the topic: &quot;public transport information as friendly as possible&quot;.

we also would be eager to find out if this approach could be further improved,

cheers,
Wojtek @ goEuropa</description>
		<content:encoded><![CDATA[<p>Hi,<br />
just wanted to throw my 2 cents worth into discussion here.<br />
it&#8217;s and interesting article, that compares different approaches to display timetables in an user-friendly format.<br />
imho, the berlin approach seems the most suitable one as it meets requirements of two groups of riders mentioned in article.<br />
we have been developing webapps for passengers in poznan,poland and in the area, and used a similar approach.<br />
with the only difference, that we list the next stops in an extra column (and not above the timetable).<br />
we are actually thinking however to revert to this idea.</p>
<p>take a look here for an example:<br />
<a href="http://www.ztm.poznan.pl/rozklad/#/showTimetable/2874/19/byLine" rel="nofollow">http://www.ztm.poznan.pl/rozklad/#/showTimetable/2874/19/byLine</a></p>
<p>timetable is in similar format to the german one, allows you to see:<br />
- all departure times for weekdays, saturdays and sundays,<br />
- list of previous and next stops on this route (with time-to-next-stop information)<br />
- info on other routes on that stop.</p>
<p>hope this could be useful in further exploration of the topic: &#8220;public transport information as friendly as possible&#8221;.</p>
<p>we also would be eager to find out if this approach could be further improved,</p>
<p>cheers,<br />
Wojtek @ goEuropa</p>
]]></content:encoded>
	</item>
</channel>
</rss>
