JavaScript Colculateroute vs ios Colculateroute不同的路由结果
H.Service.platform.getRoutingService(NULL,8)的JavaScript API“ colculateroute”函数的结果之间存在差异 以及Nmacorerouter iOS SDK“ colculateroute”函数的结果。 (Premium SDK v 3.1.9)
如果我通过选项 路由类型:最快 TransporMode:
我和卡车经过了完全相同的航路点。 例如 中途停留:-34.909797,138.5403 通过:-34.85191,138.49499 通过:-34.851,138.49494 Via:-34.84965,138.49478 通过:-34.84868,138.4947 通过:-34.84765,138.49459 VIA:-34.84681,138.49448 通过:-34.84654,138.49439 Via:-34.84556,138.49392 通过:-34.84252,138.49306 通过:-34.84131,138.49272 中途停留:-34.827869,138.500708
,然后在桥上的通行路点将使JavaScript路线沿着小路驶过桥梁。但是,iOS API将继续在桥下行驶。
有没有办法使这两个引擎计算出相同的计算?
There is a difference between the result of the Javascript API 'calculateRoute' function call from H.service.Platform.getRoutingService(null,8) (Javascript API version 3.1)
And the result of the iOS SDK 'calculateRoute' function from NMACoreRouter. (Premium sdk v 3.1.9)
If I pass in the options
routingType: fastest
transportMode: truck
And I pass in exactly the same set of waypoints.
E.g.
Stopover: -34.909797,138.5403
via: -34.85191,138.49499
via: -34.851,138.49494
via: -34.84965,138.49478
via: -34.84868,138.4947
via: -34.84765,138.49459
via: -34.84681,138.49448
via: -34.84654,138.49439
via: -34.84556,138.49392
via: -34.84252,138.49306
via: -34.84131,138.49272
Stopover: -34.827869,138.500708
Then the via waypoint that is on a bridge will make the javascript route drive down side roads to pass over the bridge. However the iOS API will continue to drive under the bridge.
Is there a way to make the two engines calculate identically?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
这两个发动机都使用不同的路由API。因此,不可能获得相同的结果。 Premium SDK v 3.1.9致力于路由V7,而JavaScripts则用于路由V8。
https://developer.here.here.here.com/documentation /documentation /documentation/Routing-api/ dev_guide/index.html
Both engines uses different routing APIs. So it is not possible to get identical results. The Premium sdk v 3.1.9 works on Routing V7 ,whereas the the javascripts works on routing v8.
https://developer.here.com/documentation/routing-api/dev_guide/index.html