Release Notification Product Update HERE Platform for Business 04/2017 (D79)

Dear Customer,

please be advised that a new release (D79) of the HERE Platform for Business is now available on the Production environment (PRD).

This email includes release notes that describe the improvements to the services in the new release. This release includes updates of: JavaScript API, Geocoder API, Geocoder Autocomplete API, Routing API, Traffic API, Positioning API, Custom Location Extension, Geofencing Extension, Fleet Connectivity Extension, Platform Data Extension, Route Match Extension, Toll Cost Extension, Waypoints Sequence Extension, HERE Android SDK and HERE iOS SDK

As well, we will publish the release documentation on the Developer Portal.

Management Summary

The release highlights are:

Integrated the Maps API for JavaScript with the Platform Data Extension REST API
Routing: Added a new range type consumption for CalculateIsoline, and a related option to CalculateRoute with consumption
Custom Location Extension API: improved geocoding for POI lists, multiple points are supported now in a single proximity.json search request
Route Match Extension: direct access to some link attributes; real time use cases support
Geofencing Extension: Multiple points can now be sent to a single search request.
Waypoints Sequence extension: Partial sequence order constraints can now be specified, such as Waypoint A must be reached before Waypoint B.
New HERE Platform Self-hosted Q1/2017 release
HERE Android and iOS SDK: Search along the route for data from PDE

For more detailed information about the major improvements of the HERE Platform for Business Services and Products, see the sections below:

JavaScript API

Version 3.0.13.0

We integrated the Maps API for JavaScript with the Platform Data Extension REST API. This includes:

Search request functionality that allows you to search data available via the Platform Data Extension API and match it with the data provided by other HERE services.
A tile provider that enables you to overlay meta information, provided by the Platform Data Extension, on the map.

Geocoder API

Version 6.2.133

Improved postal code search in Singapore where buildings are given their own unique postal code.
Improved matching of number-based streets in Brazil. The Geocoder now recognizes street names in queries that use Arabic numerals even though the map data only contains the spelled out form of the numbers. For example, Rua 701 instead of Rua Setecentos e Um.

Geocoder Autocomplete API

Version 6.2.133

Improved ranking: Results are ranked by relevance independent of the query language. Users can now use their first language or a popular language such as English to get suggestions in countries with a different default language.

Routing API

Version 7.2.79

Added a new range type consumption for CalculateIsoline, which returns a polygon representing the reachable area based on a vehicle's current state of charge. Consumption details are provided with the request and can be used for fuel or electric vehicle use cases.  
Added the following option to CalculateRoute with consumption: For any route calculation, you can determine the amount of fuel/energy needed for each link along the route. Use the newconsumptionModel and customConsumptionDetails parameters in calculateRoute. This option is useful for tasks such as predicting a vehicle's energy consumption along a route in order to decide when and where to recharge or visualize battery levels at any point.

Positioning API

Version 1.4.0

We made improvements to the locate resource 

Removed the dependency of rsrq to rsrp in LTE serving and neighbor cell object. If you specify a value for rsrq, you need to specify a value for rsrp. This is a change from previous behavior.

Custom Location Extension API

Version 2.1.0

Geocoding can deal with partially geocoded POI lists. It geocodes only those POIs that have no coordinate.  
Multiple points can now be sent to a single proximity.json search request.  
To speed to all.json attribute searches, database indexes can be defined on the relevant attributes at layer upload.  
The layer upload function upload.json now accepts zipped and unzipped WKT text files, and accepts any multipart filename.

Geofencing Extension API

Version 2.1.0

Multiple points can now be sent to a single proximity.json search request.  
The layer upload function upload.json now accepts zipped and unzipped WKT text files, and accepts any multipart filename.

Fleet Connectivity Extension API

Version 1.3.0

Google Push (Firebase Cloud Messaging) can now be used to send routes to assets or to cancel routes.

Route Match Extension API

Version 2.1.13

Link attributes, like speed limit or slope, can be retrieved directly in the response. This is an alternative to calling PDE along the route, for select use cases.  
Route Match Extension API can also be used for real time use cases, where short traces from vehicles are matched and feedback during the journey is provided (driver alerts), or the journey is influenced (re-routing). Matching a trace that contains the latest few hundred driven meters provides better match results than matching isolated coordinates. Note that for sensitive matches (alerts or rating penalties), the end of the trace (latest points) should be sent to Route Match Extension API but disregarded from the result, because they are missing future points.

Waypoints Sequence Extension API

Version 2.2.8