September 2026 Platform Release Notes

HERE SDK

Version 4.27.3.0 LTS

The HERE SDK team is pleased to announce the availability of our first Long-Term Support (LTS) release, 4.27.3.0 LTS, of the HERE SDK for iOS, Android, and Flutter.

An LTS release provides a supported production baseline for customers. Each LTS release is supported for six months, from its release date until the next LTS release becomes available. Hotfixes are provided only for currently supported LTS releases and are limited to critical issues.

Bug Fixes and Improvements

This release includes bug fixes and improvements. New features also include:

• Routing: Added Waypoint.radiusInMeters to specify the search radius, in meters, for candidate road segments to be used as waypoints during route calculation. It replaces the deprecated Waypoint.transitRadiusInMeters.

• The OCM base version has also been updated and now starts with OCM v.233 for RoW and v.100 for Japan (MOM2-based).

HERE Maps API for JavaScript 3.2.11.0

This release includes:

• Support for Map Attributes API v8

• TypeScript 6 support

• Performance improvements

HERE Platform

The following is an update to the August announcement regarding changes to HERE IAM API access.

Beginning mid-October 2026, API-based access to IAM organization or realm information will require explicit opt-in by the app manager. This will apply to all existing apps, as well as newly created apps. However, customers should not experience any impact on current app usage unless an app specifically depends on access to IAM organization or realm information.

This change supports HERE's commitment to zero trust by ensuring that access is intentional, controlled, and aligned with least-privilege principles.

What's changing

• Starting mid-October 2026, API access to IAM organization or realm information will require explicit opt-in by the app manager.

• This explicit opt-in requirement applies to all current apps and all newly created apps. If your app needs this access, follow the HERE Documentation for instructions on how to explicitly opt in.

What's not changing

General app functionality and other HERE APIs will continue to work as they do today. Apps that do not use IAM APIs or organization or realm information will not require any updates. No action is required unless your app or integration relies on information in IAM organizations or realms.

Timeline

• Now through mid-October 2026: Review whether any apps or integrations use IAM APIs or organization or realm information.

• Mid-October 2026: API access to IAM organization or realm information requires explicit opt-in by the app manager.

How to get help

If you are unsure whether you are impacted or need help, contact HERE Support.

HERE Real Time Traffic

• Improvements for the Highway Incident Source supplier in Germany.

• Traffic Incident feed improvements for Slovenia.

• Improvements made to the Tennessee Incident feed.

• Improved single-vehicle outlier handling for highways in Real-Time Flow.

• Optimized stoplight-handling thresholds for Real-Time Flow.

• Flow coverage improvements for Denmark.

• Traffic Incident feed improvements for North Carolina, US.

• Traffic Incident feed improvements for the Minneapolis Incident Feed.

• Traffic Incident feed improvements for the government incident source supplier in California.

• Expanded deep coverage in TML3.4-proto real-time and TML3.4-proto predictive feeds for the following regions: EEU, MEA, SEA, Aus/NZ, SAM.

• Launched TML3.4-proto real-time and TML3.4-proto predictive feeds for the following regions: North America and India.

• Automatic Closure Verification/Automatic Closure Detection improvements.

HERE Map Attributes

Layer Deprecation Notice

The following Map Attributes API layers will be deprecated in Q2 2027. Requests that use these layers will no longer be supported after the deprecation date.

Customers are strongly encouraged to migrate to the alternative layers listed below, where available, to ensure uninterrupted service.

HERE Map Content v2

Removal of NameType values from the Name Model

The EXONYM and ADDITIONAL_EXONYM values in Name.NameType will be completely removed by the end of November 2026. Both values are already deprecated. A new exonym field has been added to the Name message structure and will be used instead.

Three new PayPoint types in the Toll Cost layer

To improve the representation of different toll-charging models, HMC now includes three new PayPoint types in the Toll Cost layer:

• CongestionZonePayPoint

• EnvironmentalZonePayPoint

• VignettePayPoint

These new types are available in the HMC schema as of August 2026.

Schema changes

The TollSystem message has been extended with the following new PayPoint types:

CongestionZonePayPoint congestion_zone_pay_point = 6;EnvironmentalZonePayPoint environmental_zone_paypoint = 7;VignettePayPoint vignette_paypoint = 8;

Copy

The new PayPoint types behave similarly to TollSystemPayPoint, with costs associated with a toll system rather than a specific toll structure or entry/exit pair.

Important future content changes

Although schema support is being introduced in August 2026, HERE Map Content will not publish these new PayPoint types until January 2027.

By the end of January 2027, toll costs that are currently represented using TollSystemPayPoint may instead be represented as:

• CongestionZonePayPoint

• EnvironmentalZonePayPoint

• VignettePayPoint

