Route API gives a SHORTEST route which is faster than the FASTEST route

10 posts / 0 new
Last post
purchase.1
Route API gives a SHORTEST route which is faster than the FASTEST route

Hello,

I am running into the following issue, when requesting the route between two points (45.5859,4.7848) to (45.539,4.27778) with the option route type SHORTEST I get a faster solution than with route type FASTEST (see below for the relevant part of the two answers). What can be causing this issue as this result seems completely inconsistent?

 

<route>
    <sessionId>5ac78431-01c2-4ee4-02b4-254d-0ae38bcd5a94</sessionId>
    <options>
      <shapeFormat>raw</shapeFormat>
      <generalize>-1.0</generalize>
      <maxLinkId>0</maxLinkId>
      <narrativeType>text</narrativeType>
      <stateBoundaryDisplay>true</stateBoundaryDisplay>
      <countryBoundaryDisplay>true</countryBoundaryDisplay>
      <sideOfStreetDisplay>true</sideOfStreetDisplay>
      <destinationManeuverDisplay>true</destinationManeuverDisplay>
      <avoidTimedConditions>false</avoidTimedConditions>
      <enhancedNarrative>false</enhancedNarrative>
      <returnLinkDirections>false</returnLinkDirections>
      <timeType>0</timeType>
      <routeType>SHORTEST</routeType>
      <locale>en_US</locale>
      <unit>M</unit>
      <tryAvoidLinkIds />
      <mustAvoidLinkIds />
      <manmaps>true</manmaps>
      <drivingStyle>2</drivingStyle>
      <highwayEfficiency>22.0</highwayEfficiency>
      <useTraffic>false</useTraffic>
    </options>
    <boundingBox>
      <ul>
        <lat>45.58826</lat>
        <lng>4.246019</lng>
      </ul>
      <lr>
        <lat>45.441879</lat>
        <lng>4.786293</lng>
      </lr>
    </boundingBox>
    <distance>37.091</distance>
    <time>2545</time>

...

 

<route>
    <sessionId>5ac78403-0017-4ee4-02b4-2364-0ec055f42e60</sessionId>
    <options>
      <shapeFormat>raw</shapeFormat>
      <generalize>-1.0</generalize>
      <maxLinkId>0</maxLinkId>
      <narrativeType>text</narrativeType>
      <stateBoundaryDisplay>true</stateBoundaryDisplay>
      <countryBoundaryDisplay>true</countryBoundaryDisplay>
      <sideOfStreetDisplay>true</sideOfStreetDisplay>
      <destinationManeuverDisplay>true</destinationManeuverDisplay>
      <avoidTimedConditions>false</avoidTimedConditions>
      <enhancedNarrative>false</enhancedNarrative>
      <returnLinkDirections>false</returnLinkDirections>
      <timeType>0</timeType>
      <routeType>FASTEST</routeType>
      <locale>en_US</locale>
      <unit>M</unit>
      <tryAvoidLinkIds />
      <mustAvoidLinkIds />
      <manmaps>true</manmaps>
      <drivingStyle>2</drivingStyle>
      <highwayEfficiency>22.0</highwayEfficiency>
      <useTraffic>false</useTraffic>
    </options>
    <boundingBox>
      <ul>
        <lat>45.638519</lat>
        <lng>4.190581</lng>
      </ul>
      <lr>
        <lat>45.441879</lat>
        <lng>4.787023</lng>
      </lr>
    </boundingBox>
    <distance>51.171</distance>
    <time>3051</time>

...

 

 

 

 


MQBrianCoakley
Thanks for the heads up. I
Thanks for the heads up. I sent this to the routing development team and it points to a bug in their system. A ticket has been created and this should be addressed in a future update. Sorry for any inconvenience.

purchase.1
Hello,

Hello,

thanks a lot for the quick reaction. Can you keep us posted about the resolution of the issue?


MQBrianCoakley
Yup.
Yup.

purchase.1
Hello Brian,

Hello Brian,

any update on this subject? When can we expect a resolution for this issue?

Best Regards


MQBrianCoakley
No update yet. It is in the
No update yet. It is in the team's backlog. 

purchase.1
Hello Brian,

Hello Brian,

any update on this one?

Regards


MQBrianCoakley
Nope. It's still in the
Nope. It's still in the backlog.

purchase.1
It's been 3 months now, can

It's been 3 months now, can you provide an estimate about when this is going to be fixed?

Thanks in advance


MQBrianCoakley
The shortest route type is

The shortest route type is much less restrictive and can at times produce faster results. These are very rare edge cases that are related to an issue that is being evaluated now and will be addressed with a future release that we don't have an eta for at this time.

 

Is this particular route a consistent issue or are there other routes that produce similar results? Since this route ends on the side of a major highway, it is an edge case that the route algorithm is not handling well. If the route destination is moved to the driveway of the facility that the lat/lng seems to be within, rather than the highway the lat/lng is actually closer to, the route does not behave unpredictably.