Autodesk 15606-011408-9008 User Guide - Page 113
Using URL Links, Parsing Map Feature Keys
UPC - 606121429517
View all Autodesk 15606-011408-9008 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 113 highlights
Using URL Links You can display the name of a map feature in Autodesk MapGuide by pausing the mouse over the feature. The name then displays in a small yellow rectangle called a MapTip. Also, if a map feature has a URL associated with it, the pointer changes from an arrow to a hand when the mouse passes over that feature, allowing the user to double-click and open the Web page specified by that URL. Under normal circumstances, features on an Autodesk GIS Design Server theme layer will not have URL links associated with them. This is because the Autodesk GIS Design Server cache does not contain this information for each feature in the theme. If you need to have URLs associated with the features, you could create a custom utility to export the Autodesk GIS Design Server features from the database to an SDF or OLE DB data source. For example, you could use Visual Basic with Autodesk GIS Design Server Objects and the SDF Component Toolkit. This kind of utility is beyond the scope of this documentation and should be implemented by a system administrator who is familiar with Autodesk GIS Design Server and Autodesk MapGuide. Parsing Map Feature Keys If you will be developing reports, it is important to know how to parse the keys for the map feature so that you can get information about the original Autodesk GIS Design Server features. The keys of map features on Autodesk GIS Design Server theme layers are formed from a composite of the original Autodesk GIS Design Server Feature, Plan, Version Mode, Layer, and Network numbers, with a vertical bar (|) character delimiting each of the numbers as follows: F|||| For example, if the feature # is 967, plan # is 5, version mode # is 0, layer # is 20, and network # is 7, the key for the map feature will be the following string: F967|5|0|20|7 Working with Other Types of Spatial Data | 113