Release notes for 200.8

Customizable geometry editing workflows using the programmatic reticle tool

You can now configure your GeometryEditor to use the new ProgrammaticReticleTool to facilitate customized geometry editing workflows such as those using buttons rather than tap interactions. Unlike our existing tools the ProgrammaticReticleTool has no built in touch interaction. Instead, it is driven by programmatic operations allowing you to configure your own behavior and interaction using buttons or other triggers of your choosing.

Use ProgrammaticReticleTool.SelectElementAtReticle() and ProgrammaticReticleTool.PickUpSelectedElement() to select and pick up the GeometryEditorVertex or GeometryEditorMidVertex at the reticle position. Then, drop a picked-up vertex or insert a new vertex using ProgrammaticReticleTool.PlaceElementAtReticle().

The ProgrammaticReticleTool.VertexCreationPreviewEnabled property can be used to enable or disable the appearance of vertex feedback and feedback lines that are drawn underneath the reticle. It can also be used to enable or disable both visual and haptic snap feedback. This is useful when implementing workflows that do not allow for vertex creation.

Hovered and picked up element changed events

The GeometryEditor.HoveredElementChanged and GeometryEditor.PickedUpElementChanged events can be used in your app to react to state changes in the GeometryEditor, and are especially useful when working with the new ProgrammaticReticleTool.

For example, when GeometryEditor.HoveredElementChanged occurs, based on the GeometryEditor.HoveredElement, your app UI can display a button that selects and picks up the element currently underneath the reticle, as shown below. Similarly, when GeometryEditor.PickedUpElementChangedoccurs, your app UI can display a button that drops the GeometryEditor.PickedUpElement or places a new vertex, using ProgrammaticReticleTool.PlaceElementAtReticle(). You can check the GeometryEditor.PickedUpElement to indicate to the user whether or not they will be inserting a new vertex or dropping a currently picked up element.

Disable grow effect when hovering over geometry editor elements

Use the new GeometryEditorStyle.GrowEffect to enable and disable the visual effect of vertices and mid-vertices growing when hovered.

Vertices and mid-vertices can be separately configured using GeometryEditorGrowEffect.ApplyToVertices and GeometryEditorEffect.ApplyToMidVertices.

Identify geometry editor elements

Use the MapView.IdentifyGeometryEditorAsync() method to identify elements at a given position when using the GeometryEditor. This allows you to implement workflows such as selecting geometry editor elements or updating the viewpoint to be centered at that element on a long press.

Customizable precision with tolerance and resolution

Use the new SpatialReferenceBuilder to create new SpatialReference objects with custom tolerance and resolution values for high accuracy workflows and GeometryEngine.

The SpatialReference class exposes new read-only properties for SpatialReference.Tolerance, SpatialReference.VerticalTolerance, SpatialReference.Resolution, and SpatialReference.VerticalResolution.

This resolves the following enhancement request: ENH-000168892 Add ability to define the tolerance of a spatial reference.

Utility Network creation and access

The UtilityNetwork object can now be created with a ServiceGeodatabase object. When these objects are created from the same feature service source, they share the same instances of FeatureTable. This new constructor emphasizes the explicit relationship between them. Similarly, when a Map object is created from a web map containing utility network data, the layers, tables, and utility networks all use the same underlying ServiceGeodatabase object. Instead of creating a standalone UtilityNetwork, consider accessing the UtilityNetwork using the Map.UtilityNetworks property. All public samples containing utility network data have been updated to align with this change. For more detailed information, refer to the API deprecations section.

Add title property to utility association result

This release adds a title property to UtilityAssociationResult. It provides a user-friendly name for UtilityAssociations shown in a FeatureForm or Popup. The title is derived from the title of the FeatureFormDefinition or PopupDefinition of the associated feature's layer or table, with a suitable fallback if no FeatureFormDefinition or PopupDefinition has been created.

Support for on-demand and pre-planned offline map area workflows

It is now possible to create offline applications using an IPS-aware web map and implement the on-demand and pre-planned workflows. Indoor positioning data will be taken offline using ArcGIS Maps SDKs' offline jobs and the offline application will display a blue dot in the respective offline map area indoors.

ArcGISFeature access optimization

