Release notes for 200.0

This page provides details about enhancements in the 200.0 release of ArcGIS Maps SDK for Java. It also lists deprecations, resolved issues, known issues, and more.

Enhancements

ArcGIS Maps SDK for Java

API enhancements

  • Support for the Java Platform Module System (JPMS), as described in JEP 261. Previous releases only supported automatic modules.
  • JavaFX properties have been added to GeoView and its subclasses MapView and SceneView, and classes which implement the Loadable interface.
  • Support for the JavaFX Color class. Previous versions of the API used an Int based ARGB representation for colors. Supporting the JavaFX Color class makes it easier for developers to integrate with controls such as the ColorPicker.

Toolkit

  • The Toolkit and Example App have been updated to use the Java Platform Module System.
  • Methods deprecated in version 200.0 of the ArcGIS Maps SDK for Java have been removed from the Toolkit.

Scenes (3D)

Edge rendering

Visualization of edges is now supported for 3D Object Scene Layers, which are typically used to represent buildings in your 3D scenes. Edge rendering helps you create stunning scenes with more detail and improves user depth perception. With this release, the Solid edge style is supported to accentuate and stylize the visually important edges, including substructures, exterior walls, balconies, and roofs. Edges of type Solid are rendered in a single color and are unaffected by scene lighting. Edge rendering is supported in apps built with ArcGIS Maps SDKs for Native Apps running on Android, Linux, macOS, or Windows. Support for this feature on iOS is planned for a future release. The Sketch edge style, resembling hand-drawn sketched lines, is not currently supported and will be rendered as solid edges.

Edges are supported for Java apps running on Windows and Linux but do not render on macOS in the current release. Edge rendering for Java apps running on macOS will be supported in a future release.

Utility networks

Run utility network traces offline

ArcGIS Maps SDKs for Native Apps can now run utility network traces (connected, subnetwork, upstream, and downstream) in a fully disconnected environment. You can create and fine-tune trace configuration options, or leverage named trace configurations to support even more complex traces while offline. The trace result types supported with offline utility networks are elements and functions. Offline tracing requires a mobile geodatabase with full utility network topology. These can be created using ArcGIS Pro as a standalone mobile geodatabase. In the future you will be able to create sync-enabled mobile geodatabases containing utility network topology using the OfflineMapTask or GeodatabaseSyncTask, or with offline map areas.

In this release, you can use the UtilityNetworkDefinition.capabilities to determine which utility network operations are available with your data. For example, a sync-enabled mobile geodatabase created with ArcGIS Enterprise 10.9 containing utility networks supports querying associations but not tracing. However, a standalone mobile geodatabase exported with ArcGIS Pro 2.9 or later that includes a full utility network supports both querying associations and tracing.

Labels and annotation

Vertical text can display upright CJKV characters

Annotation features and labels displayed using ArcGIS Maps SDKs for Native apps can now have their character glyphs rotated in place to appear vertically. This is primarily intended for Asian text (including Chinese, Japanese, Korean, and Vietnamese). It requires that the annotation be published from ArcGIS Pro with the text symbol's block progression property set to right to left, and that the layout of the overall text is closer to vertical than horizontal. See Text symbol properties in the ArcGIS Pro documentation for more information.

Indoor positioning

Positions are restricted to the surveyed area

In previous releases, indoor positions were interpolated for areas outside of the Indoor Positioning System (IPS) survey. Positions are now only shown for areas that have been surveyed.

Quality improvements

  • Better compatibility with RouteTrackerLocationDataSource
  • More consistent ordering of time stamps
  • Improvements to positional accuracy and floor level estimation

Arcade

Support for Arcade 1.20

ArcGIS Maps SDKs for Native Apps now support Arcade 1.20. For more details, see the Arcade 1.20 release notes. Some enhancements include:

Note that the enhancement to the GetUser function to accept zero arguments always returns null, since ArcGIS Maps SDKs for Native Apps do not have the concept of an active portal.

Improved consistency with the online implementation

A trailing comma is now consistent with the online Arcade implementation. For example:

  • Function definitions function myFn(a,b,c,) {}
  • Function calls myFn(10, 11, 12,)
  • Array literals [1,2,3,]
  • Dictionary literals { hello:"world", good:"night", }

The checker that determines where function definitions are allowed has been improved. These checks are now consistent with the online implementation and prevent edge cases that could cause confusion around scoping rules. Function definitions within while statements, inside other function definitions, and codeblocks of if statements are not allowed.

Breaking API changes

  • All API that was deprecated in 100.x has been removed in this release.
  • In Arcade 1.20, the terms import and export are now keywords and are no longer available for use as variable or function names in an Arcade script.
  • Methods on classes that get a color using the Int based ARGB representation have been modified to return the JavaFX Color class. Existing setters for colors using the Int based ARGB representation still remain in the API, but are marked for deprecation.

Behavior changes

  • Arcade expressions now support case insensitive lookup of attribute names for GraphicOverlays (as they already do for FeatureLayers)
  • If a LabelDefinition.Angle expression attempts to use an attribute that does not exist, then no label will be produced (rather than assuming an angle of 0). This behavior is consistent with the LabelDefinition.Expression that produces the text.

Deprecations

API deprecations

  • Methods on classes that set a color using the Int based ARGB representation, rather than the JavaFX Color class, have been deprecated in this release.

OS and framework deprecations

There are no OS or framework deprecations with this release.

Issues resolved

  • Third Party library libexpat has been upgraded to v2.5.0
  • Third party library zlib has been upgraded to v1.2.13

Known issues

  • Edges for 3D Object Scene Layers are not supported for Java apps running on macOS in the current release. Edge rendering for Java apps on macOS will be supported in a future release.

Changes in samples

Enhancements

  • All samples have been updated to use the Java Platform Module System.
  • Methods deprecated in version 200.0 of the ArcGIS Maps SDK for Java have been removed from the samples. This includes the replacement of methods using Int based ARGB representation for colors with the JavaFX Color class, improving integration with JavaFX UI controls such as the ColorPicker.
  • JavaFX properties added in version 200.0 of the ArcGIS Maps SDK for Java have been implemented in the samples. These include a loadStatus property and drawStatus property.

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