You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

德国境内通行费计算异常技术问询:HERE API与官方费率不符

Troubleshooting Toll Rate Discrepancy Between HERE Fleet API and German Official Rates

Great question — let's break down why you might be seeing a 0.198 EUR/km rate from the HERE Fleet API versus the official 0.187 EUR/km rate for your Euro 6 truck. Here are the key areas to investigate:

1. Toll Pass/Discount Misapplication

Your request includes tollPass=transponder,Senior_Pass — but it’s possible the API is either:

  • Incorrectly applying a premium instead of a discount for one of these passes (unlikely, but worth verifying), or
  • The Senior_Pass has eligibility rules your vehicle doesn’t meet (e.g., vehicle age restrictions, route exclusions), so the API falls back to a higher non-discounted rate, or combines pass benefits in an unexpected way.

Try re-running the request without the tollPass parameter to fetch the base rate, then compare that directly to the official figure.

2. Route-Specific Segment Charges

The official 0.187 EUR/km rate is the base highway toll for Euro 6 trucks, but your calculated route might include:

  • Special segments like bridges, tunnels, or urban toll roads that carry higher per-kilometer fees, which would push the overall average rate up to 0.198 EUR/km.
  • Check the API’s route details (using the routelegattributes=li response data) to see if any individual segments have elevated toll rates that skew the average.

3. Vehicle Parameter Mismatch

Double-check if your request’s vehicle specs align with the official rate’s eligibility criteria:

  • The official 0.187 EUR/km rate may apply to a specific axle configuration (e.g., 2-axle truck + 2-axle trailer), but your request uses vehicleNumberAxles=2 + trailerNumberAxles=3 with a 40t limited weight. Some axle combinations or higher total weights trigger higher toll tiers.
  • Confirm that the official rate’s weight/axle requirements match your limitedWeight=40t and axle counts exactly.

4. Toll Database Sync Delay

It’s possible the HERE API’s toll rate database hasn’t been updated to match the latest official Toll Collect rates. Alternatively, the official rate might be a newly announced change that hasn’t rolled out to live API endpoints yet.

5. Multi-System Toll Inclusion

Germany’s toll network is dominated by Toll Collect, but some smaller regional toll systems might have different rates. The API could be including charges from these secondary systems that aren’t reflected in the main official rate page you referenced.

Quick Debug Steps

  • Strip down your request to only mandatory parameters (remove tollPass, simplify vehicle specs to match the official rate’s exact criteria) and re-calculate.
  • Inspect the API response’s toll breakdown (look for tollSystem and segment-level details) to identify which parts of the route are driving the higher average rate.

内容的提问来源于stack exchange,提问作者Dimitrij Filozofovich

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.08 11:28:15