<?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/"
	>

<channel>
	<title>Zoning &amp; Planning | Interactive News</title>
	<atom:link href="https://111things.com/tag/zoning-planning/feed/" rel="self" type="application/rss+xml" />
	<link>https://111things.com</link>
	<description>Ask follow up questions &#38; get instant answers and insights.</description>
	<lastBuildDate>Fri, 24 Jul 2026 12:18:47 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://i0.wp.com/111things.com/wp-content/uploads/2026/06/111things-apple-touch-icon-180-1.png?fit=32%2C32&#038;ssl=1</url>
	<title>Zoning &amp; Planning | Interactive News</title>
	<link>https://111things.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">126483067</site>        <div class="get111-archive-chat" data-get111-context="tag" data-get111-bot="default" data-get111-autosend="1" data-get111-term="zoning-planning" data-get111-term-name="Zoning &amp; Planning">
            <div class="get111-archive-chatbot">
                <div class='mwai-chatbot-container' data-params='{&quot;customId&quot;:&quot;get111-archive-tag-default&quot;,&quot;aiName&quot;:&quot;The 111: &quot;,&quot;userName&quot;:&quot;User:&quot;,&quot;guestName&quot;:&quot;Guest:&quot;,&quot;textSend&quot;:&quot;Send&quot;,&quot;textClear&quot;:&quot;Clear&quot;,&quot;imageUpload&quot;:false,&quot;fileUpload&quot;:false,&quot;multiUpload&quot;:false,&quot;maxUploads&quot;:1,&quot;fileUploads&quot;:0,&quot;mode&quot;:&quot;chat&quot;,&quot;textInputPlaceholder&quot;:&quot;Ask me anything&quot;,&quot;textInputMaxLength&quot;:12000,&quot;textCompliance&quot;:&quot; &quot;,&quot;startSentence&quot;:&quot;&quot;,&quot;localMemory&quot;:true,&quot;themeId&quot;:&quot;foundation&quot;,&quot;window&quot;:false,&quot;icon&quot;:&quot;&quot;,&quot;iconText&quot;:&quot;&quot;,&quot;iconTextDelay&quot;:1,&quot;iconAlt&quot;:&quot;AI Engine Chatbot&quot;,&quot;iconPosition&quot;:&quot;bottom-right&quot;,&quot;centerOpen&quot;:false,&quot;width&quot;:&quot;&quot;,&quot;openDelay&quot;:&quot;&quot;,&quot;iconBubble&quot;:false,&quot;windowAnimation&quot;:&quot;zoom&quot;,&quot;fullscreen&quot;:false,&quot;copyButton&quot;:false,&quot;pdfButton&quot;:false,&quot;headerSubtitle&quot;:&quot;Discuss with&quot;,&quot;containerType&quot;:&quot;standard&quot;,&quot;headerType&quot;:&quot;standard&quot;,&quot;messagesType&quot;:&quot;standard&quot;,&quot;inputType&quot;:&quot;standard&quot;,&quot;footerType&quot;:&quot;standard&quot;}' data-system='{&quot;botId&quot;:null,&quot;customId&quot;:&quot;get111-archive-tag-default&quot;,&quot;userData&quot;:null,&quot;sessionId&quot;:null,&quot;restNonce&quot;:null,&quot;contextId&quot;:null,&quot;pluginUrl&quot;:&quot;https:\/\/111things.com\/wp-content\/plugins\/ai-engine-pro&quot;,&quot;restUrl&quot;:&quot;https:\/\/111things.com\/wp-json&quot;,&quot;stream&quot;:true,&quot;debugMode&quot;:true,&quot;eventLogs&quot;:false,&quot;speech_recognition&quot;:false,&quot;speech_synthesis&quot;:false,&quot;typewriter&quot;:false,&quot;crossSite&quot;:false,&quot;actions&quot;:[],&quot;blocks&quot;:[],&quot;shortcuts&quot;:[]}' data-theme='{&quot;type&quot;:&quot;internal&quot;,&quot;name&quot;:&quot;Foundation&quot;,&quot;themeId&quot;:&quot;foundation&quot;,&quot;settings&quot;:[],&quot;style&quot;:&quot;&quot;,&quot;cssUrl&quot;:&quot;https:\/\/111things.com\/wp-content\/plugins\/ai-engine-pro\/themes\/foundation.css&quot;}'></div>            </div>

            <div class="get111-quicklinks" aria-label="Quick questions about Zoning &amp; Planning">
                                                        <button type="button" class="get111-quicklink" data-label="Local Snapshot" data-ask="Give me a quick local snapshot of Zoning &amp; Planning: what it&#039;s known for, neighborhoods, and vibe.">
                        Local Snapshot                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Housing Snapshot" data-ask="Give me a housing snapshot for Zoning &amp; Planning: typical rent, home prices, and neighborhood differences.">
                        Housing Snapshot                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Education &amp; Income" data-ask="Summarize education levels, incomes, and major employers in Zoning &amp; Planning.">
                        Education &amp; Income                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Economy &amp; Work" data-ask="Give me an economy breakdown for Zoning &amp; Planning: top industries, major employers, and job trends.">
                        Economy &amp; Work                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Growth &amp; Pulse" data-ask="What&#039;s the growth &amp; momentum story in Zoning &amp; Planning? New development, in-/out-migration, business growth, and what&#039;s changing.">
                        Growth &amp; Pulse                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Health &amp; Lifestyle" data-ask="Summarize health, lifestyle, and what locals do for fun in Zoning &amp; Planning.">
                        Health &amp; Lifestyle                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Climate &amp; Risk" data-ask="Summarize climate patterns and practical risks in Zoning &amp; Planning (storms, heat, flooding, etc.).">
                        Climate &amp; Risk                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Services Mix" data-ask="List common local services people look for in Zoning &amp; Planning (insurance, finance, legal, home services, etc.).">
                        Services Mix                    </button>
                            </div>
        </div>
        	<item>
		<title>Milwaukee Zoning Committee Advances TID 134 for Austin Commons—Key Terms and Next Step</title>
		<link>https://111things.com/finance/milwaukee-zoning-committee-advances-tid-134-for-austin-commons-key-terms-and-next-step/</link>
					<comments>https://111things.com/finance/milwaukee-zoning-committee-advances-tid-134-for-austin-commons-key-terms-and-next-step/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Fri, 24 Jul 2026 12:18:47 +0000</pubDate>
				<category><![CDATA[Finance]]></category>
		<category><![CDATA[Local Headlines]]></category>
		<category><![CDATA[Bayview]]></category>
		<category><![CDATA[City budgeting & TIF]]></category>
		<category><![CDATA[housing development]]></category>
		<category><![CDATA[Milwaukee, WI]]></category>
		<category><![CDATA[Tax Incremental Districts]]></category>
		<category><![CDATA[Zoning & Planning]]></category>
		<guid isPermaLink="false">https://111things.com/?p=929302</guid>

					<description><![CDATA[Milwaukee Zoning Committee advanced TID 134 for Austin Commons; Common Council adopted it July 14. $2.135M TIF repaid through 21 years of incremental taxes.]]></description>
										<content:encoded><![CDATA[<p><a href="https://milwaukee.legistar.com/MeetingDetail.aspx?GUID=301ECCBF-5D9C-4CE2-9CB5-5A6CB1CEA2C5&amp;#038;ID=1348261&amp;#038;Options=ID%7CText%7C&amp;#038;Search=260296" rel="nofollow noopener" target="_blank">Milwaukee</a>’s <strong>Zoning, Neighborhoods &amp; Development Committee</strong> took up legislation tied to a new affordable housing project in the <strong>Bayview</strong> area, advancing <strong>Tax Incremental District (TID) 134</strong> for <strong>Austin Commons</strong> on July 7, 2026.</p>
<p>After the committee recommendation, the <strong>Common Council adopted</strong> the resolution on <strong>July 14, 2026</strong>, and the <strong>Mayor signed</strong> it on <strong>July 15, 2026</strong>. The operative resolution also states TID 134 is “created” on <strong>July 14, 2026</strong> and is “effective as of” <strong>January 1, 2026</strong>.</p>
<h2>What TID 134 (Austin Commons) authorizes</h2>
<p>In the committee record and the resolution analysis, the district is described as covering <strong>three parcels</strong> at <strong>2318, 2324, and 2332 South Austin Street</strong> in the <strong>Bayview neighborhood</strong>.</p>
<p>The documents say TID 134 is being created to support new construction of a <strong>five-story</strong> project with <strong>100 affordable rental housing units</strong>. The plan describes the affordability target as <strong>30% to 80% of area median income</strong>, and says <strong>14</strong> of the <strong>100</strong> units are designated as <strong>supportive housing</strong>.</p>
<h2>Key dates written into the resolution</h2>
<ul>
<li><strong>Created:</strong> July 14, 2026</li>
<li><strong>Effective:</strong> January 1, 2026</li>
</ul>
<h2>How the $2.135 million is repaid (and where the risk sits)</h2>
<p>The resolution analysis and the <a href="https://city.milwaukee.gov/ImageLibrary/Groups/cityComptroller/Reports/TIDS-report/TID-Review/tid-134.pdf" rel="nofollow noopener" target="_blank">City</a> Comptroller’s review letter describe the practical “how it pays back” structure in plain terms:</p>
<ul>
<li>The TID funds an <strong>annual payment to the Developer for 21 years</strong>.</li>
<li>The annual payment is tied to <strong>incremental taxes</strong> generated inside the district, <strong>less $7,500 in annual expenses</strong>.</li>
<li>Those payments run up to a cap of <strong>$2,135,000 plus interest</strong>.</li>
</ul>
<p>The Comptroller’s letter also emphasizes that the <strong>Developer assumes the repayment risk</strong>—meaning the risk that the district would not generate enough incremental revenue to recapture the contribution with interest.</p>
<h2>Project timing in the plan</h2>
<p>The Austin Commons project plan sets construction timing targets: the documents say the developer is to <strong>commence construction by September 1, 2026</strong> and <strong>substantially complete</strong> the project by <strong>December 31, 2027</strong>.</p>
<p>With site work planned to start after that September 2026 threshold, nearby residents may want to keep an eye on how <strong>construction staging</strong>, <strong>parking arrangements</strong>, and <strong>street access</strong> are managed as implementation moves from approvals into actual work.</p>
<h2>What residents and a nearby business owner said—then the committee vote</h2>
<p>Legistar’s July 7 meeting record notes discussion of the existing site conditions and concerns focused on <strong>parking and density</strong>.</p>
<p>According to the record, the sponsor said there were <strong>three community meetings</strong> and that residents’ responses were <strong>divided</strong> between support and opposition, with the sponsor stating the concerns would be addressed. The record also says a neighboring business property owner, <strong>Andy Meyer</strong>, testified in <strong>opposition</strong>, citing concerns about <strong>parking, density, and street access—especially during winter</strong>.</p>
<p>Despite that testimony, the committee record shows the resolution was <strong>recommended for adoption</strong> in a <strong>4-1</strong> vote.</p>
<h2>Other TID items in the same committee workflow</h2>
<p>In addition to TID 134, the same committee meeting substituted and recommended action on resolutions involving <strong>TID 62</strong>, <strong>TID 72</strong>, and <strong>TID 74</strong>. This article focuses only on the Austin Commons/TID 134 package.</p>
<h2>What to watch next</h2>
<p>Now that the resolution has been adopted and signed, readers who live or work near South Austin Street can focus on whether implementation follows the commitments described in the <strong>TID 134 project plan</strong> and the related development agreement materials—especially around construction timing and how parking and access are handled during the building period.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://milwaukee.legistar.com/MeetingDetail.aspx?GUID=301ECCBF-5D9C-4CE2-9CB5-5A6CB1CEA2C5&amp;ID=1348261&amp;Options=ID%7CText%7C&amp;Search=260296" rel="nofollow noopener" target="_blank">Legistar meeting detail: Zoning, Neighborhoods &amp; Development Committee (July 7, 2026)</a></li>
<li><a href="https://city.milwaukee.gov/ImageLibrary/Groups/cityComptroller/Reports/TIDS-report/TID-Review/tid-134.pdf" rel="nofollow noopener" target="_blank">City Comptroller review letter: TID 134 – Austin Commons (dated July 6, 2026)</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/finance/milwaukee-zoning-committee-advances-tid-134-for-austin-commons-key-terms-and-next-step/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">929302</post-id>	</item>
		<item>
		<title>Tacoma planning commission to hold public hearing on proposed off-street parking code overhaul</title>
		<link>https://111things.com/law/tacoma-planning-commission-to-hold-public-hearing-on-proposed-off-street-parking-code-overhaul/</link>
					<comments>https://111things.com/law/tacoma-planning-commission-to-hold-public-hearing-on-proposed-off-street-parking-code-overhaul/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Wed, 08 Jul 2026 12:43:19 +0000</pubDate>
				<category><![CDATA[Law]]></category>
		<category><![CDATA[Local Headlines]]></category>
		<category><![CDATA[City Government]]></category>
		<category><![CDATA[housing development]]></category>
		<category><![CDATA[Parking]]></category>
		<category><![CDATA[Tacoma, WA]]></category>
		<category><![CDATA[Zoning & Planning]]></category>
		<guid isPermaLink="false">https://111things.com/?p=924941</guid>

					<description><![CDATA[Tacoma’s Planning Commission will hold an Aug. 5 public hearing on an off-street parking code overhaul; written comments are due Aug. 7.]]></description>
										<content:encoded><![CDATA[<p><a href="https://tacoma.gov/project/parking-code-update/" rel="nofollow noopener" target="_blank">Tacoma</a> residents will have a chance to weigh in on a proposed overhaul to the city’s off-street parking code, prompted by new Washington state limits on when cities may require parking minimums for new development.</p>
<p>The <a href="https://cms.tacoma.gov/Planning/Planning%20Commission/PC%20Agendas%202025/PC%20Agenda%20Packet%20%2812-17-25%29.pdf" rel="nofollow noopener" target="_blank">Tacoma Planning Commission</a> will hold a public hearing <strong>Wednesday, Aug. 5, 2026</strong>, at <strong>about 5:30 p.m.</strong> Written comments are due <strong>Aug. 7, 2026</strong>.</p>
<h2>Why Tacoma is updating its parking rules</h2>
<p>Washington law restricts how and when cities can impose <em>minimum</em> off-street parking requirements. For example, RCW 35.21.994 places caps on the size of <a href="https://app6.leg.wa.gov/rcw/default.aspx?Cite=35.21&amp;#038;full=true" rel="nofollow noopener" target="_blank">minimum parking requirements</a> and also limits when cities can require any minimum parking at all for certain types of housing and other developments. </p>
<p>Because Tacoma’s existing off-street parking standards were adopted before those limits, the City says it must update its parking code for new development and redevelopment. <strong>This Parking Code Update focuses on off-street parking</strong>—parking located on private property, in lots, or in garages—not on-street parking managed by the City’s Public Works Department.</p>
<h2>What Tacoma is asking the public to weigh</h2>
<p>Tacoma’s project materials describe <strong>two approaches</strong> the City and Planning Commission are evaluating:</p>
<ul>
<li><strong>Option A: State compliance only</strong> — update Tacoma’s parking standards only as needed to meet minimum requirements under state law.</li>
<li><strong>Option B: Broader citywide parking reform</strong> — go beyond minimum compliance and consider removing minimum parking requirements <strong>citywide</strong>.</li>
</ul>
<p>Tacoma says the Planning Commission directed staff to draft code amendments based on <strong>Option B</strong>, and those draft amendments are now available for public review and comment.</p>
<h2>Key dates and how to participate</h2>
<ul>
<li><strong>July 1, 2026</strong>: Tacoma says the Planning Commission released direction for the draft review to prepare public-facing code amendments.</li>
<li><strong>Wednesday, Aug. 5, 2026 (about 5:30 p.m.)</strong>: Planning Commission public hearing on the proposed Parking Code Update.</li>
<li><strong>Aug. 7, 2026</strong>: deadline for written comments.</li>
</ul>
<p>To participate, Tacoma directs people to the project’s materials and updates on the <strong>Parking Code Update</strong> page. For written input, the City says comments may be submitted during the public review period by email to <strong>planning@tacoma.gov</strong> with the subject line <strong>“Parking Code Update.”</strong></p>
<h2>Why parking minimum rules can matter</h2>
<p>Parking minimum requirements can influence real-world project decisions. When minimums are required, developers may need to build more off-street parking than they otherwise would—something that can affect site layout, development costs, and how much space is available for housing, landscaping, and other site needs.</p>
<p>Tacoma also emphasizes a common point of confusion: <strong>the city is not proposing a ban on parking</strong>. Rather, the update is about <strong>whether and when</strong> Tacoma can require developers to include minimum off-street parking, under state limits. Parking that is provided would still need to meet applicable safety and accessibility requirements.</p>
<h2>What happens next</h2>
<p>Tacoma says <strong>no final decisions have been made</strong> in the Parking Code Update. Public feedback and Planning Commission guidance will inform a recommendation to the City Council, which will consider adoption later in 2026.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://tacoma.gov/project/parking-code-update/" rel="nofollow noopener" target="_blank">City of Tacoma — Parking Code Update project page</a></li>
<li><a href="https://app6.leg.wa.gov/rcw/default.aspx?Cite=35.21&amp;full=true" rel="nofollow noopener" target="_blank">RCW 35.21.994 — Minimum parking requirements</a></li>
<li><a href="https://cms.tacoma.gov/Planning/Planning%20Commission/PC%20Agendas%202025/PC%20Agenda%20Packet%20%2812-17-25%29.pdf" rel="nofollow noopener" target="_blank">Tacoma Planning Commission — Parking Code Update draft work plan (Dec. 17, 2025 packet)</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/law/tacoma-planning-commission-to-hold-public-hearing-on-proposed-off-street-parking-code-overhaul/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">924941</post-id>	</item>
	</channel>
</rss>
