Release notes for 200.2

This page provides details about enhancements in the 200.2 release of ArcGIS Maps SDK for .NET. It also lists this release's deprecations, resolved issues, known issues, and more.


Scene layers

Filter features in 3D object and point scene layers

Scene layers of type 3D object or point scene layer now support filtering by features and by area. Support includes web scenes published containing scene layers with filtered features. Features can be filtered using one of the following new methods on the ArcGISSceneLayer class:

Filter scene layer with IDs

Features in scene layers can also be filtered spatially using one or more polygon areas. A new class called SceneLayerPolygonFilter defines a filter from a set of polygons and a spatial relationship. The spatial relationship determines whether to show only those features inside the filter area or those outside the specified area. The filter is applied to the ArcGISSceneLayer via a new polygonFilter property.

Filter scene layer with IDs

Support for relative to ground surface placement mode

Scene layers of type 3D object scene layer or point scene layer now support features with a surface placement mode value of Relative (relative to the ground surface). This enhancement adds initial support for a new collection of global 3D scene layers. With this release, the Living Atlas layer OpenStreetMap 3D Buildings (Beta) can now be used in your 3D scenes.

Edge rendering

This release completes support for displaying edges on 3D object scene layers across all Native Maps SDKs and on all platforms.


Support for custom feeds

With this release of ArcGIS Maps SDKs for Native Apps, you can create a custom DynamicEntityDataSource. This new API allows you to bring data from custom feeds that you manage into a DynamicEntityDataSource as dynamic entities. You can visualize them in your application using a DynamicEntityLayer. The API is flexible, allowing you to manage the connection and process data from any data feed required by your application. Use the custom DynamicEntityDataSource to connect to a variety of feed types from streaming feeds over a socket to data files that are updated over time.

Specify fields when connecting to an ArcGIS stream service

This release includes the ability to specify a subset of fields from an ArcGIS stream service using ArcGISStreamServiceFilter.OutFields.

Support for camera controller, viewshed, and line of sight on a dynamic entity observation

In addition to a DynamicEntity, you can now use a DynamicEntityObservation as the input to a GeoElementViewshed, GeoElementLineOfSight, and OrbitGeoElementCameraController.

Performance improvements

Several performance improvements have been made to dynamic entities in this release. DynamicEntityObservation attribute information is now compressed down to 25% of previous sizes, and observational parsing has been increased by up to a factor of four, allowing for higher throughput.


Support for clustering of point features

With this release, ArcGIS Maps SDKs for Native Apps adds support for feature clustering. Point features in a feature layer can be clustered in a map when displayed using dynamic rendering mode.


Feature clustering dynamically aggregates groups of points that are within proximity of each other so they can be represented with a single symbol. The size of the symbol indicates the relative number of points it represents. Clusters are updated as the map scale and extent changes, allowing you to see patterns in the data that may otherwise be difficult to visualize with a large number of overlapping points. You can use ArcGIS Pro or ArcGIS Online to author and publish point feature layers enabled with clustering.

Adding a cluster-enabled feature layer to your Native Maps SDKs app, or opening a web map that contains one, will render clusters if the layer's rendering mode is dynamic. If the rendering mode is set to static, individual features in the layer are drawn using the layer's renderer.

Here are some details about working with clustering in ArcGIS Maps SDKs for Native Apps:

  • A layer's renderer is separate from its cluster renderer. If a cluster renderer was not defined when authoring the data, the layer's renderer is used to infer cluster symbology.

  • If the rendering mode is set to static, individual features are drawn using the layer's renderer. This is the same appearance the layer would have if clustering was not enabled.

  • Point features that are not included in a cluster are drawn as individual features using the layer's renderer.

  • Clusters are dynamically updated as the map's scale and extent changes.

  • Identifying a clustered geoelement returns an AggregateGeoElement. The geometry of an aggregate geoelement is the centroid of the cluster graphic and its attributes are the summary fields defined at the time of authoring or publishing the layer.

  • Pop-ups on clusters are separate from the pop-ups defined on a feature layer. When you identify an aggregated geoelement, you can get access to pop-ups defined on the clusters.

  • You can toggle the visibility of clusters. When clusters visibility is turned off, the individual features are drawn.

  • Clustering does not apply to layers with polyline and polygon geometries and is not supported in 3D.