Accessing ArcGISFeatures by performing query operations on a ServiceFeatureTable or UtilityNetwork, as well as through the identify methods with FeatureLayers, has seen a significant boost in performance. This improvement is particularly evident when working with a map or scene that contains a large feature dataset, as these asynchronous operations now return results more efficiently, even while all features are still being rendered.

Improved performance and user experience of KML layers in a scene

In this release, performance and user experience for KML layers in 3D have been improved. The changes focus on line and polygon geometries. You'll notice the biggest improvements when a layer contains a large volume of data. Interaction with KML layers is now smoother, providing a much better user experience.

PDF Support

PDF files are now a supported raster file format, including GeoPDF(R) and geospatial PDFs using the ISO encoding. They can now be directly added to maps or scenes as raster layers or basemaps without the need to first convert them to another format. The first page of a PDF will be read and georeferenced according to optional embedded spatial reference information, and at a default DPI of 300.

Support for fetching Model Symbols from a mobile Style file

This release adds support to fetch a Model Symbol from a mobile Style file. You can search for a model symbol in the mobile style or fetch a symbol by providing list of keys. The type of symbol returned is a MultilayerPointSymbol and model symbol layer object is returned as a generic SymbolLayer type object. This workflow is already supported for WebStyles.

Support for new Arcade version

The SDK now supports Arcade 1.33

• Geotrigger notification profile now supports $FenceLayer.
• TranslateText function is not yet supported and will be supported in a future release.

Geographic (datum) transformations

• Added geographic (datum) transformation method Molodensky-Badekas (Position Vector). The existing Molodensky-Badekas method uses the Coordinate Frame version of the rotation matrix.
• Added geographic (datum) transformation method NTv2_Velocity. Although the method is designed to support datum anchor epochs and data epochs, only frame epochs of the geographic coordinate systems are currently supported for interframe conversions such as between NAD83(CSRS)v2 and NAD83(CSRS)v8.

Credential persistence via Fluent Configuration API

• Extended fluent configuration API to allow setting CredentialPersistence. You can now use AuthenticationExtensions.UseCredentialPersistence() extension method to enable credential persistence for an app.
• Added RuntimeImage-valued thumbnail properties to PortalInfo, PortalGroup, and PortalUser. This simplifies loading thumbnails for secured services compared to existing URL-valued properties.

Toolkit

This release adds several valuable features, enhancements and bug fixes to Toolkit.

• File Download Helper and Portal Item Download: A new download helper for portal item data now allows downloads to be paused, resumed, and restarted. This helper can be used for large portal item downloads in the toolkit.

• Toolkit support for utility network associations in popups: The popup toolkit component now includes support for UtilityAssociationsPopupElement, which offers a seamless viewing experience for utility network associations in both web and mobile maps. This enhancement allows users to access filtered associations that are organized by layers and tables, enabling easy navigation to their associated features, complete with percent along values, terminal connections, or visibility in a containment display. Maps featuring popups with utility network associations can be configured using ArcGIS Pro, MapViewer, or Native apps.

• FeatureFormView and PopupViewer Navigation: You can now navigate through utility network features from within PopupViewer and FeatureFormView.

• ValidationErrorVisibility handling: FeatureFormView now displays validation errors only after a control gets focus or Apply is pressed.

• PopupMediaView refresh interval: Support for auto-refreshing popup images using the RefreshInterval property is added, so images in popups can update at set intervals.

• FeatureFormView : New ICommand properties simplify creating apply and discard buttons which automatically enable and disable respectively, based on pending edit states.

Toolkit bug fixes and improvements

• FeatureFormView and text input borders

  • Fixed missing borders for text areas on iOS and MacCatalyst.
  • Fixed border visibility for TextBox in FeatureFormView in dark mode on UWP and Windows.

• FloorFilter component on MAUI/Windows/Android

  • Fixed crashes and navigation issues when switching or selecting sites.
  • Addressed collection view issues that were present in .NET 9, with workarounds in place for MAUI and additional bug fixes for Android.

• PopupMediaView and Portal Item Download

  • Added the ability to pause, resume, and restart downloads for portal item data using a new download helper class.
  • The download supports serialization and validation using etags and date stamps to ensure data consistency.

• Basemap Gallery and SceneView issues

  • Fixed occasional crashes relating to "Canvas trying to use a recycled bitmap" error when scrolling quickly in the Basemap Gallery Appearance sample on Android.

