Resolved issues
March 2026
| Issue ID | Description |
|---|---|
| RTGS-5427 | Improved the filtering of impractical alternatives, including some cases where the alternative route would include double-backing on itself via a divided road. |
| RTGS-5350 | Adjusted penalties for entering a rest area for EV routing, to improve charging station selection behavior in charge-aware routing. |
| RTGS-5376 | The notice for violating the minChargeAtFirstChargingStation parameter was being applied to every route section. The logic for this has been fixed. |
| HERESUP-55248 | Fixed an issue with retrieving route geometry using a route handle for a very short route. |
| HERESUP-53429 | Adjusted waypoint matching logic for vehicular transport modes to avoid matching a waypoint on level ground to bridge geometry. |
February 2026
| Issue ID | Description |
|---|---|
| HERESUP-48851 | Adjusted penalties for roundabouts with internal roads that cross through the middle of the roundabout, to actually use those shortcut roads when appropriate. |
| HERESUP-52765 | Certain cases of "dog bone" shaped roundabouts were being merged into a single roundabout for maneuver generation. This has been fixed to properly split them. |
| HERESUP-55941 | When routing with the avoid[features]=tolls parameter, taking a ferry through a toll zone will no longer report a violation of avoid tolls for the ferry section. |
January 2026
| Issue ID | Description |
|---|---|
| HERESUP-46904 | Adjusted truck routing penalties around Munich to prefer routing via the northern bypass highway. |
| HERESUP-47517 | Fixed a case of some toll costs being duplicated for routes in Western Europe. |
| HERESUP-51933 | Routing now allows u-turns at the point where a road is closed for construction, similar as it would at a dead-end. |
December 2025
| Issue ID | Description |
|---|---|
| HERESUP-48903 | Adjusted penalties for crossing between Schengen and non-Schengen countries to better avoid unnecessary border crossings. |
November 2025
| Issue ID | Description |
|---|---|
| HERESUP-48090 | Fixed an issue with waypoint matching, specifically in the case of one-way cul-de-sacs in Japan, which was causing Routing to fail. |
| RTGS-4874 | Improved the map-matching of traffic information in Montenegro. This would have caused some traffic events to not be considered by Routing. |
| HERESUP-48336 | Long-distance bicycle routes were exhibiting long calculation times after a recent refactoring. This has been fixed, and the performance is now even better than before. |
| RTGS-4465 | Error messages for parameters in the ev namespace will now show the entire parameter name. |
October 2025
| Issue ID | Description |
|---|---|
| HERESUP-44432 | Fixed an issue where road names were not appearing in the Thai language, where applicable, even when the language was set to Thai. |
| HERESUP-44165 | Fixed an issue where traffic incidents could sometimes disappear in rare circumstances, causing them to be ignored by the router. |
September 2025
| Issue ID | Description |
|---|---|
| RTGS-4416 | Speed limits in returned routes will now take number of trailers into consideration, where applicable. |
| HERESUP-39464 | Fixed rerouting behavior in truck mode to better preserve the original route, when navigating on an alternative route. This change also fixes the same issue for bicycle and pedestrian modes. Other transport modes were already working as intended. |
August 2025
| Issue ID | Description |
|---|---|
| HERESUP-36502 | Route Import requests use the units parameter correctly. |
| HERESUP-30555 | Fixed the behavior of large avoid areas for bicycle routing. |
| HERESUP-12094 | Improved the recognition of U-Turns which are legally allowed in jurisdictions where U-Turns are normally forbidden. |
| HERESUP-33002 | Fixed a false-positive case of detecting U-Turn maneuvers, involving sharp turns inside complex junctions. |
| RTGS-3721 | Improved alternative generation to allow cases that may have small loops or U-Turns near the origin and destination, in order to respect restrictions like sideOfStreet, course, minCourseDistance, etc. in the route request. |
July 2025
| Issue ID | Description |
|---|---|
| HERESUP-22371 | Improved handling of the avoid[zoneCategories]=environmental parameter. If this parameter is used, routes will only avoid environmental zones which apply to the current transport mode. For example, an environmental zone applying only to trucks will not be avoided in car mode. |
June 2025
| Issue ID | Description |
|---|---|
| RTGS-3156 | Adjusted the U-Turn penalty at stopover-type waypoints (where passThrough=false) in cases where avoid[uTurns] is specified, which was previously set to forbid U-Turns. In situations where a U-Turn must be taken in order to continue the route, a route will be returned along with a violatedAvoidUTurns notice. Previously, this would result in a Route Not Found error. |
| HERESUP-22041 | Updated misleading notices related to passing through seasonal closures. Further details can be found in this tutorial. |
| HERESUP-18362 | When there is an error calculating toll costs, a warning notice is generated on every section of the route. This notice will no longer be applied to transit sections. |
| HERESUP-19123 | Improved handling of no-through zones in the case of adjacent private roads, such as parking lots. Previously, these could be incorrectly merged into a single zone. |
May 2025
| Issue ID | Description |
|---|---|
| RTGS-2996 | Requesting the tolls[summaries] parameter can now also be used in conjunction with return=summary. Previously, it required requesting return=travelSummary. |
April 2025
| Issue ID | Description |
|---|---|
| HERESUP-10781 | Some ferry segments were incorrectly marked as toll roads. This attribution has now been removed from all ferry segments. This means ferries will not be avoided when avoiding toll roads, and there will be no violation warnings about using them returned in case the option to avoid toll roads is specified. |
March 2025
| Issue ID | Description |
|---|---|
| RTGS-2310 | originalLocation is now returned for Route Handle requests, aligning its behavior with Routing requests. |
| RTGS-3054 | Certain cases of Truck Routing with exclude-areas and truck-closed roads would result in the exclude-area attributes being ignored. This has now been fixed. |
| HERESUP-5942 | Improved the u-turn detection heuristic in cases where there is a dedicated lane for u-turns, and the turn is wide enough that it should not be considered difficult. These turns will not be avoided when the avoid[uTurns] parameter is set. |
| RTGS-2915 | baseDuration field in route summary previously did not contain the correct charging time when using physical consumption model for EV Routing. This has been fixed. |
February 2025
| Issue ID | Description |
|---|---|
| HERESUP-10664 | Fixed a rare issue where routes in car mode could fail when ending on a street with unconditional access restrictions for trucks. |
| HERESUP-5910 | Improved the recognition of U-Turns which are legally allowed in jurisdictions where U-Turns are normally forbidden. This particularly affected some allowed U-Turns in Singapore. |
| HERESUP-11426 | Isoline calculation was improved to more accurately consider sections of the isoline which would only be reachable by a U-Turn. |
January 2025
| Issue ID | Description |
|---|---|
| RTGS-2663 | Removed the unnecessary "continue" instructions on state borders. |
| RTGS-1930 | Improved handling of via waypoints in return to route calculations. If traveledDistanceOnLastSection exceeds the length of the section to which the route is returning, then the returned route will still pass through the specified via waypoint. |
| RTGS-2325 | Improved handling of start waypoints with course and minCourseDistance specified, for route handle requests. Previously, this could result in the start waypoint being off of the original route and therefore would return a different route. |
| HERESUP-7405 | Fixed the numbering of exits in roundabouts for non-car modes, in instruction generation. |
| HERESUP-8682 | Do not give roundabout instructions in pedestrian mode. |
December, 2024
| Issue ID | Description |
|---|---|
| HERESUP-4677 | Return-to-route requests with ferry sections were previously ignoring the ferry section for the lastTraveledSectionIndex parameter. This has been fixed to include those sections. |
| RTGS-2156 | Improved the handling of the course parameter in cases where a waypoint is matched to a junction nearby, or the radius parameter is used. |
| RTGS-1903 | Improved calculation of return-to-route calls with stopover waypoints. U-Turns will now be allowed at such waypoints, if they would be allowed in a normal route calculation. |
November, 2024
| Issue ID | Description |
|---|---|
| RTGS-2138 | U-Turn detection logic has been improved for certain cases of complex intersections with internal geometry. |
| RTGS-2155 | Improved the handling of waypoint matching, when using options that include all of radius, course and minimum course distance. |
| RTGS-2282 | Fixed the text of traffic incidents which were incorrectly specifying both metric and imperial units for en-US language settings. |
| HERESUP-542 | Improved handling of waypoints in parking lots. U-turns will now be allowed for such waypoints without penalty. |
October, 2024
| Issue ID | Description |
|---|---|
| RTGS-1092 | Certain road geometries involving a turn from a one-way street into another one-way street were being incorrectly recognized as forbidden U-Turns. This has been corrected. |
September, 2024
| Issue ID | Description |
|---|---|
| HERESUP-1824 | Fixed a recently introduced bug, where alternative routes with via waypoints could include strange detours. |
August, 2024
| Issue ID | Description |
|---|---|
| HERESUP-1344 | Fixed a bug where waypoint matching was using different fallback options when radius options were specified. This is now aligned to be consistent in all cases. |
| RTGS-1132 | When avoid segments are specified as part of a POST body, they will now be validated in the same way as for a GET request. |
| RTGS-1283 | Waypoint matching has been improved for cases where a small snapRadius is specified. |
| HERESUP-803 | Fixed a recently introduced bug where EV routes requesting alternatives would fail completely if no alternatives were found. |
| RTGS-1342 | Requesting "tollSystems" spans when a link is part of multiple toll systems should now work as expected. Previously, those links appeared in some cases as if they had no toll systems. |
| OLPSUP-30958 | When an isoline is created without a departure time (i.e. starting "now"), then the timestamp in the response will be displayed as the local time of the start point. This is now consistent with the Routing API. |
July, 2024
| Issue ID | Description |
|---|---|
| ROUTING-27476 | Increased routing penalties for crossing western borders of Russia and Belarus, to avoid transiting those countries when traveling elsewhere. |
| ROUTING-26994 | The routing response now provides more details when a vehicle restriction is violated. |
| ROUTING-27273, ROUTING-27274 | Improved recognition of U-Turns. U-turns on highways that use dedicated ramps and do not involve a sharp turn will not be avoided by the "Avoid U-Turns" parameter. |
June, 2024
| Issue ID | Description |
|---|---|
| ROUTING-27276 | Passing invalid coordinates in a Route Import request will now return an informative error with HTTP status 400, rather than a generic 500. |
| ROUTING-27026 | Improved handling of minCourseDistance parameter when routing directly towards a fork in the road with minor turn angles in both directions. |
May, 2024
| Issue ID | Description |
|---|---|
| ROUTING-26684 | Junction-snapped intermediate waypoints would previously not generate turn instructions at the waypoint. This has been changed. |
| OLPSUP-30314 | Support added for toll-costs that span across multiple toll-system providers. |
| ROUTING-26871 | Improved instruction generation in cases of dedicated distinct road geometry for a turn lane. |
| ROUTING-27162 | Fixed return-to-route feature to allow approaching the destination from a different direction than the original route. |
| OLPSUP-30229 | Improved waypoint matching for origin coordinates in truck mode. |
| OLPSUP-30658 | Fixed a bug in the maneuver instructions generated for scooter routes in roundabouts. |
| ROUTING-27098 | The MinCourseDistance parameter now correctly avoids turns onto unnamed streets for the desired distance, which may not have been avoided previously. |
| ROUTING-26998 | Avoid area exceptions (e.g. corridors) were not working correctly for small avoid areas. This should now be fixed to work properly regardless of size of the avoid area. |
| ROUTING-26583 | Segment offsets for the last segment of a route generated by a route import request are now correct. Previously they occasionally listed the entire segment. |
| OLPSUP-30387 | Fixed alternative routes calculation when vehicle[speedCap] is specified. |
| ROUTING-26940 | Resolving various OpenAPI deserialization bugs:
|
| ROUTING-26921 | Changed the casing of the VehicleType and TruckType enum in the OpenAPI specification to correctly match what is returned from the service, i.e. uppercase values. |
April, 2024
| Issue ID | Description |
|---|---|
| OLPSUP-30451 | Fixed a wrong toll calculation when vehicle[type]=tractor is specified. |
| OLPSUP-29167, ROUTING-25952 | Improved recognition of allowed U-Turns in jurisdictions where U-Turns are normally forbidden, such as Italy and Indonesia. |
| ROUTING-26830 | Fixed a bug where a particular route calculation would fail when requesting alternatives, but succeed without them. Now the route calculation will succeed in both cases. |
| ROUTING-26546 | Added a notice for violating "Avoid U-Turns" parameter if a U-Turn is made on the same segment in the opposite direction. |
March, 2024
| Issue ID | Description |
|---|---|
| OLPSUP-28242 | Waypoint matching should not allow matching across bodies of water (e.g. river and lake geometry). This has now been improved to also recognize water geometry from harbors. |
| OLPSUP-29788 | Toll cost will be correctly calculated with the transponder cost when toll[transponders]=all parameter is specified. |
| ROUTING-26768 | Enable eMSP preference parameter in Route Handles for EV Routing. |
| ROUTING-26769 | Route Handles will now properly persist passThrough waypoints and sideOfStreet hints. |
February, 2024
| Issue ID | Description |
|---|---|
| ROUTING-26348 | Improved recognition of certain rest areas, in order to avoid routing through them. |
| ROUTING-26385 | Fixed a case of false-positive rest area detection when opposite sides of a highway are connected by a road for making u-turns. |
| ROUTING-26456 | Routes will avoid making u-turns at via waypoints, in case the via waypoint is on a divided road. |
January, 2024
| Issue ID | Description |
|---|---|
| ROUTING-26176 | Fixed handling of certain time-dependent HOV restrictions. Particularly in the case where there are multiple time restrictions on a lane, none of them would be applied in some cases. These are now handled correctly. |
| ROUTING-26093 | Fixed a rare case of U-Turns not being detected for certain roads with multiple names. |
| ROUTING-26293 | Fixed issues with returnToRoute by reworking the behavior of lastTraveledSectionIndex. |
December, 2023
| Issue ID | Description |
|---|---|
| ROUTING-26092 | Improved names of charging stations. If name was only some kind of numerical id, it now contains name of the charging point operator instead. |
| ROUTING-26112 | Using the avoid[features]=seasonalClosure feature in combination with departureTime=any caused almost all time dependent restrictions to be avoided. This is fixed now, such that only seasonal closures are avoided. |
| ROUTING-26235 | Fixed an issue where critical notices were returned for time-dependent restriction violations when departureTime=any was specified along with return=potentialTimeDependentViolations. |
| ROUTING-26133 | Updated the documentation in the developer guide to reflect a change that was previously not documented. avoid[features]=uTurns also avoids U-turns at a stopover-type waypoint. |
November, 2023
| Issue ID | Description |
|---|---|
| ROUTING-25882 | Fixed an issue with incorrectly identifying certain turns as U-turns, relating to turns within complex intersections. |
| ROUTING-25952 | Fixed further issues with recognizing time-dependent u-turn restrictions in regions where u-turns are not allowed. |
| ROUTING-25729 | Removed extraneous "continue" instruction for maneuver generation, when incoming road is one-way against the travel direction and therefore not relevant. |
October, 2023
| Issue ID | Description |
|---|---|
| ROUTING-25787 | Fixed an issue with recognizing time-dependent u-turn restrictions in regions where u-turns are not allowed. |
September, 2023
| Issue ID | Description |
|---|---|
| ROUTING-25935 | Private Bus was using excluding violated vehicle restrictions completely, instead of taking them only when no other route is possible. This resulted in some noRouteFound notices for private buses that should have been route with critical violation notices |
| IOTSDK-19405 | Fixed unexpected zone avoidance notice code. |
| ROUTING-25797 | Adding fuel or ev parameters to the request previously could have a side-effect of suppressing notices in the route response. This has been fixed so the notices are properly returned. |
| ROUTING-23701 | Rest stops next to non-controlled-access FRC1 roads are now properly identified as no-through. |
| INC-334511, ROUTING-25680 | Optimized multiple aspects of server performance when processing multiple long-running requests in parallel. |
| ROUTING-25656 | Fixed issue with using minChargeAtDestination in combination with via waypoints in EV Routing. |
| ROUTING-25606 | Further improvements to u-turn detection heuristic when multi-digitized streets have multiple identifiers (names and route numbers). |
| ROUTING-25344 | Fixed issues with route handle serialization when reserializing routes with passThrough via waypoints after returnToRoute. Via waypoints were previously being duplicated, and eventually becoming too large to serialize the route. |
| ROUTING-25061 | Fixed a rare case where a pedestrian route would prefer a u-turn over a sharp right turn. |
| ROUTING-25351 | Added new category field to Routing Zone in response to further differentiate between the sub-categories. |
| ROUTING-24764 | Fixed issue with route import for pedestrian and bicycle modes on roads with directional access restriction. |
August, 2023
| Issue ID | Description |
|---|---|
| ROUTING-19507 | OriginalLocation is now preserved inside routeHandle. |
| ROUTING-24092 | Unintentionally exposed attribute languageCode removed from TollSystem. It was never filled with real data. |
| ROUTING-25173 | origin is not snapped to junction against the driving direction anymore. |
| ROUTING-25182 | maxSpeedOnSegment is now working for non-truck routing modes properly. Previously it was being overriden by traffic data most of the time. |
| ROUTING-25243 | U-Turn restrictions are now followed in regions with admin-wide u-turn restrictions regardless of their level in the admin-hierarchy. Previously only country-wide restrictions were considered. Now it will also obey state and city-wide restrictions. |
| ROUTING-25266 | Improved scooter mode heuristic for no-through detection to be more similar to other modes. |
| ROUTING-25361, OLPSUP-25247 | Improved u-turn detection heuristic to reduce false positive rates. This especially affects regions with admin-wide restrictions like Italy. |
| ROUTING-25375 | Removed charge from routes with fuel based consumption. It only contained nonsensical data and was accidentally exposed. |
| ROUTING-25633, ROUTING-25531 | Fixed rare crash when decoding routeHandle |
| ROUTING-25569 | Fixed missing road numbers in spans in case a span ended in the middle of a complex intersection or roundabout |
| ROUTING-25603 | Time out toll cost computation properly. Previously it could take forever, resulting in the user not getting any response. Now it will properly time out after 10s, resulting in notices in the response instead. |
| ROUTING-25266 | Improved handling of no-through access for scooter routes. |
| ROUTING-25330 | Fixed the reporting of charge levels in driving sections split by a Ferry segment. |
| ROUTING-25520 | Fixed a bug in Environmental Zone detection which affected routes in Oxford, UK. |
| ROUTING-25531 | Fixed a crash bug in RouteHandle decoding, which resulted in unexpected 5xx errors. |
July, 2023
| Issue ID | Description |
|---|---|
| ROUTING-25429 | Removed an erroneous critical HOV violation when HOV mode was selected. |
| ROUTING-25160 | Improved the detection of U-Turn maneuvers in countries where U-Turns are forbidden. Additionally, improved detection of allowed U-Turns in those countries. |
| ROUTING-25106 | Deduplicated toll cost alternatives that are completely identical. |
| ROUTING-24911 | Fixed an issue which was sometimes causing pessimistic truck ETAs in free-flowing traffic. |
June, 2023
| Issue ID | Description |
|---|---|
| ROUTING-25021 | Fixed an issue with incorrect signposts being referenced in actions when route is cyclical or has a big detour. |
May, 2023
| Issue ID | Description |
|---|---|
| ROUTING-23912 | Allow pedestrian and bicycle routing through more tunnels |
| ROUTING-24922 | Fixed issue with both Thai and transliterated street names showing up in same maneuver instruction |
Earlier
| Issue ID | Description |
|---|---|
| ROUTING-22994 | Bicycle mode new respects the course option in waypoints |
| ROUTING-21008 | Fixed issue where high value of minChargeAtDestination in EV routing caused no route to be found. |
| ROUTING-21047 | Fixed issue with alternatives in EV routing. Asking for alternatives could result in no route found, even when route was returned when no alternatives were requested. |
| ROUTING-21050 | Improved avoid segments functionality. It was previously using older algorithm which was not able to do local detours around blockage on major roads. |
| ROUTING-20829 | Fixed issue with not all toll roads being considered in avoid toll feature for trucks. |
| ROUTING-19778 | Added support for time dependent attribution related to no through zones for all vehicle types. This previously worked only for truck mode. The logic for handling no through (also static) has also changed to the one used by truck mode. No through areas can now be crossed if necessary - high penalty is applied. Previously this was not allowed. |
| ROUTING-20625 | Improved quality of isolines in Australia |
| ROUTING-19670 | Fixed: Truck routing was not using some ferry connections and truck-dedicated roads at border crossings, due to the penalization of smaller roads |
| ROUTING-20571 | Fixed: Road name spans are no longer split by empty road name span when crossing a roundabout with no name. |
| ROUTING-20455 | Fixed issue when identical origin and destination were not detected as identical and resulted in longer route. This could happen in some situations when course parameter was added to the waypoint. |
| ROUTING-20157 | HOV were erroneously taken in truck routing mode. They will now not be chosen anymore, unless explicitly enabled with vehicle[hovOccupancy]=2 |
| ROUTING-18834 | EV requests with alternatives are now working again. |
| ROUTING-15527 | The API specification of the pedestrian and vehicle spans have been corrected to match service behavior. |
| ROUTING-16605 | Park attribution is now included in the map data and provided by the service. |
| ROUTING-18413 | The service now accepts only the documented numbers of alternatives, which is 6. |
| ROUTING-16198 | Fixed: waitDuration waypoint option is handled properly. Departure and arrival times of sections are adjusted accordingly. Wait post action is generated after arriving at a waypoint with waiting time. |
| ROUTING-16198 | Fixed: The service was erroneously returning notice instead of notices in the RouteResponse. |
| ROUTING-16146 | Fixed: Only a single via waypoint could be specified in the request. |
| ROUTING-14072 | Fixed incorrect handling of lang request parameter. |
| ROUTING-15649 | departure and arrival had invalid waypoint index. |
| ROUTING-15891 | Fixed incorrect rejection of lang=he-IL |
Updated 3 days ago