Release notes for 200.7

Snap geometry edits using utility network rules

The utility network includes a set of rules to determine what features can connect to one another. For example, you can connect a fuse to an electric power line, but not to a gas pipe. You can now configure the interactive snapping behavior of a GeometryEditor to account for these connectivity rules, helping you create true edits for utility network features that can be successfully validated.

You can now configure rule-based snapping by first creating SnapRules that are applicable to the utility network asset type of the feature you will edit. If you are editing existing features, create the snap rules by passing the UtilityAssetType to SnapRules.Create(). If you are creating new features, pass the attributes of the new feature that includes the asset type to SnapRules.Create(). Next, call SnapSettings.syncSourceSettings() to synchronize the snap sources of the GeometryEditor to refer to these snap rules. Provide the SnapRules that you have created and specify the SnapSourceEnablingBehavior.

Snapping support for each sublayer of a subtype feature layer

When using GeometryEditor snapping and working with subtypes, you can now configure each SubtypeSublayer for snapping individually. Each SnapSourceSettings that corresponds to a SubtypeSublayer is now available from the SnapSourceSettings.childSourceSettings collection of its parent SubtypeFeatureLayer snap source, and can be enabled or disabled independently of its parent layer.

Check for unsaved edits in a feature form

FeatureForm has a new FeatureForm.hasEdits property that allows you to know if there are active attribute edits on the feature. You can use it to enable UI elements like buttons to prompt the user to Save or Discard the edits.

Utility network associations element in feature forms

When a feature form is created (using Map Viewer or Field Maps Designer) on a layer or table that is part of a utility network, elements can now be added to show features that are associated to the feature being edited. The association form elements show all the features associated in a particular way; for example, features connected to the feature being edited, features contained within the feature being edited, and so on.

The UtilityAssociationsFormElement objects are now supported as part of the FeatureForm.elements collection. They support fetching the associated features and returning UtilityAssociationResult objects that can be displayed in a user interface.

Form notifications when features are updated externally

When a feature is updated in a local geodatabase outside of the feature form editing experience, the feature form will reflect the feature's changes when Feature.refresh is called. This can occur when there are attribute rules that run for the feature that update the geodatabase. Feature form handles this by an observed change to FieldFormElement.value as the feature's attribute is updated via to a call to Feature.refresh.

User input location support for Popups

Arcade expressions in popups can now use Popup.userInput to access information about the map location that was used to show the popup. For more information, see popup profile in Arcade.

Override the popup definition for an individual feature in a feature collection

Popup definitions can now be defined for individual features in a feature collection, allowing map authors to customize what a popup looks like for an individual feature instead of using the same definition for all features in the collection. Use FeatureCollectionTable.setPopupDefinitionOverride() to override the feature collection popup definition for a specific feature. When an identify method returns popups, the identify result will automatically have the overridden PopupDefinition. You can also use FeatureTable.getPopupDefinition(feature) to return the overridden feature-specific PopupDefinition.

Support for user-configured popup chart colors

User-configured chart colors are now supported in popups. Use PopupMediaValue.chartColors to access the collection of colors defined for a popup when rendering charts in popups. For more information, see custom colors in pop-up charts in ArcGIS Online.

New utility associations popup element

A UtilityAssociationsPopupElement is a new type of PopupElement that gives you complete control over which associations are displayed through the use of the new UtilityAssociationsFilter class. You can configure filters to only display associations of a particular type and role (such as content or connectivity), or that the feature on the other side of the association matches a particular network source, asset group, or asset type.

A PopupDefinition with a UtilityAssociationsPopupElement will be honored when included in a web map. You can also create or update a UtilityAssociationsPopupElement and save it in a web map. Note that the UtilityAssociationsPopupElement is not integrated into the "Popup" toolkit component at this time, but is a planned improvement.

Query dynamic entities

You can now query a DynamicEntityDataSource to find dynamic entities that meet spatial and/or attribute criteria. Because dynamic entities change over time, the query returns a collection of entities that match the DynamicEntityQueryParamaters at the moment the query is executed. Although the number of dynamic entities in the result set is fixed, you can monitor these entities and be notified when new observations are received. This is useful for scenarios such as: finding a flight with a particular ID, identifying all first responders in the same task team, or returning all emergency vehicles currently within a specified distance of a reported incident.

Improved performance of feature layers in a scene

In this release, performance of feature layers in 3D has been improved for line and polygon geometries. The improvement is pronounced when the layer contains a significantly large number of vertices. This improvement can result in 3 to 5 times increase in draw times and a lower CPU usage.

