My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 09/05/2013
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2013
>
Agenda - Planning Commission - 09/05/2013
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:18:24 AM
Creation date
9/17/2013 11:53:28 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
09/05/2013
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
113
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
July 10, 2013 1 Volume 7 I Issue 13 Zoning Bulletin <br />sue of whether a planned unit development approval was invalid on its <br />face as irreconcilable with the District's comprehensive plan. <br />The Background/Facts: In November 2010, 901 Monroe Street LLC <br />(the "Developer") submitted a planned unit development ("PUD") ap- <br />plication to the District of Columbia Zoning Commission (the "Zoning <br />Commission"). The Developer proposed to transform a 60,000 square <br />foot parcel into a mixed -use commercial and residential project. <br />Simultaneously, the Developer asked that the entire parcel be rezoned to <br />C-2-B--allowing for "community business centers" of "medium -high <br />density." <br />At the time of the PUD application, the property was primarily autho- <br />rized for residential use. The zoning regulations designated a portion of <br />the property R-2 residential, and another portion C-1 commercial. The <br />Future Land Use Map ("FLUM") approved one part of the property for <br />mixed -use moderate -density uses, another part for moderate -density resi- <br />dential uses, and a third part for low -density residential uses. The <br />Generalized Policy Map ("GPM") also contemplated low -density resi- <br />dential use in the area, treating the property as a Neighborhood Conser- <br />vation Area. <br />A group of area residents who lived within 200 feet of the proposed <br />development opposed the PUD application (the "Opponents"). Most <br />significantly, the Opponents asserted that the proposal was inconsistent <br />with the District of Columbia's Comprehensive Plan. Specifically, they <br />claimed that the proposed project was contrary to the Comprehensive <br />Plan's Land Use, Upper Northeast Area, and Urban Design Elements. <br />They also argued that the proposal was inconsistent with the FLUM. <br />Ultimately, the Zoning Commission unanimously approved the <br />Developer's application. The Commission concluded that the proposal <br />would not, as a whole, be inconsistent with the Comprehensive Plan. In <br />particular, the Zoning Commission noted that the Upper Northeast Ele- <br />ment of the Comprehensive Plan encouraged moderate -density mixed - <br />use ,development, and that current zoning was inconsistent with that goal. <br />The requested rezoning, the Zoning Commission found, would bring the <br />property in line. As to the Land Use Element of the Comprehensive Plan, <br />the Commission found that the Developer's proposal would advance a <br />land use policy of using Metro stations as development anchors because <br />the proposal was the area's "most realistic development opportunity." <br />Viewing the proposed development in the context of the Comprehensive <br />Plan "as a whole," the Commission found it to be consistent with the <br />FLUM. <br />The Opponents appealed the PUD application approval. They raised <br />two primary arguments: (1) on its face, the Developer's proposal was ir- <br />reconcilable with the Comprehensive Plan, and the Commission therefore <br />had no authority to approve the developer's application; and (2) even if <br />the Developer's proposal was consistent with the Plan, the Zoning Com- <br />8 © 2013 Thomson Reuters <br />
The URL can be used to link to this page
Your browser does not support the video tag.