<?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: Followup On Sounder To Lakewood</title>
	<atom:link href="http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/feed/" rel="self" type="application/rss+xml" />
	<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/</link>
	<description>Transit in the Greater Seattle Area</description>
	<lastBuildDate>Mon, 13 Feb 2012 06:50:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Z</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-72500</link>
		<dc:creator>Z</dc:creator>
		<pubDate>Thu, 08 Oct 2009 02:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-72500</guid>
		<description>I have to say after some further consideration that Sound Transit only has themselves to blame for this mess. I&#039;ve been going to the open houses and meetings for years on this very issue, and as contentious as it is, it needs to be addressed quickly so we can finish the sounder network. Now, back to why i say that ST is to blame for this. It has nothing to do with &quot;not&quot; listening to their constituents, far from it, i think they have done a wonderful job of listening to what people want and trying make a workable solution. It’s all about the perception of the project. 

First off, with names like &quot;berm&quot; and &quot;Post and Beam&quot;, Berm sounds so hideous, much like a levee or some such being built through the south end of downtown. &quot;Post and Beam&quot; sounds so homely, so inviting and warming, when really it’s a damn trestle. People know what the MILW trestle on the eastern approach to Freighthouse Sq is like, they would probably think twice about putting something like that on the other end by downtown. Especially with the homeless shelter nearby, it would become a very attractive nuisance very quickly. They should have never started to use such names, and corrected others when they came up. The &quot;Berm&quot; option is more like a Slope/Fill to raise the grade to cross pacific avenue and continue on. And they should always have addressed the &quot;post and beam&quot; option by its proper and technical name, a trestle.

Also, Another issue i have mentioned for years is the fact you to go these public meetings, and see all sorts of diagrams, artists renditions, high level plans, and designs all printed and mounted for everyone to see. Yet you go to their website, it’s a blob of text for their projects with little other information. I would have hoped in the last nearly fifteen years of the agency they would have learned to make informative project websites, which are updated regularly and contain all matter of materials for the public perusal. Instead, it’s pathetic. They have tried in recent years such as with Lakewood station but still can’t seem to get over the one or two picture limitation that they seem to have. A picture says 1000 words, and I’ve seen a couple good pictures of the &quot;berm&quot; around (one not even on their website) and wondered why don’t they put this information on their website...</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I have to say after some further consideration that Sound Transit only has themselves to blame for this mess. I&#8217;ve been going to the open houses and meetings for years on this very issue, and as contentious as it is, it needs to be addressed quickly so we can finish the sounder network. Now, back to why i say that ST is to blame for this. It has nothing to do with &#8220;not&#8221; listening to their constituents, far from it, i think they have done a wonderful job of listening to what people want and trying make a workable solution. It’s all about the perception of the project. </p>
<p>First off, with names like &#8220;berm&#8221; and &#8220;Post and Beam&#8221;, Berm sounds so hideous, much like a levee or some such being built through the south end of downtown. &#8220;Post and Beam&#8221; sounds so homely, so inviting and warming, when really it’s a damn trestle. People know what the MILW trestle on the eastern approach to Freighthouse Sq is like, they would probably think twice about putting something like that on the other end by downtown. Especially with the homeless shelter nearby, it would become a very attractive nuisance very quickly. They should have never started to use such names, and corrected others when they came up. The &#8220;Berm&#8221; option is more like a Slope/Fill to raise the grade to cross pacific avenue and continue on. And they should always have addressed the &#8220;post and beam&#8221; option by its proper and technical name, a trestle.</p>
<p>Also, Another issue i have mentioned for years is the fact you to go these public meetings, and see all sorts of diagrams, artists renditions, high level plans, and designs all printed and mounted for everyone to see. Yet you go to their website, it’s a blob of text for their projects with little other information. I would have hoped in the last nearly fifteen years of the agency they would have learned to make informative project websites, which are updated regularly and contain all matter of materials for the public perusal. Instead, it’s pathetic. They have tried in recent years such as with Lakewood station but still can’t seem to get over the one or two picture limitation that they seem to have. A picture says 1000 words, and I’ve seen a couple good pictures of the &#8220;berm&#8221; around (one not even on their website) and wondered why don’t they put this information on their website&#8230;<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: News Roundup: Sharrows - Seattle Transit Blog</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-72269</link>
		<dc:creator>News Roundup: Sharrows - Seattle Transit Blog</dc:creator>
		<pubDate>Tue, 06 Oct 2009 22:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-72269</guid>
		<description>[...] The TNT has an excellent primer on the Tacoma berm controversy.  Ben offered his opinion here. [...]</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
