<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Transbay Blog &#187; Eminent Domain</title>
	<atom:link href="http://transbayblog.com/category/eminent-domain/feed/" rel="self" type="application/rss+xml" />
	<link>http://transbayblog.com</link>
	<description>Transportation and urban planning in the San Francisco Bay Area</description>
	<lastBuildDate>Thu, 05 Jan 2012 19:20:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='transbayblog.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://1.gravatar.com/blavatar/d764063097b0becbb43a390a1279ac5f?s=96&#038;d=http%3A%2F%2Fs2.wp.com%2Fi%2Fbuttonw-com.png</url>
		<title>Transbay Blog &#187; Eminent Domain</title>
		<link>http://transbayblog.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://transbayblog.com/osd.xml" title="Transbay Blog" />
	<atom:link rel='hub' href='http://transbayblog.com/?pushpress=hub'/>
		<item>
		<title>June 2008 Election: Propositions 98, 99 and Eminent Domain</title>
		<link>http://transbayblog.com/2008/06/02/june-2008-election-propositions-98-99-and-eminent-domain/</link>
		<comments>http://transbayblog.com/2008/06/02/june-2008-election-propositions-98-99-and-eminent-domain/#comments</comments>
		<pubDate>Mon, 02 Jun 2008 08:58:23 +0000</pubDate>
		<dc:creator>Eric</dc:creator>
				<category><![CDATA[California]]></category>
		<category><![CDATA[Election Coverage]]></category>
		<category><![CDATA[Eminent Domain]]></category>

		<guid isPermaLink="false">http://transbay.wordpress.com/?p=430</guid>
		<description><![CDATA[The Bay Area has a few rent control hotspots (notably San Francisco, Oakland, and San Jose) and is a progressive place in general &#8212; so by this point, only one day before the election, I expect most people are up to their ears in chants of &#8220;Save Rent Control, Vote No on 98.&#8221; The point &#8230; <a href="http://transbayblog.com/2008/06/02/june-2008-election-propositions-98-99-and-eminent-domain/">Continue reading <span class="meta-nav">&#187;</span></a><img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=transbayblog.com&amp;blog=1475665&amp;post=430&amp;subd=transbay&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p>The Bay Area has a few rent control hotspots (notably San Francisco, Oakland, and San Jose) and is a progressive place in general &#8212; so by this point, only one day before the election, I expect most people are up to their ears in chants of &#8220;Save Rent Control, Vote No on 98.&#8221; The point of this post is not so much to harp more on this, although I do want to strongly urge you to vote <strong>No on 98</strong> tomorrow. First, a brief remark on rent control: controversial though it would be, we probably should take a hard look at rent control and honestly assess the extent to which it has helped or not helped increase supply of affordable housing. (Yes, I say that despite living in a rent-controlled apartment.) That said, having doubts about rent control&#8217;s efficacy as a policy does not excuse slipping blanket elimination of rent control into a statewide proposition about eminent domain, as Prop 98 does, and then failing to implement a replacement relief plan. It&#8217;s a classic example of biting off more than you can chew, and that is basically Prop 98 in a nutshell.</p>
<p><span id="more-430"></span>Although the rent control aspect is the most incendiary, easily-encapsulated idea to leave in the minds of voters, Prop 98&#8242;s opponents do a partial disservice to the cause by focusing exclusively on rent control &#8212; the potential effects of 98 extend far beyond rent control. Prop 98&#8242;s extreme uphold-property-rights-at-all-costs approach &#8212; yet another attempt after voters (narrowly) denied Prop. 90 in the November 2006 election &#8212; is a prime example of the backlash that has occurred around the country since the U.S. Supreme Court&#8217;s 2005 decision in <em>Kelo v. City of New London</em>, which affirmed economic redevelopment and revitalization as a public use that would justify transferring property from one private owner to another using eminent domain. The proposition amends <a href="http://www.leginfo.ca.gov/.const/.article_1" target="_blank">Article I of the California Constitution</a> by adding several paragraphs of text to the current single paragraph Section 19. The goal is to prohibit application of eminent domain to the transfer any private property for a private use, while allowing such a transfer only for a more narrowly defined set of public uses. At first glance, this may sound like a reasonable response to <em>Kelo</em>, but the problem lies in the measure&#8217;s broad formulations. The amendment gives a few possible definitions of &#8220;private use&#8221;, including:</p>
<blockquote><p><strong>SEC. 19(b)(3)(iii)</strong> Regulation of the ownership, occupancy or use of privately owned real property or associated property rights in order to transfer an economic benefit to one or more private persons at the expense of the property owner.</p></blockquote>
<p>Governments regularly impose regulations that fall into this category, as they have been given discretion to do so. Standard planning tools like zoning and impact fees are regulations of private property that limit the property owner&#8217;s economic benefit, but the requirement that economic benefit be transferred to one or more private persons is so broad as to not be an effective limitation. San Francisco imposes many impact fees on developers (e.g. for transit, inclusionary affordable housing, child care) that provide valuable revenue, but which could be illegal if Prop 98 passes.</p>
<p>Another clause in the same section establishes that a <em>public agency&#8217;s </em>use of private property may also constitute a &#8220;private use&#8221; that would prohibit eminent domain:</p>
<blockquote><p><strong>SEC. 19(b)(3)(ii)</strong> Transfer of ownership, occupancy, or use of private property or associated property rights to a public agency for the consumption of natural resources or for the same or a substantially similar use as that made by the private owner.</p></blockquote>
<p>This clause could have <a href="http://www.noprop98.org/go/why-vote-no-on-98-and-yes-on-99/prop.-98-threatens-our-state%27s-water-quality-and-supply/" target="_blank">ramifications for California&#8217;s water supply</a>. Water is clearly a natural resource being consumed, so if private property is involved, under Prop 98 the government could be denied the right to construct canals, reservoirs and other infrastructure necessary to transporting and storing water. This, in turn, affects the supply and easy availability of water used for drinking, agriculture, and other purposes. In other words, if a <em>public</em> agency carries out an action on behalf of the <em>public</em> interest, that action could be classified as a &#8220;private use&#8221; under Prop 98. So once again, we see that the broad language of the proposition carries with it implications that are undesirable, and at times even nonsensical.</p>
<p>There is no shortage of material on the Internet explaining why Prop 98 should be defeated. Rather than repeat it here, I would urge you to read a few more sources if you haven&#8217;t already. SPUR provides a <a href="http://www.spur.org/documents/0608_ballot_analysis.shtm#98" target="_blank">methodical outline</a> of the effects, with an emphasis on possible effects to land use planning, and Marin Maven has posted a <a href="http://marinmaven.webjaw.com/2008/05/23/mavens-action-alert-defang-derail-and-defeat-prop-98-on-june-3rd/" target="_blank">vigorous call to action</a>, complete with video clips. <a href="http://www.noprop98.org/go/front/read-all-editorials.../" target="_blank">Newspapers all around the state</a> have editorialized about these two propositions.</p>
<p>Most progressive discussion has repeatedly chanted the &#8220;No on 98, Yes on 99&#8243; mantra, in part because competing eminent domain measure Prop 99 includes a poison pill provision that would void Prop 98 if Prop 99 receives more votes. Despite this, <a href="http://www.spur.org/documents/0608_ballot_analysis.shtm#99" target="_blank">SPUR has recommended a No on 99 position</a> (and obviously, No on 98, as well), suggesting that even Prop 99&#8242;s much more narrowly defined restrictions on eminent domain would restrict the extent to which local governments could follow through with transit-oriented development. I respect and appreciate SPUR&#8217;s advocacy and commitment to promoting dense growth near transit, but encouraging a &#8220;no&#8221; vote on Prop 99 on that basis might be overcautious. The Legislative Analyst blurb notes that Prop 99 &#8220;would not change significantly current government land acquisition practices,&#8221; and SPUR itself remarks that residential property (the only use which Prop 99 addresses) is not usually targeted for public uses centered on economic development. But it is a good question: can Prop 99 be reconciled with transit-oriented development, so that we can still take advantage of Prop 99&#8242;s poison pill provision, without limiting cities&#8217; freedom of movement to encourage TOD?</p>
<p>Prop 99 restricts government from applying eminent domain against &#8220;owner-occupied residence[s]&#8221; only (i.e. single-family residences, whether attached or detached; but not businesses, farms, or other uses). Compare this to Prop 98, which provides restrictions for any private property, no matter the use of the land. Prop 99 amends <a href="http://www.leginfo.ca.gov/.const/.article_1" target="_blank">Article I of the California Constitution</a>, including this provision:</p>
<blockquote><p><strong>SEC. 19(b):</strong> The State and local governments are prohibited from acquiring by eminent domain an owner-occupied residence for the purpose of conveying it to a private person.</p></blockquote>
<p>And then it lists exceptions to this general rule. The SPUR analysis focuses on the following exception:</p>
<blockquote><p><strong>SEC. 19(d):</strong> Subdivision (b) of this section does not apply when State or local government exercises the power of eminent domain for the purpose of acquiring private property for a public work or improvement.</p></blockquote>
<p>What is a &#8220;public work or improvement?&#8221;</p>
<blockquote><p><strong>SEC. 19(e), 5. </strong>&#8220;Public work or improvement&#8221; means facilities or infrastructure for the delivery of public services such as &#8230; streets or highways, public transit, railroad, airports, and seaports &#8230; and private uses incidental to, or necessary for, the public work or improvement.</p></blockquote>
<p>Of course, the transit right-of-way itself would undeniably be classified as a public work or improvement. SPUR, I believe correctly, raises the issue that dense residential development around a train station, however desirable, may not be enough to qualify as a private use &#8220;incidental to, or necessary for&#8221; a public improvement.  In the world of planning, transit and land use are inextricably linked, and decisions made about the one both influence and are influenced by decisions made about the other. But there is a real question as to the extent that symbiotic relationship has entered or will ever enter the general (and, more importantly in this case, the legal) consciousness.</p>
<p>However, it seems possible that eminent domain for transit-oriented development could still be approved under Prop 99. A fundamental assumption underlying redevelopment is that it is carried out to erase blight, with the goal of upholding the &#8220;health, safety and general welfare of the people.&#8221; See <a href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=hsc&amp;group=33001-34000&amp;file=33030-33039" target="_blank">California Health and Safety Code (CHSC) §33030</a>. In particular, if blight cannot be addressed through less forceful means, then &#8220;it is in the public interest to employ the power of eminent domain, to advance or expend public funds for these purposes, and to provide a means by which blighted areas may be redeveloped or rehabilitated.&#8221; (<a href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=hsc&amp;group=33001-34000&amp;file=33030-33039" target="_blank">CHSC §</a><a href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=hsc&amp;group=33001-34000&amp;file=33030-33039" target="_blank">33037(b)</a>.) One controversy, especially post-<em>Kelo</em>, is that under California law, a wide range of properties may be classified as &#8220;blighted,&#8221; because the conditions are far-reaching and not all that difficult to satisfy. Of course, it includes the basic provision we would all naturally think of as blighted; that is, that the property is &#8220;unsafe or unhealthy for persons to live or work.&#8221; (<a href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=hsc&amp;group=33001-34000&amp;file=33030-33039" target="_blank">CHSC  §33031(a)(1)</a>.) But it also includes other characteristics that may not jump immediately to mind, like depreciated property values. A property may also be deemed blighted if uses are incompatible with the surrounding area, with zoning, or even with a General Plan goal, such as building high-density housing near transit corridors. In terms of TOD these two characteristics are especially relevant:</p>
<blockquote><p><strong><a href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=hsc&amp;group=33001-34000&amp;file=33030-33039" target="_blank">CHSC §33031(a)(3)</a>:</strong> Adjacent or nearby incompatible land uses that prevent the develpoment of those parcels or other portions of the project area.</p>
<p><strong><a href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=hsc&amp;group=33001-34000&amp;file=33030-33039" target="_blank">CHSC §33031(a)(4)</a>: </strong>The existence of subdivided lots that are in multiple ownership and whose physical development has been impaired by their irregular shapes and inadequate sizes, given present general plan and zoning standards and present market conditions.</p></blockquote>
<p>What does this have to do with Prop 99? The relationship is a bit oblique, because the Prop 99 amendment does not insert the actual word &#8220;blight&#8221; into the Constitution, nor does it explicitly incorporate the characterizing conditions of blight from §33031<strong> </strong>into the amendment &#8212; quite understandably, because that would have made the proposition more vulnerable politically. Instead, Prop 99 confers upon governments the following exception to the 19(b) general rule:</p>
<blockquote><p><strong>SEC. 19(c):</strong> Subdivision (b) of this section does not apply when State or local government exercises the power of eminent domain <span style="text-decoration:underline;">for the purpose of protecting public health and safety</span>; preventing serious, repeated criminal activity; responding to an emergency; or remedying environmental contamination that poses a threat to public health and safety. (Emphasis mine.)</p></blockquote>
<p>So the Prop 99 amendment allows eminent domain to protect &#8220;public health and safety&#8221; &#8212; the same phrase as in the Health and Safety Code, with the &#8220;general welfare&#8221; part deleted. If a government can establish that not constructing TOD in a certain location forces the property to be blighted, does the phrase &#8220;public health or safety&#8221; here justify use of eminent domain on that basis, or does the missing &#8220;general welfare&#8221; shut the door? I don&#8217;t know, but upon reading the phrase &#8220;public health or safety&#8221; phrase in Prop 99, the blighted property issue jumped immediately to mind, so it seems like you could at least make the argument.</p>
<p>And, even more basic than the blighted property issue: Sec. 19(b) prohibits eminent domain &#8220;for the <span style="text-decoration:underline;">purpose</span> of conveying it to a private person.&#8221; (Emphasis mine.) If a government can establish a legitimate purpose other than wanting to convey the property to a private party, would that purpose be enough to justify eminent domain? In the case of TOD, it is not too hard to establish such a purpose. In fact, that purpose is basically the whole point of this website&#8211; to extol the societal and environmental virtues associated with livable cities built around transit, as opposed to auto-dependent sprawl that exacerbates congestion, pollution, and global warming.</p>
<p>Someone in favor of Prop 98, who is operating under the assumption that most government intrusion is detrimental, could easily turn many of the clauses cited earlier to argue that Prop 99 does not go far enough to provide true eminent domain reform, but Prop 99 does restrict use of eminent domain in the most sensitive cases while still affording government necessary flexibility. Prop 99&#8242;s more narrow focus is not a bad thing &#8212; much better to proceed carefully than to open the destructive Pandora&#8217;s Box that is Prop 98. In the future, restrictions on <em>Kelo</em> can and probably should be considered &#8212; and if so, they should be narrowly tailored to address specific concerns from <em>Kelo</em>. Prop 98&#8242;s broad-sweeping language is deeply troubling, and it is a strong impediment to the government&#8217;s ability to act on behalf of the public interest. &#8220;True&#8221; eminent domain reform can be dealt with after the election. For now, we should concentrate on the immediate goal of defeating Prop 98.</p>
<br /><img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/transbay.wordpress.com/430/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/transbay.wordpress.com/430/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/transbay.wordpress.com/430/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/transbay.wordpress.com/430/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gofacebook/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/facebook/transbay.wordpress.com/430/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gotwitter/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/twitter/transbay.wordpress.com/430/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/transbay.wordpress.com/430/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/transbay.wordpress.com/430/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/transbay.wordpress.com/430/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/transbay.wordpress.com/430/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=transbayblog.com&amp;blog=1475665&amp;post=430&amp;subd=transbay&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://transbayblog.com/2008/06/02/june-2008-election-propositions-98-99-and-eminent-domain/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">transbay</media:title>
		</media:content>
	</item>
	</channel>
</rss>
