Browse
Search
2010-032b Planning - Contract Professional Services Related to Orange County Unified Development Ordinance
OrangeCountyNC
>
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
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/15/2018 8:29:29 AM
Creation date
3/29/2010 11:23:00 AM
Metadata
Fields
Template:
Contract
Date
3/2/2010
Contract Starting Date
3/2/2010
Contract Ending Date
12/17/2010
Contract Document Type
Agreement - Services
Agenda Item
4l
Amount
$30,000.00
Document Relationships
Agenda - 03-02-2010 - 4l
(Linked To)
Path:
\Board of County Commissioners\BOCC Agendas\2010's\2010\Agenda - 03-02-2010 - Regular Mtg.
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
Issues Summary <br /> Zoning Ordnance Text <br /> A table of contents, index, cross-references, and headers and footers are referencing systems that can &Map Amendment <br /> greatly enhance usability of long documents such as the UDO. The table of contents is often the Review ProCen <br /> preliminary guiding tool that anchors the reader. Cross-references assist the user in identifying the relevant Pr�nlreyCone itMeedng <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. ""°�'c°d° "° <br /> A more effective referencing approach is to include a detailed master table of contents at the beginning of AvPieadon <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 /> R°Nalon of Plans and <br /> Illustrate and Summarize Key Concepts PAS46mitw(ffrcquk" . <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 concise) (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 measurements (e.g., how to measure height). Graphics can also be used to BOMA First Reading of <br /> illustrate preferred design concepts, such as parking space dimensions, parking lot landscaping, and other ' • ' <br /> landscaping and screening requirements. <br /> BOMA Public Hearing and _11� <br /> Flow charts also add clarity to specific procedural requirements and timelines, as well as explain the Second Reading of Appr.1ed <br /> Ordinance <br /> interrelationships between procedures. There are no flow charts in the existing ordinance. Flow charts <br /> are becoming commonplace in modern development regulations because of their ease of use and their <br /> power to convey complex relationships. BOMA Third and Final Reading �5 <br /> ofApproycd Ordinance <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 Y swee wan R°vi°w or Bulld'nY , <br /> Fermis <br /> CONSOLIDATE, REFINE, AND UPDATE DEFINITIONS Sample process flow <br /> Definitions are scattered in several sections in the existing ordinances. We recommend chart from another <br /> consolidating all definitions into one article so it is easy for a user to find the meaning of terms in jurisdiction <br /> one place and to reduce the chance of redundancies or conflicting definitions. We suggest re- <br /> locating the 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 <br /> Unified Development Ordinance I Draft Annotated Outline Page 5 <br /> November,2009 <br />
The URL can be used to link to this page
Your browser does not support the video tag.