ArcGIS API for JavaScript (legacy) ^3.46

• Edits are applied on the client not posted to the server.
• The feature layer generates a unique object id for new features.
• Does not support queries that need to be performed on the server, for example queries with a where clause or non-extent based spatial queries.
• The feature layer toJson method returns an object with the same properties as the feature collection. The returned object includes all the features that are in the layer when the method is called. This method can be used to access a serializable representation of the features that can be saved on the server.

"advancedQueryCapabilities" : {
  "supportsPagination" : true, 
  "supportsQueryWithDistance" : true, 
  "supportsReturningQueryExtent" : true, 
  "supportsStatistics" : true, 
  "supportsOrderBy" : true, 
  "supportsDistinct" : true,
  "supportsQueryWithCacheHint" : true
}

  {
    <String> creatorField,
    <String> creationDateField,
    <String> editorField,
    <String> editDateField
  }

True if attachments are enabled on the feature layer. Use the queryAttachmentInfos method to determine if the feature has attachments. If the layer is editable (isEditable) and supports attachments the following operations can be performed.

• Add attachments to features.
• Delete existing attachments.

• Default is xyFootprint if geometryType is esriGeometryMultiPatch. Otherwise, undefined.
• User can override this property with a different choice in the future when FS supports it.
• Queries made through the FeatureLayer will include multipatchOption parameter if returnGeometry is true.
• Applies to snapshot, ondemand, selectFeatures, and queryFeatures

{
  <Boolean> allowUpdateToOthers,
  <Boolean> allowDeleteToOthers
}

Each element in the array is an object that describes the layer's relationship with another layer or table. Use the queryRelatedFeatures method to retrieve features or records related to a feature in this layer. The object has the following properties:

If the FeatureLayer has labeling defined on it, labels will automatically display if the Map's showLabels is true.

If you do not wish to have your feature layer label, you can override this behavior by setting its showLabels property to false.

NOTE: In order for the labels to display, all fields used by the labelingInfo should be set in outFields. In addition, only simple labeling is supported, for example {CITY_NAME}. For example, SQL keywords such as "CONCAT" are not supported. Consider using the LabelLayer class where you can specify the textExpression if needing more functionality.
Added at v3.11

• The layer is hidden.
• The layer is not visible at the current map scale.
• The layer is explicitly suspended by calling the Layer.suspend method.

Edited by Bjorn seconds ago
Edited by Bjorn a minute ago
Edited by Bjorn 15 minutes ago
Edited by Bjorn an hour ago
Edited by Bjorn 5 hours ago
Edited by Bjorn on Tuesday at 1:30 PM
Edited by Bjorn on 4/27/2014 at 11:30 AM

• the layer is not initialized or
• if the layer's edit tracking settings have been turned off or
• if the feature does not have edit tracking fields in its attributes.
(Added at v2.8)

• Auto generalization will be enabled by default.
• Auto mode will treat the layer like a polygon layer.

Returns true if the FeatureLayer is editable. If the layer is editable, one or more of the following operations can be performed depending on the permissions set on the service.

• Add new features.
• Modify the geometry and attributes of existing features.
• Delete features.

To see which of the above editing actions may be performed on the layer, execute getEditCapabilities() on the layer after verifying that isEditable() returns true.

Sets the definition expression for the FeatureLayer. Only the features that match the definition expression are displayed. A definition expression limits the features available for display and queries by applying constraints to the layer's attribute fields. Setting a definition expression is useful when the dataset is large and you don't want to bring everything to the client for analysis. This method is typically called before adding the layer to the map. If the method is called after the layer is added to the map the layer will refresh itself to reflect the new definition expression.

This definition expression is combined with the layer's default definition expression which results in a further restriction of the layer.

When the feature layer's editability is updated the onCapabilitiesChange event is fired. Use the isEditable method to determine if the layer is editable.

Support for feature reduction is limited to the following scenarios:

• Point data in FeatureLayer (from service or FeatureCollection) and CSVLayer.
• The map must have a spatial reference of Web Mercator or WGS84.
• If the layer contains more than 50,000 features, then only the first 50,000 will be clustered.
• A FeatureLayer created from a service URL must point to a service that supports pagination (ArcGIS Server version 10.3.1 or higher).
• When editing is initiated with the Editor widget, then feature reduction is disabled until the Editor widget is destroyed.
• Feature reduction is disabled when the layer has one of the following renderers: HeatmapRenderer, BlendRenderer, TemporalRenderer, or ScaleDependentRenderer.

Sets the time definition for the feature layer. A time definition temporarily filters the features in the layer to match the specified time extent. Only applicable for time-aware layers. Only supported when the feature layer is in snapshot mode.

In addition to time definition, time-aware layers also support the time extent set on the map. Time-aware layers automatically update when the map's time extent is changed, similar to how layers react when the map's spatial reference is modified. If a layer's time definition is set to display features between 1970 and 1975 and the map has a time extent set to 1972-1980, the effective time on the feature layer will be 1972-1975

Time offset allows you to display the features at a different time so they can be overlaid on top of previous or future time periods. For example, to visualize the growth pattern of two wild fires that happened in two different years, one of the layers can be given an offset that will cause it to appear as if the fire started at the same time as the other fire. Note that the offset does not change the temporal component of the data itself and has no effect if the layer is not time aware.

Example: If a layer has data recorded for the year 1970, an offset value of 2 years would temporarily shift the data to 1972 (for display purposes only, query and selection are not affected by offset).

Returns an easily serializable object representation of the layer. Regardless of the layer's mode of operation, only features currently available on the client are included.

{

  layerDefinition: <Object>,

    featureSet: {

    features:<Object[]>

  }

}