[...] The TNT has an excellent primer on the Tacoma berm controversy.  Ben offered his opinion here. [...]<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BNSF Construction Updates &#8211; August 2009 - Seattle Transit Blog</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-65413</link>
		<dc:creator>BNSF Construction Updates &#8211; August 2009 - Seattle Transit Blog</dc:creator>
		<pubDate>Tue, 01 Sep 2009 01:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-65413</guid>
		<description>[...] Ben reported earlier &#8211; Do It Right Tacoma is protesting the berm that Sound Transit has selected for the [...]</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
[...] Ben reported earlier &#8211; Do It Right Tacoma is protesting the berm that Sound Transit has selected for the [...]<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ricksemple</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-61148</link>
		<dc:creator>ricksemple</dc:creator>
		<pubDate>Mon, 10 Aug 2009 07:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-61148</guid>
		<description>sound transit has not come close to having completed their design for the section from E B street to Pacific.
so any possibilities are still on the table. jAll without adding delay or additional cost.
rick semple</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
sound transit has not come close to having completed their design for the section from E B street to Pacific.<br />
so any possibilities are still on the table. jAll without adding delay or additional cost.<br />
rick semple<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-61003</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Sun, 09 Aug 2009 10:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-61003</guid>
		<description>I think a grander bridge over Pacific Avenue is the way to go.  How about a two-span, with a wide, lit, artistic pedestrian underpass on one side, which doesn&#039;t sink as deep?  Hey, make the sidewalk wide enough and you can even let street vendors into it.  ;-)

If development is ever needed adjacent to the railway berm elsewhere, retaining wall is the way to go.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I think a grander bridge over Pacific Avenue is the way to go.  How about a two-span, with a wide, lit, artistic pedestrian underpass on one side, which doesn&#8217;t sink as deep?  Hey, make the sidewalk wide enough and you can even let street vendors into it.  ;-)</p>
<p>If development is ever needed adjacent to the railway berm elsewhere, retaining wall is the way to go.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-61002</link>
		<dc:creator>Nathanael</dc:creator>
		<pubDate>Sun, 09 Aug 2009 10:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-61002</guid>
		<description>I&#039;ve seen &quot;business under&quot; in Victorian arch structures repeatedly in London.  Although a lot of the arches are vacant and boarded up.  But there used to be a great mass behind St. Pancras railway station.

But thick brick-and-stone Victorian arch structures seem to have some significant advantages over post-and-beam when it comes to stuffing retail underneath it.  It essentially has a built-in proper ceiling, some distance below the floor which the trackbed is on, and built-in walls on two sides.  The only necessary maintenance is occasional tuckpointing which can be done while the business is operating.

In contrast, modern post-and-beam viaducts would require construction of, in essence, an entire building underneath the viaduct, which would interfere with maintenance of the underside of the structure and the posts.  They&#039;re simply not *designed* for putting shops under, in the way that the brick Victorian arches, being fully finished on the underside, pretty much are suited for putting shops under.  While one could build a viaduct specifically designed for putting shops under, it would be rather different from an off-the-shelf viaduct.  And much more expensive.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I&#8217;ve seen &#8220;business under&#8221; in Victorian arch structures repeatedly in London.  Although a lot of the arches are vacant and boarded up.  But there used to be a great mass behind St. Pancras railway station.</p>
<p>But thick brick-and-stone Victorian arch structures seem to have some significant advantages over post-and-beam when it comes to stuffing retail underneath it.  It essentially has a built-in proper ceiling, some distance below the floor which the trackbed is on, and built-in walls on two sides.  The only necessary maintenance is occasional tuckpointing which can be done while the business is operating.</p>
<p>In contrast, modern post-and-beam viaducts would require construction of, in essence, an entire building underneath the viaduct, which would interfere with maintenance of the underside of the structure and the posts.  They&#8217;re simply not *designed* for putting shops under, in the way that the brick Victorian arches, being fully finished on the underside, pretty much are suited for putting shops under.  While one could build a viaduct specifically designed for putting shops under, it would be rather different from an off-the-shelf viaduct.  And much more expensive.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernie</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60946</link>
		<dc:creator>Bernie</dc:creator>
		<pubDate>Sun, 09 Aug 2009 00:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60946</guid>
		<description>I still don&#039;t know why an overpass for Pacific wasn&#039;t considered. It would be expensive but probably less than the $75M the berm has added. Redmond is building a &lt;a href=&quot;http://redmondlibrary.blogspot.com/2009/01/new-bridge-for-redmond-ne-36th-street.html&quot; rel=&quot;nofollow&quot;&gt;super whoop overpass&lt;/a&gt; diagonally across SR-520 for $40M.

