July 2020 Release Notes
Welcome to the latest release notes for the HERE Location Services. This post covers the D119 release of HERE Location Services.
These releases includes updates of: Routing API, Geocoder and Search API, Fleet Telematics API and HERE SDK for Android, iOS and Flutter.
You will find all API documentation and release notes on the Developer Portal.
Routing (Versions 8.3.3 – 8.6.4)
- Added length to OffsetAction
- Added support for traffic incidents in sections and spans.
- Added floating point pedestrian[speed] parameter.
- Added support for all parameters from /routes for /routes/{routeHandle} endpoint, except for parameters origin, destination, via, alternatives, and routingMode.
- Added boolean passThrough parameter via waypoints.
Geocoding and Search (Version 7.0.50)
- All endpoints: primary category flag for all place results with multiple categories
- Discover, Browse, Lookup: Place results contact information (phone, mail, web, fax)
- Discover, Browse, Lookup: Place results opening hours with isOpen flag
- Autosuggest query terms completion and termsLimit filter
HERE SDK for Android, iOS and Flutter Lite Edition (Version 4.4.2.0)
- Added Place.getGeoCoordinates() method to get the GeoCoordinates of a Place.
- Added departure/arrival information to the Section of a Route: waypointIndex
- originalCoordinates
- mapMatchedCoordinates
- waypointIndex
- originalCoordinates
- mapMatchedCoordinates
- Added Departure class with the following fields:
- Added Arrival class with the following fields:
- Added Section.get_departure() method.
- Added Section.get_arrival() method.
- Added Suggestion.getType() to get the new SuggestionType enum that indicates whether this Suggestion is a place, a chain like a store, restaurant or bussiness chain - or a category .
HERE SDK for Android, iOS and Flutter Explore Edition (Version 4.4.2.0)
Same new features as Lite edition
HERE SDK for Android and iOS (Navigate Edition) (Version 4.4.2.0)
Added a new NavigatorProtocol which describes the main turn-by-turn functionality of a Navigator. Plus, same new features as the Lite and Explore versions.
Fleet Telematics API (Version 3.0.32)
- New Custom Routing feature: Avoid Unpaved roads
- User can specify whether and how strict unpaved roads shall be avoided
- New Custom Routing feature: Choose Speed Category
- Now it is also possible to overrule the automatically determined speed profile and use a specific one.
- New Custom Routing Feature: Modify all roads within a polygonal area
- The "Area Override" overlay upload operation modifies the attributes of all links of the given LINK_ATTRIBUTE_FCN layer(s)
- More granular axle weight restrictions in Advanced Datasets
- The "Area Override" overlay upload operation modifies the attributes of all links of the given LINK_ATTRIBUTE_FCN layers
Important:
Link IDs will exceed 32 bits soon, PLEASE PREPARE YOUR APPLICATIONS TO HANDLE LINK_ID VALUES > 4 BILLION!
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 users that have a contract with a license term based on Transactions such as Location Mapping when they start using Location Services on Platform. 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 |
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 |
*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
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