This document is archived and information here might be outdated. Recommended version. |
Provides access to the Map Server Identify Result Interface.
Use IMapServerIdentifyResult to access properties of map features returned as a result of using the IMapServer Identify method.
Name | Description | |
---|---|---|
LayerID | The layer ID of the identified object. | |
Name | The name of the identified object. | |
Properties | A set of name-value pairs for the field names and values of the identified object. | |
RelatedRows | The related rows (relationships) of the identified object. | |
Shape | The geometry of the identified object. |
Classes | Description |
---|---|
MapServerIdentifyResult | The Map Server Identify Result coclass provides information about an 'identify result'. |
MapServerIdentifyResult include a number of properties. Name returns the value of the primary display field for the feature. Properties returns a set Field-value pairs. These are returned as strings. This also includes the Shape field. To get geometry do not use the Shape field contained within the Properties' field-value pairs, use the Shape property instead. MapServerIdentifyResult honors field formating, field visibility and field aliases set in the source map document or in the GeoDatabase. If you are interested in information about the layer that the feature belongs to you can use LayerID.
A layer can be related to a table. RelatedRows returns a collection of MapServerRelationship objects. IMapServerRelationship contains the name of the relate and Rows . This property returns a collection of MapServerRow objects. Using IMapServerRow you can access properties (Name, PropertySet and RelatedRows) of the row of a related table.
In order to control the amount of information MapServer needs to process for a query, a maximum number of records can be set. This value is contained in the MaxRecordCount property on IMapServerInit2. The default value for this property is 500. If 600 features match a given query only the first 500 results will be returned. You will be unable to access the remaining 100 records. To be able to access these records the MaxRecordCount would need to be increased to 600. The number of rows of a relationship returned is not limited by MaxRecordCount.