Fleet Telematics API无法找到路线 [英] Fleet Telematics API fails to find route

问题描述

在计算路线时，我使用Fleet Telematics API来计算通行费(我知道目前没有其他API可以取代TCE).它通常比路由API慢，并且对于同一点，路由有时会稍有不同(为什么?)，但大多数情况下都可以.最大的问题是它会阻塞某些路线，例如以下3个航路点:

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

可以立即在标准路由API上找到相同的路由:

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

更新:问题似乎是Fleet API未使用航路点半径(此处的半径为500m，37086m和500m).我发誓它在先前的测试中正常工作，但也许我弄错了.

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.

更新2 :在当前版本(当前= 2020-12-21)中已修复

UPDATE 2: it's fixed in the current version (current = 2020-12-21)

推荐答案

waypoint2的运输半径37086m在您的Fleet.api请求中具有很大的价值，并且在计算时会检查此半径内的很多道路链接.请在request参数中减小传递半径.

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.

这篇关于Fleet Telematics API无法找到路线的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！