July 2026 Platform Release Notes

HERE SDK

Version 4.27.0.0

Bug Fixes and Improvements

• Indoor map: Added support for multimodal indoor routing and via waypoints

The OCM base version was also adapted, and now starts with OCM v.225 for RoW and 97 for Japan (MOM2-based).

Version 4.26.5.0

Bug Fixes and Improvements

• Map view: Added MapView.onStop() and MapView.onRestart() to be called on matching Activity lifecycle events

• Routing: Added Span.isoCountryCode to be used with RoadShieldIconProperties.isoCountryCode

The OCM base version was also adapted, and now starts with OCM v.223 for RoW and 97 for Japan (MOM2-based).

HERE Real Time Traffic

Bug Fixes and Improvements

• Enabled 3.4 Proto Realtime for South Africa, Southeast Asia (SEA), Oceania (OCE), and South America (SA).

• Enabled 3.4 Proto Predictive for Middle East Asia (MEA) and South Africa.

• New Traffic Incident Source Provider for the Netherlands.

• Improved map matching for Japan Traffic Incident Feed.

• Improved roadworks incident handling for the Spain region.

• Improved incident processing logic for various scenarios.

• Improved incident coverage for the Canada region by updating the processing of the incident provider.

• Enabled Automated Roadwork Detection and Verification Service for Italy.

• Improved handling of disabled vehicle scenarios.

• Real-time flow model tuning and stoplight optimizations on arterial roadways.

HERE Maps API for JavaScript

Version 3.2.8.0

The new version 3.2.8.0 of Maps API for JavaScript contains the following improvements:

• Enhanced Self-Hosting support
  A new functionality to override the styleBaseUrl is introduced to fetch style assets from a custom URL. In addition a new npm package to support self-hosting assets is added to the product deliverables. A comprehensive guide is available in the documentation.

• Improved CSP compliance
  Prevent "wasm-unsafe-eval" when vector rendering is not used. The full Content Security Policy (CSP) documentation is here.

• Performance improvements
  Improved performance for vector-rendered maps and local objects.

HERE Routing

Truck Routing ETA changes in hilly terrains

By the end of August, a slope-aware truck speed model will be introduced to improve ETA predictions on uphill road segments. The model adjusts estimated truck speeds based on vehicle weight and road gradient, reflecting real-world vehicle performance on steep ascents.

Testing of this model with multiple truck probe datasets demonstrated improved ETA accuracy on mountainous and hilly routes for heavier vehicles. We expect this change will help customers achieve more reliable route planning and arrival-time estimates.

HERE Style Editor 1.17.0

Version 1.17.0 released

The new version 1.17.0 of HERE Style Editor contains new map style customization features and tool improvements.

• Font ​style customization - This new functionality gives customers more control and flexibility on how text is presented on the map. Regular, Italic, Bold, or Bold Italic can be applied to labels for greater visibility, or to create a more refined typographic style.

  

  Font Style customization of base map with HERE Style Editor

   

• Line of Control for Country Boundaries - The new feature lets you control how different types of geopolitical boundaries are displayed on the map.

For more information, refer to the developer guide.

Maps API for JavaScript

Deprecation Notices

Maps API for JavaScript 3.1.x will reach the end of support on Sep 30, 2026. It’s recommended to migrate to Version 3.2.x of Maps API for JavaScript. For a migration guide, refer to the documentation.

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 utilized 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 should 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 of the Gulf of Basra. If the Arabian Gulf/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 Jun 1, 2026. The 4-month window between the political view creation and 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

HERE Map Rendering Services

HERE Map Image API

Support for larger and more complex map overlays

We've added POST request support to the HERE Map Image API, enabling map image generation with larger route geometries and complex overlays that exceed URL length limitations. Customers can now render sophisticated routes, detailed polylines, and large geometry datasets more reliably and at greater scale.

For more information, see the documentation.

HERE Vector Tile API

New Feature added

• Added support for kind:country_code to the earth layer.

Bug Fixes and Improvements

• Improved the mechanism for derived building simplification at zoom level 16.

• Fixed inconsistent population properties by removing the population_rank property and adding the population property to the borough feature type.

For all HERE Map Rendering APIs

