≡
31.03.2025rss_feed

HERE platform release announcement - Update March 2025

Dear customer,

we are pleased to inform you about our recent releases of the HERE platform.

 

Highlights

HERE Geofencing API v8.01

 

Added originalLat and originalLon fields to the geofence GET/POST response, and added assetId parameter to both the geofence GET/POST request and response. These options help when using the multi-request feature to better match the response with the input data.

 

HERE platform

 

Pipeline Management: Stream-6.0 runtime environment supporting Flink 1.19.1 for stream pipelines is now available

 

With this release, the Stream-6.0 run-time environment supporting Apache Flink 1.19.1 is supported for HERE platform pipelines and replaces Stream-5.0 / Apache Flink 1.13.5:

  • As of March 1, 2025, new releases of the HERE Data SDK for Java & Scala support Flink 1.19.1 only.
  • More information can be found in the following resources:

 

Pipeline Management: Deprecation reminders and announcements

 

Reminder Breaking Change and Action Required - 6-month deprecation notice:

 

Starting May 1, 2025, the Contact field for all Spark and Flink pipelines available from the HERE platform / pipelines will be a required field. Pipeline Create and Pipeline Update operations will not be possible without first updating the Contact field. Automated CI/CD pipeline jobs will be impacted if you don't update the Contact field by May 1, 2025.

HERE recommends that you update the Contact field with a group distribution email rather than an individual email address to mitigate the risk of a single point-of-contact being responsible for your pipelines. Contact field information provides HERE with the ability to reach out directly to pipeline owners with future, critical deprecation notifications which help ensure that your data processing and business goals are not interrupted.

The Contact field is supported today, so you don't have to wait until May 1, 2025, to make this update. HERE recommends updating this field for all pipelines as soon as possible to avoid potential interruptions.

 

deprecation announcement Action required - Deprecated pipeline Stream-5.0 runtime environment for stream pipelines no longer supported as of March 1, 2026.

 

The Stream-5.0 run-time environment supporting Apache Flink 1.13.5 is deprecated as of March 1, 2025.

The version of Apache Flink in the platform pipeline environment and the HERE Data SDK for Java & Scala has been upgraded to 1.19.1 (Stream-6.0).

Both Stream-5.0 (Apache Flink 1.13.5) and Stream-6.0 (Apache Flink 1.19.1) will be supported between March 1, 2025, and March 1, 2026, enabling you to migrate to Stream-6.0 before the deprecation end date.

As of March 1, 2025, new releases of the HERE Data SDK for Java/Scala only support Flink 1.19.1.

Existing stream pipelines using the Stream-5.0 run-time environment will continue to operate normally until March 1, 2026.

Until this time:

  • The Stream-5.0 run-time environment will only receive security patches.
  • Use the HERE Data SDK for Java/Scala 2.71.8 or older to continue developing pipelines with the Stream-5.0 environment until you upgrade.

 

As of March 1, 2026, the Stream-5.0 run-time environment will be removed and pipelines using it will be canceled.

Migrate your stream pipelines to the new Stream-6.0 (Flink 1.19.1) run-time environment to benefit from the latest functionality and improvements.

For more details about migrating an existing stream pipeline to the new Stream-6.0 run-time environment, see the Migration Guide.

For more information, you can also refer to the Changelog.

 

HERE SDK 4.21.5.0

 

HERE SDK 4.21.5.0 for iOS, Android, and Flutter is a minor release for the 4.21.5.0 code line that provides bug fixes and improvements based on customer feedback, alongside the following new features:

  • Search: Extended search details: Added WebImage.publicationDatethat contains the photo publication date. It is meant to replace WebImage.date . These features are also supported for the OfflineSearchEngine , if available for your edition.
  • Search: Added enum values SearchError.queryEmpty , SearchError.invalidArea , SearchError.filterEmpty , SearchError.invalidCorridorPolyline , SearchError.invalidUrl , SearchError.invalidCustomOptionFormat , SearchError.invalidTruckClass ,SearchError.badRequest . These features are also supported for the OfflineSearchEngine , if available for your edition.
  • Navigation: The VisualNavigator is now able to render traffic on the route itself during turn-by-turn navigation. Added VisualNavigator.isTrafficOnRouteVisible to set and get TrafficOnRoute visualisation state. Added VisualNavigatorColors.trafficOnRouteColors to set and get the colors used for TrafficOnRoute visualization. Note that only when no TrafficOnRoute was ever set, historical traffic data will be used instead.
  • Navigation: Added new TrafficMergeWarning and related delegate to warn on upcoming merging roads. There will also be a text notification emitted together with the warner notification via EventTextListener , such as Merging road ahead, which can be enabled or disabled from the TrafficMergeWarningOptions.
  • Added a NameID data type to represent name-id pairs.
  • Routing: Added the following properties to ChargingStation : brand to include the brand name and ID of a charging station, chargePointOperator to include the name and ID of the charging point operator, and matchingEMobilityServiceProviders to list the matched E-Mobility service providers.
  • Routing: Added support for all categories of AvoidanceOptions.zoneCategory and AvoidanceOptions.zoneIds . These features are also supported for the OfflineRoutingEngine , if available for your edition.
  • Added SDKNativeEngine.getDeviceId(…) to get the unique identifier assigned to the device for an application. This device ID is primarily used for tracking Monthly Active Users (MAUs). If a device has a different device ID within the same month, it is counted as a separate MAU. However, if the device ID changes across different months, it still contributes to the same overall MAU count. Note that MAUs are only counted depending on your contract.

 

For more information, see the changelog for your HERE SDK edition and platform.

 

HERE Waypoints Sequence API v8

 

Improved handling of waypoints with multiple access time windows and introduced limit of seven access time windows per waypoint. Multiple time windows are now considered per single waypoints when finding the optimal sequence.

 

Changes, additions, deprecations, and known issues

This email focuses on highlights. However, a lot more has happened since our last announcement. Our APIs, SDKs, and tools publish their detailed API level changes in form of changelogs or release notes. For the recent changes, refer to the corresponding changelog or release notes directly:


arrow_backNewsletter: HERE

 

:

Tel.
+49 (0)2161 / 277 380 0 		Mail
info@intersolute.de 		Kontakt
© 2015 HERE
top