问题
I use the Fleet Telematics API to calculate tolls when calculating a route (I understand there's no other current API for that as it supercedes TCE). It's generally slower than the routing API, and the routes are sometimes slightly different for the same points (why ?), but it's mostly OK. The big problem is that it chokes on some routes, for instance these 3 waypoints:
https://fleet.api.here.com/2/calculateroute.json?app_id=xxx&app_code=xxx&waypoint0=geo!46.14571,4.10844;500&waypoint1=geo!44.26294,0.302;500&waypoint2=geo!47.57652571374621,2.6147460937500004;37086&waypoint3=geo!50.77318,4.53766;500&mode=truck;fastest;traffic:disabled
The same route on the standard route API is found instantly:
https://route.cit.api.here.com/routing/7.2/calculateroute.json?app_id=xxx&app_code=xxx&waypoint0=geo!46.14571,4.10844;500&waypoint1=geo!44.26294,0.302;500&waypoint2=geo!47.57652571374621,2.6147460937500004;37086&waypoint3=geo!50.77318,4.53766;500&mode=truck;fastest;traffic:disabled
UPDATE: the problem seems to be that the waypoint radius is not used by the Fleet API (here the radius are 500m, 37086m and 500m). I'd swear that it was working in a previous test but maybe I'm mistaken.
UPDATE 2: it's fixed in the current version (current = 2020-12-21)
回答1:
The transit radius 37086m for waypoint2 is very big value in your fleet.api request and causes to check very much road links in this radius while calculated. Please reduce the transit radius in the request parameter.
来源：https://stackoverflow.com/questions/58403052/fleet-telematics-api-fails-to-find-route