Autodesk 15606-011408-9320 User Guide - Page 107
Discrepancies in the Data Conversion, Working with Other Types of Spatial Data
UPC - 606121429586
View all Autodesk 15606-011408-9320 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 107 highlights
Discrepancies in the Data Conversion This section provides additional information about how VISION* features are converted and displayed in Autodesk MapGuide. Differences in the Feature Geometry and Symbology Models Because of differences in the feature geometry model between VISION* and Autodesk MapGuide, there are small differences in the way features are drawn. These differences include the following: Each VISION* polypolyline and polypolygon can contain up to 2048 indi- vidual polylines or polygons, with maximum total vertices of 16384. If the total vertices in a polypolyline or polypolygon exceeds 16384, the feature will be generalized, and the number of vertices will be reduced to save space. VISION* symbols are drawn as polylines. VISION* markers are drawn as polylines. VISION* circles are drawn as polylines. Likewise, because of differences in the symbology models between the two products, there are small differences in the way features are styled when drawn. These include the following: VISION* colors are mapped to the closest available Autodesk MapGuide color. Text drawn using the VISION* PostScript and TrueType fonts that are not available to the Autodesk MapGuide clients are drawn using the default SYSTEM font. Complex VISION* line styles are drawn using the closest available Autodesk MapGuide line style. Complex polygon hatch styles are filled using the closest available Autodesk MapGuide hatch style or a series of polylines. To improve performance, you can choose colors, line styles, and hatch styles in your VISION* themes that map directly to those in Autodesk MapGuide, and use common TrueType fonts instead of the VISION* vector fonts. Working with Other Types of Spatial Data | 107