FeatureRequestMode

The features are requested from the server by an explicit call to ServiceFeatureTable.populateFromService, which populates the local cache. Queries performed on the table will be executed locally. In this mode, the features have all fields defined by the MutableList of String you pass to ServiceFeatureTable.populateFromService.

The features are requested from the server as they are needed, in response to user or developer interaction with the layer (pan, zoom). Features are cached in the local table for the duration of the session. Queries are executed on the local cache or (if requested features are not resident in the cache) on the server. This mode is the default. In this mode, features have a minimum set of attributes, and feature geometries have no m-values even if m-values are defined by the service. This is an optimization for faster rendering. To access all attributes or access geometries that contain m-values, the features you get from a query must be loaded. You can load them yourself or request that the query method return them already loaded (see QueryFeatureFields.LoadAll). For more information, see the class description for ServiceFeatureTable.

The features are always requested from the server and are never cached. This mode ensures that you are working against the latest data, but it has a high network bandwidth since it goes to the server for all interactions (pans, zooms, selects, or queries). In this mode, features have a minimum set of attributes, and feature geometries have no m-values even if m-values are defined by the service. This is an optimization for faster rendering. To access all attributes or access geometries that contain m-values, the features you get from a query must be loaded. You can load them yourself or request that the query method return them already loaded (see QueryFeatureFields.LoadAll). For more information, see the class description for ServiceFeatureTable.

Indicates the feature table has not been loaded and the mode has yet to be set.