Feature tiling modes available to feature layers. This determines how feature tiling is handled for each layer. Using the default mode is highly recommended. As of now, only services based on service feature tables support feature tiling.
public enum FeatureTilingMode
Feature tiling is disabled.
When in this mode, feature tiling will not be used even if a service supports it. This reduces the number of requests sent by each layer. Disabling feature tiling results in less features returned from a service.
Use feature tiling whenever a service supports it. Feature tiling retrieves more features per layer from a service by making multiple, smaller requests to said service. Since each request gathers a portion of the total features, this allows more features to be rendered in the extent than what the MaxRecordCount would normally allow.
When in this mode, all rendering requests to services will use feature tiling unless the following applies: FeatureRequestMode is ManualCache, the service does not support coordinate quantization, or if the service does not support tile result types. This is the default mode.
Use feature tiling and request full resolution geometries when supported by the service. If the latter is not supported, EnabledWhenSupported is used instead.
This mode requires the service to support the edit quantization mode, which returns all vertices of the source geometry in a high resolution. Use this mode for workflows that benefit from precise geometry editing, such as snapping feature geometries, without loading the feature. This mode may impact performance due to the increase in network traffic.
|.NET Standard 2.0||100.10 - 200.3|
|.NET||100.13 - 200.3|
|.NET Windows||100.13 - 200.3|
|.NET Android||200.0 - 200.3|
|.NET iOS||200.0 - 200.3|
|.NET Framework||100.10 - 200.3|
|Xamarin.Android||100.10 - 100.15|
|Xamarin.iOS||100.10 - 100.15|
|UWP||100.10 - 200.3|