TollCosts not calculated












0














I asked about a thousand times for truck tollcosts. And they all return values.



Except this one: Link



In the warning section I get a couple of dosins errrors like: "context : "Route link id -50964891 not found in map. This might be a mismatch between map releases. Ignoring it for toll cost calculation.""










share|improve this question



























    0














    I asked about a thousand times for truck tollcosts. And they all return values.



    Except this one: Link



    In the warning section I get a couple of dosins errrors like: "context : "Route link id -50964891 not found in map. This might be a mismatch between map releases. Ignoring it for toll cost calculation.""










    share|improve this question

























      0












      0








      0







      I asked about a thousand times for truck tollcosts. And they all return values.



      Except this one: Link



      In the warning section I get a couple of dosins errrors like: "context : "Route link id -50964891 not found in map. This might be a mismatch between map releases. Ignoring it for toll cost calculation.""










      share|improve this question













      I asked about a thousand times for truck tollcosts. And they all return values.



      Except this one: Link



      In the warning section I get a couple of dosins errrors like: "context : "Route link id -50964891 not found in map. This might be a mismatch between map releases. Ignoring it for toll cost calculation.""







      here-api






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 23 '18 at 9:35









      frank vdb

      91




      91
























          1 Answer
          1






          active

          oldest

          votes


















          1














          As stated in the warning section this is due to the mismatch between map releases.
          Fleet Telematics api uses Routing API internally when you set attribute cost_optimize = 1 in your query. Since the two APIs have their own release cycles there could be a mismatch in the link Ids (only for a short period though). In your case, we don't see the link Id mentioned anymore in the response. You could try using other cost_optimize attribute options. Please read in the developer site for more information. Happy Coding!






          share|improve this answer





















          • Ok thanks. I will retry it a next run.
            – frank vdb
            Nov 23 '18 at 14:14











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443993%2ftollcosts-not-calculated%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          As stated in the warning section this is due to the mismatch between map releases.
          Fleet Telematics api uses Routing API internally when you set attribute cost_optimize = 1 in your query. Since the two APIs have their own release cycles there could be a mismatch in the link Ids (only for a short period though). In your case, we don't see the link Id mentioned anymore in the response. You could try using other cost_optimize attribute options. Please read in the developer site for more information. Happy Coding!






          share|improve this answer





















          • Ok thanks. I will retry it a next run.
            – frank vdb
            Nov 23 '18 at 14:14
















          1














          As stated in the warning section this is due to the mismatch between map releases.
          Fleet Telematics api uses Routing API internally when you set attribute cost_optimize = 1 in your query. Since the two APIs have their own release cycles there could be a mismatch in the link Ids (only for a short period though). In your case, we don't see the link Id mentioned anymore in the response. You could try using other cost_optimize attribute options. Please read in the developer site for more information. Happy Coding!






          share|improve this answer





















          • Ok thanks. I will retry it a next run.
            – frank vdb
            Nov 23 '18 at 14:14














          1












          1








          1






          As stated in the warning section this is due to the mismatch between map releases.
          Fleet Telematics api uses Routing API internally when you set attribute cost_optimize = 1 in your query. Since the two APIs have their own release cycles there could be a mismatch in the link Ids (only for a short period though). In your case, we don't see the link Id mentioned anymore in the response. You could try using other cost_optimize attribute options. Please read in the developer site for more information. Happy Coding!






          share|improve this answer












          As stated in the warning section this is due to the mismatch between map releases.
          Fleet Telematics api uses Routing API internally when you set attribute cost_optimize = 1 in your query. Since the two APIs have their own release cycles there could be a mismatch in the link Ids (only for a short period though). In your case, we don't see the link Id mentioned anymore in the response. You could try using other cost_optimize attribute options. Please read in the developer site for more information. Happy Coding!







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 23 '18 at 11:43









          HERE Developer Support

          1,249169




          1,249169












          • Ok thanks. I will retry it a next run.
            – frank vdb
            Nov 23 '18 at 14:14


















          • Ok thanks. I will retry it a next run.
            – frank vdb
            Nov 23 '18 at 14:14
















          Ok thanks. I will retry it a next run.
          – frank vdb
          Nov 23 '18 at 14:14




          Ok thanks. I will retry it a next run.
          – frank vdb
          Nov 23 '18 at 14:14


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53443993%2ftollcosts-not-calculated%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          What visual should I use to simply compare current year value vs last year in Power BI desktop

          Alexandru Averescu

          Trompette piccolo