October 2025 Platform Release Notes

Maps API for JavaScript 3.2.0.0 released!

Version 3.2.0.0 is a major update of Maps API for JavaScript.

The new version introduces new default settings for the utilized rendering engine, the style family, and the connected HERE Location services.

For customers already using the Location Service on platform and the HARP engine, the migration is backward compatible and simple to perform. Review the full migration guide at: HERE Technologies Documentation | HERE Docs

In addition to the modernized setup and architecture of version 3.2.x, new features include:

• POST Request submission to REST Location Services

• Reduced download size for customers utilizing the HARP engine.

• Proper resolution of type declarations by IDEs, improving the developer experience and eliminating issues related to type discovery

Full release notes description can be seen at HERE Technologies Documentation | HERE Docs .

Comprehensive documentation and updated examples have been published alongside with the new version.

With this release, Maps API for JavaScript 3.1.x moves into a deprecation state. Bug fix support will end in October 2026. 

HERE Style Editor 1.14.0

The new version 1.14.0 of HERE Style Editor introduces new application features as well as map style customization features in HERE SDK, Maps API for JavaScript and HERE Navigation.

Application features

• New and improved dashboard for better guidance in base style selection

• Bulk upload in the Icon library screen

• Schematic maps for Japan and POIs

Map Style customization features

• Support for changing public transit icons

• Support for changing traffic incidents icons

Raster Tile API 3.0.65-67 and Map Image API 3.0.45-47

• Added full support for the ETag header in requests for image-based satellite tiles

• Added support for displaying multiple road shields on a single road link to provide a more accurate representation and assist users with map orientation.

Vector Tile API 2.3.56

Added the hgv_gross_weight_mass flag to advanced roads, enabling differentiation of truck restrictions based on gross weight versus current weight.

HERE Real Time Traffic

• New Incident Provider has been onboarded for Finland.

• CDS(Construction Detection Service) Data has been enabled for Benelux Countries.

• Improved Algorithm for Merge Rules/Logic for Confidence Score.

HERE SDK 4.24.1.0

This release contains bug fixes and UX improvements. New features include:

• Map view: Added MaterialReflectivity class, and LocationIndicator.getMaterialReflectivity and LocationIndicator.setMaterialReflectivity functions to enable the Location Indicator to interact with scene lighting. The Location Indicator casts and receives shadows when the MapFeatures.shadows feature is enabled. Note that this feature is in a beta state and may exhibit bugs or unexpected behavior. Related APIs are subject to change in future releases without a deprecation process.

• Added GeoCoordinates.interpolate() to interpolate between two coordinates.

• Added GeoPolyline.coordinatesAtOffsetInMeters() to convert offsets along the polyline to coordinates

• Added SegmentConnectivities data to SegmentData and introduced an option in SegmentDataLoaderOptions to enable it.

• Added sdk.mapdata.SegmentSpanData.urban to identify road or ferry segment spans located within a built-up area.

• Added ElectronicHorizon class responsible for providing ElectronicHorizonPaths.

• Added ElectronicHorizonPath representing a path from ElectronicHorizon calculation. Added ElectronicHorizonPaths , a structure containing all paths provided by ElectronicHorizon.

• Added ElectronicHorizonListener and ElectronicHorizonPositionListener to subscribe and receive notifications from ElectronicHorizon updates. Added ElectronicHorizonPathSegmentId indicating the ID of a segment added to ElectronicHorizonPath.

• Added ElectronicHorizonPathSegment representing a segment of the path. Added ElectronicHorizonUpdate containing information about updates from ElectronicHorizon.

• Added ElectronicHorizonPathPosition representing the current position on ElectronicHorizonPaths . Added ElectronicHorizonOptions to configure the logic of ElectronicHorizon.

• Added ElectronicHorizonDataLoader which loads data based on updates from ElectronicHorizon.

• Added ElectronicHorizonDataLoaderResult providing results of requested data from ElectronicHorizonDataLoader .

• Added routing support to the indoor module, enabling routing within venues.

• Added loadDirectedSegmentData to SegmentDataLoader to enable loading data for directed segments.

• Map view: Introduced MapSurface.attachSurface(Context context, Surface surface, int width, int height) and MapSurface.attachSurface(Context context, Surface surface, int width, int height, @NonNull RenderListener renderListener) , which throw an exception if the provided surface is unusable. In such cases, the MapSurface remains unmodified

• Map style update: Enabled display of traffic lights at zoom levels >= 18. Data available in hrn:here:data::olphere:ocm with version >= 182.

