<?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/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Solving the Ashby Paradox</title>
	<atom:link href="http://www.neohouston.com/2009/08/solving-the-ashby-paradox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/</link>
	<description>advocating urbanism in the opportunity city</description>
	<lastBuildDate>Mon, 16 Jan 2012 11:06:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Andrew Burleson</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-449</link>
		<dc:creator>Andrew Burleson</dc:creator>
		<pubDate>Wed, 12 May 2010 14:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-449</guid>
		<description>DreamingKat - 

Great suggestions all around. That&#039;s a lot to absorb, but I think the general idea you&#039;re talking about makes sense. Thanks for the input.</description>
		<content:encoded><![CDATA[<p>DreamingKat &#8211; </p>
<p>Great suggestions all around. That&#8217;s a lot to absorb, but I think the general idea you&#8217;re talking about makes sense. Thanks for the input.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dreamingkat</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-448</link>
		<dc:creator>Dreamingkat</dc:creator>
		<pubDate>Mon, 10 May 2010 20:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-448</guid>
		<description>To expand on that idea, I&#039;m not saying merge those three zone types into one big zone type.  Keep them and use them to regulate things other than height.  Like the existing parking and setback regulations that you have on there.  I would add a few lines in your chart - one for &quot;community use&quot; spaces (parks, educational establishments, public transit waiting areas, etc) and one specifically for transit regulations.  

For instance, once you&#039;re into zones T5 and T6, it&#039;s reasonable to mandate that future development account for light rail, larger and/or more frequent bus stops.  Transit regulations for zone T3 might be something like requiring that 3/4 of the streets be connecting streets wide enough for buses (or trucks) with parking on only one side.  Lets call that &quot;large vehicle access&quot;.


Zone 3
building height: up to 3 stories
large vehicle access: 75% of streets 
bike lanes/trails: 10% of streets
pedestrian path: 100% of streets
3+ lane wide right-of-way: 10% of streets
parking requirements/restrictions: none; optional no-yard-parking  
public use: 10% of total lot size of development.  expected uses: schools (spec. elementary), parks, libraries, community gardens, park-n-rides

Zone 4
building height: up to 6 stories
large vehicle access: 75% of streets
bike lanes/trails: 25% of streets
pedestrian paths: 100% of streets
3+ lane wide streets or equiv right-of-way: 25% of streets
parking requirements/restrictions: none, 70&#039; max setback 
public use: 10%  expected uses: zone 3; scenic pathways (pedestrian and bike) with benches, water fountains, art installations, public restrooms; trolley stops and larger bus stops (covered benches, etc)

Zone 5:
building height: up to 12 stories
large vehicle access: 80% of streets
bike lanes: 33% of streets
pedestrian paths: 100% of streets
3+ lane wide streets or right of way: 33% of streets
streets with dedicated public transit lane: 10%
parking requirements/restrictions: no-yard parking, parking only in rear or structures 
public use: 7%  expected uses: zone 4, light rail stops, transportation hubs, publicly accessible rooftop gardens (during building hours), publicly accessible pedestrian tunnels (during building hours)

Zone 6:
building height: unlimited
large vehicle access: 80% of streets
bike lanes: 50% of streets
pedestrian paths: 100% of streets
3+ lane wide streets or right way: no requirement
streets with dedicated public transit lanes: 25%
parking requirements/restrictions: no surface level parking
public use: 5%  expected uses: same as zone 5</description>
		<content:encoded><![CDATA[<p>To expand on that idea, I&#8217;m not saying merge those three zone types into one big zone type.  Keep them and use them to regulate things other than height.  Like the existing parking and setback regulations that you have on there.  I would add a few lines in your chart &#8211; one for &#8220;community use&#8221; spaces (parks, educational establishments, public transit waiting areas, etc) and one specifically for transit regulations.  </p>
<p>For instance, once you&#8217;re into zones T5 and T6, it&#8217;s reasonable to mandate that future development account for light rail, larger and/or more frequent bus stops.  Transit regulations for zone T3 might be something like requiring that 3/4 of the streets be connecting streets wide enough for buses (or trucks) with parking on only one side.  Lets call that &#8220;large vehicle access&#8221;.</p>
<p>Zone 3<br />
building height: up to 3 stories<br />
large vehicle access: 75% of streets<br />
bike lanes/trails: 10% of streets<br />
pedestrian path: 100% of streets<br />
3+ lane wide right-of-way: 10% of streets<br />
parking requirements/restrictions: none; optional no-yard-parking<br />
public use: 10% of total lot size of development.  expected uses: schools (spec. elementary), parks, libraries, community gardens, park-n-rides</p>
<p>Zone 4<br />
building height: up to 6 stories<br />
large vehicle access: 75% of streets<br />
bike lanes/trails: 25% of streets<br />
pedestrian paths: 100% of streets<br />
3+ lane wide streets or equiv right-of-way: 25% of streets<br />
parking requirements/restrictions: none, 70&#8242; max setback<br />
public use: 10%  expected uses: zone 3; scenic pathways (pedestrian and bike) with benches, water fountains, art installations, public restrooms; trolley stops and larger bus stops (covered benches, etc)</p>
<p>Zone 5:<br />
building height: up to 12 stories<br />
large vehicle access: 80% of streets<br />
bike lanes: 33% of streets<br />
pedestrian paths: 100% of streets<br />
3+ lane wide streets or right of way: 33% of streets<br />
streets with dedicated public transit lane: 10%<br />
parking requirements/restrictions: no-yard parking, parking only in rear or structures<br />
public use: 7%  expected uses: zone 4, light rail stops, transportation hubs, publicly accessible rooftop gardens (during building hours), publicly accessible pedestrian tunnels (during building hours)</p>
<p>Zone 6:<br />
building height: unlimited<br />
large vehicle access: 80% of streets<br />
bike lanes: 50% of streets<br />
pedestrian paths: 100% of streets<br />
3+ lane wide streets or right way: no requirement<br />
streets with dedicated public transit lanes: 25%<br />
parking requirements/restrictions: no surface level parking<br />
public use: 5%  expected uses: same as zone 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dreamingkat</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-447</link>
		<dc:creator>Dreamingkat</dc:creator>
		<pubDate>Mon, 10 May 2010 15:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-447</guid>
		<description>For Zones T3-T5, why not use guidelines like &quot;no more than 2 stories higher&quot; than the mean of the adjacent lots, possibly with more weight going to the lots that share a street with you.  Using rounding, not truncating, to smooth transitions.  

This would mean that in a neighborhood of mostly single story homes, you could put up a 3 story home, a small apartment building, small biz, strip malls, grocery stores, etc.  But no large apartment complexes or large malls.  So if this is anywhere near an urban center or suburb, you have a neighborhood where the mean height slowly goes up (maybe only on some blocks?) and larger buildings can be built.  Once you have a concentration of 2 story homes, 3 story apt buildings, and 2 story grocery stores (they only have one floor to walk on, but they always seem to be at least 2 stories high), you can start building larger apartment buildings, small malls, etc.  I suppose its important to note that I&#039;m using the highest external point to measure height.  There should a way to get an exception to the height - maybe by popular vote - so that if you have a bunch of single story homes and you want to build a church steeple that&#039;s 4 stories high, you can do so.  Exceptions probably shouldn&#039;t count towards the average hight calculation. 

Of course, that should be coupled with developers paying for infrastructure improvements, but it prevents someones tree-lined neighborhood street from turning into a 6 lane blvd in 6 months. 

This does cause more uniformity in the neighborhood and slow change, but I think that&#039;s primarily what people want with zoning type laws anyway.

Of course, this doesn&#039;t apply at all to land that&#039;s not yet developed.  It applies to development in existing zones only.  I&#039;m not suggesting that all new large developments be limited to less than 3 stories - but honestly, it really does seem like it almost always is anyway.</description>
		<content:encoded><![CDATA[<p>For Zones T3-T5, why not use guidelines like &#8220;no more than 2 stories higher&#8221; than the mean of the adjacent lots, possibly with more weight going to the lots that share a street with you.  Using rounding, not truncating, to smooth transitions.  </p>
<p>This would mean that in a neighborhood of mostly single story homes, you could put up a 3 story home, a small apartment building, small biz, strip malls, grocery stores, etc.  But no large apartment complexes or large malls.  So if this is anywhere near an urban center or suburb, you have a neighborhood where the mean height slowly goes up (maybe only on some blocks?) and larger buildings can be built.  Once you have a concentration of 2 story homes, 3 story apt buildings, and 2 story grocery stores (they only have one floor to walk on, but they always seem to be at least 2 stories high), you can start building larger apartment buildings, small malls, etc.  I suppose its important to note that I&#8217;m using the highest external point to measure height.  There should a way to get an exception to the height &#8211; maybe by popular vote &#8211; so that if you have a bunch of single story homes and you want to build a church steeple that&#8217;s 4 stories high, you can do so.  Exceptions probably shouldn&#8217;t count towards the average hight calculation. </p>
<p>Of course, that should be coupled with developers paying for infrastructure improvements, but it prevents someones tree-lined neighborhood street from turning into a 6 lane blvd in 6 months. </p>
<p>This does cause more uniformity in the neighborhood and slow change, but I think that&#8217;s primarily what people want with zoning type laws anyway.</p>
<p>Of course, this doesn&#8217;t apply at all to land that&#8217;s not yet developed.  It applies to development in existing zones only.  I&#8217;m not suggesting that all new large developments be limited to less than 3 stories &#8211; but honestly, it really does seem like it almost always is anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keep Houston Houston</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-446</link>
		<dc:creator>Keep Houston Houston</dc:creator>
		<pubDate>Wed, 23 Sep 2009 22:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-446</guid>
		<description>Of course, the flipside would be that the developers decide a 20-story tower doesn&#039;t pencil out with the cost of street improvements, but a 45-story tower does - and so they build something twice as tall.

Impossible in the current real estate market, but in the future? Think about it.</description>
		<content:encoded><![CDATA[<p>Of course, the flipside would be that the developers decide a 20-story tower doesn&#8217;t pencil out with the cost of street improvements, but a 45-story tower does &#8211; and so they build something twice as tall.</p>
<p>Impossible in the current real estate market, but in the future? Think about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-445</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 21 Sep 2009 13:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-445</guid>
		<description>KHH:

I&#039;m not saying it would piss off Southhampton any less (it would probably piss them off more). Plus, I don&#039;t think the traffic impact was really going to be that severe - it was just the leverage the city was able to invent.

But, if traffic was the issue, and if we did have a requirement that said you couldn&#039;t build over X stories on a street of less than Y lanes, I think that would have killed Ashby. The cost of widening Bissonnet from Montrose to  Shepherd / Greenbriar (the closest major thoroughfares on either side) would have made the project unfeasible.

However, if at the end of the day they decided that they were willing to pay the cost to widen the streets to and from their project in order to accommodate the level of development they were proposing, then I would say they should be allowed to do it.

What that would say to me is that the value of the land has gotten dramatically past the uses that are currently occupying it, and if the market is willing to go to such an extreme effort to &#039;unlock&#039; the value there, then it probably should be allowed to do so.</description>
		<content:encoded><![CDATA[<p>KHH:</p>
<p>I&#8217;m not saying it would piss off Southhampton any less (it would probably piss them off more). Plus, I don&#8217;t think the traffic impact was really going to be that severe &#8211; it was just the leverage the city was able to invent.</p>
<p>But, if traffic was the issue, and if we did have a requirement that said you couldn&#8217;t build over X stories on a street of less than Y lanes, I think that would have killed Ashby. The cost of widening Bissonnet from Montrose to  Shepherd / Greenbriar (the closest major thoroughfares on either side) would have made the project unfeasible.</p>
<p>However, if at the end of the day they decided that they were willing to pay the cost to widen the streets to and from their project in order to accommodate the level of development they were proposing, then I would say they should be allowed to do it.</p>
<p>What that would say to me is that the value of the land has gotten dramatically past the uses that are currently occupying it, and if the market is willing to go to such an extreme effort to &#8216;unlock&#8217; the value there, then it probably should be allowed to do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-444</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Sat, 19 Sep 2009 18:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-444</guid>
		<description>A well written article in which you have obviously put in a lot of thought and ideas of many...However;

&quot;This would be reflective of the practice we already have in allowing Management Districts (like the Texas Medical Center) to voluntarily self-regulate.&quot;

This is the scary part! TMC will in NO WAY &quot;self-regulate&quot; and is destroying surrounding neighborhoods as I type.  City ordinances must be written to protect homeowners from the self-interests of multi-billion dollar corporations.  What did we learn from the Lehman Brother, Countrywide Financial, AIG like domination of markets?
 TMC is a private non-profit given the power of eminent domain by the Texas Legislature long before most readers of this website were born.  Perhaps eminent domain powers were appropriate in the late fifties.  Consider what did the area look like then as compared to the present?  TMC abuses its power of eminent domain through &quot;blockbusting&quot; property values and overriding deed restrictions, a homeowners strongest protection(as in the Central City neighborhood). TMC&#039;s meeting are private!  In any other eminent domain discussion, there would be a series of meetings affecting all stakeholders. TMC&#039;s Board of Directors all have one address...the main TMC office.  No contrary thought of TMC&#039;s directors could ever reach the board members.
  TMC speaks with a PUBLIC face and a PRIVATE face.  John Kajander, TMC vice-president, states publicly in their web video, &quot;Unprecedented Construction Growth in the Texas Medical Center&quot; how TMC &quot;doesn&#039;t want to negatively impact neighborhood in which they surround&quot;, &quot;how they communicate with neighborhoods about ingress-egress solutions&quot;. LIES, LIES, and DAMN LIES.  The truth about protecting neighborhoods is accurately and poignantly expressed by TMC Vice-President Robert Stott, when requested  by Devonshire Place residents to deflect over 1200 vehicles daily from a local street, &quot;It would not be in our best self-interests.&quot;

Houston neighborhoods need protection now.  Transition areas must integrate residential and commercial development.  Tall buildings next to residential homes simply do not sustain long term growth and certainly not SMART URBAN GROWTH.  
While original zoning ideas were to keep &quot;smokestacks&quot; away from families, todays smokestacks come in the form of light pollution, noise pollution, and unbridled traffic on local residential streets.  Some of the very medical institutions that form TMC produce research about the unhealthy aspects of light, noise, and traffic pollution.  Unfortunately, the growth driven by excessive profits over smart urban development and co-existence with surrounding neighborhoods may be too late.</description>
		<content:encoded><![CDATA[<p>A well written article in which you have obviously put in a lot of thought and ideas of many&#8230;However;</p>
<p>&#8220;This would be reflective of the practice we already have in allowing Management Districts (like the Texas Medical Center) to voluntarily self-regulate.&#8221;</p>
<p>This is the scary part! TMC will in NO WAY &#8220;self-regulate&#8221; and is destroying surrounding neighborhoods as I type.  City ordinances must be written to protect homeowners from the self-interests of multi-billion dollar corporations.  What did we learn from the Lehman Brother, Countrywide Financial, AIG like domination of markets?<br />
 TMC is a private non-profit given the power of eminent domain by the Texas Legislature long before most readers of this website were born.  Perhaps eminent domain powers were appropriate in the late fifties.  Consider what did the area look like then as compared to the present?  TMC abuses its power of eminent domain through &#8220;blockbusting&#8221; property values and overriding deed restrictions, a homeowners strongest protection(as in the Central City neighborhood). TMC&#8217;s meeting are private!  In any other eminent domain discussion, there would be a series of meetings affecting all stakeholders. TMC&#8217;s Board of Directors all have one address&#8230;the main TMC office.  No contrary thought of TMC&#8217;s directors could ever reach the board members.<br />
  TMC speaks with a PUBLIC face and a PRIVATE face.  John Kajander, TMC vice-president, states publicly in their web video, &#8220;Unprecedented Construction Growth in the Texas Medical Center&#8221; how TMC &#8220;doesn&#8217;t want to negatively impact neighborhood in which they surround&#8221;, &#8220;how they communicate with neighborhoods about ingress-egress solutions&#8221;. LIES, LIES, and DAMN LIES.  The truth about protecting neighborhoods is accurately and poignantly expressed by TMC Vice-President Robert Stott, when requested  by Devonshire Place residents to deflect over 1200 vehicles daily from a local street, &#8220;It would not be in our best self-interests.&#8221;</p>
<p>Houston neighborhoods need protection now.  Transition areas must integrate residential and commercial development.  Tall buildings next to residential homes simply do not sustain long term growth and certainly not SMART URBAN GROWTH.<br />
While original zoning ideas were to keep &#8220;smokestacks&#8221; away from families, todays smokestacks come in the form of light pollution, noise pollution, and unbridled traffic on local residential streets.  Some of the very medical institutions that form TMC produce research about the unhealthy aspects of light, noise, and traffic pollution.  Unfortunately, the growth driven by excessive profits over smart urban development and co-existence with surrounding neighborhoods may be too late.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keep Houston Houston</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-443</link>
		<dc:creator>Keep Houston Houston</dc:creator>
		<pubDate>Fri, 18 Sep 2009 22:13:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-443</guid>
		<description>An interesting concept.

Do you think the Southampton kids would have thrown less of a fit if the Ashby high-rise developers had paid to widen Bissonnet to four lanes? I mean, there&#039;s enough room in the existing ROW if you just take out all the street trees and narrow the sidewalks a bit...</description>
		<content:encoded><![CDATA[<p>An interesting concept.</p>
<p>Do you think the Southampton kids would have thrown less of a fit if the Ashby high-rise developers had paid to widen Bissonnet to four lanes? I mean, there&#8217;s enough room in the existing ROW if you just take out all the street trees and narrow the sidewalks a bit&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-442</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 18 Sep 2009 12:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-442</guid>
		<description>KHH,

It is a kind of zoning map if you do it by fiat.

The opportunity to do something better is to create an urban network plan where the transect level of a property is automatically and non-negotiably determined by its infrastructure.

Therefore, if you&#039;ve got the appropriate infrastructure, you&#039;re automatically allowed to build much bigger stuff - or, if you build the infrastructure, then you&#039;re allowed to build bigger stuff.

The challenge with that approach is it hasn&#039;t been done anywhere, so there&#039;s no model or case study to point to and be sure that it works as it should.</description>
		<content:encoded><![CDATA[<p>KHH,</p>
<p>It is a kind of zoning map if you do it by fiat.</p>
<p>The opportunity to do something better is to create an urban network plan where the transect level of a property is automatically and non-negotiably determined by its infrastructure.</p>
<p>Therefore, if you&#8217;ve got the appropriate infrastructure, you&#8217;re automatically allowed to build much bigger stuff &#8211; or, if you build the infrastructure, then you&#8217;re allowed to build bigger stuff.</p>
<p>The challenge with that approach is it hasn&#8217;t been done anywhere, so there&#8217;s no model or case study to point to and be sure that it works as it should.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keep Houston Houston</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-441</link>
		<dc:creator>Keep Houston Houston</dc:creator>
		<pubDate>Fri, 18 Sep 2009 11:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-441</guid>
		<description>Dude, &lt;a href=&quot;http://keephoustonhouston.wordpress.com/2009/09/18/a-few-problems-with-smart-codes/&quot; rel=&quot;nofollow&quot;&gt;you can&#039;t tell that&#039;s not a zoning map.&lt;/a&gt; That&#039;s a zoning map, period. Maybe it&#039;s a &quot;smart code&quot; zoning map but it&#039;s still a zoning map, and a zoning map is a zoning map.</description>
		<content:encoded><![CDATA[<p>Dude, <a href="http://keephoustonhouston.wordpress.com/2009/09/18/a-few-problems-with-smart-codes/" rel="nofollow">you can&#8217;t tell that&#8217;s not a zoning map.</a> That&#8217;s a zoning map, period. Maybe it&#8217;s a &#8220;smart code&#8221; zoning map but it&#8217;s still a zoning map, and a zoning map is a zoning map.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A few problems with &#8220;smart&#8221; codes. &#171; Keep Houston Houston.</title>
		<link>http://www.neohouston.com/2009/08/solving-the-ashby-paradox/#comment-440</link>
		<dc:creator>A few problems with &#8220;smart&#8221; codes. &#171; Keep Houston Houston.</dc:creator>
		<pubDate>Fri, 18 Sep 2009 10:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.neohouston.com/?p=1361#comment-440</guid>
		<description>[...] 18, 2009 &#183; Leave a Comment  Andrew over at neoHouston has an excellent post summarizing many of the pros and cons of the current regulatory environment. But there&#8217;s more [...] </description>
		<content:encoded><![CDATA[<p>[...] 18, 2009 &middot; Leave a Comment  Andrew over at neoHouston has an excellent post summarizing many of the pros and cons of the current regulatory environment. But there&#8217;s more [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

