Lecture 4

Map Design

1. linework and lettering

- Linework: the drawn part of the map
--- includes outlines, patterns, symbols
- Lettering: the written part of the map
--- includes title, scale, explanation of map contents

2. traditional approach (until about 1975):

- use pen and ink to draw outlines, patterns
- use stencils or other means to produce lettering by hand

3. intermediate approach (until about 1985): - use pen and ink to draw outlines, patterns
- use a computer typesetter to prepare text
- paste text onto the map, "paste-up"

4. contemporary approach: - use computer for both lettering and linework.
- desktop publishing.
- web graphics design.

Computer mapping methods

Steps in making a map with a computer:

1. Gather data: base map, information to be portrayed.
2. Rough design. On a sketch, Locate title, legend etc., design symbols etc.
3. Set up map design on screen: neatline, internal boxes.
4. Use the drawing tools to trace shapes over the scanned map.
5. Discard the scanned image.
6. Add text, colours, symbols, any other features to map.
7. Print the map on paper and/or save file for further use.

Raster and Vector graphics

Two fundamentally different ways of making pictures.

Raster
- Image is made up of dots called pixels (picture elements)
--- example: 1000 lines, each with 1000 pixels = 1,000,000 pixels.
- pictures are built up by changing brightness or colour of some pixels.

Typical painting or photo-editing software work like this
examples: Corel Photopaint; Adobe Photoshop

Vector
- image is made of lines, shapes etc. defined by their coordinates.
--- line segment defined by x,y coordinates of end points
--- circle defined by coordinates of centre and radius
--- line thickness, colour etc. defined by "attribute" codes

Typical drawing, drafting and CAD software work like this
examples: Corel Draw; Adobe Illustrator

Comparison of raster and vector
- consider a drawing of a triangle:
--- raster: three lines of dark pixels on background of white pixels
------ all pixels are stored and drawn however many are actually used.
------ simple to draw and manipulate, but large file.
------ if enlarged or reduced, line becomes blurred.
--- vector: three pairs of coordinates, a few attributes for width, colour etc.
------ more complex software needed to draw it, but small file.
------ line remains sharp if picture size changes (only coordinates change)

- note: computer screen is a raster device.
- Vector drawings must be converted to raster for display.

Linework

The main graphic element of the map

- shows shapes of features (shorelines, roads etc.)

- can be varied to distinguish different features

--- solid ___________
--- broken - - - - - - - - - ...................
--- thin or thick (weight of the line)
--- patterned + + + + + + +
--- single or multiple
--- colour

Lettering

The main source of detailed information on the subject of the map

- Title - the first point of contact between cartographer and map user
- labels - placenames etc.
- explanation of symbols, other map features
- source statement - where did data come from? (if not entirely your own)
- attribution statement - who made the map?

- can be varied to distinguish features:

--- case (CAPITALS, lower case, Upper and Lower)
--- size (point size: 12 point etc.)
--- style (Times Roman, Helvetica, Billboard etc.)
--- upright or italic
--- weight (normal, bold)
--- colour

Map contents 1

1. Title

- keep it brief. Use sub-title if it helps. Give subject, place, date of subject if significant

--- example: Population of Africa in 1955

2. Neatline

- a box completely surrounding every part of the map including your name.
--- EVERY map produced for this course must be enclosed in a neatline.

3. Legend

- an explanation of symbols IF NECESSARY. Be sure to state units of measurement.

4. Scale

State units of measurement.

5. Direction indication

