Why do we get a negative insertTourDistance in proposal func

This forum deals with any kind of trip optimization based on xTour1, xTour2 and the Developer APIs "RouteOptimization" and "SequenceOptimization". No matter whether it is automatic planning or manual dispatching, refering to transport orders or service planning.
Attention: this does not refer to PTV Optiflow SaaS and PTV Developer RouteOptimization Optiflow.
Post Reply
User avatar
jmamy
Posts: 31
Joined: Wed Jul 02, 2014 7:21 am

Why do we get a negative insertTourDistance in proposal func

Post by jmamy »

We use one of the proposal functions of xTour. One of the proposals of findTourForUnplannedOrders contains a negative value for the additional insertTourDistance. Is this a bug? What is the reason for that?
Attachments
response.xml
Request on NAM
(1.4 KiB) Downloaded 360 times
request.xml
(27.7 KiB) Downloaded 357 times
Julien Mamy
Logistics Software Sales Engineer
PTV AMERICA
User avatar
Bernd Welter
Site Admin
Posts: 2695
Joined: Mon Apr 14, 2014 10:28 am
Contact:

Re: Why do we get a negative insertTourDistance in proposal

Post by Bernd Welter »

Hello Julien,

that's an effect I can easily explain based on an other example. I'd label the question "why does an additional waypoint reduce the distance of a track?":
insertTourDistance.PNG
Look at the attached image: The original fastest route from Karlsruhe (Southwest) to Heilbronn(Northeast) takes a quick ride via a highway and so the time is "just" 53 minutes with a distance of almost 90km.
Now by adding another waypoint (blue icons) the "best" route is more or less the straight connection via some minor roads. The new track is just 74km so adding the blue qaypoint did save about 15km.

In other words:
- it is not a bug
- it simply requires an explanation ;-)

Best regards,
Bernd
Bernd Welter
Technical Partner Manager Developer Components
PTV Logistics - Germany

Bernd at... The Forum,LinkedIn, Youtube, StackOverflow
I like the smell of PTV Developer in the morning... :twisted:
Post Reply