Editing patterns

You can edit features using the following patterns.

• Online feature service editing: ServiceFeatureTables are packaged inside a ServiceGeodatabase that you create from a feature service. You retrieve a table from the local geodatabase, make feature edits, save them to the table. You can then apply the changes back to the service. This pattern is suitable for multi-user editing scenarios in a connected environment.

• Offline feature service editing: GeodatabaseFeatureTables are packaged inside a Geodatabase that you created from a sync-enabled feature service before going offline. You retrieve a table from the local geodatabase while offline, make feature edits, and save them to the table. You can then synchronize your changes back to the service when the device is back online. This pattern is suitable for multi-user workflows where users are disconnected from the internet while entering edits. See Offline maps, scenes, and data for more information about offline workflows in ArcGIS Maps SDK for .NET.

• Feature collection editing: A FeatureCollectionTable contains features from an ArcGIS web map or a feature collection portal item. Edits are made and changes are saved to the ArcGIS web map or feature collection portal item. This is a suitable workflow for sharing static data to multiple clients but should not be used to edit data across clients or to share dynamic data ( i.e., data that changes frequently).

• Offline file-based editing: Edits can be made to features from a GeoPackage file (.gpkg) that supports the OGC geopackage specification. Such a file is stand-alone and is not backed by a feature service; it is fully offline. If your workflow includes sharing edits online and managing edits across many users, it is recommended that you use online feature service editing.