In this topic
- Create a feature table
- Add layers to the map
- Add features
- Update features
- Delete features
- Select features
- Commit your edits
You can let users edit features while online (connected) or offline (disconnected). Editing includes adding new features, deleting features, and updating existing features by changing their geometry (location or shape), attributes, or attachments. There are two models for editing features: feature table editing and feature layer editing. This topic focuses on feature table editing. For an introduction to editing and the editing models, see Editing.
Whether you are online or offline, the workflow to edit features is similar. In both cases, you need to do the following:
- Create a feature table—In a connected workflow, create it from a feature service. In a disconnected workflow, create it from a geodatabase you generated with a sync-enabled feature service before you went offline, as described in Create an offline map.
- Create a feature layer from the feature table and add the layer to the map.
- Perform any edits against the feature table (add, update, and delete features and feature attachments).
- Commit your edits—In a connected workflow, apply any edits you make to the feature service right away. In a disconnected workflow, sync all your edits back to the service once you have a network connection, as described in Sync offline edits.
The class hierarchy between these is as follows:
The methods to add, update, and delete features and feature attachments are common to FeatureTable and GeodatabaseFeatureTable. Therefore, all the methods you have at your disposal to edit in an offline workflow are also available for an online workflow, since GeodatabaseFeatureServiceTable inherits GeodatabaseFeatureTable. The GeodatabaseFeatureServiceTable used in connected editing provides additional methods to apply feature edits and attachment edits back to the service. You should apply any edits to the service as soon as you have made them on your feature table.
To update or delete features, your app should enable users to select features on the map, as described below in Select features.
Create a feature table
Before you can edit features, you need to obtain feature data from a feature service. In an online workflow, create a feature table from a feature service right before you want to edit features, for example, on application load. In an offline workflow, generate a geodatabase from a sync-enabled feature service while you have a network connection, in preparation for editing features offline. When offline, create feature tables from the geodatabase to edit the features locally. In both cases, check the capabilities of the feature service to ensure the editing capability is available.
In an online workflow, create a geodatabase feature service table (GeodatabaseFeatureServiceTable) from a feature service. You can then create a feature layer using this feature table. Once you add the feature layer to a map, features in the map extent are added to the feature service table and can be edited. As you pan and zoom the map (that is, change the map extent), more features are retrieved from the feature service and added to the geodatabase feature service table.
The number of features you see when you initially visit a new area of the map is limited by the feature service's MaxRecordCount property (the default value for this property is 1,000). Pan and zoom to query the service for more features. Once features are retrieved from the service and visible in your map, they are available in your geodatabase feature service table for editing and querying.
The GeodatabaseFeatureServiceTable must be initialized and added to a FeatureLayer after the Map has obtained a spatial reference from its basemap layer. This is required so that the GeodatabaseFeatureServiceTable initializes in the correct spatial reference to work with its imported features.
Connect to and wait for the Map::mapReady() signal to be emitted to determine when the Map has obtained its spatial reference.
// Create a feature service table from a feature service
const QString featureServiceURL="Feature service URL goes here";
// Create a feature layer from the feature service table
EsriRuntimeQt::FeatureLayer* featureLayer = new EsriRuntimeQt::FeatureLayer(featureServiceTable, this);
// Add the feature layer to the map
In an offline workflow, generate a geodatabase from a sync-enabled feature service while you have a network connection. Follow the geodatabase generation process described in Create an offline map. This process results in a geodatabase stored locally on disk. The geodatabase contains one or more feature tables, one for each service layer or service table that you requested in the geodatabase generation process. When offline, create geodatabase feature tables (GeodatabaseFeatureTable) from the geodatabase, for example, on application load. The features in the geodatabase feature tables are available for editing whether you create a feature layer or not, but in most cases you'll want to create a feature layer from the feature tables to display the features on a map. Also, consider generating an offline basemap to give the feature data some geographical context when your users edit offline, as described in Include a basemap.
The following code sample shows how to create a feature table from a local geodatabase:
// Create a GeodatabaseFeatureTable for the first feature layer
// in the local geodatabase
QString geodatabaseFile = "PATH_TO_GEODATABASE";
EsriRuntimeQt::Geodatabase* geodatabase = new EsriRuntimeQt::Geodatabase(geodatabaseFile, this);
m_geodatabaseFeatureTable = geodatabase->geodatabaseFeatureTables().at(0);
m_featureLayer = new EsriRuntimeQt::FeatureLayer(m_geodatabaseFeatureTable, this);
Add layers to the map
Display the features contained in the feature table in a map so your users can view and edit them. Create a feature layer from the feature table and add the layer to a map. The feature layer, once added to a map, takes care of displaying the features contained in your feature table that fall within the map extent displayed. When you make edits to features in the table, these edits are visible right away in the associated feature layer and map, but not yet committed back to the service.
The following code sample shows how to create a feature layer from a feature table:
// Get the feature table created from the service layer specified in 'LAYER_ID' const int layerId = 2; geodatabaseFeatureTable = geodatabase->geodatabaseFeatureTableByLayerId(layerId); // Create a feature layer featureLayer = new EsriRuntimeQt::FeatureLayer(geodatabaseFeatureTable, this); // Add the layer to the map m_map->addLayer(featureLayer);
To add or insert new features into a feature table, create the geometry (for example, point, line, or polygon) and attributes for the new feature, and then call the addFeature method. This method returns the unique feature ID of the added feature, which you can store for later use, such as if you want to modify the geometry or attributes of this particular feature later on. Adding a feature to a geodatabase feature table is shown in the code below:
To add or insert new features into a geodatabase table, create the geometry (for example, point, line, or polygon) and attributes for the new feature, and then call the addFeature method. This method returns the unique feature ID of the added feature, which you can store for later use, if you want to modify the geometry or attributes of this particular feature later on. Adding a feature to a geodatabase table is shown in the code below:
// Build a QMap of attributes for the new feature
QMap<QString, QVariant> attributes;
attributes["TYPEDAMAGE"] = "Minor";
attributes["PRIMCAUSE"] = "Earthquake";
attributes["TYPEDAMAGE_INT"] = 3;
// Get a geometry for the new feature
EsriRuntimeQt::Point point = get_report_point(); // Function gets location of report
// Create a new feature
EsriRuntimeQt::GeodatabaseFeature* feature =
new EsriRuntimeQt::GeodatabaseFeature(attributes, geodatabaseFeatureTable, point, this);
// Add the new feature, get its ID
qint64 fid = geodatabaseFeatureTable->addFeature(feature);
// If -1 returns, there was an error during add operation
if (fid == -1) // failure
// report/handle error
Features can be updated with the updateFeature method on the GeodatabaseFeatureTable.
The code sample below shows a method that updates a point feature in the geodatabase feature table with a new point geometry, changing its location on the map.
// Create new location geometry
// Populate newLocation...
// Create a feature ID
// Populate featureId with the ID of the feature you want to update
// Get the current feature contents by its ID
// so we can preserve the attributes
EsriRuntimeQt::GeodatabaseFeature* currentFeature =
// Create a new feature with the new geometry and the old attributes
EsriRuntimeQt::GeodatabaseFeature* updatedFeature =
geodatabaseFeatureTable, newLocation, this);
// Update (replace) the feature in the feature table
Features are deleted using the unique ID of the feature you want to delete. This unique ID can be stored when you add a feature to a geodatabase table or can be obtained, for example, through a query on the table. If you have selected the features to delete, the following line of code removes them from the layer:
In a typical map application involving editing, users should be able to select features to edit. You can programmatically select features in a feature layer using their unique IDs. You can obtain feature IDs by performing a query on the feature table from which the feature layer was created, or by letting your users click the map and obtain the IDs of any features within a certain pixel tolerance around the clicked point. The following code sample shows how to use a click event listener on the map to select clicked features:
void feature_service_table_editing_sample::onMouseRelease(QMouseEvent& event)
EsriRuntimeQt::FeatureLayer* m_featureLayer = new EsriRuntimeQt::FeatureLayer(this);
// Only accept the event if left button was pressed
if (event.button() != Qt::LeftButton)
// Create a Point geometry from the mouse click location
QPoint point = event.pos();
// Find the first 1000 features within five pixels of the mouse click
QList<qint64> hitFeatureIds = m_featureLayer->featureIds(point.x(), point.y(), 5, 1000);
// Select the list of found features, keeping any selected features
Commit your edits
Committing your feature table edits to the feature service is different depending on whether your workflow is fully connected or disconnected.
In a fully connected workflow, you should apply feature edits and attachment edits back to the service as you make them. That way, anyone else using the same feature service will have access to your changes right away.
To commit your local feature edits to the service, call the applyFeatureEdits() method. Optionally, you can list the current locally edited features by using addedFeatures(), updatedFeatures(), and deletedFeatures(). Changes to the features returned by those three functions will be committed to the service on a call to applyFeatureEdits(). Once the edits have been applied, newly added features will be given the server-generated object ID. You can find out the value of the new object ID by getting the feature back out of the feature table and checking its object ID attribute value. The applyFeatureEdits() method is asynchronous; any errors from this method will be returned in the applyFeatureEditsComplete signal as a list of GeodatabaseEditError objects.
To commit your local feature attachment edits to the service, call the applyAttachmentEdits() method. A feature needs to exist on the server before attachment edits for this feature can be applied. Generally, you should call applyAttachmentEdits after a successful call to applyEdits. The applyAttachmentEdits() method is asynchronous; any errors from this method call will be returned in the applyAttachmentEditsComplete signal as a list of GeodatabaseEditError objects.
For descriptions of errors that can arise during edit commits, go to the Apply Edits (Feature Service) topic and click the error code link in the Description section.
In a disconnected workflow, commit all edits back to the service, and optionally pull the latest changes from the service back to your geodatabase through a sync operation, as described in Sync offline edits. Syncing requires a network connection; therefore, do this when you are back online. Note that the edits that are last committed to the service will overwrite previously committed edits, even if committed edits were made at a later time.