My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Package - 10-18-10
public access
>
Clerk
>
AGENDA PACKAGES
>
2010
>
Agenda Package - 10-18-10
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/13/2010 2:56:25 PM
Creation date
12/13/2010 2:53:13 PM
Metadata
Fields
Template:
Admin-Clerk
Committee
Board of Commissioners
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
46
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
GO? <br />As stated earlier, these two sections of the UDO are used frequently and have provided a solid <br />framework for staff to use in these situations. However, staff suggests additional language <br />should be added to these sections to remove concerns about vagueness and clarify references <br />to other sections of the UDO. The following have been identified: <br />Sections 3.2.3.3 and 3.2.3.4 do not clarify (or reinforce) that such parking areas should be <br />paved as set forth in Section 8.2.6 of the UDO. Section 8.2.6.1 states that, "All required <br />parking and vehicular traffic surfaces shall be graded for drainage and shall be surfaced with <br />concrete or bituminous asphalt pavement,... ". Staff is recommending that Sections 3.2.3.3 <br />and 3.2.3.4 simply be amended to include a specific reference to Section 8.2.6.1. <br />These sections also do not make reference to Section 10.7 which requires architectural design <br />standards for projects located along our major corridors. Again, staff is recommending <br />adding language to these two sections to reference these standards. <br />Lastly, Section 10.1 of the UDO requires screening of solid waste storage areas (dumpsters) <br />and, again, staff recommends that reference language be added to Sections 3.2.3.3 and 3.2.3.4 <br />to clarify that this standard is required. <br />Please note that the Joint Planning Commission (JPC) met on Sept. 23, 2010 to review this <br />proposed amendment. The JPC recommended that the proposed amendment be forwarded to <br />all three jurisdictions for consideration of adoption. <br />Draft land age far consideration: See Attachment A for the proposed changes /new language. <br />Amendment 2 — Section 4.7.3.2 provides language for setbacks on lots that have more than <br />one street frontage. The last sentence of this section reads, "All other frontages shall be <br />considered street side yards and the rear yard shall be the yard that is opposite the designated <br />front yard." Unfortunately, the current ordinance language does not clearly spell out what the <br />setback for a "street side yard ", so staff is recommending that language be added to clarify <br />that a street side yard setback is the same as a front yard setback. <br />Please note that the Joint Planning Commission (JPC) met on Sept. 23, 2010 to review this <br />proposed amendment. The JPC recommended that the proposed amendment be forwarded to <br />all three jurisdictions for consideration of adoption. <br />Draft language for consideration (changes in Italics): <br />4.7.3.2 SETBACKS FOR LOTS WITH MORE THAN ONE STREET <br />FRONTAGE. <br />Strictures shall meet the front yard setback from all abutting street rights -of -way <br />unless otherwise provided in this Ordinance. For undeveloped multiple frontage lots, <br />the developer has the option to determine which yard shall be considered the "front' so <br />2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.