<?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: Interstate 129 in Text</title>
	<atom:link href="http://www.aaroads.com/blog/2007/05/02/interstate-129-in-text/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.aaroads.com/blog/2007/05/02/interstate-129-in-text/</link>
	<description>Road news.  Pictures.  Crazed ranting.</description>
	<lastBuildDate>Tue, 16 Mar 2010 22:19:07 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://www.aaroads.com/blog/2007/05/02/interstate-129-in-text/comment-page-1/#comment-27701</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Fri, 16 Nov 2007 18:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.aaroads.com/blog/?p=85#comment-27701</guid>
		<description>Although I didn&#039;t get it in writing, conversations with SCDOT a number of years ago confirmed that the text signs for I-126 on I-26 eastbound were for the same reason: confusion with the mainline interstate.   (Before the text signs, there were signs that had the &quot;I-126&quot; removed and read US 76 EAST with I-126 totally absent.)  There is some justification in the I-126 case since the I-26 EAST roadway continues as I-126 and I-26 itself exits to the right.  The confusion is compounded by the fact that even many locals call I-126 I-26.  (I remember a wedding invitation with directions that stated that &quot;I-126 is what I-26 is called within the Columbia city limits.&quot;)  It doesn&#039;t help that TO I-26 and TO I-126 signs seem to be used interchangeably in downtown Columbia and that a resigning a few years back replaced a large overhead sign on westbound I-126 with &quot;I-26/US 76 WEST.&quot;

I suggested to SCDOT that a clear  &quot;identity&quot; be given to I-126 by giving it an exit number off of I-126 and by posting exit numbers for its own interchanges.  I claim no credit but the exit is now 108B off of I-26 but as of May 2007 there are no exit numbers on the road itself.</description>
		<content:encoded><![CDATA[<p>Although I didn&#8217;t get it in writing, conversations with SCDOT a number of years ago confirmed that the text signs for I-126 on I-26 eastbound were for the same reason: confusion with the mainline interstate.   (Before the text signs, there were signs that had the &#8220;I-126&#8243; removed and read US 76 EAST with I-126 totally absent.)  There is some justification in the I-126 case since the I-26 EAST roadway continues as I-126 and I-26 itself exits to the right.  The confusion is compounded by the fact that even many locals call I-126 I-26.  (I remember a wedding invitation with directions that stated that &#8220;I-126 is what I-26 is called within the Columbia city limits.&#8221;)  It doesn&#8217;t help that TO I-26 and TO I-126 signs seem to be used interchangeably in downtown Columbia and that a resigning a few years back replaced a large overhead sign on westbound I-126 with &#8220;I-26/US 76 WEST.&#8221;</p>
<p>I suggested to SCDOT that a clear  &#8220;identity&#8221; be given to I-126 by giving it an exit number off of I-126 and by posting exit numbers for its own interchanges.  I claim no credit but the exit is now 108B off of I-26 but as of May 2007 there are no exit numbers on the road itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Field</title>
		<link>http://www.aaroads.com/blog/2007/05/02/interstate-129-in-text/comment-page-1/#comment-6428</link>
		<dc:creator>Andy Field</dc:creator>
		<pubDate>Fri, 25 May 2007 06:07:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.aaroads.com/blog/?p=85#comment-6428</guid>
		<description>But how can that I-129 argument hold water when there are signs elsewhere in Iowa for Business loops (such as those on I-35)?  Wouldn&#039;t the green sign for Business I-35 be just as confusing as I-29 vs. I-129? Sounds like the logic of a pancake.</description>
		<content:encoded><![CDATA[<p>But how can that I-129 argument hold water when there are signs elsewhere in Iowa for Business loops (such as those on I-35)?  Wouldn&#8217;t the green sign for Business I-35 be just as confusing as I-29 vs. I-129? Sounds like the logic of a pancake.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.aaroads.com/blog/2007/05/02/interstate-129-in-text/comment-page-1/#comment-5802</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Fri, 11 May 2007 01:42:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.aaroads.com/blog/?p=85#comment-5802</guid>
		<description>oh that was interesting! we should write DOTs more often.</description>
		<content:encoded><![CDATA[<p>oh that was interesting! we should write DOTs more often.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
