<?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: What Caltrain should do for bike parking</title>
	<atom:link href="http://www.greencaltrain.com/2008/06/what-caltrain-should-do-for-bike-parking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.greencaltrain.com/2008/06/what-caltrain-should-do-for-bike-parking/</link>
	<description>BayRail Alliance Blog</description>
	<lastBuildDate>Fri, 03 Feb 2012 19:12:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Caltrain: More bike parking - Cult of the Bicycle</title>
		<link>http://www.greencaltrain.com/2008/06/what-caltrain-should-do-for-bike-parking/comment-page-1/#comment-14</link>
		<dc:creator>Caltrain: More bike parking - Cult of the Bicycle</dc:creator>
		<pubDate>Fri, 13 Jun 2008 00:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://greencaltrain.wordpress.com/?p=25#comment-14</guid>
		<description>[...] they plan to present include bike sharing and a folding bike subsidy. Caltrain bike pain elsewhere:Green Caltrain: &quot;The Bicycle Master Plan, unfortunately, will be a big disappointment for some bicyclists who [...]</description>
		<content:encoded><![CDATA[<p>[...] they plan to present include bike sharing and a folding bike subsidy. Caltrain bike pain elsewhere:Green Caltrain: &quot;The Bicycle Master Plan, unfortunately, will be a big disappointment for some bicyclists who [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evans</title>
		<link>http://www.greencaltrain.com/2008/06/what-caltrain-should-do-for-bike-parking/comment-page-1/#comment-13</link>
		<dc:creator>Evans</dc:creator>
		<pubDate>Thu, 12 Jun 2008 20:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://greencaltrain.wordpress.com/?p=25#comment-13</guid>
		<description>First, myself is not opponent for bike on board.

I believe that some of bike capacity issue can be improved by thier time table. You stated that &quot;I would not have to wait for the bus and I would not be at risk for missing my train because of a late bus.&quot; If Caltrain have express train every 15minutes in peak hour, late bus will not be a big problem.

Current Caltrain schedule, for example evening NB from San Jose, depart each 05, 25, 29, 39, 45. There are 5 train/h but sometimes you need to wait more than 20 minutes. Train spacing is not constant and each train have different stop pattern.

&quot;Baby Bullet SJ to SF within hour&quot; is great. However, I prefer &quot;Express train depart every 15min but SF-SJ takes 65 minutes&quot;. Every 15min (4 train/h) seems to difficult because Caltrain runs 4 out of 5 train runs as express.

If express train runs every 15 minuts, do you still need bicycle?</description>
		<content:encoded><![CDATA[<p>First, myself is not opponent for bike on board.</p>
<p>I believe that some of bike capacity issue can be improved by thier time table. You stated that &#8220;I would not have to wait for the bus and I would not be at risk for missing my train because of a late bus.&#8221; If Caltrain have express train every 15minutes in peak hour, late bus will not be a big problem.</p>
<p>Current Caltrain schedule, for example evening NB from San Jose, depart each 05, 25, 29, 39, 45. There are 5 train/h but sometimes you need to wait more than 20 minutes. Train spacing is not constant and each train have different stop pattern.</p>
<p>&#8220;Baby Bullet SJ to SF within hour&#8221; is great. However, I prefer &#8220;Express train depart every 15min but SF-SJ takes 65 minutes&#8221;. Every 15min (4 train/h) seems to difficult because Caltrain runs 4 out of 5 train runs as express.</p>
<p>If express train runs every 15 minuts, do you still need bicycle?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

