Class FeatureCollectionLayer

All Implemented Interfaces:
LayerContent, Loadable

public final class FeatureCollectionLayer extends Layer
A layer that can visualize a feature collection.

A feature collection provides a way of grouping logically-related tables of features. Tables in the collection can 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 data that is 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. Once 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.

Related samples

See Also:
  • Constructor Details

    • FeatureCollectionLayer

      public FeatureCollectionLayer(FeatureCollection featureCollection)
      Creates a FeatureCollectionLayer from a FeatureCollection.
      featureCollection - the FeatureCollection to visualize with this FeatureCollectionLayer
      IllegalArgumentException - if featureCollection is null
  • Method Details

    • getItem

      public Item getItem()
      Description copied from class: Layer
      Gets the Item associated with this layer.
      getItem in class Layer
      the associated Item or null if this layer is not associated with an Item
    • getFeatureCollection

      public FeatureCollection getFeatureCollection()
      Gets the FeatureCollection visualized by this FeatureCollectionLayer.
      the FeatureCollection visualized by this FeatureCollectionLayer
    • getLayers

      public List<FeatureLayer> getLayers()
      Gets the FeatureLayers that correspond to the FeatureCollectionsTables of the associated FeatureCollection.
      an unmodifiable list of FeatureLayers
      See Also:
    • copy

      public FeatureCollectionLayer copy()
      Creates a deep copy of this FeatureCollectionLayer instance.
      a deep copy of this FeatureCollectionLayer instance, which means that copies of all fields of this layer are made including its loading state