Here are a few known issues with clustering in this release:

  • Clusters do not display labels.

  • Cluster graphics cannot be selected or highlighted.

  • Pop-up expressions that use the $aggregatedFeature variable are not evaluated.

  • If the authored cluster symbology contains size visual variables on a summary field other than cluster_count, the cluster symbols do not display with the correct sizes.


Programmatically move, rotate, and scale geometry

The GeometryEngine class introduces new static methods to move, rotate, or scale geometries.

Geometry editor

A new GeometryEditor class provides a simple way to create or edit geometries interactively in a map view. It supports a wide array of use cases, from creating quick notes on a map to allowing feature geometry editing workflows. The interactive use of GeometryEditor is complemented by its support for programmatic creation and editing methods, providing a powerful way to guide and supplement the built-in UX workflows. The appearance of the edited geometry can be customized using the range of symbology available in the API.

GeometryEditor provides functional equivalence with the legacy SketchEditor while offering greater flexibility and improved support for multipart geometries, shape editing, and programmatic usage. With the deprecation of SketchEditor in 200.2, it is recommended that you use new GeometryEditor instead.

Utility network

Utility Network offline tracing enhancements

Offline tracing support was added to the Native SDKs 200.1 release and has been improved in 200.2 with additional bug fixes and tracing support.

  • The ArcGIS Maps SDKs for Native Apps now support tracing of utility networks taken offline from an ArcGIS Enterprise 11.1 feature service.
  • Offline traces now support nearest neighbor trace results and loops tracing.
  • Offline traces have an improved performance when tracing with propagators. These new tracing enhancements are available for all mobile geodatabase types.

SubtypeSublayer feature templates

Custom feature templates can be configured for each FeatureSubtype in a Subtype Group Layer using ArcGIS Pro, and the Native Maps SDKs now provide these templates via the SubtypeSublayer.FeatureTemplates property.


Support for Arcade 1.23

ArcGIS Maps SDKs for Native Apps now support Arcade V1.23. Enhancements include the following:

  • Support for new geometry functions NearestCoordinate and NearestVertex.

  • Support for binary and octal number literals.

  • Updates to Feature and Dictionary functions. These functions now accept more types, easing conversions between features, dictionaries, and geometries.

  • Reduction of preparation time by half when a script is evaluated. This reduction is most significant in multiple evaluations of a small script, for instance a script calculating a value from a few feature attributes.

The newly added GetEnvironment function has limited support: locale and application values always return empty strings.

SDK Enhancements

Improvements and optimizations

  • Enhanced reporting of rendering errors is now available for all UI frameworks and all platforms supported by ArcGIS Maps SDK for .NET. In the unlikely event a rendering error occurs, the GeoView will pause rendering and the error message will be displayed.
  • With this release, load errors caused due to AuthenticationManager.ChallengeHandler not being set will be logged and written out to console output.
  • Improved HTTP cache performance on UWP and .NET 6 platforms.
  • Callouts can now automatically apply dark mode styling on Android, iOS, and Mac Catalyst.
  • OAuth 2.0 and Refresh Token improvements:
    • Added a new property RefreshTokenExpirationDate to estimate how long the user will stay logged in.

    • Allow setting TokenExpirationInterval to TimeSpan.MaxValue to request tokens with the longest allowed lifespan.

Enhancements and new features for the .NET Toolkit

  • The PopupViewer control included with the Toolkit for .NET MAUI now has improved text formatting and is enhanced to support the display of rich elements such as media, charts, and attachments. This enhancement was previously only available with version 200.1 of the Toolkit when using WPF.

Local Server

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

You can use ArcGIS Maps SDK for .NET 200.2 with ArcGIS Maps SDK for Local Server 200.1 or 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 Runtime Local Server SDK or ArcGIS Maps SDK for Local Server. For more information see the Deploy Local Server guide topic.

