Autodesk 15606-011408-9330 User Guide - Page 116

Planning the Data, Planning Layers

Get Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6 PDF manuals and user guides
UPC - 606121429609
View all Autodesk 15606-011408-9330 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 116 highlights

Planning the Data In planning the data you will need, data engineers and map authors should consider the following questions along with possible solutions:  How should the data look? For example, what colors, symbols, linestyles, and fills will you use?  Does the data relate to a database table? If so, create an OLE DB data source for that database, and determine which data you will use as the key.  Is it point/text data or line/polygon data? If text, do you need to rotate or resize the text differently? Does the location of the text need to be "fixed," that is, placed precisely? You can add columns in the table that indicate the rotation angle, height, and width, so that Autodesk MapGuide® can rotate and resize the text accordingly.  Do you need to display database information thematically? If so, which column contains the theme data?  How large is the data set? Do you want to show different versions of the data, each of which is used at different display ranges?  Will you need to use raster data? Where is the raster data referenced? How is this data georeferenced? Planning Layers After you have created, gathered, converted, and prepared all of your data, authors can use it to create their maps. Remember that when you create a map and add data to it, you add the data to layers. Therefore, you need to plan the layer to which you will add the data carefully. Before you create the layer, consider the following questions:  What naming standard are you using for layers?  Do you want to organize layers into layer groups?  Do you want to use a different name in the Viewer legend? You can enter a separate name for the layer in the Legend Label box on the General tab of the Map Layer Properties dialog box. This is useful if you want to have long descriptive names appear in the Design tab of the Autodesk MapGuide Author Map Explorer when you're working with the map, but you want shorter names to appear for Autodesk MapGuide Viewer users. 116 | Chapter 6 Planning and Designing Maps

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
116
|
Chapter 6
Planning and Designing Maps
Planning the Data
In planning the data you will need, data engineers and map authors should
consider the following questions along with possible solutions:
How should the data look? For example, what colors, symbols, linestyles,
and fills will you use?
Does the data relate to a database table? If so, create an OLE DB data source
for that database, and determine which data you will use as the key.
Is it point/text data or line/polygon data? If text, do you need to rotate or
resize the text differently? Does the location of the text need to be
“
fixed,
”
that is, placed precisely? You can add columns in the table that indicate
the rotation angle, height, and width, so that Autodesk MapGuide
®
can
rotate and resize the text accordingly.
Do you need to display database information thematically? If so, which
column contains the theme data?
How large is the data set? Do you want to show different versions of the
data, each of which is used at different display ranges?
Will you need to use raster data? Where is the raster data referenced? How
is this data georeferenced?
Planning Layers
After you have created, gathered, converted, and prepared all of your data,
authors can use it to create their maps. Remember that when you create a
map and add data to it, you add the data to layers. Therefore, you need to
plan the layer to which you will add the data carefully. Before you create the
layer, consider the following questions:
What naming standard are you using for layers?
Do you want to organize layers into layer groups?
Do you want to use a different name in the Viewer legend? You can enter
a separate name for the layer in the Legend Label box on the General tab
of the Map Layer Properties dialog box. This is useful if you want to have
long descriptive names appear in the Design tab of the Autodesk
MapGuide Author Map Explorer when you
’
re working with the map, but
you want shorter names to appear for Autodesk MapGuide Viewer users.