version Unreleased

  • There are no more missing M:N route combinations in the the edge list returned by route_matrix() (see #30).
  • All lengths of origin and destination are now accepted as input in route_matrix() (see #31).

version 0.3.0 2020-01-07

  • HERE has updated the authentication process and changed from APP_ID and APP_CODE to a single API_KEY. Therefore set_auth() and unset_auth() are defunct and replaced by set_key() and unset_key() (see #23).
    NOTE: .Deprecated() was skipped because the API endpoints have also changed. After updating to a version greater than 0.2.1 the authentication must be adjusted.
  • Added a minimum jam factor filter to traffic(..., product = "flow"). Now it is possible to only retrieve flow information of severe congestion with a jam factor greater than min_jam_factor, which speeds up requests.
  • Public Transit API: Transit route The new feature connection() implements requesting the most efficient and relevant transit connections between given pairs of locations.
  • Public Transit API: Find stations nearby The new feature station() retrieves nearby public transit stations with corresponding line information.
  • Package cosmetics: Renamed the start parameter to origin and unified the utilization of the datetime and arrival parameters in route(), route_matrix(), isoline() and connection().
  • Adjusted the handling of datetime objects in the requests: All c("POSIXct", "POSIXt") inputs for the requests (mostly departure) are converted to UTC using .encode_datetime() and the responses are parsed and returned in the input timezone (or if missing: Sys.timezone()) using .parse_datetime() (see #28).
  • Added @import sf to the package documentation to ensure sf objects are handled correctly.
  • Added departure and arrival datetime column to the return value of route(), route_matrix() and isoline().
  • Removed data.table object type from function return values. New: Pure data.frame or sf, data.frame because this integrates better with other packages (e.g. the overline2() function from the stplanr package).

version 0.2.1 2019-12-16

  • Enhanced traffic(): Clarified that from_dt and to_dt have no effect on the traffic flow (product = "flow"). Traffic flow is always real-time. Detailed documentation of the variables in the return value.
  • Improved coverage of testthat.
  • Added an id column to the output of geocode() and removed the id ordered row.names in order to be consistent with other functions of the package. Using the id column the addresses to geocode can be joined to the coordinates after geocoding (see #9).
  • Added an id column also to autocomplete(), reverse_geocode(), route(), isoline(), traffic() and weather(). Using the id column the result can be joined to the input.
  • Fixed the handling of failing requests in .get_content(). The id column is still in correct order, even if there are failing requests in a function call (see #17).
  • Added rownames() <- NULL to all functions before returning the result.
  • Renamed the city column in the returned object of weather() to station, as it stands for the name of the nearest meteorological station.
  • Test for empty geometries in the input POIs and AOIs and throw an error if some are found (see #16).

version 0.2.0 2019-11-13

  • Enhanced geocode(): In the case of empty responses the row names match the index of the geocoded addresses. Improved input checks. Option to use autocomplete by setting autocomplete = TRUE.
  • Geocoder API: Autocomplete The new feature autocomplete() allows autocompleting addresses.
  • Geocoder API: Reverse geocode The new feature reverse_geocode() implements reverse geocoding POIs in order to retrieve suggestions for addresses or landmarks.

version 0.1.0 2019-11-05

First release of the hereR package, an sf-based interface to the HERE REST APIs. The packages binds to the following HERE APIs:

  • Geocoder API: Get coordinates (lng, lat) from addresses.
  • Routing API: Routing directions, isolines and travel distance or time matrices, optionally incorporating the current traffic situation.
  • Traffic API: Real-time traffic flow and incident information.
  • Destination Weather API: Weather forecasts, reports on current weather conditions, astronomical information and weather alerts at a specific location.

Locations and routes are returned as sf objects and tables as data.table objects.