Skip to main content
Release notes 8 min read

June 2024 Platform Release Notes

June 2024 HERE Technologies platform release notes

HERE Routing

The current release brings the following updates:

Toll Costs - Transponder names are part of the response
Transponder names can now be found in the routing response when requesting tolls. In Japan, for example, customers are now able to distinguish between ETC and ETC2.0 transponders.

HERE Geofencing is now fully commercially available on HERE platform
Customers can now license HERE Geofencing v8.0 on the HERE platform (no change in functionality to current Geofencing v8.0). Geofencing will be available as asset an based plan. Onboarding/Request for the HERE Geofencing API needs to be done via contacting your account manager - unfortunately we cannot provide this service for self-service customers.

HERE Map Content v2

The following dataset enhancements and new features were implemented*

Place category descriptions are now available for so-called level 1 and 2 Places categories.

  • For example, "100" represents level 1 category "Eat & Drink"
  • For example, "100-1000" represents level 2 category "Eat & Drink - Restaurant"
  • Category descriptions are provided in over 50 languages and can be found in the Places Metadata layer (ID places-metadata)

Several non-breaking schema changes were introduced, resulting from bring your own map (BYOM) programs 

  • Introduction of low speed limit zones 
  • Motorcycle use-case related restrictions and regulations

The Places layer (ID here-places) is now also publishing attributes for the following categories:

  • Fueling Stations
  • Truck Service Locations

See also the deprecation notice for the applicable layers

*Please consult your Account or Technical Support representative for further details.

HERE Tour Planning

The HERE Tour Planning API comes with the following new features and enhancements:

Define the job position within a tour

You can now determine the position of jobs within a tour by using the position object, which offers the values first, ordered, any, and last. This flexibility enables tailored prioritization of jobs in a tour based on factors such as urgency, proximity, and resource availability.

For example a logistics company needs to manage a fleet of delivery trucks. By determining the position of assignments, the company can ensure that the trucks complete all deliveries before making any pickups. This prevents the trucks from carrying unnecessary load, improves fuel efficiency, and reduces delivery times.

[ALPHA] Minimize tours that overlap with one another

Create more compact tours, with less overlaps between them. With the minimizeTourOverlap objective, vehicles can operate in distinct areas without duplication, resulting in improved fuel efficiency, shorter travel times, and enhanced cost-effectiveness.

For more information, see:

[ALPHA] Specify additional objectives for more efficient tours

Define additional goals or constraints to optimize the efficiency of the tours in more complex ways. Examples of advanced objectives in Tour Planning include minimizing the total solution cost, maximizing the number of vehicles used in a tour, balancing duration of all tours, and many more.

For more information, see:

[ALPHA] Designate PUDO locations in job groups

Incorporate "PUDOs," or "Pick-Up and Drop-Off" points, into the tour. You can define first or last PUDOs within group jobs to optimize efficiency at the beginning or end of a job group.

For example, in the context of a courier service, you can position the first PUDO as the initial stop at locations such as stores or pickup lockers where customers drop off packages for courier delivery. Conversely, you can position the last PUDO as the final stop at such locations as delivery lockers for customers who can't receive packages during regular delivery hours.

For more information, see:

[ALPHA] Cluster nearby jobs

Group jobs that are geographically close to each other into a single stop to ensure that they are served together. You can define the clustering strategy based on the duration to the longest job, a constant cluster duration, or you can limit the cluster duration to the sum of job durations with a maximum threshold.

For example, a postal service might cluster nearby jobs to optimize delivery routes, reducing fuel consumption and increasing daily deliveries. In pedestrian-friendly areas, delivery personnel can park vehicles and deliver mail on foot to clustered addresses, enhancing efficiency.

For more information, see:

Increased the maximum break limit in a shift

The maximum number of breaks in a shift has been increased to 5.

For more information, see:


HERE SDK for iOS, Android and Flutter is a minor release for the 4.18 code line with a lot of bug fixes and improvements based on customer feedback. We also added some new features for this release, for example

  • Search: Added TripAdvisor support via SearchEngine.setCustomOption(). Note that this option is only available for customers who own a HERE license for rich content access including TripAdvisor.
  • Map view: Added MapContentType.POINT, PointDataPointDataBuilderPointDataAccessorPointDataSource and PointDataSourceBuilder for creating and managing custom geodetic point data sources. Note that this is a beta release of this feature.
  • Navigation: Added Span.getCar/Scooter/Truck/WalkAttributes() to get AccessAttributes for car, trucks, scooters, and pedestrians.
  • Navigation: Added roadSignSegment to RoadSignWarning to provide a reference to the road sign location.
  • Added EngineBaseURL.RASTER_TILE_SERVICE enum value to set a custom base URL template for the raster tile service. The EngineBaseURL can be set via SDKOptions. This option can be used to switch back to our legacy Map Tile service starting with HERE SDK Note that this option will do nothing until HERE SDK
  • Added LayerConfiguration.implicitlyPrefetchedFeatures to define what features are downloaded during online usage - for example, when panning the map view or during navigation (if available for your edition). Note that this is a beta release of this feature.

Take a look at the latest changelog for your edition and platform to find out more details.

HERE Map Content v2

Layer deprecation notice

Please be aware that the following layers are deprecated:

  • Places for HERE Essential Map (layer ID here-places-essential-map)
  • Transport Service Locations (layer ID here-truck-service-locations)
  • Fueling Stations (layer ID here-fueling-stations)

Consumers of these layers are advised to switch to the Places layer (layer ID here-places) which is publishing all applicable attributes meanwhile.

The deprecated layers will remain accessible, but will not be updated anymore as of Q3 2024.

The deprecated layers will be physically removed from the catalog as of Q4 2024.

Furthermore, the following layer will be put to maintenance mode:

  • Electric Vehicle Charging Stations (layer ID electric-vehicle-charging-stations )

Instead, users of this layer are advised to switch to the Electric Vehicle Charging Locations layer (layer ID electric-vehicle-charging-locations) which contains the latest EV attributes according to industry standard OCPI. 

The Electric Vehicle Charging Stations layer will remain accessible, but will only receive content updates. Removal this layer is planned for Q2 2025.

HERE Workspace

Final Notice and Action Required - Deprecated pipeline runtime environments for stream and batch pipelines no longer supported as of June 27, 2024

Per deprecation announcements included in the Pipeline API Changelog on January 24, 2022 [for Stream Pipelines] and on December 19, 2023 [for Batch Pipelines] , we are following up here with a final notice that all deprecated pipeline runtime environments will be deleted on June 27, 2024, representing the end of the 6 month [or longer] deprecation periods. Please see the respective changelog deprecation notices here:

The list of deprecated pipeline runtime environments includes:

  1. Stream Environments with the IDs stream-2.0.0, stream-3.0.0, stream-4.0.
  2. Batch Environments with the IDs batch-2.0.0, batch-2.1.0, batch-3.0.

All existing, running, scheduled, and paused jobs using the deprecated runtime environments will be shut down as of June 27. All requests to create and activate pipelines for these environments will fail.

Required Action:

All pipelines must be migrated to the latest supported runtime environments (either batch-4.0 or stream-5.0) before June 27.

The migration guides to the latest environments can be found here:

Christo Mitov

Christo Mitov

Have your say

Sign up for our newsletter

Why sign up:

  • Latest offers and discounts
  • Tailored content delivered weekly
  • Exclusive events
  • One click to unsubscribe