Autodesk 15606-011408-9320 User Guide - Page 95

Setting Up Your Attribute Database, Setting Up Your Data

Page 95 highlights

When setting up your attribute data, you should consider whether you will be creating themes, and whether the data in the table lends itself easily to this task. For example, for a roads layer, do you already have a column that contains the text "Interstate" or "City Street" for each feature in the table? If so, it will be very simple to specify this column as the theme column and specify that if the column contains "Interstate", the feature will be drawn as a thick yellow line, and if the column contains "City Street", the features will be drawn as a thin black line. However, if you want your roads to be drawn in such a way as to show how heavy the traffic is, a column indicating whether it's an interstate highway or city street will not be useful-you will need a column that indicates how much traffic each road has. You can then use this third column to specify how the roads are drawn to show traffic. For example, you might create four theme categories: fewer than 200 cars per month, between 201 and 5,000, between 5,001 and 10,000, and greater than 10,000. You can then specify the display attributes separately for each of these categories, so that roads with the lightest traffic are drawn in thin black lines and roads with heaviest traffic are drawn in thick red lines, and so on. If you are using point or text data, you need to consider which symbols you will want to use for each theme category. For more information, see "Working with Symbols" on page 104. Setting Up Your Attribute Database You need to take the following points into consideration when setting up your attribute database:  Before Autodesk MapGuide can use your databases, you must set them up and configure them as OLE DB data sources. See "Setting Up Your Data Sources" on page 74 for more information.  You can limit users' access to data sources by setting up passwords for users or for groups or by assigning access keys to the resource.  When naming your attribute data sources, avoid using the ampersand (&) in the names of databases, tables, and columns. This character is unsupported in all names in Autodesk MapGuide, including SDF names, layer names, user names, access keys, tracking IDs, and passwords.  Make sure that the fields containing the coordinates, keys, names, and URLs are all in the same table, view, or query in the OLE DB data source. Your theme data can be located in a different table, but it must contain keys that match those in the source data. Working with Attribute Data | 95

  • 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

Working with Attribute Data
|
95
When setting up your attribute data, you should consider whether you will
be creating themes, and whether the data in the table lends itself easily to
this task. For example, for a roads layer, do you already have a column that
contains the text
Interstate
or
City Street
for each feature in the table? If
so, it will be very simple to specify this column as the theme column and
specify that if the column contains
Interstate
, the feature will be drawn as
a thick yellow line, and if the column contains
City Street
, the features will
be drawn as a thin black line. However, if you want your roads to be drawn
in such a way as to show how heavy the traffic is, a column indicating
whether it
s an interstate highway or city street will not be useful
you will
need a column that indicates how much traffic each road has. You can then
use this third column to specify how the roads are drawn to show traffic.
For example, you might create four theme categories: fewer than 200 cars per
month, between 201 and 5,000, between 5,001 and 10,000, and greater than
10,000. You can then specify the display attributes separately for each of
these categories, so that roads with the lightest traffic are drawn in thin black
lines and roads with heaviest traffic are drawn in thick red lines, and so on.
If you are using point or text data, you need to consider which symbols you
will want to use for each theme category. For more information, see
Working with Symbols
on page 104.
Setting Up Your Attribute Database
You need to take the following points into consideration when setting up
your attribute database:
Before Autodesk MapGuide can use your databases, you must set them up
and configure them as OLE DB data sources. See
Setting Up Your Data
Sources
on page 74 for more information.
You can limit users
access to data sources by setting up passwords for users
or for groups or by assigning access keys to the resource.
When naming your attribute data sources, avoid using the ampersand (&)
in the names of databases, tables, and columns. This character is unsup-
ported in all names in Autodesk MapGuide, including SDF names, layer
names, user names, access keys, tracking IDs, and passwords.
Make sure that the fields containing the coordinates, keys, names, and
URLs are all in the same table, view, or query in the OLE DB data source.
Your theme data can be located in a different table, but it must contain
keys that match those in the source data.