Release notes for 200.4

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

Enhancements

The following enhancements have been added with this release.

Editing

Snapping

The GeometryEditor now supports feature snapping when interactively creating and editing geometries. Snapping allows you to create geometries that connect and are coincident, so that interactive edits are more accurate, with fewer errors. When snapping is enabled in the SnapSettings, visual cues indicate to the user when edits have snapped to features. See SnapSource for information about configuring layers to be valid SnapSourceSettings.

Snapping can be used during interactive edits that move existing vertices using the VertexTool. It is also supported for adding new vertices for input devices with a hover event (such as a mouse move without a mouse button press).

The snapping functionality provides one of a series of geometry editing enhancements that will roll out in future releases.

Layers and display

Support for OGC 3D Tiles Layer

This release of ArcGIS Maps SDKs for Native Apps adds support for a new layer type Ogc3DTilesLayer. The layer is based on the OGC specification for 3D Tiles. With Ogc3DTilesLayer, you can add 3D Tiles data from a public service, portal item, or a local file that includes .3tz files. The layer behaves similar to ArcGISSceneLayer and can also participate in 3D analyses.

Clustering support for GraphicsOverlay

This release adds support for clustering point graphics on a GraphicsOverlay in dynamic rendering mode. In addition, there are new APIs to highlight an aggregate geoelement in a clustered FeatureLayer or GraphicsOverlay and get access to the underlying geoelements.

Dynamic entity track line rendering

With this release, track line attributes have been enhanced to include the entity ID attribute that uniquely identifies the track. This means you can now apply a renderer to trackLineRenderer in the TrackDisplayProperties that highlights or distinguishes between tracks using one of the attribute-based renderers.

Data and query

New field types

ArcGIS Maps SDKs for Native Apps now supports fields to store the following types of date and time values:

Date only—Store values that indicate a day, month, and year. No time values are stored for date only fields.
Time only—Store values that describe a moment in time (hours, minutes, and seconds).
Timestamp offset—Store date and time values that include the time offset from the Coordinated Universal Time (UTC).

Big integer and 64-bit ObjectID fields are also now supported.

Date only - esriFieldTypeDateOnly

Use a date only field to store data that was captured in the granularity of days or that represent an entire day, such as a date of birth, a hire date, a software release date, or a holiday. Date only fields store values in the format: YYYY-MM-DD (For example: 2024-04-10).

Query exact matches against the esriFieldTypeDateOnly type using the DATE keyword along with a date value. These queries are in the format: field_name = DATE 'YYYY-MM-DD'.

For example: MyDateOnlyField = DATE '2024-04-10'.

Time only - esriFieldTypeTimeOnly

Use a time only field to store data that repeats daily or for information where only the time component matters, such as a daily meeting time, a store opening time, or a sunset time. Time only fields store values in the format: HH:MM:SS (For example: 18:30:55).

Query against the esriFieldTypeTimeOnly type using the TIME keyword along with a time value. These queries are in the format: field = TIME 'HH:MM:SS'.

For example: MyTimeOnlyField = TIME '18:30:55'

Timestamp offset - esriFieldTypeTimestampOffset

Use a timestamp offset field for data where the local time value is important and the values can cross multiple time zones, such as events recorded in local time, airline departures and arrivals, or tracking product shipments. Timestamp offset fields store values in the format: YYYY-MM-DD hh:mm:ss ± OffsetFromUTC (For example: 2024-03-30T18:30:55-05:00).