• SearchView Geocoder

  • Fixed an issue where the EnableDefaultWorldGeocoder setting was not being properly honored in SearchView.

• New MapViewController MVVM control

  • The new MapViewController now uses IdentifyGeometryEditorAsync and MapView specific methods to streamline MVVM workflows for map view operations.

• Toolkit Controls – WinUI AoT Support

  Updated BookmarksView, Legend, OverviewMap, and FloorFilter controls to support WinUI ahead-of-time (AoT) compilation, fixing rendering and binding issues.

• Other Toolkit Improvements

  • Added UtilityAssociationsFormElement to FeatureFormView for improved utility network editing workflows.
  • Improved error handling and UI consistency across platform toolkits.
  • Optimized FeatureFormView performance with large form definition.
  • Improved accessibility for BasemapGallery and ScaleLine controls.

ArcGIS Maps SDK for Local Server is deprecated. The last release of Local Server will be ArcGIS Maps SDK for Local Server 200.8. For more information, see the deprecation announcement.

ArcGIS Maps SDK for Local Server 200.8 is an incremental compatibility release that provides support for geoprocessing and map packages created with ArcGIS Pro 3.5.

ArcGIS Maps SDK for .NET 200.8 supports:

• ArcGIS Maps SDK for Local Server 200.8
• ArcGIS Maps SDK for Local Server 200.6
• ArcGIS Maps SDK for Local Server 200.1
• ArcGIS Runtime Local Server SDK 100.15

To use a specific version of Local Server, reference the version of the Esri.ArcGISRuntime.LocalServices NuGet package that corresponds to the version of ArcGIS Maps SDK for Local Server or ArcGIS Runtime Local Server SDK. For more information see the Deploy Local Server guide topic.

There are no breaking API changes with this release.

• With this release, GeometryEngine.Reshape() now supports true curves.
• With ArcGIS Online now supporting true curves, you can now apply edits to circular arcs in an ArcGIS Online hosted feature service.
• The wkt2 string description of a SpatialReference is now read in preference over wkt for FeatureLayers and Geodatabases and is also contained in their Spatial Reference output json.
• JSONSerializable.toJSON() method now serializes properties from the unknownJSON collection.
• This is the last release where creating an IntegratedMeshLayer using the ArcGISSceneLayer constructor workflow is supported. Starting from next release, it is recommended that you use the IntegratedMeshLayer constructor to create a layer of that type.

• Class ArcGISHttpClientHandler is now deprecated. To make requests using the SDK's network stack, taking advantage of its authentication and caching features, use ArcGISHttpMessageHandler instead. If your app relied on HttpRequestBegin and HttpRequestEnd events, switch to IHttpMessageInterceptor instead.
• ArcGISHttpRequestMessage.Handler property is deprecated. Use HttpConfigurationExtensions to change the default handler, or set an IHttpMessageInterceptor that implements custom handling for individual messages.
• ServerInfo class and related APIs are now deprecated. To configure OAuth for a server, create an OAuthUserConfiguration.
• ArcGISPortal.GetLoginTypeForUriAsync method and PortalLoginType enum are now deprecated. To determine login type, use ArcGISPortal.CreateAsync with loginRequired=true. Then check CredentialRequestInfo in the ChallengeHandler.
• GenerateTokenOptions and related types such as GenerateTokenOptions are marked deprecated with this release. GenerateTokenOptions are only used by obsolete TokenCredential types. To configure token creation for ArcGISCredential subclasses, use the configuration parameter to the CreateAsync() of those subclasses.

• The UtilityNetwork constructors with URI are deprecated and will be removed in a future release. Use the constructor that accepts a ServiceGeodatabase instead.
• unknownJSON and unsupportedJSON properties have been deprecated from the JsonSerializable JsonSerializable interface and objects which follow a similar pattern. Use the JSONSerializable.toJSON() instead to get all JSON data for an object. Since Map and Scene objects can be large and expensive to parse and serialize, a new unusedJSON property has been added specifically to those root objects.

• The FeatureSubtype.domains property is deprecated and will be removed in a future release. Use the Field.domain in the FeatureSubtype.fieldOverrides instead.

• IntegratedMesh enum value is deprecated from SceneLayerDataType.