Support for subtype group tables

Similar to SubtypeFeatureLayer, subtype group tables allow each FeatureSubtype in a non-spatial object class to have their own query methods, edit operations, popup definitions, and more.

If a web map contains a subtype group table, the ArcGISFeatureTable.subtypeSubtables collection will be populated with SubtypeSubtable objects when the web map is loaded. You can also create, configure, and add new SubtypeSubtable objects to this collection and save them in the web map.

Load a WMTS layer from a portal item

With this release, you can now load a WmtsLayer from a portal item.

Support for image overlays in map views

MapView now supports image overlays; previously only supported in scene views. You can use an ImageOverlay to quickly render frequently changing images such as realtime sensor data. For example, to display a dynamic weather system, each frame from the weather radar is represented as a static image. This image is constantly updated via a new ImageFrame as new data comes in to give a fast-refreshing display.

Support for new Arcade version

The SDK now supports Arcade 1.31.

The following functions have been added:

• Geotrigger profile support for the Data Access bundle.
• Different curve types support in geodetic geometry functions.

Adaptive radio positioning

Indoor positioning accuracy has been improved using enhanced algorithms in our indoor positioning system (IPS) engine. The indoor location data source (ILDS) now caches statistics on received radio signals and uses the cached data to deliver more accurate positions in subsequent sessions. In addition to this new feature, the behavior of the blue dot on Android phones has been improved. Due to poor quality built-in sensors, some Android phones struggle to provide the same level of positioning accuracy as phones with higher quality sensors. The new adaptive radio positioning algorithm will mitigate this by continuously adjusting the received radio signals so that our IPS engine can calculate more accurate indoor positions.

Stand still filter

The user experience when standing still has been improved. A new filter detects when the user stops walking and locks the blue dot. If the IPS engine receives more accurate positions during this stationary period, the position of the blue dot is slowly updated.

Improved startup

During the startup phase, the IndoorsLocationDataSource (ILDS) response has been improved when a sensor fails to start or when permissions are missing. When the ILDS is running, alert handling from sensors has been enhanced and the ILDS now presents appropriate warnings.

Coordinate systems and transformations

• Available coordinate systems and transformations have been updated to EPSG v12.002.
• The names of EGM vertical coordinate systems have been revised to align with the official EPSG names.
• EGM2008 geoid transformations in the behind-the-scenes processes have been updated to use the official NGA methods.
• ArcGIS Coordinate Systems Data supplement component now includes new geographic transformation grids for Germany and the United Kingdom, as well as new vertical transformation models for Bonaire (Dutch Caribbean), European continent (EVRF systems), Finland, and Slovenia.

Augmented Reality - World Scale

The WordScaleSceneView composable function renders ArcGISScene content overlaid on the camera feed to scale, aligning real-world features like streets and buildings with the scene content.

It supports two WordScaleTrackingModes:

• World: uses the device's GPS to position the scene content.
• Geospatial: uses the ARCore Geospatial API for high-accuracy location in areas with Google StreetView data.

The composable provides parameters to configure and interact with the SceneView, such as specifying an ArcGISScene,GraphicsOverlays, and lighting. It requires an ARCore-supported device with Google Play Services for AR installed and appropriate camera and location permissions.

If using WorldScaleTrackingMode.Geospatial, the developer must configure their app to use Keyless or API key authentication with Google Cloud Console. More information on how to set this up is available here.

Scalebar

The Scalebar composable toolkit component allows developers to show a linear measurement on the map, aiding users to gauge the size of features or distances between them. This component is highly configurable, allowing users to choose between bar or line styles, customize colors, and automatically hide the scalebar after panning or zooming actions. It supports both metric and imperial units and dynamically adjusts its size and measurements based on the map's extent. The scalebar utilizes geodetic computations to ensure accuracy, making it a valuable addition for any mapping application.

Legend

The Legend composable visually explains the symbols used on a map, showing the names of Layers, sublayers, and the LegendInfo used in the map or scene. It dynamically updates to include only visible layers, adjusting as layers go in and out of scale range. Key features include filtering out layers hidden due to scale via the respectScaleRange property, reversing the order of displayed layers with the reverseLayerOrder property, and customizing the legend title using the title property. For implementation, the Legend composable can be rendered within a composition and should be displayed in a container.

Basemap Gallery

The BasemapGallery composable provides a grid display of available basemap styles, allowing users to browse and select basemaps for their map view. It accepts a lambda function to define actions when a gallery item is clicked. The basic usage involves creating a collection of BasemapGalleryItems from a BasemapStylesService and displaying them in a BasemapGallery below a MapView. The gallery's onItemClick lambda can be used to set the selected basemap on the map view.

