Details
-
Bug
-
Resolution: Won't Do
-
P2: Important
-
None
-
5.11.1
-
None
Description
It seems that, in certain cases, the "toLink" field of the maneuvers in the HERE routing response has weird/wrong info.
example xml responses attached.
In the attached files, M25 M32 and M38 have all the same toLink, but very different positions.
The fix should ideally not use link information anymore to reconstruct the path of the segments, but instead request this information to the server (see json response, produced using: https://route.api.here.com/routing/7.2/calculateroute.json?app_code=<hidden>&app_id=<hidden>&departure=2018-09-11T14:06:08&jsonAttributes=41&language=en_US&legattributes=all&linkattributes=none,sh,ds,rn,ro,nl,pt,ns,le,fl&maneuverattributes=all&metricSystem=metric&mode=fastest;pedestrian;traffic:disabled;&routeattributes=none,sh,wp,sm,bb,lg,no,li,tx,la&transportMode=pedestrian&walkSpeed=1.4&waypoint0=geo!52.515509,13.367024;;Stra%C3%9Fe+des+17.+Juni&waypoint1=geo!52.43199,13.53314;;Erich-Thilo-Stra%C3%9Fe&waypoint2=geo!52.51725,13.44945;;Fritz-Schiff-Weg)