https://developers.arcgis.com/net/latest/wpf/guide/edit-features.
htm
In a connected workflow, the type of feature table you use and edit is
a ServiceFeatureTable . In a disconnected workflow, the type of feature table you use
and edit is a GeodatabaseFeatureTable . Both classes inherit from ArcGISFeatureTable ,
which itself inherits from FeatureTable .
The class hierarchy between these is as follows:
For working with features by value, the type of table you use
is FeatureCollectionTable . Feature collection tables do not contain attachments and
inherit directly from FeatureTable .
Offline feature services
In an offline workflow, you need to first generate a runtime geodatabase from a sync-
enabled feature service while you have a network connection. Follow the
geodatabase generation process described in Take a layer offline. 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
https://developers.arcgis.com/net/latest/wpf/guide/layer-types-
described.htm#ESRI_SECTION1_1807E1AD839D4ABF9CB5B3C38C3A2703
Feature layer
API
types: FeatureLayer , ServiceFeatureTable , GeodatabaseFeatureTable , ShapefileFeature
Table , GeoPackageFeatureTable, WfsFeatureTable
Feature layers display data from feature services or supported local data sources,
including shapefiles, GeoPackages, and geodatabases. Feature layers can be used
to display, select, and query features in a layer. If the underlying feature service or
table supports editing, you can use it with a feature layer as a basis for editing
geometry, attributes, and attachments. Feature layers are used to store features
associated with a utility network.
Features are retrieved as needed by the app. Features can be downloaded from a
sync-enabled feature service when the device is connected and cached locally for
use when the device is offline. Edits can then be synchronized back to the service.
Functional characteristics
There are many sources that can be rendered using a feature layer:
Feature service – backed by a service feature table; feature data from the service is cached
locally in the table. New features are retrieved automatically when you navigate the map.
The local table cache is discarded when the layer is disposed. If sync is enabled, features can
be created, edited, and pushed to the server.
Geodatabase – backed by a geodatabase feature table; The geodatabase can be a replica of
a feature service, which allows synchronizing with a feature service, or taking the content of
a feature service offline. Use a geodatabase sync task to synchronize the geodatabase with
the service.
Shapefile – backed by a shapefile feature table; Use a feature layer to show the contents of
shapefiles (.shp).
Geopackage – backed by a geopackage feature table; use a feature layer to render the
tables in a GeoPackage (.gpkg). A GeoPackage is a data source that conforms to the OGC
GeoPackage specification. Geopackage feature tables can be edited and saved, but can't
support sync, because there is no backing feature service. ArcGIS Runtime supports
GeoPackage versions 1.0, 1.1, and 1.2.
Web Feature Service (WFS) – backed by a WFS feature table. You can populate the table
using Runtime query parameters or raw XML-encoded GetFeature queries. WFS feature
table only supports manual cache feature request mode. See Performance characteristics for
more details. Runtime supports OGC WFS versions 2.0.0 and 2.0.2.
o WFS server implementations are inconsistent in how they expect coordinates to be
formatted. Some return and expect coordinates in (X,Y) order, while others expect
(Y,X). Runtime guesses the correct order by default. This behavior can be configured
with the AxisOrder and FilterAxisOrder properties.
Individual features can be queried and filtered based on spatial queries or SQL queries.
Introduced at 100.3.0, string comparisons for features queried in service feature tables are
case insensitive.
Local tables cannot be reprojected automatically. Find out more about editing features.
For details on viewing, identifying, querying, and editing features offline, see Take a layer
offline for more information.
Feature layers expose an unSupportedJson property that, for feature layers based on a feature
service, returns a dictionary of values known to the supported web map specification but not
explicitly exposed through the Runtime API. This allows you to access information that was
saved with the layer but not used by Runtime. Feature layers also provide
an unKnownJson property to return JSON that was not recognized.
Performance characteristics
As full feature information is cached locally in a geodatabase, shapefile, or GeoPackage, and
features are drawn natively, this layer type offers excellent display performance when
zooming and panning the map within the extent of cached features. Querying features is also
efficient, enabling app functions like real-time updates of query results in a map.
The local cache must be initially created, which can be resource-intensive for the server. The
initial download to the device may require extensive network usage and subsequent local
device storage. App memory increases with the number and complexity of the features
cached. Network usage can be eliminated by provisioning the cache directly to the device in
advance.
Feature tables backed by a service define three feature request modes. The table's feature
request mode controls how and when features are requested from the service:
On interaction cache – Features are requested automatically for the visible map or
scene extent. As the user pans and zooms, features are cached locally. If the user
returns to an area where features have already been loaded, the table won't need to re-
download those features.
Manual cache – Features must be manually populated using a call
to PopulateFromServiceAsync . Once populated, all queries are made against the local
table only. PopulateFromService can be called again to retrieve more features from the
service.
On interaction, no cache – Features are requested automatically for the visible map extent.
As the user pans and zooms, features outside the visible extent are not cached and must be
re-downloaded each time.
See Layers and tables for more information about feature request modes.
Learn more
Sample: Feature layer (geopackage)
Sample: Feature layer (query)
Sample: Feature layer (shapefile)
Sample: Service feature table (manual cache)
Guide: Symbols, styles, and renderers
Guide: Edit features
https://developers.arcgis.com/net/latest/wpf/guide/layers.htm
Tables
Tables provide a source of data that can be worked with directly, or perhaps
displayed in a feature layer. Tables in ArcGIS define a schema for features – a
consistent set of fields that features are expected to have. Tables can have many
features. Entries in spatial tables can have geometries. Tables can come from
several sources:
Shapefiles
Geopackages
Maps or scene
ArcGIS feature services
WFS feature services
Geodatabases
Tables can be:
Queried
Edited (depending on the source)
Shown in a feature layer
Taken offline
https://developers.arcgis.com/net/latest/wpf/guide/work-with-offline-layers.htm
Layers of data can be sourced from either online services such as ArcGIS Online,
WFS, or WMS, or offline sources such as mobile geodatabases, shapefiles,
GeoPackages, tile packages and raster datasets. Using ArcGIS Pro and ArcMap you
can create these GIS files and packages and deliver them via email, FTP, the cloud,
networks, thumb drives, and so on. The recipient just copies (or sideloads) the files
and directories onto their device so that the ArcGIS Runtime apps can work offline
without a network connection.
ArcGIS Runtime supports the following offline layers
Tiled layer data stored in tile packages (.tpk or .tpkx).
Vector tiled layer data stored in vector tile packages (.vtpk).
Feature layer data stored in the following formats:
o ArcGIS features held in a mobile geodatabases (.geodatabase).
o Features stored in a GeoPackages provisioned by the OGC file format
(.gpkg).
o Features stored in the Shapefile format provided by the .shp file and its
associated files (.dbf, .shx, etc).
Raster layer data stored in a raster dataset file or in a GeoPackage (.gpkg).
ArcGIS Pro and ArcMap provide a range of tools to create these GIS files and
packages. The following sections demonstrate how you prepare these data files, add
then to your ArcGIS Runtime app and create layers to display in your map.
