Fine grained control over editing operations is available by using the editing API, allowing you to create and edit features, add, edit or remove feature attachments, and edit the geometry of features.
For editing workflows that use a local geodatabase, you can use geodatabase transactions to manage a set of edits (transaction). You can then control when those edits are committed (saved) or rolled back (discarded) as a single unit.
The enterprise geodatabase can use versioning to accommodate multiuser editing scenarios and long transactions. If you require multiple editors concurrently accessing services with the ability to undo and redo their edits, you can take advantage of branch versions in your ArcGIS Enterprise portal. For more information, see Use branch versioned data in this guide or Share branch versioned data in the ArcGIS Pro documentation.
For some feature service editing workflows, it's a good idea to have an analyst using ArcGIS Pro periodically review the edits to verify data integrity. Although components in the API can perform some data validation, other tasks such as validating topologies cannot be performed using the API alone.
Feature editing can be broken up into two parts, geometry or attribute editing, when the need arises. In certain scenarios, you might only be interested in editing the location of a feature, while in other situations you might only want to edit attributes. The referenced documentation will explore editing individual parts of the feature in greater detail.
Add features
For creating new features, it's common for an app to allow the user to click the map to specify a new feature's location. You can provide this capability by listening to a click event on your map view, which in turn will call a function for adding a new feature.
To add features to a feature table, create a new feature from geometry (for example, point, line, or polygon), create attributes for the new feature, and then call add feature. This adds the feature to a table stored locally on your device.
If these edits need to be shared with the parent feature service, apply them to the table's service geodatabase. See Apply edits to the service geodatabase for more information.
// Connect to the mouse clicked signal on the MapQuickView.
connect(m_mapView, &MapQuickView::mouseClicked, this, [this](QMouseEvent& mouseEvent)
{
// Obtain the map point where the user clicked with the mouse in the map view.
const Point newPoint = m_mapView->screenToLocation(mouseEvent.position().x(),
mouseEvent.position().y());
// Create the feature attributes (i.e. a key/value pair collection) and set a
// few attribute values.
QMap<QString, QVariant> featureAttributes;
featureAttributes.insert("typdamage", "Minor");
featureAttributes.insert("primcause", "Earthquake");
// Create a feature using the feature attribute and the map point.
Feature* feature = m_featureTable->createFeature(featureAttributes, newPoint, this);
// Add the feature to the feature table using the add feature async method.
m_featureTable->addFeatureAsync(feature).then(this,[]()
{
// continue processing....
});
});
Add true curves
Your app can add features with true curves to ArcGIS feature services that support true curves.
You can use ArcGISFeatureServiceInfo to find out what type of curve support a feature service has so that you can adapt your app behavior to it. For example, if the service doesn't support true curves, you can densify any curve geometries before sending them to the service. Or, if the service does support true curves, you could use the setServiceCurveGeometryMode() and ServiceCurveGeometryMode enum to fetch curve geometries, and reactively enable a curve-aware user experience in your app. ArcGIS REST API feature service reference contains more details about curve support.
For geometry information on true curves, see Segments in the Geometry topic.
You may know true curves as parametric curves.
Update features
Feature updates include moving or reshaping a feature's geometry or making edits to attribute values. All edits are stored in the feature table on the client.
If these edits need to be shared with the parent feature service, apply them to the table's service geodatabase. See Apply edits to the service geodatabase for more information.
// Loop thru the list of selected features.
for (Feature* feature : selectedFeatures)
{
// Replace all of the "TraumaLevel" attributes with the number 101.
feature->attributes()->replaceAttribute("TraumaLevel", 101);
}
// Update the list of selected features in the hospital feature table
// using the update features async method.
hospitalTable->updateFeaturesAsync(selectedFeatures).then(this,[]()
{
// continue processing....
});
Update true curves
Feature services can be published with protections that disallow edits to existing true curves from curve-unaware clients. If your app supports preserving curve segments when editing, you can use the new setServiceCurveGeometryMode() and ServiceCurveGeometryMode enum to inform the service your app is a true-curve client. Use properties on ArcGISFeatureServiceInfo to find out what curve support a feature service has. ArcGIS REST API feature service reference contains more details about curve support.
Delete features
You can delete several features from a feature table using the delete features method that accepts a list of features, or just a single feature with a call to delete feature. All edits are stored in the feature table on the client.
If these edits need to be shared with the parent feature service, apply them to the table's service geodatabase. See Apply edits to the service geodatabase for more information.
// Delete the list of selected features in the hospital feature table
// using the delete features async method.
hospitalTable->deleteFeaturesAsync(selectedFeatures).then(this,[]()
{
// continue processing....
});
Undo changes
There are times when making changes to data that you might want to undo all the edits in all of the local tables you are working with. The ServiceGeodatabase, a container for a collection of ServiceFeatureTables connected to a feature service, provides ServiceGeodatabase::hasLocalEdits() to determine if any of the tables have unapplied edits. If you confirm that edits exist, then you can use ServiceGeodatabase::undoLocalEdits() to asynchronously undo all of the local edits in all the tables. This logic could be applied before or after you apply or synchronize edits back to the feature service. In addition, you could utilize this logic during an editing workflow where you wish to provide a UI component to allow a user to undo their changes.
// Continue if the service geodatabase has local edits.
if (serviceGdb->hasLocalEdits())
{
// Call the undo local edits async method to undo all local edits
// in all tables of the geodatabase.
serviceGdb->undoLocalEditsAsync().then(this,[]()
{
// continue processing....
});
}
Work with geometry
There are many ways you can go about creating or editing geometries when editing features. Knowing all your geometry coordinates up front, then geometry constructors can be used to create the geometry all at once. When a more iterative process is required to build up or edit your geometry, then geometry builders are better suited. You might also want to perform actions on existing geometries that result in new geometries. In this case, the geometry engine provides geometric operations to help with that workflow. Lastly, you want to create or edit geometries interactively in a map view to better support your application users. The geometry editor is well suited to help out in this use-case. To learn more about these options and help you determine which one fits your requirements best, see the Create and edit geometries topic.
Edit data from a branch version
Edits can be made to service feature tables from a branch version in the same way they are made to any ServiceFeatureTable. The same process described above for adding, updating, and deleting features or their attachments can be applied here.