Edit features

Editing geographic data is the process of adding, updating, or deleting features and related data on layers in a map. Each layer is connected to a data source that defines and stores the features. Fine-grained control over editing operations are available by using the editing API, allowing you to do the following:

• Add and delete features

• Update geometry (for example, moving or reshaping a feature)

• Update attributes of features

• Add or delete feature attachments

Feature layers in your map that support editing expose editing functionality through the underlying FeatureTable.

Basic editing workflow

1. Editing patterns describes the supported editing patterns available to you.

2. Prepare data examines things to consider before you start building your editing applications. For example, there are situations where you might be required to create a feature service. Although this is not a development task, useful resources are provided to help you create your own feature services that in turn can be consumed and used in your application.

3. Edit features covers the foundational edit operations: add, update, and delete that are key for any of the previously described editing patterns. The ability to undo or roll back changes is also explored.

4. Edit geometry explains how to use the geometry editor to edit the geometry of a feature. It also explains different ways to create a new geometry.

5. Persist edits show how to persist your local edits to the service feature database (online pattern) or a replica geodatabase (offline pattern) in a feature service.

Advanced editing capabilities

The data you are editing might have been enhanced with such advanced data design as attribute rules, contingent rules, and related features. These enhancements are defined in ArcGIS Online, ArcGIS Server, or ArcGIS Pro, but are consumed by the ArcGIS Maps SDK for Qt API. In addition, some geodatabases can use branch versioning to support multiple editors and transactions to promote the data consistency of local commit.

• Attribute rules can automatically populate attributes, restrict invalid edits during edit operations, and perform data validation checks on existing features to help improve data integrity for geodatabase datasets.

• Contingent values are used to make allowed values in one attribute dependent upon the current values of other fields. They are built on top of attribute domains and add a further level of data integrity for user input.

• Related features allow you to relate a feature in one table to a feature in another table. For example, you might want a user to be able to view building inspections from an inspection table and view general building information (such as common name, year built, or tenants) from a buildings table for the same set of buildings.

• Branch versioned data provides support for isolating edits between multiple users making changes to a feature service. A quality assurance and control workflow can be used to audit the changes made — with only approved changes making it into a production database where key stakeholders view the data. Branch versioning applies to ServiceGeodatabases only.

• Geodatabase transactions allow a set of edits to be committed or rolled back as a single batch. They apply only to sync-enabled mobile Geodatabases.

Samples