This content migration may be a breaking change for consumers that explicitly depend on TollSystemPayPoint.

Consumers are encouraged to update their implementations during the transition period between July 2026 and January 2027 to ensure support for the new PayPoint types before content publication begins.

Planned removal of layers

Following earlier messaging, by the end of Q3 2026, the following layers will be permanently removed from the HERE Map Content catalog:

• Pedestrian Attributes

• Bicycle Attributes

These products have been retired by HERE. For questions, contact your HERE Account Executive or Technical Services point of contact.

Removal of catalog history

The removal of catalog history has been postponed until the end of Q4 2026. An exact date will be communicated in a future Developer Note. Going forward, HERE will remove catalog versions older than 18 months.

For questions, contact your HERE Account Executive or Technical Services point of contact.

Removal of layers postponed

The removal of the Warning Locations (layer ID warning-locations) layer is postponed to 2027. This layer will be replaced by one or more new layers publishing an enhanced HERE Safety Cameras content offering.

The removal of the Vehicle Regulations (layer ID vehicle-regulations) and Commercial Vehicle Regulations (layer ID commercial-vehicle-regulations) layers is also postponed to 2027.

Both layers will be replaced by new layers that publish a new HERE Motorized Vehicle Regulations content offering. The new layers will be:

• Vehicle Regulations Attributes (layer ID vehicle-regulations-attributes)

• Commercial Vehicle Regulations Attributes (layer ID commercial-vehicle-regulations-attributes)

Restricted Driving Maneuver changes

In Q2 2027, a redesign of the Restricted Driving Maneuvers schema and implementation will be introduced.

This will impact the following layers:

• Topology Attributes (layer ID topology-attributes)

• Truck Attributes (layer ID truck-attributes)

Additional details will be announced later.

Attribute Anchor optimizations

Starting Q2 2027, all segment attribute anchors will be aggregated, resulting in a smaller set of anchors and reduced attribute partition payload sizes.

An example is provided below, where 6 anchors were previously published for the Functional Class attribute on segment 205550780, compared to a single anchor matching its full extent.

This change will apply to the following layers:

• Topology Attributes

• Truck Attributes

• ADAS Attributes

• Lane Attributes

• Complex Road Attributes

• Traffic Pattern Attributes

For any questions regarding this change, contact your HERE Account Executive or Technical Services point of contact.

HERE Map Content v2 / HERE SDKs / Map Rendering Services

Coming Soon

Arabian Gulf Name Change

On Dec 1, 2026, the default name for the Arabian Gulf will be changed to the Persian Gulf. This change also affects the default international map view used by HERE SDK Navigate and Explore, HERE Maps API for JavaScript, Vector Tile API, Raster Tile API, and Map Image API.

The Arabian Gulf name can be preserved by setting the politicalView parameter for any of the countries listed in the table below. For Türkiye, the politicalView parameter must be configured to retain the name Gulf of Basra. If the Arabian Gulf or Gulf of Basra name is desired, you must update your application logic accordingly.

All countries in the table below that did not already have a political view will have one added on or before Sep 1, 2026. The three-month window between the creation of the political view and the default name change is intended to give customers sufficient time to implement the new view. During this period, implementing the view will have no impact on the naming of the Arabian Gulf.

These references explain how to set the political views for the affected countries:

• Android SDK

• Maps API for JavaScript

• Vector Tile API

• Raster Tile API

• Map Image Developer Guide

Lake Ontario Geopolitical Name Update

Starting in October 2026, the USA political view will include Lake America as a replacement name for Lake Ontario. This change affects only the USA view and will not appear in the international view or other political views. The USA political view already includes Gulf of America as a replacement name for the Gulf of Mexico.

EV Charge Points

Bug Fixes and Improvements

Improved Charging Location Lifecycle Management in EV Charge Points API v3

The EV Charge Points API v3 now provides enhanced support for charging location lifecycle management. New retention handling for deleted charging locations and improved charger status handling will help applications maintain consistency during data synchronization.

Higher result limits in EV Charge Points API v3

The EV Charge Points API v3 can now return up to 100 charging locations per request, reducing the number of requests required to retrieve charging location details.

Feature Showcase

Reliability Indicators Available in EV Charge Points API v3

Reliability Indicators are now live and available through EV Charge Points API v3. These indicators provide additional insights into charging station reliability.

Walking Distance Information in EV Charge Points API v3 and HERE Map Content

Walking distance attributes are now available in selected countries, which can help drivers better understand the distance between charging locations and nearby destinations. Coverage will continue to expand incrementally across additional markets over the coming months.

Coming Soon

EV Pricing data product

A new EV Pricing data product is coming to HERE Map Content, offering EV charging price information as a dedicated catalog product. While this data is already available through EV Charge Points API v3, the new product will provide customers with direct access through HERE Map Content.