Skip To Content ArcGIS for Developers Sign In Dashboard

<GeodatabaseTypes.h> - Geodatabase Enums

Collection of Geodatabase enumerations. More...

Header: #include <GeodatabaseTypes.h>

Types

enum class EditOperation { Unknown, Add, Update, Delete }
enum class EditResultType { Unknown, FeatureEditResult, EditResult }
enum class FeatureObjectType { Unknown, ArcGISFeature, Feature }
enum class FeatureRequestMode { Undefined, OnInteractionCache, OnInteractionNoCache, ManualCache }
enum class FeatureTableType { Unknown, FeatureTable, ServiceFeatureTable, GeodatabaseFeatureTable, FeatureCollectionTable, …, OgcFeatureCollectionTable }
enum class GeodatabaseDatasetType { Unknown, TransportationNetworkDataset }
enum class OgcAxisOrder { Auto, Swap, NoSwap }
enum class QueryFeatureFields { IdsOnly, Minimum, LoadAll }
enum class RelationshipConstraintViolationType { None, Cardinality, Orphaned }

Detailed Description

Type Documentation

enum class EditOperation

Enumerates types of feature dataset edit operations.

The EditOperation can be one of:

ConstantValueDescription
EditOperation::Unknown-1Unknown operation
EditOperation::Add0Add a feature
EditOperation::Update1Update a feature
EditOperation::Delete2Delete a feature

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class EditResultType

Enumerates types of editing results.

The EditResultType can be one of:

ConstantValueDescription
EditResultType::Unknown-1Unknown edit result type
EditResultType::FeatureEditResult0Edit result on features
EditResultType::EditResult1Basic edit result

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class FeatureObjectType

Enumerates feature object types.

The FeatureObjectType can be one of:

ConstantValueDescription
FeatureObjectType::Unknown-1Unknown feature object type
FeatureObjectType::ArcGISFeature0An ArcGIS feature type used with an ArcGISFeatureTable
FeatureObjectType::Feature1A feature type

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class FeatureRequestMode

Enumerates feature request modes for the feature table.

The feature request mode for a service feature table. This determines (1) whether features are cached locally (for quicker access by map and scene layers) and (2) whether queries are performed on the local cache or on the server.

The FeatureRequestMode can be one of:

ConstantValueDescription
FeatureRequestMode::Undefined0The feature request mode is undefined and will be set on initialization of the table. If it's a spatial table then the feature request mode will be set to OnInteractionCache. If it's a non-spatial table the feature request mode will be set to ManualCache.
FeatureRequestMode::OnInteractionCache1The features are requested from the server as they are needed, in response to user or developer interaction with the layer (pan, zoom). Features are cached in the local table for the duration of the session. Queries are executed on the local cache or (if requested features are not resident in the cache) on the server. This mode is the default. In this mode, features have a minimum set of attributes, and feature geometries have no m-values even if m-values are defined by the service. This is an optimization for faster rendering. To access all attributes or access geometries that contain m-values, the features you get from a query must be loaded. You can load them yourself or request that the query method return them already loaded (see Esri::ArcGISRuntime::QueryFeatureFields::LoadAll at Esri::ArcGISRuntime::QueryFeatureFields). For more information, see the class description for Esri::ArcGISRuntime::ServiceFeatureTable.
FeatureRequestMode::OnInteractionNoCache2The features are always requested from the server and are never cached. This mode ensures that you are working against the latest data, but it has a high network bandwidth since it goes to the server for all interactions (pans, zooms, selects, or queries).
FeatureRequestMode::ManualCache3The features are requested from the server by an explicit call to Esri::ArcGISRuntime::ServiceFeatureTable::populateFromService(), which populates the local cache. Queries performed on the table will be executed locally. In this mode, the features have all fields defined by the outFields argument you pass to Esri::ArcGISRuntime::ServiceFeatureTable::populateFromService().

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class FeatureTableType

Enumerates feature table types.

The FeatureTableType can be one of:

ConstantValueDescription
FeatureTableType::Unknown-1Unknown feature table type.
FeatureTableType::FeatureTable0Feature table base type
FeatureTableType::ServiceFeatureTable1A service feature table consuming and interacting with a connected feature service layer.
FeatureTableType::GeodatabaseFeatureTable2A local feature table consuming a feature table from a mobile geodatabase.
FeatureTableType::FeatureCollectionTable3A feature collection table.
FeatureTableType::ShapefileFeatureTable4A shapefile feature table.
FeatureTableType::GeoPackageFeatureTable5A GeoPackage feature table.
FeatureTableType::WfsFeatureTable6A WFS feature table.
FeatureTableType::OgcFeatureCollectionTable7An OGC Feature Collection Table.

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class GeodatabaseDatasetType

Enumerates geodatabase dataset types.

The GeodatabaseDatasetType can be one of:

ConstantValueDescription
GeodatabaseDatasetType::Unknown-1Unknown geodatabase dataset type.
GeodatabaseDatasetType::TransportationNetworkDataset0A transportation network dataset, which is used to perform network-based analyses like finding a route.

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class OgcAxisOrder

Enumerates the different ways to treat the x/y coordinates order.

The OgcAxisOrder can be one of:

ConstantValueDescription
OgcAxisOrder::Auto0Indicates swapping the axis order will be based on the OGC standard specification, version, and spatial reference.
OgcAxisOrder::Swap1Indicates the order of x/y coordinates will be swapped.
OgcAxisOrder::NoSwap2Indicates the order of x/y coordinates will stay as is, and all swapping rules by the OGC standards will be ignored.

This enum was introduced or modified in Esri::ArcGISRuntime 100.5.

enum class QueryFeatureFields

Enumerates query feature options.

Controls which attributes are included in the features returned by Esri::ArcGISRuntime::ServiceFeatureTable::queryFeatures() or Esri::ArcGISRuntime::ServiceFeatureTable::queryRelatedFeatures().

The QueryFeatureFields can be one of:

ConstantValueDescription
QueryFeatureFields::IdsOnly0Includes only the object id and global id in the ArcGISFeatures of the query result. The features are returned with no other attributes. The geometry returned by this request does not include m-values, even if they are defined in the feature service. To get full feature details, you should load the feature.
QueryFeatureFields::Minimum1Includes the minimum set of attributes in the ArcGISFeatures of the query result. The geometry returned by this request does not include m-values, even if they are defined in the feature service. To get full feature details, you should load the feature.
QueryFeatureFields::LoadAll2Includes all available attributes in the ArcGISFeatures of the query result. This constant loads the features returned by the query, which makes all attributes available. The geometry returned by this request includes m-values if defined in the feature service.

This enum was introduced or modified in Esri::ArcGISRuntime 100.0.

enum class RelationshipConstraintViolationType

Enumerates the type of constraint violation for a given feature participating in a relationship.

The RelationshipConstraintViolationType can be one of:

ConstantValueDescription
RelationshipConstraintViolationType::None0There are no constraint violations.
RelationshipConstraintViolationType::Cardinality1Cardinality of the given feature is violated.
RelationshipConstraintViolationType::Orphaned2The given feature is an orphaned destination feature in a composite relationship. Note: Orphaned destination feature in a simple relationship is not considered a violation.

This enum was introduced or modified in Esri::ArcGISRuntime 100.1.


Feedback on this topic?