My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Planning Commission - 11/12/2015
Ramsey
>
Public
>
Agendas
>
Planning Commission
>
2015
>
Agenda - Planning Commission - 11/12/2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/21/2025 10:23:53 AM
Creation date
12/16/2015 11:03:11 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Planning Commission
Document Date
11/12/2015
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
145
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
Zoning Bulletin October 10, 201.5 I Volume 9 1 Issue 19 <br />DECISION: Judgment of circuit court affirmed. <br />The Court of Special Appeals of Maryland concluded that the Town's <br />Plan did comply with and satisfy the specific requirements of the Mary- <br />land Land Use Articles ("LU") with regard to the Plan's substantive <br />content. In so holding, the court rejected the Objector's arguments and <br />held that, under Maryland law, a comprehensive plan is not required to <br />include data to support the plan's goals, policies and recommendations. <br />In support of its argument that a comprehensive plan was required to <br />include data, the Objectors had pointed to LU § 3-112 and § 1-201. § 3- <br />112 sets out the matters that must be addressed in a comprehensive plan's <br />municipal growth element. § 1-201 articulates the visions that a local plan- <br />ning commission "shall implement . . . through the comprehensive <br />plan[.]" <br />Looking at the texts of that statute both in isolation particularly the <br />definitions of the words "include" and "implement"—as well as the text in <br />the context of the larger statutory scheme, the court determined thatit did <br />not support the Objectors' contentions. The court found "[i]nclude" was <br />defined as "[t]o contain as a part of something," and "[i]mplement" was <br />defined as "to cavy into effect: to fulfill; to accomplish[.]" The court found <br />that these dictionary definitions of "include" and "implement" failed to <br />support the Objectors' contention that the statutes in question required a <br />local planning commission to include detailed factual analyses as part of <br />the plan. <br />The court also found that the only provision in the LU addressing the <br />means by which comprehensive plans should be prepared required only <br />"careful and comprehensive study;" it did not mandate use of particular <br />methodologies or analytical techniques. The court looked at another ap- <br />plicable LU § —LU § 3-202(b)(1). Section 3-202(b)(1) required that the <br />elements of a comprehensive play "may be expressed in words, graphics, <br />or any other appropriate form." The court similarly found that this section <br />fell short of a requirement that a plan must contain data -based analyses to <br />support the plans' conclusion and recommendations. <br />The court concluded that the relevant statutory provisions did not sup- <br />port the Objectors' contentions that the LU required planning commission <br />to use specific analytical techniques or that comprehensive plans, in their <br />final and adopted forms, must contain discussions of data. <br />Finally, the court noted that because the Town's planning commission <br />and the Town council were acting, respectively, in quasi -legislative and <br />legislative capacities, "neither body was obligated to create a record to <br />provide a basis for its decision." "If the planning commission and the town <br />council were not obligated to create an evidentiary record to support their <br />decisions to adopt the Plan, then a fortiori, the text of the Plan itself need <br />not contain such infoiination," concluded the court. <br />See also: Lewis v. Gansler, 204 Md. App. 454, 42 A.3d 63 (2012). <br />© 2015 Thomson Reuters 9 <br />
The URL can be used to link to this page
Your browser does not support the video tag.