BeMapAPI
BeMap 4.1.0

Changelog

What changed in each BeMap release, from BeMap's release notes. Running today: BeMap 4.1.0 in production and preproduction.

New in the API with 4.1.0, compared with 4.0.3:
  • Operation POST /vehicle/1.1/getlevelvehicleinfo
  • Field RoutingRequest.startUTurnThreshold
  • Field RoutingVehicleProf.routingCrossPenaltiesCoefficients
  • Field ChargingCostEstimation.energyUsed
  • Field Condition.startUTurnThreshold
  • Type LevelVehicleInfoRequest
  • Type RoutingCrossPenaltiesCoef

4.1.0 2026-09-03 In production and preproduction

Autocomplete / Geocoding:

  • Improvements:
    • Added an explicit error message when the Autocomplete service is not configured on a client's account to facilitate troubleshooting.
  • Fixes:
    • Added an explicit error message when the required place parameter is missing from an Autocomplete request.

Mapping:

  • New features:
    • New version 2 of the BeMap JS API library. This version adds a BeNomad Tiles vector display through a new MapLibre rendering engine. Leaflet and OpenLayers are unchanged. This version ships with the customizable default BeNomad map style, a browser cache for better performance, and a unified attribution widget that gathers legal notices. The three engines are interchangeable through a common API (flyTo, easeTo, jumpTo…). The v2.0 documentation and its tutorials are provided.
  • Documentation:
    • Added a tutorial for retrieving a satellite image via WMS.

Routing:

  • New features:
    • New startUTurnThreshold field in the request: forces the departure angle (heading) of a route to be taken into account, even when honoring it requires a significant detour. Previously, the angle could be ignored beyond a certain threshold.
    • New routingCrossPenaltiesCoefficients field in the request: allows adjusting the weighting of the penalties applied at intersections during route calculation, in order to refine the estimated travel time (ETA), which could be overestimated on some networks.
  • Documentation:
    • Added, in the Routing integration example, an address search field (autocomplete) allowing a start or end point to be entered by its address rather than by coordinates.
    • Added UI support for the startUTurnThreshold parameter in the documentation interface, and documentation for configuring the cross-penalties coefficient.

EV Smart Routing:

  • New features:
    • Support for the startUTurnThreshold parameter in the planner (same setting as the Routing field above, now available for EV Smart Routing).
    • Support for the cross-penalties coefficient in the planner (same setting as routingCrossPenaltiesCoefficients).
  • Fixes:
    • Fixed the charging cost calculation: the charging point is now identified by its ID, ensuring the correct tariff is applied.
  • Documentation:
    • Added UI support for the startUTurnThreshold parameter in the documentation interface, and documentation for configuring the cross-penalties coefficient.

Charging cost:

  • Improvements:
    • Charging cost calculation now takes into account tariff rules including: VAT (tax_included), tariff validity periods, time bands (e.g. day/night tariff) and duration or energy tiers. Cost estimates now more closely match the amount actually billed to the driver.
  • Documentation:
    • Updated the charging cost request example.
    • Added timezone retrieval; a clarification on how to obtain tariffs; and a tutorial of the full process to build a request from the Charging Station and Tariffs services.

Vehicles:

  • New features:
    • Support for both GET and POST methods on the getlevelvehicleinfo endpoint (new LevelVehicleInfoRequest model), which allows parameters to be sent in the request body.
    • Added support for the variant parameter on getlevelvehicleinfo, to target a specific vehicle variant.
  • Documentation:
    • Added request examples for the Vehicle 1.1 endpoints, including getmotortypes (MotorType).

GeoServer Info:

  • Improvements:
    • Added servicesInfo support for the herehlp geoserver and filtering of exposed services according to the server configuration (each deployment only exposes the services actually declared).
  • Fixes:
    • Fixed the serviceName returned by geoserverinfo for the ChargingTime and OpenLrParser services.

Land feature:

  • Fixes:
    • Fixed invalid JSON output from the Land Feature service (BND v1) where an unmapped feature was returned.

General documentation:

  • Reworked the authentication documentation (reorganized sections, enriched examples, auth API details), deprecated URL-based authentication and clarified session reuse options. Fixed a typo: X-Aith-ID → X-Auth-ID.
  • Additions to the internal REST reference: added missing HTTP methods and request examples; fixed the Traffic example; and renamed reversegeocodingbacth → reversegeocodingbatch.

4.0.3 2026-07-24

Charging stations:

  • Improved stability of the charging station download process for certain data providers.

4.0.2 2026-07-09

Charging stations:

  • Improved stability of the charging station download process for certain data providers.

4.0.1 2026-07-06

  • Minor configuration fix.

4.0.0 2026-07-01

Release 4.0.0 is a significant upgrade to BeMap's technical foundation. Implemented to strengthen security and improve long-term maintainability, this release brings BeMap's dependencies up to their latest stable versions.

This version includes the following updates:

Autocomplete geocoding:

  • Improved accuracy of geocoding results from the OSM/Nominatim provider. When a place name matches several OpenStreetMap entries at different administrative levels, for example a town and a broader administrative area sharing the same name, the service now uses the place_rank field from the Nominatim API to prioritize the most specific result. The returned coordinates now correspond more closely to the expected location, rather than the geographic center of a broader area.
  • Added a new geocoder, Photon, self-hosted by BeNomad and available as an alternative provider for both autocomplete and reverse geocoding (selected via the geoserver parameter).

Charging time:

  • The Charging Time service now factors in each vehicle's specific charging curve. By using the vehicle's own charging profile, the service provides more accurate charging time estimates that are fully aligned with those produced by the EV route calculation service, EVSmartRouting.