- North Arrow (SMALL arrow pointing north, labelled 'N' or 'north'.
- Use only if north is in the same direction in all parts of the map.

- latitude / longitude grid.
- Not needed on maps we will draw in this course.
- If it is present and labelled there is no need to use a north arrow.

- pole indicated by label.

- recognition
--- some shapes are so familiar that you can omit a north arrow or grid
--- e.g. Africa, Australia, North America, or on a world map.

Map contents 2

Titles

- Titles should be brief but complete and unambiguous.
- Subtitles often help:

TORONTO: HIGH INCOME RESIDENTIAL AREAS, 1986

Census tracts having mean annual family incomes greater than $150,000

- TITLE includes: place + subject + date

- Subtitle gives more details:

--- high = over $150,000
--- income = mean annual family income
--- areas = census tracts

Note: Unnecessary (so forbidden on grounds of inefficiency) to say 'MAP OF....' in the title (we know it's a map).

Legends.

- Use a descriptive title - "City Populations", "Mean Income" etc.
- The word 'legend' is NOT needed.
--- (Also no need for the word 'scale' near the scale bar.)
- ALWAYS state units in the scale and legend.

User friendly maps

Some maps (topographic map, city bus route map) are very complex.

- legibility, clarity, ease of use essential.

The 'user friendly' concept: - The USER of the map is more important than the CARTOGRAPHER.
--- If something needs to be done to help understand the map, YOU do it so the USER does not have to.
--- e.g. add location map to plan of a small area, to show where it is. The User does not need to consult other maps.

The 'logical relationship' concept: - make map easier to interpret without constant reference to a legend.
- establish a logical link between the features on the map and the features being represented.

--- thicker lines for more important linear features.
--- bigger text for more important labels.
--- darker patterns for more significant areas.
--- similar patterns for similar types of feature.
--- different patterns for different types of feature.
--- dramatic colours for very significant features.
--- visual cues.

Visual cues

These logical or representational similarities help the user make sense of the map:

pictorial symbols

- e.g. a picture of a lighthouse as a symbol for a lighthouse
--- a line representing a railway is drawn to look like train tracks

line style

- straight line, smooth curve for artificial feature (road, fence)
- rougher, less controlled, line for natural feature (river, coast)
--- (in the past, natural features drawn freehand, artificial ones with a ruler)
- solid line for real or permanent features
- road, coastline, permanent river
- broken line for abstract or intermittent features
--- city limits, national boundaries
--- seasonal streams, seasonal roads

Conventions

User friendly maps do NOT require the user to learn new symbols, concepts, terms for each new map.
Conventions are standardized ways of doing things. They help the map user.

Do conventions stifle creativity?

- on maps for your own use you can abandon conventions
- on maps made for others, be aware of their needs, follow conventions.
--- this still leaves many opportunities to be creative.

Some conventions include:

- use of blue for water features in colour maps
- use of green for parks in multicolour maps
- italic lettering for names of water bodies
- upright lettering for land features, map title
- broken lines for borders, city limits etc.
- METRIC MEASUREMENTS ONLY in maps for this course

Legibility

Very important - you can't use text that you can't read

Map user may not be able to read what you can
- only you know what it is supposed to say.
- Have a friend comment on legibility.

Things to avoid:
- point size too small (no smaller than 8 point usually)
- lettering crossing a line (if it must, erase line under the text)
- text over dark patterns. Erase or hide the pattern under the text.
- clutter. So much detail that the map is hard to read.
--- omit something or change the design.
--- divide it into two maps.

Map design - further considerations

1. Review:
- logical relationship between map symbols and things they represent.
- overall symmetry of design where possible.
- no large blank spaces.
- 'visual box': keep edges of map components aligned and spaces between them equal if possible.

2. Labels:
- placement of text labels:

Imhof's classic paper:

- Don't read the whole thing but look at illustrations and see how good choices make text easier to read and understand.

3. Long Names in Crowded Maps:
- Most important: label must refer clearly to its point of reference.
--- NO room for ambiguity.

- options:
--- Avoid breaking multi-word names with a line (keep on one side of a river etc.)
--- Slant or curve if necessary to fit between other labels.
--- If a label will not fit well, omit one or more labels or redraw the map at a larger scale.
--- curve or tilt names of elongated features (river, road, lake etc.) to be parallel with the objects themselves.
--- Put the name of an area IN the area if possible.
------ If not, place it beside the area.
------ Avoid breaking the boundary of the area with the label.

--- Short names for large areas may be S T R E T C H E D
------ (type a space between each letter) to fill a space better.
------ Make them bold to show up better.
--- keep other labels from interfering with the stretched label
------ (use a different "Imhof" position (location around the point the name refers to), etc.)

--- Keep labels horizontal wherever possible.
------ parallel to a grid if preferred.
------ tilt if they would interfere with an important line
------ (a coast, river, road, contour etc.)
------ if several names are tilted, tilt them the same way so they can be read without turning the map.