planBasicTours - double Transport points

This forum deals with any kind of trip optimization whether it is automatic planning or manual dispatching, refering to transport orders or service planning.

planBasicTours - double Transport points

Postby sgebhardt » Tue Apr 18, 2017 1:32 pm

Hello PTV team,
after some time I got a question from my customer concerning a planing.
We used startPlanBasicTours to get the sequence between different transport points.
I have the same coordinate twice in different transport points. xTour desides to drive from A to B and back to A. There are no other restrictions.

The request and the response is in the attachement of the post.
This transport point is existing twice:
xml code
<ns10:transportPoint id="100930249" coDriverRequired="false" openingIntervalConstraint="START_OF_SERVICE" servicePeriod="300" useServicePeriodForRecreation="false">
<ns10:location><common:point x="15.07637" y="47.06511"/></ns10:location>
<ns10:transportPoint id="100930302" coDriverRequired="false" openingIntervalConstraint="START_OF_SERVICE" servicePeriod="300" useServicePeriodForRecreation="false">
<ns10:location><common:point x="15.07637" y="47.06511"/>
</ns10:location>


The response id 100931411 is between 100930249 and 100930302.
The transport point is on the same road.. Any chance that I can avoid that feature and plan A, A, B? :?
Attachments
RequestandResponse.zip
(4.62 KiB) Downloaded 11 times
sgebhardt
 
Posts: 4
Joined: Mon Jan 25, 2016 2:37 pm

Re: planBasicTours - double Transport points

Postby Bernd Welter » Thu Apr 20, 2017 1:00 pm

wow, sounds like a very academic condition. Maybe the following effect is responsible for the strange behaviour:

Usually one would expect that a route like A:C is shorter than a route A:B:C.
But: if B is located somewhere along the direct track the additional stop creates a change in the data structure and the definition of the cost function. Look at the following sample:

Academic.PNG
Left route: simple routing from Karlsruhe to Heilbronn. Track length about 90km. Optimisation set to 90% (shortest time).
Right track: same optimization but additional waypoint somewhere in the countryside which enforces directions. Track length is only 76km.


I know this sounds confusing ;-)
In your example the virtual loss of quality is just about 500m.
Let's have a look at a potential distance matrix:
Academic.DIMA.PNG
distance matrix simulating the case from above
Academic.DIMA.PNG (6.39 KiB) Viewed 35 times


The sequence KA-Country-HN-Country-KA is in fact shorter but might require more time!) than the sequence KA-Country-Country-HN-KA because the leg HN-KA performs a large detour.

Happy with that?

Best regards Bernd
Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

https://www.youtube.com/channel/UCgkUli9yGf0gwTDdxbMZ-Kg
User avatar
Bernd Welter
Site Admin
 
Posts: 588
Joined: Mon Apr 14, 2014 10:28 am

Re: planBasicTours - double Transport points

Postby sgebhardt » Mon Apr 24, 2017 7:40 am

Thanks for the response. Not realy what I hoped to hear.
Didn't thought that there can be higher costs between the same stop (geocoordinate) and another.

So the solution is to put the stop just one time in my list. The other parameters are atm not relevant for us.
sgebhardt
 
Posts: 4
Joined: Mon Jan 25, 2016 2:37 pm


Return to PTV xTourServer

cron