• Added support for the ct country code for Northern Cyprus in geopolitical perspective filtering. Learn more in the Names documentation.

• Improved rendering accuracy for disputed islands between Greece and Türkiye when using political view filtering.

HERE Account Web

Deprecation Notices

End of Support for Select Languages on July 13, 2026

As part of HERE's ongoing effort to streamline and improve the quality of our localization services, we are announcing the end of support for select languages in HERE Account Web.

Affected Languages

The following languages will no longer be supported in HERE Account Web: Afrikaans, Albanian, Azeri (Latin), Basque, Belarusian, Dutch (Belgium), Estonian, Farsi (Persian), Galician, Hausa, Kazakh, Latvian, Lithuanian, Macedonian, Slovenian, and Uzbek (Latin).

What This Means for You

• If you currently use HERE Account Web in one of the affected languages, the user interface will automatically fall back to English.

• Your account data, credentials, and access to HERE services are not affected. This change applies only to the languages used in HERE Account Web.

Why We Are Making This Change

The end of support for these languages allows HERE to focus on the languages most commonly used by our customers, and to improve translation quality and speed for those languages.

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.

New Vietnam administrative structure

Vietnam’s administrative structure has changed. The following key changes will be reflected in HERE Map Content by the end of Oct 2026:

• The current Level 3 (District Level) administrative boundaries will be removed.

• The existing Level 4 (Commune Level) will be elevated to replace Level 3.

• This elevation will involve significant merging of communes, resulting in a reduced number of administrative units at the new Level 3.

Three new PayPoint types in the Toll Cost layer

The existing types are listed below. New types (in bold) will be reflected in HERE Map Content by the end of July 2026:

• A = Administrative Area (price per kilometer)

• C = Congestion Zone

• E = Environmental Zone

• F = Toll System

• K = Toll Road Segment (price per kilometer)

• S = Toll Structure

• V = Vignette

Removal of catalog history

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

For questions, reach out to your HERE Account Executive or Technical Services point-of-contact.

Restricted Driving Maneuver changes

In Q4 2026, a redesign of the Restricted Driving Maneuvers schema and implementation (Restricted Driving Manoeuvre) 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 in Q3 2026.

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, reach out to 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 multiple 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) is also postponed to 2027.

Both layers will be replaced by new layers publishing 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)

EV Charge Points API v3

Feature Showcase

EV Charge Points API v3 introduces several improvements to help drivers make more informed charging decisions. Truck charging support has been expanded to provide more information about charging point-level attributes, including vehicle dimensions, parking layout, trailer support, and truck-focused amenities, enabling more accurate assessment of charger suitability for commercial vehicles.

Nearby Places coverage has been extended to AC charging stations, allowing drivers to discover nearby services and amenities at a broader range of charging locations and supporting longer charging stops. In addition, parking restriction information is now available at the individual charging point level, providing more detailed accessibility information for route planning and charging decisions.

Coming Soon

Reliability Indicators (Alpha) provide early insights into charging location reliability, helping drivers better evaluate charging options and make more informed charging decisions. This capability is currently available as an alpha feature.

HERE Tour Planning

The HERE Tour Planning API introduces the following improvements:

• Stop on the correct side of the street at PUDO and parking locations 
  The sideOfStreetHint in PudoPlace.location and ParkingPlace.location prevents dangerous U-turns at busy pickup points and ensures drivers stop on the accessible side. The nameHint improves accuracy when multiple businesses share an address.

• Park once and walk to nearby deliveries with stopConfiguration (Alpha)
  This feature optimizes urban scenarios where drivers park once and walk to multiple addresses. Configure profile: pedestrian and maxIntraStopDistance to cluster nearby jobs, with the API calculating actual walking paths and reporting total walking distance per stop (for example, "3 deliveries, 180m walking"). This feature replaces the deprecated stopConfig. For more information, see Cluster nearby stops.

• Start duty breaks early with canStartEarly (Alpha)
  This feature allows duty breaks to start earlier than strictly required, minimizing wait times and improving schedule efficiency. For example, when a driver arrives early at a customer, they can begin their mandatory 45-minute break at 4h20m instead of idling until the required 4h30m mark, keeping schedules in order while maintaining hours-of-service compliance.