Release notes for 200.6

Geometry guides

When using the GeometryEditor with SnapSettings::isEnabled(), you can now make use of geometry guides to help you create rectilinear features and make consistently aligned changes to your geometry. When using either the VertexTool or ReticleVertexTool, and SnapSettings::isGeometryGuidesEnabled() is true, additional visual cues appear to which you can snap your edits. Each guide appears only when applicable, helping you to easily and quickly make the following types of geometry edits.

• Create 90 degree corners.
• Create parallel segments.
• Extend the length of existing segments while maintaining the segment direction.
• Snap to existing segments or vertices of the edited geometry.

A new SnapSettings::isFeatureSnappingEnabled() property can be used to quickly enable or disable existing feature and graphic snapping functionality, independently of geometry guides.

Haptic feedback when snapping geometry edits

Haptic feedback can contribute to a richer app experience for your users. When used to confirm or highlight app state changes based on user interactions, this can help increase confidence in app usage. Haptic feedback can now be enabled for interactive geometry editing with snapping, with haptic feedback occurring when an edit is snapped to a feature, graphic, or geometry guide. No haptic feedback occurs when the edit unsnaps. To provide custom haptic feedback for snapping, see the new GeometryEditor::snapChanged() event described below.

Haptic feedback occurs when snapping using the GeometryEditor, SnapSettings::isHapticFeedbackEnabled() is true, and haptic feedback is supported by the device.

Snap changed event

When using the GeometryEditor with snapping, the new GeometryEditor::snapChanged() event can help you to provide additional, confirmatory effects to your app. For example, if the built-in haptic feedback described above does not suit your needs, you can use this event to provide custom haptic feedback using haptic patterns that differ from the built-in functionality. Alternatively, you may want to augment your app with audio affects to provide alternative or additional user confirmation of a snap where haptics are not available. For example, users cannot feel haptic feedback if they are working in the field with gloves or if they are working on a desktop.

The SnapState parameter of this new event indicates whether the snap was to a feature or graphic, to a geometry guide, or if the edit position became unsnapped.

User experience enhancements

This release includes a number of improvements to the reticle user experience, including eliminating the jitter seen during map pans, more consistency when moving vertices and hovering the reticle crosshairs over vertices, and improved polygon appearance for island and concave shapes.

Support for attribute rules in sync-enabled geodatabases

With ArcGIS Enterprise 11.4 or later feature services, sync-enabled geodatabases can execute immediate calculation and constraint rules for client evaluation during editing. These custom rules automatically populate and validate permissible combinations of attribute values, enhancing the user editing experience and ensuring data integrity for geodatabase datasets. GenerateGeodatabaseParameters::isSyncAttributeRules() is enabled by default when supported by the service. To verify if attribute rules can be downloaded with the geodatabase, check SyncCapabilities::isSupportsAttributeRules() on the feature service.

This SDK now supports Arcade 1.29

The following functions have been added:

• FeatureInFilter checks if a feature satisfies an Esri Standardized SQL where clause expression.
• StandardizeFilename translates the characters in a filename using the rules described in ArcGIS Pro's Export Attachment tool.
• Centroid has been updated to offer the Label Point algorithm along side the geometric algorithm.

Construct from a portal item

You can now create a DynamicEntityLayer or ArcGISStreamService from a stream service or feed portal item. There are new constructors that take a PortalItem on DynamicEntityLayer and ArcGISStreamService classes.

A new read-only ArcGISStreamService::portalItem() property is now exposed and is only set if the stream service object is created with the new constructor.

Explicitly set the query expression language

• This release adds a new OgcFeatureCollectionTable::populateFromServiceAsync() overload to allow for explicitly setting the language that the QueryParameters::whereClause() is written in. OGC feature services will use this property to properly format feature population requests. OGC feature services can support multiple languages such as cql2-text and cql2-json, and this parameter allows the user to choose the language that the whereClause is written in.

Utility network synchronization

Ahead-of-time workflow: Utility networks downloaded from an offline map area now support editing and bidirectional synchronization when the web map's advanced offline utility network option is set to "Trace and edit features, and view associations" for ArcGIS Enterprise 11.4 or later portals and feature services.

On-demand workflow: For offline editing of utility networks with full topology, download the ArcGIS Enterprise 11.3 patch, when available, to take full advantage of feature service synchronization.

Utility network sync capabilities