• OpenStreetMap (OSM) basemaps are in mature support and will no longer be updated. They will be removed in a future version of the ArcGIS Maps SDK for .NET. For more information, see the Overture Maps Data in ArcGIS blog. We recommend that you replace your OSM BasemapStyle with the equivalent Open Basemap styles, as follows:

  OSM Basemap style	Open Basemap style
  OSMStandard	openOSMStyle
  OSMStandardRelief	openOSMStyleRelief
  OSMStandardReliefBase	openOSMStyleReliefBase
  OSMStreets	openStreets
  OSMStreetsRelief	openStreetsRelief
  OSMLightGray	openLightGray
  OSMLightGrayBase	openLightGrayBase
  OSMLightGrayLabels	openLightGrayLabels
  OSMDarkGray	openDarkGray
  OSMDarkGrayBase	openDarkGrayBase
  OSMDarkGrayLabels	openDarkGrayLabels
  OSMStreetsReliefBase	openStreetsReliefBase
  OSMBlueprint	openBlueprint
  OSMHybrid	openHybrid
  OSMHybridDetail	openHybridDetail
  OSMNavigation	openNavigation
  OSMNavigationDark	openNavigationDark

• BingMapsLayer and BingMapsLayerStyle are now deprecated and will be removed in a future version of ArcGIS Maps SDK for .NET. Microsoft has deprecated Bing Maps for Enterprise, which will retire and be replaced by Azure Maps on June 30, 2028. As a result, use of Bing Maps in ArcGIS Maps SDK for .NET is also deprecated. You can migrate from Bing Maps to Azure Maps by following the instructions in the Microsoft Azure documentation.

There are no OS or framework deprecations with this release.

Issues addressed in this release are listed below.

• Memory leak issues that occur when reloading a mobile map with a UtilityNetwork could lead to failures in trace operations.
• UtilityNetworkValidationJob does not propagate server errors when it is unable to acquire a lock.
• UtilityNetworkValidationJob encounters failures when provided with an extent that includes m-values.
• FeatureLayer.FloorDefinition property is not honored by a floor-aware SubtypeFeatureLayer when included in a web or mobile map.
• ContingentValuesDefinition fails to load with version 11.5 ArcGIS Enterprise reference feature services
• Issue reported on Esri Community: Rapid zooming in using the mouse wheel causes a much higher zoom level than expected.

• Unable to evaluate FeatureSetByName() Arcade function referencing a SubtypeFeatureLayer in pop-ups.
• The ServiceFeatureTable.UndoLocalEditsAsync() and ServiceGeodatabase.UndoLocalEditsAsync() methods fail to revert the addition of features in a change-tracked non-spatial table.

• BUG-000174584 - Polyline feature symbol based on DictionaryRenderer moves instead of resizing when its length is edited in ArcGIS Maps SDK for .NET v200.6.

• Layers configured with custom dictionaries do not display on the map when parsing dictionary version in a web style.
• BUG-000174246 - When drawing a graphic line with static rendering mode, unnecessary graphics are drawn along with the graphic line in a 3D SceneView.

• BUG-000177255 - Authentication fallback in ArcGIS Maps SDK for .NET v200.7 causes request queuing and slow map loading for maps with 7+ layers.
• Issue reported on Esri Community: Non-stop loop of authentication challenges are issued.
• Creating a Polyline with MapPoint containing X,Y and Z generated a polyline with Z values.
• KmlPlacemark extent not updating after KmlPlacemark.KmlGeometry is changed.
• Some items missing from PortalQueryResultSet when PortalQueryParameters.CanSearchPublic is false.

Known issues or limitations for this release are listed below.

• BUG-000152185 - Query fails when using a large geometry in (only in ArcGIS Runtime Local Server SDK or ArcGIS Maps SDK for Local Server).
  • Workaround: Use GeometryEngine.Generalize() method to reduce the size of the request. In general, we recommend using the mobile geodatabase format instead of the Local Server component.
• BUG-000174311 - Space character replaced with + symbol when applying edits (only in ArcGIS Runtime Local Server SDK or ArcGIS Maps SDK for Local Server).
  • Workaround: Use client-side logic to validate user attribute entry and avoid spaces in attribute strings. Alternatively, implement server-side post-processing logic to validate attribute strings and replace "+" characters. In general, we recommend using the mobile geodatabase format instead of the Local Server component.

• Consolidated scene layer samples.
• Raster sample has been enhanced to demonstrate applying HillshadeRenderer to offline raster data.