• We are pleased to announce the release of a new version of the HERE SDK Reference Application. Version 1.15.0 introduces support for HERE SDK 4.23.0.0, updates relevant application dependencies and the icon set, and includes minor bug fixes and other enhancements.

HERE SDK 4.24.2.0

We fixed a lot of bugs and did some changes to improve the user experience. But we also added some new features to this release, e.g.: 

• Map data: Added SegmentSpanData.specialSpeedSituations to identify segment spans with speed limits that exist only under special circumstances.

• Routing: Added RoadFeature.seasonalClosure as an avoidance option in isoline calculations to improve route accuracy by excluding roads that are seasonally closed.

• Electronic Horizon: The methods electronicHorizon.update(...) and electronicHorizonDataLoader.loadData(...) have been changed from synchronous to asynchronous to avoid blocking the main thread. Results are now delivered on the main thread. Added ElectronicHorizonDataLoadedStatus to indicate the loading status for a specific level, andelectronicHorizonDataLoader.addElectronicHorizonDataLoaderStatusListener(...) / removeElectronicHorizonDataLoaderStatusListener(...) to register or unregister an ElectronicHorizonDataLoaderStatusListener. Note that this is a beta release of this feature.

• Updated the latest supported Flutter version from 3.32.5 to 3.35.4 and Dart from 3.8.1 to 3.9.2 for the HERE SDK. The minimum supported Flutter version remains unchanged (Flutter 3.29.3 and Dart 3.7.2). Other versions may also work but are not guaranteed to be work.

HERE Tour Planning API

The API comes with the following set of new ALPHA features:

• Cost per waiting time - Introduces configurable cost calculations for vehicle waiting periods through the perWaitingTime property in cost configurations. This feature enables more accurate cost modeling by assigning monetary values to idle time.

• Excess cost for waiting time - Adds extra costs when waiting time exceeds predefined thresholds through the waitingTime property in excessCosts. The optimization algorithm now applies additional charges for extended idle periods beyond acceptable limits.

• Excess cost for duration - Tours that exceed maximum duration constraints can now incur additional costs through the excessCosts.duration property. This feature helps optimize scheduling by discouraging overly long tours.

• Dedicated profile for clustering - Enables more efficient clustering by introducing the option to specify the vehicle profile for the optimization algorithm to use for calculating distances between activities.

• Location-specific duration through shared parking places - Automatically adds parking-specific durations to job times based on associated parking locations, based on the the parkingIds property. When a job links to a known parking place, the system includes the parking time (separate from service time) in the total job duration.

Product

Announcement

Clarification on Usage of Routing Reference client

The Reference Client has transitioned from a free legacy version (refclient.ext.here.com) to the new platform (demo.routing.ext.here.com) that requires customer login via their HERE Platform realm and potential charges per transaction, with usage tracked through HERE’s internal APP_ID: QTmoWsSsUzsw3I0MliO5 (see screenshot below). Transactions now count against the customer's realm, but actual impact is minimal due to the Reference Client's low usage for testing purposes and the generous HERE free tier, which provides between 2,500 and 30,000 free monthly transactions depending on routing mode (e.g., EV, Trucks, or Basic Car). For details please refer to the HERE Base Plan Pricing.

What's in the works

HERE Map Content API v2: Layer/attribute removal dates and deprecation notifications

Removal of NameType values from the Name Model

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

Deprecated layers

The following layers are deprecated and will be removed from the catalog by the end of Q1 2026:

• Road Attributes

• Navigation Attributes

• Advanced Navigation Attributes

• Recreational Vehicle Attributes

Consumers of these layers should migrate their applications to the new Topology Attributes layer.

Deprecated attributes

The CurvatureHeadingAttribute, published by ADAS Attributes, is deprecated and will be removed from the schema by the end of Q4 2025.The attribute is replaced by the following two new attributes:

• CurvatureAttribute

• HeadingAttribute

Removal of catalog history

In Q1 2026, HERE plans to remove catalog versions older than 18 months, provided that this action will have no impact on customer applications. For questions, reach out to your HERE Account Executive or Technical Services point-of-contact.

Map Attributes API

Announcement - Beginning in December 2025, HERE Map Attributes (RME, WSE, GFE) API v8 will no longer support GET requests with HTTP request lines longer than 8000 characters. To ensure that your solution remains fully functional, use POST requests or limit the line length to 8000 characters or less. To learn more about the available endpoints and methods, see the API reference.

Style updates to default schemas of HERE SDK, Maps API for JavaScript and Raster Tile API

HERE plans to improve the default style schemas for normal, logistics, lite and topo.

The following changes will be introduced as new defaults for the individual products.

Refer to the corresponding release notes for each product for details and implementation guidance.