New capabilities for synchronizing utility networks with full topology are now available. SyncCapabilities::isSupportsUtilityNetworkTopologySync() indicates support for both editing and bidirectional synchronization of the utility network. Conversely, SyncCapabilities::isSupportsUtilityNetworkTopologySyncDownloadOnly() signifies that the utility network is read-only, allowing edits only through download sync direction. Without support for synchronization, the utility network can only be downloaded and replaced by setting GenerateGeodatabaseParameters::setSyncModel() to SyncModel::None.

Flow direction-based tracing

With the upgrade to utility network schema version 7 in ArcGIS Enterprise 11.3 or later feature services, upstream and downstream traces can now leverage digitized direction in both online and offline utility networks by setting UtilityTraceConfiguration::isUseDigitizedDirection(). This enhancement removes the need for modeling subnetwork controllers or subnetworks for directional tracing, which is particularly beneficial for stormwater and wastewater assets.

Additional metadata for utility network editing

UtilityAssetType now includes properties for container split policy and linear connectivity policy, enabling applications to develop utility network-aware editing tools for snapping, moving, vertex-editing, and performing split container operations.

Advanced Editing license check

Creating or editing features in a named version requires an Advanced Editing extension license with ArcGIS Enterprise 11.2 or later feature services. This license validation is now performed during the creation process using ServiceGeodatabase::createVersionAsync(), as well as during add, update, or delete operations on features and attachments.

Editing subtypes

When using SubtypeFeatureLayer, you can customize edit capabilities at the subtype level by adjusting SubtypeSublayer::isAllowsEditing() property. The enableEditing property on subtype layers in web maps are now honored and persisted with Native Maps SDKs, allowing you to restrict the addition, modification, or deletion of features for certain subtypes.

Support for CIM spec 3.4

ArcGIS Maps SDKs for Native Apps now support the latest CIM spec version 3.4. ArcGIS Pro 3.4 will be required to author maps targeting CIM spec version 3.4.

Military symbology

This release adds support for three additional Military symbology dictionary styles following new standards: MIL-STD-2525D Change 1, MIL-STD-2525E, and APP-6(E).

Grids in a scene view

This release adds support for displaying coordinate system grids in a SceneView. Grids in a SceneView are the same as grids in a MapView with the exception of using screen anchored placements. Screen placement of grid labels for MGRS, UTM, and USNG grid types are not currently supported in a SceneView.

Since grids are now supported for both MapView and SceneView, the property has been moved to the GeoView base class: GeoView::grid().

3D basemaps support

This release adds support for 3D basemaps. A 3D Basemap can be constructed from a url or portal item and then added to a scene. Layers in a 3D basemap are added to the basemap's Basemap::baseLayers() collection. Currently, only buildings layers and vector tiled layers are supported. If present in the Basemap, layers containing trees, points of interest, or labels will report a failed to load status.

Create and edit KML track and multi-track

With this release, you can now create and edit KML tracks, which allows the visualization of a series of geographic points along a path with timestamps. It is ideal for applications that require time-sequenced data, such as route mapping or tracking of movement.

Complex track structures can be constructed as a multi-track, enabling the consolidation of multiple KmlTrack objects into a single KmlMultiTrack object. This facilitates handling multiple journeys or paths within a single file.

Editing KML extended data

In this release, the SDK fully supports editing extended data within KML elements and provides greater flexibility to add custom metadata.

Other KML geometries

Support for creating KmlMultiGeometry is added with this release, allowing users to combine multiple geometry types (points, polylines, polygons, etc.) into a single feature. This also allows for a nested tree structure of geometries in KML.

This release adds a new KmlModel class. You can instantiate instances of KmlModel with a URI to a Collada model (local or network), a geographic location (point), the altitude mode, and optionally scale and orientation values.

Indoor positioning configuration

The indoor positioning definition, which stores information to create an IndoorsLocationDataSource (ILDS), has a new configuration property called IndoorPositioningDefinition::configuration(). This configuration is specified in an IPS-aware map using ArcGIS Pro. ILDS automatically uses this configuration and you can programmatically alter its properties, if required.

Support for fully disconnected offline workflows

You can now consume mobile map packages (.mmpk) that contain both the indoor map and indoor positioning data. These types of mobile map packages allow you to build applications that work completely offline while displaying the blue dot indoors.

Beacon scanner