It seems like for $75M a solution could be found that would greatly improve the S. Tacoma Way and Pacific intersection and do a lot more than save a few people having to stop and wait for the train to go by.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I still don&#8217;t know why an overpass for Pacific wasn&#8217;t considered. It would be expensive but probably less than the $75M the berm has added. Redmond is building a <a href="http://redmondlibrary.blogspot.com/2009/01/new-bridge-for-redmond-ne-36th-street.html" rel="nofollow">super whoop overpass</a> diagonally across SR-520 for $40M.</p>
<p>It seems like for $75M a solution could be found that would greatly improve the S. Tacoma Way and Pacific intersection and do a lot more than save a few people having to stop and wait for the train to go by.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tacomamama</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60943</link>
		<dc:creator>Tacomamama</dc:creator>
		<pubDate>Sun, 09 Aug 2009 00:00:26 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60943</guid>
		<description>Argh.  Then it must be totally lost in the ether. I meant to save a copy first, it was definitely in this thread.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Argh.  Then it must be totally lost in the ether. I meant to save a copy first, it was definitely in this thread.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin H. Duke</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60940</link>
		<dc:creator>Martin H. Duke</dc:creator>
		<pubDate>Sat, 08 Aug 2009 23:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60940</guid>
		<description>Tacomamama,

I recently approved a comment (I think of yours) that had too many links to be automatically accepted by our spam filter.  I&#039;m not showing any other comments awaiting approval, so if it&#039;s not in this thread somewhere it&#039;s not going to be.  Did you post in the other Tacoma thread?

Your comments have been well within the bounds of our comment policy (linked in the sidebar) and would not intentionally be deleted.  Thanks for contributing to an intelligent discussion of the issues.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Tacomamama,</p>
<p>I recently approved a comment (I think of yours) that had too many links to be automatically accepted by our spam filter.  I&#8217;m not showing any other comments awaiting approval, so if it&#8217;s not in this thread somewhere it&#8217;s not going to be.  Did you post in the other Tacoma thread?</p>
<p>Your comments have been well within the bounds of our comment policy (linked in the sidebar) and would not intentionally be deleted.  Thanks for contributing to an intelligent discussion of the issues.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Stefan</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60937</link>
		<dc:creator>Chris Stefan</dc:creator>
		<pubDate>Sat, 08 Aug 2009 23:06:29 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60937</guid>
		<description>I doubt Link will ever go much further in Tacoma than 10th &amp; Commerce. In any of the &quot;way out there&quot; plans I&#039;ve seen Link only goes as far as the Dome Station and the rest of Tacoma is served with streetcars. I think a case can be made on merit for extending Link all the way to the Downtown Tacoma transit hub, but I just don&#039;t see the case being there for taking it further into the city, especially considering the funds available.

Maybe it makes sense for any further expansion of the current streetcar based Tacoma Link to be built to Central Link standards, but do realize that comes with greatly added costs and may very well make an extension to TCC unfordable.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I doubt Link will ever go much further in Tacoma than 10th &amp; Commerce. In any of the &#8220;way out there&#8221; plans I&#8217;ve seen Link only goes as far as the Dome Station and the rest of Tacoma is served with streetcars. I think a case can be made on merit for extending Link all the way to the Downtown Tacoma transit hub, but I just don&#8217;t see the case being there for taking it further into the city, especially considering the funds available.</p>
<p>Maybe it makes sense for any further expansion of the current streetcar based Tacoma Link to be built to Central Link standards, but do realize that comes with greatly added costs and may very well make an extension to TCC unfordable.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Stefan</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60936</link>
		<dc:creator>Chris Stefan</dc:creator>
		<pubDate>Sat, 08 Aug 2009 22:54:09 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60936</guid>
		<description>The editors of this blog are free to delete any comments they see fit to. They &quot;own the press&quot; here so to speak. If you don&#039;t like it you are free to take your comments elsewhere or start your own forum.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