Support for Android devices configured with 16KB page sizes

ArcGIS Maps SDK for Kotlin now supports Android devices/emulators that are configured to use a memory page size of 16 KB.

• FeatureType.id has been marked nullable to accommodate datasets containing feature types without an ID.

• GeometryEngine methods GeometryEngine.convexHullOrNull(), GeometryEngine.tryConvexHull(), and GeometryEngine.densifyGeodeticOrNull() now support true curve input, producing densified curves in the result geometries.

• The string provided by the ArcGISException.message property used to take the form:
  Use dark colors for code blocksCopy

  1
  message=<messageText>, additionalMessage=<additionalMessageText>, errorCode=<errorCode>
  for example:
  Use dark colors for code blocksCopy

  1
  message=Invalid argument., additionalMessage=Label offset must be positive., errorCode=2
  This has been changed to make the message clearer. The format is now:
  Use dark colors for code blocksCopy

  1
  <messageText>. <additionalMessageText>.
  for example:
  Use dark colors for code blocksCopy

  1
  Invalid argument. Label offset must be positive.
• The message property and toString() function of ServiceException have also changed. They are now completely consistent with what is described above for ArcGISException, whereas previously:
  • ServiceException inserted a colon between the <messageText> and <additionalMessageText>.
  • ServiceException.toString() didn't used to append errorCode=<errorCode>, but now it does.

• The IndoorsLocationDataSource constructors that use a FeatureTable are deprecated and will be removed in a future release. Use the constructors that accept a IndoorPositioningDefinition instead.

• The ArcGISException.additionalMessage property has been deprecated. The errorCode property is still available, and the errorCode is appended to the message by the toString() function. For the above example, ArcGISException.toString() returns:

  Use dark colors for code blocksCopy

  1
  com.arcgismaps.exceptions.ArcGISExceptionImpl: Invalid argument. Label offset must be positive. (errorCode: 2)

• Support for Android 8 (API 26) is deprecated. The last release to support this version is 200.7. A minimum of Android 9 (API 28) will be required at the next release.

Issues addressed in this release are listed below.

• BUG-000158647/BUG-000157410 - Layer with access key fails to load. This has been resolved by adding portal item support to WmtsLayer.
• BUG-000174246 - After running for extended periods of time (24+ hours) an application using composite symbols to render graphics will lead to a runtimecore access violation error and crash the program.
• BUG-000170373 - A custom display field displayFieldExpressionInfo is not honored in Native SDKs.
• BUG-000173617 - When related records of a feature that has 0 related records in M:N relationship are queried in ArcGIS Map SDKs, an error is returned com.esri.arcgisruntime.ArcGISRuntimeException: Geodatabase item not found, instead of an empty list.
• BUG-000174741 - The composite locator bundled in a mobile map package fails to load in the application.

• BUG-000167296 - LocationDisplay.mapLocation is not updated after first location update.

• Issue reported on Esri Community: Cancellation token not working during IdentifyLayersAsync operation causes the application to freeze.

• FeatureForm.validationErrors contains errors that are not actionable. It should only contain errors from field form elements that are visible and editable.

Known issues or limitations for this release are listed below.

• ArcGISSceneLayer does not render on x86_64 Android emulators that have a memory page size of 16KB.

New samples

• Analysis
  • Show viewshed from point on map
• Augmented Reality
  • Augment reality to show tabletop scene
• Edit and Manage Data
  • Create and edit geometries
  • Create KML multi-track
  • Download preplanned map area
  • Generate offline map with custom parameters
  • Manage features
  • Show popup
  • Set feature request mode
• Layers
  • Add raster from file
• Maps
  • Show device location using fused location data source
  • Show scale bar
• Routing and Logistics
  • Navigate route with rerouting
• Scenes
  • Display web scene from portal item
  • Filter features in scene
  • Get elevation at point on surface
• Utility Networks
  • Snap geometry edits with utility network rules
  • Trace utility network
  • Validate utility network topology
• Visualization
  • Animate images with image overlay
  • Apply hillshade renderer to raster
  • Create symbol styles from web styles

Enhancements

• Migrated 12 XML view-based samples to use Jetpack Compose, leveraging the GeoView-Compose Toolkit module.
• Replaced Sketch on map with the new Create and edit geometries sample.
• Migrated the code to use Android Gradle plugin 8.7.3, which is compatible with Gradle version 8.9.

Bug fixes

• Fixed issue with Android Studio debugging into local build files.