May 2025 Platform Release Notes

HERE Map Content v2

Schema changes

In order to distinguish between abbreviations ( such as IL for Illinois ) and shortened names ( such as ‘Frankfurt’ for ‘Frankfurt Am Main’ ) name type SHORT_NAMEwas added to the Name model/schema.

Country code USA was added to the list of political views. For more information, see the PoliticalView ENUM.

HERE platform

In 2024, HERE launched a new feature for platform.HERE.com to allow org admins to set their Organization Settings to an Open setting. This setting allows identities to access resources purchased or shared to them without the need to manage different project scoped and unscoped tokens. The current default setting (and for all orgs created previously) had a Strict setting, which restricted the use of project based resources to project scoped tokens only and required linking of resources and services that were purchased or shared to the org.

Beginning 1 July, all newly created platform.here.com orgs will have the Organization Setting set to Open as the default. This provides org users with fewer org constraints when initially creating App IDs and projects, and allows users to learn more quickly about HERE's products and services. As users become more comfortable with the powerful features available in HERE Platform, users can opt to change the Organization Setting to Strict or choose to manage individual project level isolation, for use cases where specific resources or services need to be available for only certain identities. For more information, see the documentation.

HERE Raster Tile API 3.0.55

• Added a "stack" icon to indicate that additional truck restrictions are present but not explicitly displayed. By zooming in you can see them all in turn.

• Added the dem style that provides Digital Elevation Model (DEM) tiles. This style encodes heights above sea level as RGB color components in 256x256 PNG tiles. This is intended to be used by a client-side rendering engine to create interactive and visually appealing 3D maps of terrain, including shading effects that simulate real-world illumination. For more information, see the HERE Raster Tile API Developer Guide.

   

We have also added the HERE Raster Tile API playground to the Developer Guide. You can interactively check all the service styles, features and settings and even general a simple client code for HERE Maps API for JavaScript and Leaflet. 

HERE Real Time Traffic

Upgraded Real-time traffic 

Real Time Traffic Engine has been updated to Q225 Map. This ensures improved coverage for areas.

Improved Coverage for Brazil 

Added TMC Table feeds, flow, predictive and incident (beta incident feed), for new Brazil TMC Tables B54, B55, and B56.  The existing Table B14 will continue to be covered.

New Feeds for Israel  

Beta launch of Flow 3.3 feed for Israel.  The official launch is planned for June and it will include incidents.

Improvement for Incident Closures 

Improved OpenLR reference creation by decreasing offsets for smaller links.  This reducing the amount of missing OpenLR references for closures by over 97%.

Improved Confidence level for Individual Traffic Incidents

This would benefit ADAS/AD customers by providing incident level confidence score (0 - 100 —> Low - High) for Traffic.

HERE SDK 4.22.2.0

The following updates are available for minor HERE SDK 4.22.2.0:

• Navigation: Added EventText.distanceInMeters, representing the distance to the event for which the EventText object is generated.
• Search: Added PassThroughFeature enum with ONLINE_SEARCH value. Enabling of this passthrough feature allows usage of online search in offline mode.
• Map view: Added support for changing font in MapMarker. Added constructor to MapMarker.TextStyle with font name parameter and a new getFontName() method.
• Map style update: Added pedestrian path styling by removing dash patterns and improving visual clarity. Reviewed unpaved walkway relevance within driving-related use cases to ensure appropriate representation. Note that this feature was already introduced with the HERE SDK 4.21.4.0.
• Map style update: Added new vehicle restriction icons for through-vehicles. The new add-on highlights restricted road segments which can be accessed if a delivery takes place on that segment.
• Routing: Added BatterySpecifications.maxPowerAtLowVoltageInKilowatts to allow vehicles which support 800V to use lower voltage charging stations.
• Offline routing: Added SectionNoticeCode.noThroughRestriction enum and use it during parsing of SectionNotice in OfflineRoutingEngine.

HERE SDK 4.22.3.0

The following updates are available for minor HERE SDK 4.22.3.0:

• Routing: Added new APIs to better support Electric Light Commercial Vehicles (eLCVs) and various types of trucks, such as light trucks under 7.5 tons. Extended the RoutingEngine and OfflineRoutingEngine to accept the new RoutingOptions class, which consolidates several existing option classes - including CarOptions , TaxiOptions , TruckOptions , and RefreshRouteOptions - into a unified configuration model. While the existing RouteOptionsclass can still be used as before, RoutingOptions provides the same capabilities in a more generic structure suitable for all supported transport modes. When creating a new route, make sure to specify RoutingOptions.transportMode . The new class also introduces extended routing configurations via the new classes CommonRouteOptions , VehicleSpecification , ElectricVehicleOptions with the new EmpiricalConsumptionModel and PhysicalConsumptionModel , and TransportedCargo . For example, it is now possible to specify whether a car is carrying cargo. Previously, this was only available for trucks. The existing RouteOptions can now be set under CommonRouteOptions . Note that this is a beta release of the new feature. Also, the OfflineRoutingEngine is only available in the Navigate Edition.
• Removed the beta label from the horizontalAccuracyInMeters field of MapMatchedLocation . The API is now considered to be stable.
• Search for EV charging stations: The APIs EVChargingPool, Details.evChargingPool, EVChargingStation, EMobilityServiceProvider, EVChargingPool.eMobilityServiceProviders, EVChargingPool.cpoId, and EVChargingPool.evseInfo are now available to all customers and work with your standard credentials. Previously, these APIs were available only to our closed alpha group. Note that these APIs are also supported for the OfflineRoutingEngine, if available for your edition.

What's in the works

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

Planned removal of layers:

Removal of Electric Vehicle Charging Stations layer

Following previous customer communications, the Electric Vehicle Charging Stations layer ( layer ID electric-vehicle-charging-stations ) will be removed on the 30th of June 2025. Users should migrate to the Electric vehicle Charging Locations layer ( layer ID electric-vehicle-charging-locations ) that was introduced in 2024.

2D/3D buildings layers removal

The following layers are deprecated and will be removed from the catalog on the 23rd of September 2025:

• 2D Building Footprints
• 3D Buildings

Consumers of these layers must migrate their applications to the new Buildings layer that was introduced in 2024 ( layer ID buildings ).

Places Footprints layers removal

The following layers are deprecated and will be removed from the catalog on the 23rd of September 2025.

• Enhanced Buildings ( layer ID enhanced-buildings )
• Parking Areas ( layer ID parking-areas )

Reach out to your HERE Account Executive or Technical Services point-of-contact in case of any questions.

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 are advised to migrate their applications to the new Topology Attributes layer.

Deprecated attributes

The following attribute, published by ADAS Attributes, is deprecated:

• CurvatureHeadingAttribute

The attribute will be decomposed in two new attributes that will be introduced during Q2 2025

• CurvatureAttribute
• HeadingAttribute

Removal of CurvatureHeadingAttribute from the schema is targeted for the end of Q3 2025

HERE Real Time Traffic

Planned removal of catalog

HERE Real Time Traffic Incident Catalog Version 1 (RTTI V1; HRN: hrn:here:data::olp-here:olp-traffic-1) is now deprecated. Please use the existing HERE Real Time Traffic Incident Catalog Version 2 (RTTI V2; HRN: hrn:here:data::olp-here:here-traffic-incidents-v2) instead. RTTI V2 provides the same content as RTTI V1 with multi‑region support. For more information on RTTI V2 layers in the catalog, see the Fetch Incident Data section of the HERE THERE Real-Time Traffic Incident - User Guide.

RTTI V1 will be removed in Q3 2025.