The editors of this blog are free to delete any comments they see fit to. They &#8220;own the press&#8221; here so to speak. If you don&#8217;t like it you are free to take your comments elsewhere or start your own forum.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60930</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Sat, 08 Aug 2009 22:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60930</guid>
		<description>Building more earthen berms after what happened in 2004 just east from there? Berms gave way and had to be shored up and repaired for a few million dollars. Delays, cost overruns and a derailment.  I prefer to pay a bit more to do it right once, instead of going in and fixing a mess.  Nice to see how much you trust ST thought. Would be endearing if not for your early insults.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Building more earthen berms after what happened in 2004 just east from there? Berms gave way and had to be shored up and repaired for a few million dollars. Delays, cost overruns and a derailment.  I prefer to pay a bit more to do it right once, instead of going in and fixing a mess.  Nice to see how much you trust ST thought. Would be endearing if not for your early insults.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60926</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Sat, 08 Aug 2009 22:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60926</guid>
		<description>10 years for at grade. Berm since 2008.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
10 years for at grade. Berm since 2008.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tacomamama</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60925</link>
		<dc:creator>Tacomamama</dc:creator>
		<pubDate>Sat, 08 Aug 2009 22:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60925</guid>
		<description>I&#039;ve seen the SEPA addendum before.  I don&#039;t see anything in either of those documents that provides the level of specificity necessary for meaningful design critique.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I&#8217;ve seen the SEPA addendum before.  I don&#8217;t see anything in either of those documents that provides the level of specificity necessary for meaningful design critique.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tacomamama</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60922</link>
		<dc:creator>Tacomamama</dc:creator>
		<pubDate>Sat, 08 Aug 2009 22:04:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60922</guid>
		<description>I meant grade separated and I think you can get that from the context of my comment.  I would really love it if an administrator would please approve my long comment from this morning.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I meant grade separated and I think you can get that from the context of my comment.  I would really love it if an administrator would please approve my long comment from this morning.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zed</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60918</link>
		<dc:creator>Zed</dc:creator>
		<pubDate>Sat, 08 Aug 2009 20:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60918</guid>
		<description>I meant to say the design east of I-705, the part that&#039;s in the Dome District, not west. I&#039;m direction dyslexic.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I meant to say the design east of I-705, the part that&#8217;s in the Dome District, not west. I&#8217;m direction dyslexic.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zed</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60917</link>
		<dc:creator>Zed</dc:creator>
		<pubDate>Sat, 08 Aug 2009 19:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60917</guid>
		<description>Actually the design for the at-grade solution was completed in 2002:

&quot;The project, including the Tacoma Section, is fully described in the Lakewood-to-Tacoma Commuter Rail and SR 512 Park-and-Ride Expansion Final Environmental Impact Statement, dated May 2002 (Final EIS), and follow-up environmental documentation.&quot;

http://www.psrc.org/projects/tip/selection/2002/lwsoundapp.pdf

http://www.soundtransit.org/Documents/pdf/projects/seis/TacomaD-M/DtoMSt_SEPAAddendum_Final_11-30-07.pdf