Breaking API changes

  • Projection Engine compatibility: The internal directory structure of the Projection Engine data files has changed. The new file structure within the Projection Engine data files version 200.2 is supported with ArcGIS Maps SDKs for Native Apps version 200.1 or later. If your application deployment includes the Projection Engine data files, you may need to update your build or setup process to reflect this change.

Behavior changes

  • GeometryEditor.symmetricDifference now supports curves.
  • Projection engine (PE) data for geographic transformations are arranged in a different file structure than previous releases. This change is designed to accommodate the increasing number, complexity, and size of the data files. See the readme in the projection engine data download for more information.
  • LabelDefinition.WhereClause sql can now include N for literal unicode text.


API deprecations

There are no API deprecations with this release.

OS and framework deprecations

  • The last release to support .NET 6 and .NET 7 is version 200.2. A minimum of .NET 8 will be required at the next release.
  • Support for Windows 10 Enterprise LTSC Version 1809 (Build 17763) and Windows Server 2019 Standard and Datacenter is deprecated. Version 200.2 is the last release to support these versions. A minimum of Windows 10 Enterprise LTSC Version 21H2 (Build 19044) and Windows Server 2022 Standard and Datacenter will be required at the next release.
  • Support for iOS/iPadOS 14 is deprecated. The last release to support this version is 200.2. A minimum of iOS/iPadOS 15 will be required at the next release.

Issues resolved

Issues addressed in this release are listed below.

  • BUG-000148628: After tilting scene towards the zenith, it is not possible to tilt it back towards the earth's surface.

  • BUG-000149324 Fixed an issue where pop-ups did not load when certain fields are hidden before publishing.

  • BUG-000152125: Changing the visibility of GroupLayer layers for map image layers does not trigger the layer viewer state change handler on a MapView object.

  • BUG-000155877: The nested feature group layer stored in a mobile map package (.mmpk) shows inconsistent visibility when the group feature layer's toggle button in the layer list is switched on or off.

  • BUG-000157495: Fixed an issue where new attachments may not be submitted for features to a feature service layer when the service contains a second layer without a global ID field.

  • BUG-000158130: Fixed the value reported by the scaleSymbols property of SubtypeFeatureLayer.

  • BUG-000158132: Fixed an issue where cloning a SubtypeFeatureLayer did not retain the scaleSymbols properties of sublayers.

  • BUG-000155955: The second raster image from a mosaic dataset disappears while interacting with the MapView.

  • The 3rd-party Libtiff library has been upgraded to 4.5.1.

  • Fixed a bug where an utility network that is configured with the "only include simple features" option could not be loaded from an ahead-of-time offline map.

  • Fixed a bug that did not preserve the rendering or pop-up configuration for a SubtypeFeatureLayer when taken offline in some scenarios.

  • Improved performance and decreased memory usage when reading mobile map packages, webmaps, and webscenes.

  • Fixed a bug that cleared attributes of a child feature in a simple relationship when its parent feature was deleted.

  • LocationDisplay.LocationChanged not firing when a .NET iOS app is backgrounded.

  • BUG-000152965 The current location displayed as a blue colored dot disappears when switching between apps on an iOS device.

  • Setting HttpConfiguration.IsCacheEnabled had no effect.

  • Refresh tokens would sometimes expire before the token is refreshed. Default RefreshTokenExchangeInterval is now 24 hours. Setting this property to TimeSpan.Zero will disable automatic refresh-token exchange.

  • Basemap Gallery control occasionally throws InvalidOperationException: Collection was modified; enumeration operation may not execute due to a race condition when layers are loading and populating as the map starts up.

Known issues

Known issues or limitations for this release are listed below.

  • BUG-000160506: Using GeometryEditor to transform a geometry that has a different spatial reference than that of the associated map view can appear to distort the geometry. A workaround for this bug is to first project the geometry to the spatial reference of the map view and then pass it to the GeometryEditor.
  • When a freehand or a shape tool is selected in the GeometryEditor, using multi-touch gestures on the GeoView (such as pan/zoom/rotate) unexpectedly activates the tool and creates geometries.

Changes in samples

New samples


  • Replaced SketchEditor with new GeometryEditor.

  • Updates to WinUI sample viewer to use single packaged app project.

  • Implemented Central Package Management for all sample viewers.

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.