Oct 2026 Platform Release Notes

HERE Real Time Traffic

• Expanded deep coverage in TML3.4-proto realtime and TML3.4-proto predictive feeds for regions North America and India.

• Traffic incident feed improvements for Germany (Berlin), Canada (Manitoba), United States (Illinois), and Croatia regions.

• Improved alignment of specific Alert-C codes to event type categories in the incident feed. Most Alert-C code changes are closure-related, and so will now be mapped to a Closure event type.

• Enabled truck bias for the Czech Republic, Slovakia, and Slovenia.

• Enabled stoplights for the WEU region.

• Implemented predictive rush-hour improvements based on fresh pattern content indicating high traffic.

• Major probe provider integrated in the EU region.

• Improvements to closure on the Bay Bridge in San Francisco.

• Traffic ramp segments incident feed improvements for North America and EU regions.

• Improved deep coverage for automatic closure verification.

• Improvements for automatic closure detection/automatic closure verifications to address superlink issues.

• Rollback of realtime flow model tuning and stoplight optimizations on arterial roadways.

HERE SDK

Version 4.28.0.0

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

• Map data:

  • Added DirectedLocalSegmentId and LocalSegmentId to represent map-data segments. Added SegmentData.localSegmentId, SegmentDataLoader.getLocalSegmentsAroundCoordinates, SegmentDataLoader.loadLocalData, and SegmentDataLoader.loadDirectedLocalSegmentData for working with these segment types.

• Map view: Added MapView.setOwningWindowAndScene(_:_:) to set the owning window and scene in CarPlay use cases, enabling proper handling of scene activation events and immediate, up-to-date display metrics.

• Search:

  • Added SearchEngine.searchByPlaceIds(placeIdQueries: [PlaceIdQuery], languageCode: LanguageCode?, and completion:PlaceIdsSearchCompletionHandler) to resolve up to 50 place IDs in a single request.

  • Added PlaceIdResult, which holds the input queryId and resolved place. The place field is nil when no place can be resolved for the input PlaceIdQuery.id. PlaceIdsSearchCompletionHandler is called on the main thread when the request completes.

• Search: Added Details.streetInfos, containing a list of StreetInfo objects with street-name decomposition metadata (for example, extracting "Mariacka" from "ulica Mariacka"). Note that this is a beta release of this feature.

• Routing: Added the optional RouteHandle.source property to identify the RoutingEngineSource that created the handle. Added RoutingError.incompatibleRouteHandle, which indicates that a route handle was passed to a routing engine other than the one that created it. Such calls now fail with this error instead of issuing a request or returning RoutingError.invalidParameter.

• Indoor routing:

  • Added built-in default marker icons to IndoorRouteStyle. If no custom markers are set for the start, destination, walk, drive, or level-change features, the SDK displays default icons automatically.

  • Added the IndoorRoutingController.showRoute(route:) overload to render a route with the default style without an IndoorRouteStyle instance.

• Map view: Changed the return type of DataAttributeValue.getType() from deprecated DataAttributeValueValueType to DataAttributeValueType. Note that this is a beta release of this feature.

• Search: Added Address.intersectionStreets field, which is populated instead of Address.street when PlaceType is PlaceType.INTERSECTION.

• Map view: Added DataAttributeValueType to replace DataAttributeValueValueType.

• Routing: Removed the beta tag from EmpiricalConsumptionModel and PhysicalConsumptionModel. EVConsumptionModel and EVCarOptions are planned to be removed in an upcoming release.

• Flutter plugin: Added Swift Package Manager support for the HERE SDK iOS plugin. This avoids warnings with Flutter 3.44 and later. The plugin remains compatible with CocoaPods.

The OCM base version was also adapted and now starts with OCM v.237 for RoW and v.101 for Japan (MOM2 based).

HERE Map Content v2 / HERE SDKs / Map Rendering Services

Lake Ontario Geopolitical Name Update

Beginning September 28, 2026, the USA political view includes Lake America as a replacement name for Lake Ontario. This change only affects 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.

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, and Map Rendering Services. The political view 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 September 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

Environmental Zones: Introduction of relative_age_range [Breaking Change]

Effective January 2027, Environmental Zones will publish vehicle age restrictions using the new relative_age_range attribute instead of vehicle_age.relative_age

The vehicle_age.relative_age attribute will remain available in the HMC schema but will no longer be populated in Environmental Zones publications. Vehicle age restriction data will be provided exclusively through relative_age_range.

relative_age_range provides support for:

• start and end date ranges,

• upper-bound-only restrictions,

• lower-bound-only restrictions.

This is a breaking change. Organizations using vehicle_age.relative_age must migrate to relative_age_range before January 2027.

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;

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.

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 Account

Deprecation Notices

Reminder: As a reminder from the March notification, HERE will deprecate SMS-based two-factor authentication and introduce authenticator-based authentication for platform accounts using password-based platform account logins as an option. There is no change for SSO-based authentication.

HERE Platform / Identity & Access Management

Reminder: Beginning Oct 15, 2026, the default access model for IAM API access via apps will be blocked. Any access to the IAM API by apps will require an explicit opt-in by detaching the access filter that is attached by default to every app.Users can detach the access filter that restricts IAM API access in the app UI on the Access Filters tab, or by using the OLP CLI. For CLI instructions, see OLP CLI access filter commands: https://docs.here.com/workspace/docs/olp-cli_topics_permission-access-commands.