Charging cost:

  • The Charging Cost service now takes the charging station's time zone into account (the timeZone field) when evaluating tariffs subject to time-based restrictions, such as a day/night tariff. Previously, these time windows were evaluated using Paris local time, which could cause the wrong tariff to be applied to stations located in other time zones. The applied tariff now reflects the station's local time.
  • Improved cost calculation for duration-tiered tariffs, whose brackets are defined by the minDuration and maxDuration fields. The final open-ended bracket (with no maxDuration) is now correctly taken into account: time spent beyond the last bounded bracket is properly billed, as in the case of a parking tariff with an uncapped overtime penalty.

EV Smart Routing:

  • The EV Smart Routing API version 2.0.0 now supports the following parameters for the departure point, destination point, and waypoints, already available in the standard route calculation service:
    • radius: search radius around a point
    • ignorePoint: skip a waypoint
    • ignoreTrafficDirections: ignore one-way directions
    • ignoreRestrictions: ignore routing restrictions
    • avoidUTurn: avoid U-turns
    • useStartAngle: use the specified departure heading
    • useStopRoadSide: use the specified side of the road for arrival

Traffic:

  • Improved filtering of the traffic information used by the routing engine, for better routing results and performance.

Vehicles:

  • Fixed a 400 error returned by the getlevelvehicleinfo 1.0.0 API when retrieving the list of AC chargers for certain vehicles. The endpoint now returns the correct list of AC chargers.

3.51.1 2026-05-07

Routing:

  • Fixed missing detour between 2 points with sames coordinates but with opposite angle in Routing API (useStartAngle property was ignored).
  • Fixed possible data race in route calculations (multi-threading).
  • Routing mode Matrix fails to calculate all coefficients when some points are matched on a same road element.

Traceroute:

  • Fixed an issue in TraceRoute API with minimal waypoints (when 2 points with same coordinates and the first one is a U-turn waypoint).
  • Fixed an issue in TraceRoute API when removing a small U-turn near the start can cause the minimal waypoint to fail.

3.51.0 2026-03-31

Charging stations:

  • Fixed the search for truck charging stations (see filters array for filter system version 2).

EV Smart Routing:

  • Fixed the search for truck charging stations (see filters array for filter system version 2).
  • Fixed unused csfsVersion parameter in EV SmartRouting API v2.0.0.

Reverse-Geocoding:

  • Added new THROUGH_POINT_ADDRESS option to search for the nearest Point Address.

Roads Extractor:

  • Added a new Roads Extractor service which performs a map-matching on all road segments inside a given polygon.

Routing:

  • Added support of arrivalTime option to Routing API version 1.0.0.
  • Permit the start and stop coordinates on blocked roads when real-time traffic (option TRAFFIC) is enabled.

Documentation:

  • Added a tutorial demonstrating trip planning with a truck transport type in EV Smart Routing API v2.0.0.
  • Added documentation for the new Roads Extractor service (v1.0.0).

3.50.1 2026-03-12

Charging stations:

  • Fixed the extra memory consumption issue when too many pools with tariffs are found.

Routing:

  • Fixed an issue where traffic data for blocked roads was not refreshing after OpenLR updates.

3.50.0 2026-02-27

Charging stations:

  • Added support of heavy vehicle profiles to factor in limited parking restrictions (Charging Station Search API only).
  • Added new APIs for retrieving:
    • List of charge passes.
    • AD/HOC, MSP and Sub-CPO charge pass tariffs.
    • Added new filterVersion parameter to Charging StationSearch API to improve charging station searches.

EV Smart Routing:

  • Added charge cost computation to the EV Smart Routing service, based on selected charge passes and AD/HOC tariffs. The service returns the lowest computed cost and charge pass used (or AD/HOC) information.

3.49.7 2026-02-19

Charging Station:

  • Fixed the null pointer exception error on RFID Auth filter test.

Geofencing:

  • Updated API to support polygons and circle fences.

LandFeature:

  • Updated interactive example page to display the geometry.

NearPOI:

  • Replaced the "internal error"message by the original error message.

Routing:

  • Added stopDuration and totalDuration fields in response of Routing API.
  • Added localisation of the routesheet in Dutch (NL) and Polish (PL) languages (see RoutingInstruc.text field in Routesheet response of Routing API.

Traceroute:

  • Added totalDuration field in response of Traceroute API.
  • Added localisation of the routesheet in Dutch (NL) and Polish (PL) languages (see RoutingInstruc.text field in Routesheet response of Routing API.

Traffic:

  • Fixed to avoid unexpected line returns and double quotes in CSV traffic export file.

3.49.6 2026-01-16

Core:

  • Updated JSIV version from 3.24.5 to 3.24.6 based on CoreSDK 6.37.1.
  • Fixed potential stack-buffer-overflow and heap-buffer-overflow issues in Planner.
  • Fixed a length inconsistency between TraceRoute/SetMinimalWaypoint and routing API.
  • Fixed OpenLR encoding issues.
  • Fixed an issue where off-road waypoints were incorrectly map-matched in TraceRoute.

Documentation:

  • Updated the documentation for the useStartAngle parameter in the Routing and TraceRoute APIs.

3.49.5 2025-12-18

Charging stations:

  • Added support for new GBT AC/DC charging connector for OCPI providers.

Geocoding:

  • Fixed possible deadlock issue when running mixed geocoder/traceroute APIs concurrently.
  • Fixed an issue where the Geocoder did not return the city name when two cities were found in the same postcode (e.g. Country = "France", City = "Rambures", Zip = "80140")
  • Fixed possible multithreading issue when running mixed geoserver/geocoding APIs concurrently.

Traceroute:

  • Fixed incorrect map-matching of points in offroad sections.
  • Fixed incorrect map-matching of points in offroad sections (backward).