| Use strong visual variables (saturated colors, thick lines, solid patterns, for example) to emphasize the important parts of a map. Use weaker visual variables (light, unsaturated colors, thin and dashed lines, sparse patterns) for the background material in a map. In short, let the map's purpose determine how the map will be displayed. | |
| Whenever possible, create maps that work even when rendered in black and white. | |
| Avoid labeling a map until as late in the map creation process as possible. Get everything else right first. | |
| Do not use labels in place of symbols. A map is for displaying the patterns of underlying data. When you want to present numerical or text data, put it into tables. | |
| In ArcView, separate the function of mapping the data from the function of decorating the map. The view is for mapping the data. The layout is for decorating the map. |
You can use much more than changes of color to distinguish geographic objects on a map. Commonly recognized visual variables include
| symbol size | |
| shape | |
| orientation | |
| texture | |
| color hue, value, and saturation | |
| location |
Complex symbols, such as those representing polygonal shapes, can be combinations of two or more symbols, such as one symbol for the interior and another for the outline, thereby multiplying the options available for distinguishing symbols.
Using a map to display data means determining how the data will be used to modify the values of the visual variables. Since in many cases the data are first classified, the nature of the map is specified by associating visual variables with the classifications.
ArcView's Symbol Window provides an interface for modifying these visual variables. The symbol window is opened from the Window menu, using the ctrl-P keyboard shortcut (question: how could you have determined the shortcut by yourself?), or by double-clicking on a classification symbol within the Legend Editor.
Exercises 10a and 10b ask you to modify the symbolization of themes in a View to create a more effective map. For these exercises it will be useful to begin with views already created for you. Here are the steps to follow:
Experiment with choices of the visual variables to improve the map you produce while working exercises 10a and 10b.
Here are some additional thought questions:
Can you develop some principles for visual display of maps? Here are some things to look for:
![]()
As you will learn, there are at least four different ways to make a mark on a map in ArcView:
You have learned #1. Exercise 10c shows how to create labels in a view using ArcView's Auto-label tool (#2) and using the Text tool (#3).
| Creating and, especially, positioning labels on a map can be time consuming for any software. One trick in ArcView is to position the view so that most features to be labeled are outside the view's extent (the visible area): this greatly speeds up the process. See Chapter 12 for ways of changing a view's extent. | |
| Labeling is always tricky. Labels must be positioned, symbolized, and sized to avoid obscuring important map features. None of this information about position, symbol, or size is contained in the thematic data; if something is not quite right, you might have hours or days of work to redo. Therefore avoid labeling a map until as late in the map creation process as possible. Get everything else right first. | |
| Do not use labels in place of proper symbols. A map displays the patterns of underlying data much better through an appropriate symbolization than by posting the values with labels. If you have to use labels, you might be better off just making a table of the data. | |
| A View is an image, albeit imperfect, of objects in the "real world." Therefore avoid drawing things in a View that are really just map artifacts: things like scale bars, legends, miscellaneous texts, north arrows, and so on. In ArcView, the proper place to put such ancillary "paper world" objects is the Layout (Chapter 22). |
![]()
This page was last updated 12 March 2004. It was reformatted. The "Summary of principles" section was added. Minor editorial changes were made to clarify portions of the text.