|
The use of graphics is
<br />increasing, particularly as design
<br />guidelines become more common.
<br />Graphics convex, messages that
<br />words alone cannot. Graphics can
<br />be hand-drawn and pasted into the
<br />text; they can be hand-drawn, and
<br />the image scanned to create a
<br />computer graphics file that can be
<br />imported and positioned into thc
<br />text; or they can be computer-
<br />drawn using graphics software and
<br />imported and positioned into the
<br />text. The latter produces the most
<br />consistent qualJD'. The swle of
<br />computer graphics is much easier
<br />for other staffto duplicate for
<br />subsequent code amendments.
<br /> Language S.rvte. The rules of
<br />good grammar and punctuation
<br />apply. If there are questions,
<br />consult The Elemenu of So, lc by
<br />William Strunk, Jr., and E.B.
<br />SS/hire, a classic text on plain
<br />English. A few key ideas to
<br />remember: keep the language style
<br />simple and to the point, use lists
<br />instead of text, avoid words with
<br />double meanings, use common
<br />terms rather than inventing new
<br />ones, and avoid jargon.
<br /> The way in which certain terms
<br />and punctuation are used in the
<br />zoning code should be established
<br />in the general provisions. Define
<br />terms like "would?' "should." and
<br />"sba}F; how the words "and" and
<br />"or" are used; how the use of
<br />
<br /> Improving Tables and Graphics
<br />
<br />For tables:
<br />· Hold to an estabtisi~ed format throughout the enure zoning
<br /> code. Consider using a smaller p,,'pe size.
<br />i~ Use grids. They help transpose in£ormation across a column or
<br /> row. particular}), for large tab}es.
<br />· For use-classification tables, usc abbreviations in the boxes, such
<br /> as "P" for permitted and "CUP" for conditional use permit.
<br /> Leave the "Not Permitted" boxes blank to avoid clutter, include
<br /> a legend.
<br />· ]£a table includes more than one page, successive pages should
<br /> include complete coiunm titles and legends. Use "Cottmtuedan
<br /> next page' and 'Continued from prewous page "when
<br /> appropriate.
<br />· Use portrait rather than landscape format. Using both is
<br /> awkward.
<br />· Create and label major land-use groupings. Separate them with
<br /> blank spaces. Aiphabetize land uses. Put the most used
<br /> development regulations ar the beginning of the table.
<br />· include a separate column for "additional regulations." Use
<br /> footnotes or reference code sections in this column.
<br />
<br />For graphics:
<br />· Keep images simple. Use shading for highlights. Use scale for
<br /> realism and avoid abstract illustrations. Use a consistent graphic
<br /> sD, lc.
<br />· Text and accompanying graphics should appear on the same or
<br /> opposing page. incorporate labeling that uses the exact words
<br /> found in the accompanying text.
<br />· Usc graphics that show "Unacceptable" and "Acceptable"
<br /> examples.
<br />· Many users have difficukv reading "plan views." For example,
<br /> most people can visualize an oblique perspective showing the
<br /> standards for residential fences much better than the)' can
<br /> visuaiize a plan view.
<br />
<br />punctuation affects the meaning of words and phrases; and how
<br />common meaning rules apply.
<br /> It is important that terms not be mixed with others having
<br />the same meaning. For example, either "apartments': or
<br />"mu}dfami}y" should be used, but not both.
<br /> One easih, avoided trap is the use of legal jargon. Some codes
<br />still use it extensively. "Therefore," "nonvithstanding," and
<br />"herein" are terms that should be used sparingi)', if at all. A
<br />
<br />Zoning News is a monthly newsietter published by the American Planning
<br />Association. Subscriptions are available for S45 (U.S.) and 554 fforeignL
<br />Michael B. Barke~. Executive Director: Frank S. So. Deputy Executive Director:
<br />~qlliam R. Klein, Director of Research.
<br />
<br />Zoning News is produced a~ APA. Jim Schwab, Editor; Michael Barrette. Dan Biver,
<br />Sarah Bohien. Fa)' Doinick. Michelle Gregory, Alissa Hammer, Saniay Jeer. Marya
<br />Morris. Reporters; Cynthia Cheski, Assistant Edimr~ Lisa Barton. Design and
<br />Production.
<br />Copyright 01994 by American Planning Association, 1313 E. 60th St.. Chicago, IL
<br />60637. The American Planning Association has headquarsers offices at 1776
<br />Massachusetts Ave., N.W.. Washingrom DC 20036.
<br />
<br />Ail rights reserved. No part of this put, iicauon ma:,' be reproduced or utilized in any
<br />form or bt, any means, electronic or mechanical, inciuding photocopying, recording,
<br />or b?' an?' information storage and retrieval system, without permission in writing
<br />from the American Planning Association.
<br />
<br />Printed on recycled paper, including 50-7030 ~ec)'cled fiber
<br />
<br />graphic should accompany
<br /> text that is unavoidably
<br />.complicated.
<br /> Avoid double
<br />referencing. One example:
<br />"A"o accesso~., building sba/~
<br />exceed a height ~f ru,e/t,c
<br />(12)feet. or filSee,
<br />where a mi,tmum rooJ~itc/,
<br />of three O).ket i, zu,dvc
<br />(]2)feet is provided. "Use
<br />the numerical expression
<br />and never write out
<br />numbers except for the
<br />number one. It Js much
<br />easier to spot a number on
<br />a page of text than to find
<br />that number in text form.
<br /> Numbering. Before
<br />deciding on a numbering
<br />system, consult with your
<br />legal counsel. You may be
<br />relegated to following the
<br />numbering system
<br />established by the local
<br />government code. Even
<br />so, there may be room for
<br />fiexibiliw.
<br /> The general rule is to
<br />keep the numbering
<br />system simple and allow
<br />(or future amendments.
<br />As additions occur, most
<br />systems require that new
<br />sections include a
<br />decimal, In some cases,
<br />further additions require
<br />additional decimals. For
<br />
<br />example, a new section added after Section 1 50 is numbered
<br />Section 150.1. A new section added after Section 150.! must
<br />be numbered Section 150.1.1.
<br /> Over time, a zoning code's origina} organization and
<br />numbering system may become needless}), complicated because
<br />of misplaced and compound amendments. In numbering a new
<br />code, allow room between sections for future additions. Using
<br />the above example, Section 150 is part of a numbering sequence
<br />that continues with Sections 160, 170, 180, and so on. This
<br />number sequencing allows nine new sections ro be added
<br />without the use of decimals. Showing unused numbers as
<br />reserved ("Sections 16]-169 reserved for farure use") is
<br />superfluous and can add substantially to the code's length.
<br />Subsections should use uppercase letters followed by numbers
<br />for subordinate subsections, for example, Secrio, 24-]02. A. This
<br />avo/ds conflicts with section numbers.
<br /> Finally, man)' zoning codes cite ordinance numbers,
<br />amendments, and dates in the footer. Consider placing this
<br />information at the end of each section because it is the section
<br />that is amended, not the page. The information should include
<br />reference to the ordinance number and a date (for example,
<br />Amena'ed by Ordinance No. 8754' on Ma). 15, 1994).
<br /> Next month, Zoni,g ]Vews will deal with specific content
<br />issues, printing and binding, zoning maps, and computerizing
<br />the zoning code.
<br />
<br />
<br />
|