Autodesk 15606-011408-9320 User Guide - Page 115

General Guidelines, AutoCAD Map User, s Guide

Page 115 highlights

General Guidelines Following is a list of guidelines you should consider when designing your map.  The map should be made up of elements of nearly equal size with no fea- tures dominating the map. Text size should be neither too small to read nor so large that the text dominates or obscures features.  Use different symbols to represent different features. For example, you can use symbols to represent landmarks, such as hospitals, churches, and cemeteries. Draw symbols at an appropriate scale so they are legible and do not obscure other data.  Use line type and colors to represent different features. Representing roads as double lines can be helpful for small areas, such as subdivisions, or for maps in which right-of-way information is important.  Do not use an excessive number of colors. Otherwise, the map becomes too bright and the colors dominate. Try to limit the map to four colors.  If you are not using themes, use one color per layer. For example, if you have an SDF that contains roads and highways, and you want to draw them in different colors, it's usually best to create a separate roads layer and highway layer and apply one color to each. The other option is to create one layer and create theme categories for roads and highways on that layer, applying the colors you want to the theme categories. However, this approach can decrease performance.  Make layers selectable only if necessary. Always ask yourself whether the data on this layer is there to help orient the user on the map or contains features the user needs for retrieving information. If it's there for orientation, such as lakes and parks in a parcel map, make the layer unselectable.  Do not try to present too much data on the map at once. Maps are more effective when they show topics clearly. Always set up the map so that only the most necessary layers are turned on when the user first accesses the map; this also speeds up the initial loading of the map. The user can then turn on additional layers to get more information as needed. For more information about designing and creating the features that appear on the map, refer to the documentation for the program you are using to create map data, such as the AutoCAD Map User's Guide. Designing the Map | 115

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

Designing the Map
|
115
General Guidelines
Following is a list of guidelines you should consider when designing your
map.
The map should be made up of elements of nearly equal size with no fea-
tures dominating the map. Text size should be neither too small to read
nor so large that the text dominates or obscures features.
Use different symbols to represent different features. For example, you can
use symbols to represent landmarks, such as hospitals, churches, and cem-
eteries. Draw symbols at an appropriate scale so they are legible and do
not obscure other data.
Use line type and colors to represent different features. Representing roads
as double lines can be helpful for small areas, such as subdivisions, or for
maps in which right-of-way information is important.
Do not use an excessive number of colors. Otherwise, the map becomes
too bright and the colors dominate. Try to limit the map to four colors.
If you are not using themes, use one color per layer. For example, if you
have an SDF that contains roads and highways, and you want to draw
them in different colors, it
s usually best to create a separate roads layer
and highway layer and apply one color to each. The other option is to
create one layer and create theme categories for roads and highways on
that layer, applying the colors you want to the theme categories. However,
this approach can decrease performance.
Make layers selectable only if necessary. Always ask yourself whether the
data on this layer is there to help orient the user on the map or contains
features the user needs for retrieving information. If it
s there for orienta-
tion, such as lakes and parks in a parcel map, make the layer unselectable.
Do not try to present too much data on the map at once. Maps are more
effective when they show topics clearly. Always set up the map so that
only the most necessary layers are turned on when the user first accesses
the map; this also speeds up the initial loading of the map. The user can
then turn on additional layers to get more information as needed.
For more information about designing and creating the features that appear
on the map, refer to the documentation for the program you are using to
create map data, such as the
AutoCAD Map User
s Guide
.