Class FeatureCollectionLayer

A layer that can visualize a FeatureCollection.

Inheritance

Object

Layer

FeatureCollectionLayer

Implements

INotifyPropertyChanged

ILoadable

ILayerContent

Layer.LoadAsync()

Layer.CancelLoad()

Layer.RetryLoadAsync()

Layer.LoadStatus

Layer.LoadError

Layer.Item

Layer.Attribution

Layer.Description

Layer.MaxScale

Layer.MinScale

Layer.SpatialReference

Layer.Opacity

Layer.Id

Layer.FullExtent

Layer.Clone()

Layer.CanChangeVisibility

Layer.IsVisible

Layer.IsIdentifyEnabled

Layer.Name

Layer.ShowInLegend

Layer.SublayerContents

Layer.GetLegendInfosAsync()

Layer.IsVisibleAtScale(Double)

Layer.PropertyChanged

Layer.OnPropertyChanged(String)

Layer.Loaded

Layer.LoadStatusChanged

Object.Equals(Object)

Object.Equals(Object, Object)

Object.GetHashCode()

Object.GetType()

Object.MemberwiseClone()

Object.ReferenceEquals(Object, Object)

Object.ToString()

Namespace: Esri.ArcGISRuntime.Mapping

Assembly: Esri.ArcGISRuntime.dll

Syntax

public sealed class FeatureCollectionLayer : Layer, INotifyPropertyChanged, ILoadable, ILayerContent

Remarks

A feature collection groups logically-related tables of features even though they may have different schema, geometry types, and symbology. A feature collection layer allows multiple tables with different schemas to be managed as a group.

Functional characteristics

Sketch information (called Map Notes in ArcGIS Online), may contain points, lines, polygons, and associated text to describe things in the map. Because they have different schema and geometry types, these features are stored in several distinct tables. A feature collection layer allows these tables to be rendered and managed as a group.

A feature collection can be saved in the map or as a stand-alone portal item. If you need to share the feature collection between several maps, it's best to store it as a separate portal item. If you need to make frequent (near real-time) edits to features in a collection, consider storing these in a feature service instead, because the feature collection is not refreshed until the map or portal item is reloaded. If features are used by a single map or are not subject to frequent updates, it might be best to store them directly in the map. Edits made to features stored in a map will be saved when the map is saved. Edits made to features stored in a portal item (and loaded into a map, for example) must be explicitly saved to the original portal item.

Performance characteristics

Feature collection layers are designed to display a moderate amount of feature data (hundreds or thousands of features). They are ideal for sharing static data (not subject to frequent updates) among several clients.

As full feature information is cached locally in a geodatabase and features are drawn natively, this layer type offers excellent display performance when zooming and panning the map, within the extent of cached features.

Downloading features to the device may require extensive network usage and local device storage space. After the features are present on the client, the app no longer needs to make requests for the data. App memory usage increases with the number and complexity of the features in the collection.

Sample Code:

Constructors

Name	Description
FeatureCollectionLayer(FeatureCollection)	Initializes a new instance of the FeatureCollectionLayer class.

Properties

Name	Description
FeatureCollection	Gets the feature layers associated with this layer.
Layers	Gets the feature layers associated with this layer.

Applies to

Target	Versions
.NET Standard 2.0	100.3 - 100.14
.NET 6.0	100.13 - 100.14
.NET 6.0 Windows	100.13 - 100.14
.NET Framework	100.0 - 100.14
.NET 5	100.10 - 100.12
.NET Core 3.1	100.7 - 100.12
Xamarin.Android	100.0 - 100.14
Xamarin.iOS	100.0 - 100.14
UWP	100.0 - 100.14