The new design with an elevated crossing of Pacific, which was requested by the city, was proposed in December 2007. Most of the delay in this is due to having to redesign it to cross Pacific with a bridge. Whether it&#039;s elevated or not, the alignment is the same, the design West of I-705 is the same, and the berm across the gulch was the same and public outreach for this project has been going on since at least 2000, so people shouldn&#039;t be acting like this was sprung on them at the last minute. Most of the onus should be on the Tacoma City Council for causing the delay, not Sound Transit. The at-grade alignment could have been built 5 or 6 years ago, saved $100 million, and we wouldn&#039;t even be having this conversation. But then I guess people would be griping about having to wait for trains to cross Pacific. You can&#039;t please everybody! :-)</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
Actually the design for the at-grade solution was completed in 2002:</p>
<p>&#8220;The project, including the Tacoma Section, is fully described in the Lakewood-to-Tacoma Commuter Rail and SR 512 Park-and-Ride Expansion Final Environmental Impact Statement, dated May 2002 (Final EIS), and follow-up environmental documentation.&#8221;</p>
<p><a href="http://www.psrc.org/projects/tip/selection/2002/lwsoundapp.pdf" rel="nofollow">http://www.psrc.org/projects/tip/selection/2002/lwsoundapp.pdf</a></p>
<p><a href="http://www.soundtransit.org/Documents/pdf/projects/seis/TacomaD-M/DtoMSt_SEPAAddendum_Final_11-30-07.pdf" rel="nofollow">http://www.soundtransit.org/Documents/pdf/projects/seis/TacomaD-M/DtoMSt_SEPAAddendum_Final_11-30-07.pdf</a></p>
<p>The new design with an elevated crossing of Pacific, which was requested by the city, was proposed in December 2007. Most of the delay in this is due to having to redesign it to cross Pacific with a bridge. Whether it&#8217;s elevated or not, the alignment is the same, the design West of I-705 is the same, and the berm across the gulch was the same and public outreach for this project has been going on since at least 2000, so people shouldn&#8217;t be acting like this was sprung on them at the last minute. Most of the onus should be on the Tacoma City Council for causing the delay, not Sound Transit. The at-grade alignment could have been built 5 or 6 years ago, saved $100 million, and we wouldn&#8217;t even be having this conversation. But then I guess people would be griping about having to wait for trains to cross Pacific. You can&#8217;t please everybody! :-)<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tacomamama</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60905</link>
		<dc:creator>Tacomamama</dc:creator>
		<pubDate>Sat, 08 Aug 2009 18:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60905</guid>
		<description>I wrote a long timeline comment with lots of documentation, which is probably sitting in your spam filter. The gist of it is that  the at-grade solution was not definite until December of 2007, public input on design was not sought until September 11, 2008, and community stakeholders have been quite vocal and visible at every meeting since.

If Sound Transit is behind on their schedule it is not because of anything the community is doing.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I wrote a long timeline comment with lots of documentation, which is probably sitting in your spam filter. The gist of it is that  the at-grade solution was not definite until December of 2007, public input on design was not sought until September 11, 2008, and community stakeholders have been quite vocal and visible at every meeting since.</p>
<p>If Sound Transit is behind on their schedule it is not because of anything the community is doing.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tacomamama</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60895</link>
		<dc:creator>Tacomamama</dc:creator>
		<pubDate>Sat, 08 Aug 2009 16:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60895</guid>
		<description>I can&#039;t find any support for your assertion that you&#039;ve known that the berm would be the final solution since 2005, when the Sound Transit board didn&#039;t approve the grade separated option until December 13, 2007.</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
I can&#8217;t find any support for your assertion that you&#8217;ve known that the berm would be the final solution since 2005, when the Sound Transit board didn&#8217;t approve the grade separated option until December 13, 2007.<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Claudia</title>
		<link>http://seattletransitblog.com/2009/08/05/followup-on-sounder-to-lakewood/#comment-60894</link>
		<dc:creator>Claudia</dc:creator>
		<pubDate>Sat, 08 Aug 2009 16:49:08 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=7055#comment-60894</guid>
		<description>http://www.seattlepi.com/transportation/177204_transpo10.html
here the link again, the other one is broken.
Tacomamama did the digging, thanks!</description>
		<content:encoded><![CDATA[<p><!-- google_ad_section_start --><br />
<a href="http://www.seattlepi.com/transportation/177204_transpo10.html" rel="nofollow">http://www.seattlepi.com/transportation/177204_transpo10.html</a><br />
here the link again, the other one is broken.<br />
Tacomamama did the digging, thanks!<!-- google_ad_section_end --></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching 1/5 queries in 0.003 seconds using disk
Object Caching 416/431 objects using disk

Served from: seattletransitblog.com @ 2012-02-13 00:26:37 -->