Query against the esriFieldTypeTimestampOffset type using the TIMESTAMP keyword along with a full ISO string. These queries are in the format: field = TIMESTAMP 'YYYY-MM-DD HH:MM:SS.mss ±HH:MM'`.

For example: MyTimestampOffsetField = TIMESTAMP '2024-03-30 18:30:55 -05:00'

Relative date and time queries

Relative date and time queries are now supported with all date fields (except time only) by providing the intervals in the query. Relative date queries can be performed relative to the current date or to a specified (anchored) date.

Query relative to an anchored date using this format: DateField >= AnchoredDate -+ INTERVAL 'IntervalValue' TimeStampFormat.

For example:

Date: InspectionTime >= TIMESTAMP '2024-04-10 07:00:00' - INTERVAL '2' DAY

Timestamp offset: InspectionTimeStamp >= TIMESTAMP '2024-04-10 07:00:00' - INTERVAL '2' DAY

Date only: InspectionDate >= TIMESTAMP '2024-04-10' - INTERVAL '2' DAY

There are two main formats for queries relative to the current date or time:

<DateField> >= CURRENT_DATE -+ INTERVAL '<IntervalValue>' <TimeStampFormat>

<DateField> >= CURRENT_TIMESTAMP -+ INTERVAL '<IntervalValue>' <TimeStampFormat>

For example:

Date: InspectionTime >= CURRENT_TIMESTAMP - INTERVAL '2' DAY

TimeStampOffset: InspectionTimeStamp >= CURRENT_TIMESTAMP - INTERVAL '2' DAY

Date Only: InspectionDate >= CURRENT_DATE - INTERVAL '2' DAY

You aren't limited to DAY for TimeStampFormat when using INTERVAL. Other values include HOUR, MINUTE, SECOND, DAY TO HOUR, HOUR TO MINUTE, and so on.

Utility networks

Support for shortest path traces while offline

ArcGIS Maps SDKs for Native Apps now supports the shortest path trace type for offline utility networks. This type of trace requires two starting points and a network attribute (such as shape length) and returns the shortest path based on the provided attribute. This means that utility networks with full topology from a stand-alone or sync enabled mobile geodatabase now support all of the trace types that utility networks from a feature service support.

Licensing changes

A Utility Network extension license is no longer required to analyze (trace) utility networks, and has been removed from these methods: UtilityNetwork.traceAsync(), UtilityNetwork.queryNamedTraceConfigurationsAsync(), and ArcGISMap.getNamedTraceConfigurationsFromUtilityNetworkAsync().

A new Advanced Editing extension license is now required to edit utility network features as well as create a version and edit features and tables in a branch version enabled feature service. This extension requires a minimum ArcGIS Runtime license level of Basic. Detailed information about the licensing changes made for ArcGIS Maps SDKs for Native Apps 200.4 and the specific methods that will require this license extension can be found in the License levels and capabilities topic in this guide.

Arcade

Support for Arcade 1.26

This SDK now supports Arcade 1.26

The following linear referencing functions have been added:

DistanceToCoordinate
MeasureToCoordinate
PointToCoordinate
DefaultValue and HasKey have been updated to support checking nested dictionaries, arrays, and geometries.

Notes: KnowledgeGraph functionality which is available in Arcade version 1.26 with support in Pro and Online will be available in a future ArcGIS Maps SDKs for Native Apps release. The profile variables, $userInput and $graph, added to the PopUp and Popup Element profiles are currently set to null. A non-null $userInput implementation is planned for an upcoming release.

Projection Engine updates

Coordinate systems and transformations

Available coordinate systems and transformations have been updated to EPSG v11.003. These include the Equi7 projected coordinate systems, which divide the world into seven continental areas and are designed for imagery use. New vertical transformations based on geoids, quasi-geoids, or other conversion grids can transform to or between gravity-related vertical coordinate systems for the British Isles, Corsica (France), Finland, New Zealand, St. Helena Island, and the United States. The National Geodetic Survey's historic geoid models (GEOID99, GEOID03, GEOID06, and GEOID09) and VERTCON 3.0 conversion grids for the United States are now supported. Vertical transformations using VERTCON 2.1 grids are deprecated but remain available. Transformations using VERTCON 2.1 grids appear at the bottom of the list of transformation paths.

Breaking API changes

There are no breaking changes with this release.

Behavior changes

ArcGIS Pro 3.3 introduces the ability to define output fields (Reverse Output Fields) for reverse geocode operations. With locators created using ArcGIS Pro 3.3 and later, only fields enabled in Reverse Output Fields are returned from a reverse geocode operation in 200.4 and later. Supported output fields for geocode operations (including reverse geocode) are listed in the REST API under Geocode Service output fields. For locators created before ArcGIS Pro 3.3, reverse geocode results contain all output fields.
Following the deprecation of VERTCON 2.1 and introduction of VERTCON 3.0 by National Geodetic Survey, vertical transformations using VERTCON 3.0 grids will now be returned from appropriate TransformationCatalog calls. Vertical transformations using VERTCON 2.1 grids remain usable and will still be returned from TransformationCatalog.getTransformationsBySuitability calls but will now appear at the bottom of the returned lists which are sorted by suitability. To make use of transformations using VERTCON 3.0 grids, the required grid files must be deployed with your app. These can be found in the Projection Engine Data download for this release. See the Projection Engine updates section for additional coordinate system and transformation enhancements introduced with this release.

Deprecations

API deprecations

ArcGIS Maps SDK for Java is deprecated. For more information, see the deprecation announcement.

OS and framework deprecations

Support for macOS Monterey (version 12) is deprecated. The last release to support this version 200.4. A minimum of macOS Ventura (version 13) will be required at the next release.

Issues resolved

Issues addressed in this release are listed below.

Geodatabase methods for managing transactions (beginTransaction(), commitTransaction(), and rollbackTransaction()) have been made thread-independent. Any thread can end a transaction started by any other thread, integrating with modern language and platforms' concurrency models.

Known issues

Known issues or limitations for this release are listed below.

BUG-000166643: A sceneview containing a scene with vector tiled layer can result in a crash if it's created and destroyed repeatedly. A possible workaround is to avoid using a vector tiled layer as a basemap, for example as an imagery basemap.