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 and attachments. 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.
lifecycleScope.launch {
// Create attributes for the feature.
val attributes = mutableMapOf(
"firstname" to "John",
"lastname" to "Doe",
"typdamage" to "Minor",
"primcause" to "Earthquake"
)
// Create a new feature from the attributes and the point.
val arcGISFeature = damagePointsTable.createFeature(attributes, point) as? ArcGISFeature
?: return@launch logErr("New feature is not an ArcGISFeature.")
// Check if features can be added to the feature table.
if (damagePointsTable.canAdd()) {
// Add the feature to the local table.
damagePointsTable.addFeature(arcGISFeature).onFailure { error ->
return@launch logErr("Could not add feature to table: ${error.message}")
// If the feature table is a service feature table, then
// apply edits to its service geodatabase.
// ...
}
}
}
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 serviceCurveGeometryMode 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.
// Check if the feature can be updated.
if (damagePointsTable.canUpdate(arcGISFeature)) {
// Change the feature's attribute value.
arcGISFeature.attributes["typdamage"] = "Inaccessible"
// Check if the feature's geometry can be edited.
if (arcGISFeature.canUpdateGeometry) {
// Change the feature's geometry.
val currentLocation = arcGISFeature.geometry as? Point
?: return@launch logErr("Current feature does not have a point geometry.")
val newLocation =
Point(
x = currentLocation.x,
y = currentLocation.y + 250.0,
spatialReference = map.spatialReference
)
arcGISFeature.geometry = newLocation
}
// Update the feature on the local table.
damagePointsTable.updateFeature(arcGISFeature).onFailure { error ->
return@launch logErr("Could not update feature in table: ${error.message}")
}
// If the feature table is a service feature table, then
// apply edits to its service geodatabase.
// ...
}
Update true curves
Feature services can be published with protections that disallow edits to existing true curves from curve-unaware clients. 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.
val selectedFeatures = damageLayer.getSelectedFeatures().getOrElse { error ->
return@launch logErr("Could not get list of selected features: ${error.message}")
}
// Delete the features.
damagePointsTable.deleteFeatures(selectedFeatures)
// If the feature table is a service feature table, then apply edits to
// its service geodatabase.
// serviceGdb.applyEdits()
Edit attachments
If the feature's table has attachments enabled, you can associate documents and photographs with individual features. You can add any file, that has a supported attachment format, to the feature's collection of attachments using ArcGISFeature.addAttachment(). For more information about enabling attachments on the feature layer, see the ArcGIS Online, ArcGIS Enterprise, and ArcGIS Pro documentation.
if (serviceFeatureTable.hasAttachments) {
// Add the attachment to the selected feature.
arcGISFeature.addAttachment(
name = attachmentName,
contentType = "image/png",
data = imageBytes
).onFailure {
return@launch showError(it.message.toString())
}
// Update the feature changes in the loaded service feature table.
serviceFeatureTable.updateFeature(arcGISFeature).getOrElse {
return@launch showError(it.message.toString())
}
}
If the feature's table has attachments enabled and the feature's attachment collection can be edited, you can update any attachment with new details.
if (serviceFeatureTable.hasAttachments && arcGISFeature.canEditAttachments) {
// Delete the attachment from the selected feature.
arcGISFeature.updateAttachment(
attachmentInfo = attachment,
name = "DamagedTree.png",
contentType = "png",
data = dataElement
).getOrElse {
return@launch showError(it.message.toString())
}
// Update the feature changes in the loaded service feature table.
serviceFeatureTable.updateFeature(arcGISFeature).getOrElse {
return@launch showError(it.message.toString())
}
}
Or, you can remove any attachment from the feature's attachment collection.
// Delete the attachment from the selected feature.
arcGISFeature.deleteAttachment(attachment).getOrElse {
return@launch showError(it.message.toString())
}
// Update the feature changes in the loaded service feature table.
serviceFeatureTable.updateFeature(arcGISFeature).getOrElse {
return@launch showError(it.message.toString())
}
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.
// Double-check edits exist in any of the local tables.
if (serviceGdb.hasLocalEdits()) {
lifecycleScope.launch {
// Undo all the local edits for all the tables in the service geodatabase.
serviceGeodatabase.undoLocalEdits().onFailure { error ->
return@launch logErr("Unable to undo local edits: ${error.message}")
}
}
}
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.
Work with attributes and attachments
The code examples illustrated above show a typical workflow for editing attribute values and attachments when adding or updating features. In these scenarios, the manner in which the attribute values are obtained and validated are left to your creativity during application development.
Feature layers (hosted feature layers, hosted feature layer views, or ArcGIS Server feature layers), that are contained in a web map, may have a pre-configured form that is designed to ease attribute and attachment collection and validation. This form can help guide users to the correct fields and allowable attribute values. The form is built into the web map when the feature layer is defined. We recommend that you display this feature form in your app by utilizing the composable FeatureForm toolkit component.
If the feature layer has attachments enabled on it, the toolkit component will automatically support attachments. In addition to adding, updating and deleting attachments, you will be able to preview attachment thumbnails, download and open the full attachment for viewing, capture a new attachment from the device camera, and add attachments from a file or gallery.
If you have requirements that go beyond the capabilities of this toolkit component, you can work with the API directly as described in the Edit attribute values.
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.