Release notes
June 2025 Platform Release Notes
Christo Mitov — 06 June 2025
Release notes
7 min read
12 February 2021
January 2021 Release Notes
Welcome to the latest release notes for the HERE Location Services. The first one in 2021 which will hopefully see a brighter and safer year for everyone. Here's what's new:
These releases include updates of: Routing API, Geocoding and Search API, Route Matching API, Advanced Datasets API, Maps API for JavaScript, Destination Weather API and HERE SDK for Android, iOS and Flutter.
For detailed information about the major improvements of the HERE Location Services, see the sections below.
You will find all API documentation and release notes on the Developer Portal.
Reminder: IMPORTANT INFORMATION regarding new license terms for Location Services on Platform*: For some of our new Location Services made available on Platform, we have changed the Transaction definitions in your current contract with HERE. This will impact all existing Location Services customers that have a contract with a license term based on Transactions such as Location Mapping when they start using Location Services on Platform. By continuing to use the Location Services on Platform, you accept the new terms. The changes are the following: Category Feature Definition Previous Geocoder Autocomplete or Places Autosuggest No Charge New Geocoding and Search Autosuggest or Autocomplete One Transaction is counted for every 10 Requests Previous Intermodal Park and Ride One Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal max parameter in the API request. If the system determines that there are no available Park and Ride routes, the Request is still counted as one Transaction New Intermodal Park and Ride One Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal alternative’ parameter in the API request. If the system determines that there are no available Park and Ride routes, the Request is still counted as one Transaction New Vector Tiles One Transaction is counted for every 5 Requests Previous Isoline Routing One Transaction means one Request New Isoline Routing One Transaction equals each individual Isoline within an Isoline Request Large Scale Matrix Routing and Matrix Routing included in Routing API will be merged into Matrix Routing API V8 Previous Large Scale Matrix Routing One Transaction is counted for every 20 Elements in a Large-scale Matrix Routing API Request. The number of Elements equals the number of start points times the number of destination points. Large-Scale Matrix Routing Requests generating less than 100,000 individual elements are always counted as 5,000 Transactions New Matrix Routing V8 • Small matrices, where either the number of Starting Points or number of Destination Points is Limited to 15x100 size and 100x1 are calculated by multiplying the number of Starting Points by the number of Destination Points • Large matrices, where the number of Starting Points and number of Destination Points are more, the number of Transactions is calculated by multiplying the greater of the number of Starting Points and the number of Destination Points by 15 Previous Matrix Routing One Transaction is counted for each start point Request New Matrix Routing V8 • Small matrices, where either the number of Starting Points or number of Destination Points is Limited to 15x100 size and 100x1 are calculated by multiplying the number of Starting Points by the number of Destination Points • Large matrices, where the number of Starting Points and number of Destination Points are more the number of Transactions is calculated by multiplying the greater of the number of Starting Points and the number of Destination Points by 15 New EV Charge Aware Routing Ten Transactions are counted for every Request *Location Services on Platform are the latest major releases such as Geocoding and Search API V7, Routing, Matrix Routing, Isoline Routing, Transit and Intermodal API´s V8 and Vector Tile API V2 | Category | Feature | Definition | Previous | Geocoder Autocomplete or Places Autosuggest | No Charge | New | Geocoding and Search Autosuggest or Autocomplete | One Transaction is counted for every 10 Requests | Previous | Intermodal Park and Ride | One Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal max parameter in the API request. If the system determines that there are no available Park and Ride routes, the Request is still counted as one Transaction | New | Intermodal Park and Ride | One Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal alternative’ parameter in the API request. If the system determines that there are no available Park and Ride routes, the Request is still counted as one Transaction | New | Vector Tiles | One Transaction is counted for every 5 Requests | Previous | Isoline Routing | One Transaction means one Request | New | Isoline Routing | One Transaction equals each individual Isoline within an Isoline Request | Large Scale Matrix Routing and Matrix Routing included in Routing API will be merged into Matrix Routing API V8 | Previous | Large Scale Matrix Routing | One Transaction is counted for every 20 Elements in a Large-scale Matrix Routing API Request. The number of Elements equals the number of start points times the number of destination points. Large-Scale Matrix Routing Requests generating less than 100,000 individual elements are always counted as 5,000 Transactions | New | Matrix Routing V8 | • Small matrices, where either the number of Starting Points or number of Destination Points is Limited to 15x100 size and 100x1 are calculated by multiplying the number of Starting Points by the number of Destination Points • Large matrices, where the number of Starting Points and number of Destination Points are more, the number of Transactions is calculated by multiplying the greater of the number of Starting Points and the number of Destination Points by 15 | Previous | Matrix Routing | One Transaction is counted for each start point Request | New | Matrix Routing V8 | • Small matrices, where either the number of Starting Points or number of Destination Points is Limited to 15x100 size and 100x1 are calculated by multiplying the number of Starting Points by the number of Destination Points • Large matrices, where the number of Starting Points and number of Destination Points are more the number of Transactions is calculated by multiplying the greater of the number of Starting Points and the number of Destination Points by 15 | New | EV Charge Aware Routing | Ten Transactions are counted for every Request | ||||||||||||||||||
Category | Feature | Definition | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Previous | Geocoder Autocomplete or Places Autosuggest | No Charge | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | Geocoding and Search Autosuggest or Autocomplete | One Transaction is counted for every 10 Requests | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Previous | Intermodal Park and Ride | One Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal max parameter in the API request. If the system determines that there are no available Park and Ride routes, the Request is still counted as one Transaction | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | Intermodal Park and Ride | One Transaction is counted for each returned alternative Intermodal Route(s) set by the Customer for the intermodal alternative’ parameter in the API request. If the system determines that there are no available Park and Ride routes, the Request is still counted as one Transaction | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | Vector Tiles | One Transaction is counted for every 5 Requests | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Previous | Isoline Routing | One Transaction means one Request | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | Isoline Routing | One Transaction equals each individual Isoline within an Isoline Request | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Large Scale Matrix Routing and Matrix Routing included in Routing API will be merged into Matrix Routing API V8 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Previous | Large Scale Matrix Routing | One Transaction is counted for every 20 Elements in a Large-scale Matrix Routing API Request. The number of Elements equals the number of start points times the number of destination points. Large-Scale Matrix Routing Requests generating less than 100,000 individual elements are always counted as 5,000 Transactions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | Matrix Routing V8 | • Small matrices, where either the number of Starting Points or number of Destination Points is Limited to 15x100 size and 100x1 are calculated by multiplying the number of Starting Points by the number of Destination Points • Large matrices, where the number of Starting Points and number of Destination Points are more, the number of Transactions is calculated by multiplying the greater of the number of Starting Points and the number of Destination Points by 15 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Previous | Matrix Routing | One Transaction is counted for each start point Request | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | Matrix Routing V8 | • Small matrices, where either the number of Starting Points or number of Destination Points is Limited to 15x100 size and 100x1 are calculated by multiplying the number of Starting Points by the number of Destination Points • Large matrices, where the number of Starting Points and number of Destination Points are more the number of Transactions is calculated by multiplying the greater of the number of Starting Points and the number of Destination Points by 15 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
New | EV Charge Aware Routing | Ten Transactions are counted for every Request |
HERE Location Services
**Routing (**Version 8.18.0 + 8.20.1)
Added a notice for using emergency gates.
Added notices as an option for spans parameter. This can be used to get the actual locations of violated restrictions in truck routing.
Added brand attribute to ChargingStationPlace.
Added (Alpha) taxi and bus routing modes.
Added routingZones to _return_s and spans parameters.
**Route Matching (**Version 8.0)
New redesigned standalone service succeeding Route Matching of Fleet Telematics API.
Following the same API spec as the other new services and using the same underlying map content from the HERE Platform.
**Advanced Datasets (**Version 8.0)
New redesigned standalone service succeeding Advanced Datasets of Fleet Telematics API.
Following the same API spec as the other new services and using the same underlying map content from the HERE Platform.
**Geocoding and Search (**Version 7.6.1)
Response API title enhancement: Clarifying the match for end users by adding matched names in parentheses to the title.
MEX: Recognize name of cross street in Geocoder queries
Major Places catalog update for Japan
Additional content from Trip Advisor (standard attributes including opening hours, food types)
Postal code search support for Japan
Destination Weather (Version 3.0)
Updated API structure to make it more consistent with other new HERE APIs.
The Weather 1.0 API is marked as deprecated but will be supported going forward.
**Maps API for JavaScript (**Version 3.1.22.0)
Improvements to the Japan style include:
Changes to the rendering order between the railways and buildings.
The style now uses the default system CJK fonts.
Updates to the POI display
Minor roads now consider "toll" and "bridges" attributes.
Label priorities were changed to improve readability of the map.
Train stations do not have duplicate labels.
Rendering of the icons for the multimodal transit stations.
The label positioning was changed to reduce the "flickering".
New more easy way to set a political view to the map.
Added the support of the Public Transit API v8.
HERE SDK for Android**, iOS and Flutter (**Version 4.6.1)
Cancel animation.
Simple FlyTo animation.
Implement zone categories once format/types are available.
Improve names of fields for Address struct.
Expose access types.
Implement new Location fields/constructor in iOS.
All Location Services deliver map content updates every week.
Raymond Camden
Share article
Related articles
Sign up for our newsletter
Why sign up:
Latest offers and discounts
Tailored content delivered weekly
Exclusive events
One click to unsubscribe
