Autodesk 15606-011408-9320 User Guide - Page 106

Under normal circumstances, features on a VISION* theme layer will not have names or URL links associated with them. This is because the VISION* cache does not contain this information for each feature in the theme. If you need to have names or URLs associated with the features, you could create a custom utility to export the VISION* features from the database to an SDF file or OLE DB data source. For example, you could use Visual Basic with VISION* 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 VISION* 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 VISION* features. The keys of map features on VISION* theme layers are formed from a composite of the original VISION* 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 Note The version mode number used in the key is different from the version number associated with a feature in the VISION* database. The version mode number indicates whether the feature is from the VISION* permanent version or from one of the more recent versions, as defined in the following table. Version Mode Value 0 1 Description Permanent version. Always version number 0 in the VISION* database. A recent version. The most recent version number in relation to when the theme was generated. 106 | Chapter 5 Working with Data in Autodesk MapGuide