Release notes for 100.10
This section describes new features and improvements (what's new).
With ArcGIS Runtime 100.10.0, you can access content on ArcGIS Online, such as web maps, web scenes, layers, items, and services, with an API key. An API key is a unique identifier used to provide authenticated access to a secured resource. An API key is similar to a token, but does not expire and can be used to monitor service usage from your apps.
A default API key is created for you when you sign up for an ArcGIS Developer account. If you already have an ArcGIS account, you can use your dashboard to edit your default API key or to create new keys. You can configure an API key with the following:
- Services your key is permitted to access
- Map or layer content (items) accessible with the key, such as hosted feature services, web maps, web scenes, tile layers, and so on
For more information about creating, configuring, using, and monitoring API keys see the API keys topic in the guide.
ArcGIS Runtime 100.10 introduces a new enum,
BasemapStyle, that defines a set of Esri basemaps for use in a map or scene. These basemaps are based on services that are secured and globally load-balanced for high performance. They can be accessed via an API key (described above) or a named user account. When using an API key, you can monitor the usage of the basemap services from your apps.
Multi-version, side-by-side deployments of the WPF API included with ArcGIS Runtime SDK for .NET are now supported. This enhancement required a minor change to the deployment profile: RuntimeCoreNet.WPF.dll and RuntimeCoreNet.dll files now include the version number in the file name: RuntimeCoreNet100_10.dll RuntimeCoreNet100_10.WPF.dll. Additionally, a manifest file is now included with the native libraries and must be included in your deployments to enable multi-version, side-by-side support. Note that if you are using WPF for .NET Core and have written a custom DllImportResolver, you will need to update the dll name string. Consider using
String.StartsWith("RuntimeCoreNet") to locate the library.
With ArcGIS Runtime 100.10.0, the following Arcade 1.11 functions in popups are now supported:
Support for all other Arcade 1.11 functions in popups was added at 100.9.0. See the Arcade version matrix for more details about Arcade support for the ArcGIS platform.
ArcGIS Runtime 100.10 now provides an option to limit viewing and editing access to branch versioned feature services through session types (
FeatureServiceSessionType). A service geodatabase in a persistent session will acquire a shared lock from the server during load which may be upgraded to an exclusive lock during an edit to allow multiple simultaneous viewers or a single editor. A service geodatabase in a transient session will not hold a lock in order to allow concurrent viewers and editors. A new close method has been added to service geodatabase that will stop any active viewing or editing by releasing any acquired locks. A web map or web scene with feature layers and tables from branch versioned feature services will load in a transient session by default and may be changed to load in a persistent session at the map or scene level via load settings.
There is a significant improvement in this release when creating graphics with multiple attributes or setting multiple attribute values on graphics. Compared to the previous release, performance for such operations is up to 40% faster.
ArcGIS Runtime 100.10 includes a new location data source,
NmeaLocationDataSource, for parsing NMEA messages from high-accuracy GNSS devices (GPS receivers). NMEA versions 4.11 and earlier are supported. The locations that are generated contain advanced metadata, such as satellite configuration, dilution of precision (HDOP, VDOP, PDOP), differential correction age, etc. This is similar to the functionality included in ArcGIS Collector.
Feature layers displayed in a scene now use tile-based requests to fetch and display features when the underlying feature service supports this capability. Feature tiles enable ArcGIS Runtime to display more features from the service, and provides faster initial load time by generalizing complex geometries for display. Feature tiles use a Protocol Buffers binary format to compress the data being transferred, along with advanced HTTP caching semantics to reduce the impact of network latency and improve performance. This functionality was added at 100.9 for 2D maps.
You can now enable labeling in a
SceneView in the same way you could previously in a
MapView. Point, line, and polygon feature layers from web scenes, line and polygon feature layers from mobile scene packages (.MSPK), and graphics overlays can all display labels on or around features rendered in the 3D scene.
LabelDefinition specification for each label class attached to a feature layer or graphics overlay is used to control positioning of the text labels.
Labeling of point feature layers from a mobile scene package or using a
LabelSymbol3D from a web scene is not supported in this release.
Rendering of Image Service rasters in a map has been improved by using a single request to fetch image data from the server. This results in a single, consistent, contiguous image that fills the view extent, rather than displaying a patchwork of individual tiles, and in some cases, reduces the latency of displaying the data.
At this version, ArcGIS Runtime supports version 2.18 of the web map specification. The supported specification governs which properties are preserved when loading and saving maps. See the web map specification documentation for more information.
Network/Transportation datasets can now include an abbreviation table, which allows ArcGIS Runtime to apply more accurate and flexible abbreviation expansion when generating voice guidance instructions from the direction text. These tables can be created and populated using ArcGIS Pro.
In this release,
OfflineMapTask has been updated to recognize settings made by the web map author, to allow leaving layers online. In previous releases, offline workflows either skipped online-only content entirely, or required the developer to specify which layers should remain online. With this update, using the web map author's settings now allows apps to be much more data-driven and gives the author more options for configuring workflows. For example, an author can set up a map to include online-only layers (such as traffic or weather), or they can mandate that a specific layer always remain online (perhaps because it is updated on a regular basis). Currently, there is no online authoring experience to allow the web map author to configure these settings.
This release of ArcGIS Runtime supports the newer, Compact Cache V2 (.tpkx) format for exporting tiles using
ExportTileCacheTask. This is in addition to the existing .tpk format already supported. Data in Compact Cache V2 format conform to this open Tile Package Specification, which is used widely across the Esri platform, including ArcGIS Pro. Exporting tiles in the Compact Cache V2 (.tpkx) format is supported by ArcGIS Server, beginning with version 10.9, and by Esri's public basemaps.
When taking Esri's vector basemaps offline, the full set of fonts provided by the Esri’s World Basemaps are included in the vector tile package (vtpk file). This can add significant overhead and bloat the size of the download, especially when taking small areas offline. This release includes the option to download Vector Basemaps (for Export), which provides a reduced set of fonts instead. This option includes fewer fonts and can significantly reduce the time required to export and download a vector tile package (vtpk) file. Note that because not all fonts are included, some styles containing labels and text in non-latin characters will not display correctly, so this option is not appropriate for all use-cases.
At 100.10.0, if you are experiencing problems synchronizing your geodatabase, you can retain, inspect and troubleshoot the synchronization delta geodatabase files. If you set the
keepGeodatabaseDeltas parameter on the
OfflineMapSyncParameters then the delta geodatabase files will be saved to the app user’s temp directory. There are two types of delta files:
- Upload delta files contains local geodatabase changes to be sent to the originating feature service.
- Download delta files contains changes from the feature service to be applied to the local geodatabase.
At this release, ArcGIS Runtime supports filtering OGC API feature collections using a query based on the
TimeExtent of the
GeoView that contains them.
At this release, ArcGIS Runtime provides additional support for Common Query Language (CQL). Version 100.9 introduced support for
CQL_text, and this release extends CQL support to include
CQL_JSON expressions in the
At 100.10.0, ArcGIS Runtime supports loading and querying of features from a non-spatial OGC feature collection table.
When populating or updating a local table from an OGC service, you can now request features in a specified spatial reference (also referred to as
SRS in ArcGIS or
CRS in OGC). This leverages the power of the server to return features in the same spatial reference as your map rather than having to reproject them on the client.
With this release, the spatial reference will be honored when using a bounding box (
Envelope) or output spatial reference to query a feature collection. This allows you to return features in the specified spatial reference without having to reproject them on the client.
The following new styles are available for
Long dash dot
Short dash dot
Short dash dot dot
Note that the default cap style for
SimpleLineSymbol is now
butt which matches ArcGIS Pro and ArcGIS Online. This differs from the previous ArcGIS Runtime release, which used a
rounded cap style. To create dash patterns with rounded caps use
MultiLayerSymbol with a rounded cap style.
Cartographic Information Model (CIM) symbols, also known as advanced symbols, are now included in the web map specification for representing points. At this release, ArcGIS Runtime is able to read advanced point symbols saved in a web map, and also save them.
ArcGIS Pro release 2.6 allows you to publish a style file to ArcGIS online or Enterprise portal. This published style is referred to as a "web style". At this release, you can work with a web style just as you would a style file stored on your local filesystem or device. You can create a style from a URL or portal item and then search and retrieve symbols as you would a local style. You can also use the Esri web styles for 2D and Esri web styles for 3D in your maps and scenes.
At this version of ArcGIS Runtime, the desktop style that corresponds to a given web style stored with a dictionary renderer will be discoverable when taking a map offline. This will be available as a URL in the
WebStyle2DesktopStyle relationship. Publishing a web style with a related desktop style is available with Pro 2.7 and ArcGIS portal 10.9.
At this release, ArcGIS Runtime SDK honors a scale expression defined in a dictionary renderer.
With ArcGIS Runtime 100.10.0, you can now read a web map that contains utility network information (available when published with ArcGIS Pro 2.6). A new
utilityNetworks property returns a collection of utility networks stored with the map. All utility networks in this collection are also saved in the web map.
ArcGIS Runtime 100.10.10 can now run a trace and get associations on a named version. A new read-only service geodatabase property has been added to allow feature tables participating in a utility network to be grouped and collectively switch to a named version, apply service-level editing, and run related record queries. The service feature tables for every utility network source will load in a transient session and connect to the default version. When loading a utility network from a web map, use the
LoadSettings for the map to change the session type and then switch versions on the
ServiceGeodatabase to work on a named version.
With ArcGIS Runtime 100.10.0, you can now query connectivity associations between spatial features and nonspatial junction and edge objects in a utility network with schema version 4 or later. New nonspatial enumeration values that describe nonspatial connectivity have been added to
UtilityAssociationType, as well as a new property
UtilityAssociation that defines how far the junction is located from the nonspatial edge. Nonspatial associations may be returned when a utility element is used to get associations.
At 100.10.0, you can now collect and send filter barriers when running a trace in a utility network from ArcGIS Enterprise 10.8.1 or later. Feature barriers can now be treated like filter barriers in subnetwork-based traced where they would otherwise restrict traversal from the trace starting points to the subnetwork controllers. A new property,
FilterBarriers, has been added to
UtilityTraceParameters for this purpose.
ArcGIS Runtime Local Server 100.10 now supports geoprocessing and map packages created with ArcGIS Pro 2.7. At this release, support for packages created with ArcGIS Desktop 10.x has been removed following the deprecation notice. Information on migrating from ArcMap to ArcGIS Pro can be found in the topic Get Started – For ArcMap users.
net5.0-windows) will introduce two breaking changes:
- In XAML, types in different assemblies now require explicit XAML namespace mappings frameworks (multiple assemblies and multiple code namespaces are no longer aggregated to map to a single XAML namespace).
- In XAML, content properties (such as
Map.OperationalLayers, for example) must be set explicitly. Implicit content property values are no longer supported.
A utility network created from a map with feature layers from standalone service feature tables will no longer be composed of shared table instances. This means a branch version is not guaranteed and utility element to feature conversion needs to use the utility network source’s name instead of a table reference. To ensure table instances are shared, the map could either be created from a web map or its feature layers created from a service geodatabase matching the utility network’s feature service.
When taking Esri basemap services offline (using the
OfflineMapTask) you are no longer required to specify an export-enabled version of the service. Starting with version 100.10.0, ArcGIS Runtime will automatically switch to an appropriate export-enabled service when exporting a .tpk or .vtpk. Be aware that exporting tiles from Esri basemap services requires you to be authenticated with the service using a named user account or an API key.
The default cap style for
buttwhich matches ArcGIS Pro and ArcGIS Online. This differs from the previous ArcGIS Runtime release, which used a
roundedcap style. To create dash patterns with rounded caps use
MultiLayerSymbolwith a rounded cap style.
- Locators created with the
Create Address Locatortool (Geocoding toolbox) will not be supported after ArcGIS Runtime version 100.11. With the 100.12 release, only the locators created with the
Create Locatortool (Geocoding toolbox) will be supported. The deprecated locator format is composed of the files
.lox. The newer locator format is composed of the files
- Support on the Windows operating system for graphics hardware rendering of maps and scenes at and below Direct3D Feature Level 9_3 has been removed. Version 100.9 was the last release to include support for this capability. Version 100.10 requires Direct3D Feature Level 10_0 minimum to enable hardware GPU rendering of maps and scenes. On devices with a maximum Direct3D Feature Level at or below 9_3, ArcGIS Runtime will use the DirectX component WARP to support the display of maps and scenes via software rendering. To determine the Direct3D Feature Level(s) supported by the hardware on a specific device, follow the instructions to Open and run DxDiag.exe, select the Display tab, and within the Drivers section refer to the Feature Level value(s) listed.
- Support for deploying apps to iOS 12 is deprecated. A minimum of iOS 13 will be required at the next release.
- Support for ArcGIS Desktop 10.x packages with ArcGIS Runtime Local Server was deprecated at version 100.9 and has now been removed. The next version of ArcGIS Runtime Local Server will require packages to be created with ArcGIS Pro.
- When building Windows desktop applications with WPF, the recommended .NET target framework is .NET Core 3.1 or .NET 5. ArcGIS Runtime SDK for .NET includes a Visual Studio project template for creating an ArcGIS application with WPF on .NET Core. While ArcGIS Runtime SDK for .NET continues to support development with WPF on .NET Framework, the previous release, version 100.9, was the last release to include a project template for that combination. Find out more about Migrating WPF apps to .NET Core in the Microsoft docs.
- BUG-000135039 Japanese characters are not correctly displayed in Vector Tiled Layer
- BUG-000132755 MrSID imagery renders slowly compared to previous versions
- BUG-000132824 Importing delta fails during sync with a geodatabase containing many-to-many relationship
- BUG-000133218 The DictionaryRenderer is not honoring Size overrides specified in the .stylx file's Arcade script.
- Generalized feature geometry returned when loading featurelayer See Esri Community post
- BUG-000134479 Identify operation fails to identify circular polygon features on large scales.
- ENH-000105118 Functionality to track locations using GPS, other than the system's built-in location provider, should be included in ArcGIS Runtime
- BUG-000133727 ArcGIS Runtime does not display french accent characters correctly from Shapefile.
- BUG-000133310 The GroupLayer sublayer labels are visible despite the layers being toggled off in a mobile map package.
- BUG-000134839 ArcGIS Runtime does not render all features from a point operational layer residing in a mobile map package.
- ENH-000134742 Provide support for KMLGroundOverlay class with a 2D MapView
- BUG-000123990 When adding a UserControl to an Element Host, the Windows Form Designer Error message, "Could not find Type [Namespace.UserControl]" is returned in ArcGIS Runtime SDK application
- BUG-000120566 When attaching an image file to a feature in ArcGIS Runtime for .NET, the ArcGISFeature.AddAttachmentAsync method leads to an error: "Response status code does not indicate success: 404 Not Found".
- BUG-000132920 The error message, "SQL error or missing database" is returned when syncing a large number of edits.
- BUG-000133189 Labels in a mobile map package (.mmpk) don't give a nice user experience when the map rotates in the Navigation mode.
- BUG-000135349 Layers with refresh interval are visibly redrawn on the map, causing a flicker effect.
- BUG-000135111 Poor performance during zoomin and zoomout with WMTS layer
- BUG-000136638 Renderer.getSymbol returns Null if renderer references a dictionary web style.