Autodesk 15606-011408-9320 User Guide - Page 108

Primitives and Styles Simulated Using Polylines, Working with Data in Autodesk MapGuide

Page 108 highlights

Differences in Clipping VISION* supports a clipping primitive that is occasionally used to avoid drawing in areas where annotations might later be drawn. For example, when labeling a line, a clip area might be defined over the area where the label will appear, creating a gap where the label will be drawn. Although lines will be clipped by such a region, PostScript and TrueType fonts and polygons will not be clipped. Therefore, some maps might display differently in Autodesk MapGuide. Primitives and Styles Simulated Using Polylines To account for feature geometry and style model differences between VISION* and Autodesk MapGuide, several primitives and styles will be simulated in Autodesk MapGuide using polylines. Scale-Dependent Symbology Displayed as Fixed Some scale-dependent VISION* symbology (for example, line thickness) is displayed in Autodesk MapGuide at a fixed scale. In this case, the scale will be correct when the symbology is initially displayed in Autodesk MapGuide, but as the user zooms, the lines will not get thicker. Polygons Obscuring Non-Polygons When a map has two or more VISION* theme layers, and the themes contain features composed of polygon primitives and other feature types such as annotations, some of the polygon primitives from the upper layers may obscure the non-polygonal features and annotation from the lower layers. You can reconstruct your VISION* cache using separate themes for polygons and other feature types such as annotations, which will allow you to display the polygons separately on a layer lower in the display order than the annotation layer. You need to plan the display order of layers carefully, in order to minimize the effect of features from upper layers obscuring those on lower layers. 108 | Chapter 5 Working with Data in Autodesk MapGuide

  • 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

108
|
Chapter 5
Working with Data in Autodesk MapGuide
Differences in Clipping
VISION* supports a clipping primitive that is occasionally used to avoid
drawing in areas where annotations might later be drawn. For example,
when labeling a line, a clip area might be defined over the area where the
label will appear, creating a gap where the label will be drawn. Although lines
will be clipped by such a region, PostScript and TrueType fonts and polygons
will not be clipped. Therefore, some maps might display differently in
Autodesk MapGuide.
Primitives and Styles Simulated Using Polylines
To account for feature geometry and style model differences between
VISION* and Autodesk MapGuide, several primitives and styles will be simu-
lated in Autodesk MapGuide using polylines.
Scale-Dependent Symbology Displayed as Fixed
Some scale-dependent VISION* symbology (for example, line thickness) is
displayed in Autodesk MapGuide at a fixed scale. In this case, the scale will
be correct when the symbology is initially displayed in Autodesk MapGuide,
but as the user zooms, the lines will not get thicker.
Polygons Obscuring Non-Polygons
When a map has two or more VISION* theme layers, and the themes contain
features composed of polygon primitives and other feature types such as
annotations, some of the polygon primitives from the upper layers may
obscure the non-polygonal features and annotation from the lower layers.
You can reconstruct your VISION* cache using separate themes for polygons
and other feature types such as annotations, which will allow you to display
the polygons separately on a layer lower in the display order than the anno-
tation layer. You need to plan the display order of layers carefully, in order to
minimize the effect of features from upper layers obscuring those on lower
layers.