Browse
Search
Agenda - 03-02-2010 - 4l
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
2010's
>
2010
>
Agenda - 03-02-2010 - Regular Mtg.
>
Agenda - 03-02-2010 - 4l
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/26/2010 9:23:42 AM
Creation date
2/26/2010 9:18:26 AM
Metadata
Fields
Template:
BOCC
Date
3/2/2010
Meeting Type
Regular Meeting
Document Type
Agenda
Agenda Item
4L
Document Relationships
2010-032 Planning - Professional Services Related to the Orange County Unified Development Ordinance
(Linked From)
Path:
\Board of County Commissioners\Contracts and Agreements\General Contracts and Agreements\2010's\2010
2010-032b Planning - Contract Professional Services Related to Orange County Unified Development Ordinance
(Linked From)
Path:
\Board of County Commissioners\Contracts and Agreements\General Contracts and Agreements\2010's\2010
Minutes 03-02-2010
(Linked From)
Path:
\Board of County Commissioners\Minutes - Approved\2010's\2010
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
158
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
95 <br />Issues Summary <br />A table of contents, index, cross-references, and headers and footers are referencing systems that'can <br />greatly enhance usability of long documents such as the UDO. The table of contents is often the <br />preliminary guiding tool that anchors the reader. Cross-references assist the user in identifying the relevant <br />regulations that apply to the particular use, development permit, or development proposal: Headers and <br />footers highlight the section number and topic on each page (e.g., "Sec. 1.1, Title"), allowing a reader to <br />quickly thumb through the UDO and find a section. <br />A more effective referencing approach is to include a detailed master table of contents at the beginning of <br />the UDO and a table of contents at the beginning of each article. We also recommend adding an index of <br />topics at the end of the document, with headings and cross-references that serve as guideposts to direct the <br />user to the particular topic of interest to the user. <br />Illustrate and Summarize Key Concepts <br />Another way to make a code "customer-friendly' is through illustrations, graphics, Flowcharts, and tables. <br />The old adage "a picture is worth 1,000 words" is certainly true when talking about communicating zoning <br />concepts. Illustrations, graphics, flowcharts, and tables are also very helpful in development codes because <br />they convey information concisely (and in many instances more clearly), eliminating the need for lengthy, <br />repetitive text <br />There is an opportunity to include graphics and illustrations to convey key concepts in the new UDO, such <br />as required dimensional measurementr (e.g., how to measure height)•arkin pot~landscal in band othe~ <br />illustrate preferred design concepts, such as parking space dimensions, p g P <br />landscaping and screening requirements. <br />Flow charts also add clarity to specific procedural requirements and timelines, as well as explain the <br />interrelationships between procedures. There are no Flow charts in the existing ordinance. How charts <br />are becoming commonplace in modern development regulations because of their ease of use and their <br />power to convey complex relationships. <br />Based on our experience in other jurisdictions, we have found summary tables can be very helpful in <br />presenting information succinctly and eliminating repetition and inconsistent terminology <br />Sample process flow <br />CONSOLIDATE, REFINE, AND UPDATE DEFINITIONS chart from another <br />Definitions are scattered in several sections in the existing ordinances. We recommend ~nCISdICtIOn <br />consolidating all definitions into one article so it is easy for a user to find the meaning of terms in <br />one place and to reduce the chance of redundancies or conFlicting definitions. We suggest re- <br />locatingthe definitions to the last article of the UDO, since it typically serves as a supplementary reference tool rather than a <br />primary source of regulatory information. <br />We also recommend the new code include new definitions of key terms, as well as the updating and modernizing of existing <br />definitions, as appropriate. For example, terms such as buffer, xeriscape, manufactured home, and mobile home need <br />definition. All use types identified in the code should be defined - a number of common uses in the existing ordinance are <br />not described (e.g., multi-family residential, recreational facility, commercial use, and others). <br />Finally, all definitions will be reviewed and will be written in plain English. <br />CLARIFY REVIEW STANDARDS <br />Many of the development review standards in the existing regulations are in need of revision and clarification. <br />There are also several unintended consequences in the current provisions that are resulting in development that is not <br />consistent with the town's goals. <br />Standards that are unclear invite different interpretation or application and create uncertainty for development applicants as <br />well as staff and the public. Development standards should clearly establish the community's goals for the development of a <br />Hillsborough, North Carolina Page 5 <br />Unified Development Ordinance 1 Draft Annotated Outline <br />Novembeq 2009 <br />Zoning Ordinance Text <br />& Map Amendment <br />Review Process <br />
The URL can be used to link to this page
Your browser does not support the video tag.