This release introduces a BeaconScanner class that picks up radio signals from any surrounding beacons. The BeaconScanner can be used to set up and maintain an IPS deployment, and the information from it can be used to update the IPS_Beacons feature class.

At this initial release, BeaconScanner includes information about the parsing battery level of detected beacons and supports Kontakt.io beacons.

Errors and warnings

The behavior of errors and warnings has been updated slightly. Errors, such as missing or incomplete IPS data, are now only triggered during the startup phase of ILDS. Warnings can occur while ILDS is running. They indicate a possible degradation in the quality of the calculated indoor position. A warning is issued once at the end of a position calculation cycle, and then reset to null once ILDS is running smoothly. The same warning will not be triggered again in subsequent calculation cycles.

Coordinate systems and transformations

• Available coordinate systems and transformations have been updated to EPSG v11.015.
• New vertical transformations based on geoids, quasi-geoids, or other conversion grids can transform to or between gravity-related vertical coordinate systems for Australia, Canada, Czechia, and Germany.
• New vertical transformations for EGM96 and EGM2008 heights are using bicubic natural spline interpolation used by NGA.
• Geographic transformations between NAD 1927 and NAD 1983 (various re-adjustments) that are using NADCON, HARN, and GEOCON grids are deprecated but remain available in the software. Transformations using these grids will appear at the bottom of a list of transformation paths. The recent NADCON5 transformations available in the Projection Engine Data supplemental download should be used instead.

There are no SDK enhancements with this release.

There are no Local Server updates with this release.

• The ArcGISStreamService::url() property is now nullable. The url will only be null when creating the ArcGISStreamService using the PortalItem constructor and if the item's serviceUrl property is empty, typically when the item is not loaded or if the item is not valid for creating a stream service.

• GeometryEngine.offset now supports true curve input geometries, producing densified curves in the result geometries.

• The default color for grids in MapView has been changed to white. This applies to any grid with one or multiple levels.

• Qt's Bluetooth module is no longer automatically included by the SDK qmake and CMake project files. This was changed to reduce your app's dependencies and entitlements required for app store submissions. If your app uses IndoorsLocationDataSource or BeaconScanner, you will need to explicitly add bluetooth support to your project.

CMake:

1
2
3
if(ANDROID OR IOS)
  target_link_libraries(${PROJECT_NAME} PRIVATE Qt6::Bluetooth)
endif()

qmake:

1
android|ios: QT += bluetooth

200.6 is the last release to support:

• Qt 6.5.6, 6.6, and 6.7. Next release will require Qt 6.8.
• Xcode 15. Next release will require Xcode 16.
• MSVC 2019. Next release will require MSVC 2022.
• Red Hat 8.4. Next release will require Red Hat 8.6.
• Android 8. Next release will require Android 9.
• Android SDK Tools 26. Next release will require Android SDK Tools 28.
• JDK 11 for Android development. Next release will require JDK 17.
• NDK r25b for Android development. Next release will require NDK r26b.

Issues addressed in this release are listed below.

• BUG-000171542 Internal Nullability Violation error for the DefaultVisibility property when working with feature layers hosted in Enterprise Portal and apps built with ArcGIS Maps SDKs for Native Apps version 200.5.

• BUG-000171844 Using scheduled updates with ArcGIS Maps SDKs for Native Apps incorrectly downloads entire new replica instead of incremental changes.

• BUG-000171919 Creating offline replica with a full utility network incorrectly requires that all layers from the feature service are included.
• BUG-000171920 OfflineMapTask can fail when including a utility network.

• ENH-000134743: Provide support for displaying a Grid in a 3D SceneView.

• Issue reported on Esri Community: Incorrect shadow rendering for buildings in relative to ground mode.
• Inconsistent dirty area creation when incorporating geodatabase delta with utility network association deletion.
• Persistent geodatabase file lock from an ahead-of-time download of a UN web map.
• Sublayer visibility should update based on scale in an offline map.
• Handle directional traces where the trace configuration is different from the tier's.
• Identifying a clustered feature layer without a popup definition does not return results.

• BUG-000169385 - Qt Android apps using 3D and IndoorsLocationDataSource crash with Qt 6.7+

BUG-000172414 Android Bluetooth scanning silently stops working after 10 or 30 minutes, impacting IndoorsLocationDataSource and BeaconScanner.

• Samples now use Qt's permission APIs.
• Display a grid sample has been renamed to Show grid, and has been updated to support 3D Scenes.