PTV Group - Logistics Forum

So here we go... though I can't provide a 100% solution I have new info about this (thanks to Frank for the analysis):

The area we are refering to seems to be restricted by so-called gates.

Let's start with some screenshots from an internal tool: But probably it is not a sufficient approach to enable this kind of flexibility.
http://devblog.ptvgroup.com/2014/01/10/ ... -vehicles/
So for now I can only explain the response.

If you set the deliveryFlag to false the linking favours a segment which can be reched without such problems: Does this help?

Bet regards,
Bernd

Hi Bernd,
actually did the trick for us. Thank you very much, your support is really outstanding!!

If you are happy with our work: tell our management.
If not: tell us

Best regards,
Bernd

I recently ran into a similar issues, I believe that these are are actually map errors. IMO the gates should have exceptions for the authorized flag. I' m checking this with our data department.

Hi Bernd

I'm facing the same error "Cannot calculate route concerning leg *number*" with the following address:

Rue de la Source 5
1020 Renens

https://goo.gl/maps/8dyJykFku9ZmCArSA



I have tried the suggestions:
http://devblog.ptvgroup.com/2014/01/10/ ... -vehicles/
https://xserver.ptvgroup.com/forum/post ... 552#pr1950

But none worked for me.

But, it works by changing the delivery flag: alternating this boolean parameter switches from error (isDelivery=true) and success (isDelivery=false)


Thank you in advance for your support.
Best regards
Pedro Diogo

Hello Pedro,

looks like the road is forbidden in the TOMTOM data: In the HERE map it is a regular road. Maybe you can provide your exact XML request so we can reproduce and "tune" it?

Best regards,
Bernd

Hi Bernd

Thank you for your fast reply.
Follows attached the XML request.

Best regards
Pedro Diogo

Hello Pedro,

here's the result of our development team's analysis:

The violation concept does not help here as this is only valid for segment attributes like blockings. For geographic restrictions used here there is no possibility other than modifying them (e.g. including France to the allowed countries).
In this special case you can play around with the linking. If you set the link type of the second waypoint to "NEXT_NODE" than it works as the waypoint is linked a bit more east. Or you can "move" the waypoint a bit more away from the border. In any case you have to handle such waypoints manually.

So while violations can help with a spcific category of restrictions this does not apply in your scenario.
Sorry for that output - sounds like this case needs a special manual treatment.

Best regards,
Bernd

PS: I also want to emphasize that this isn't a but of the engine.

Hi Bernd

It's clear now.
Thank you for your help.

Best regards
Pedro Diogo

Hello,

we also have a problem with the error message "cannot calculate route (concerning leg X)".
We have already tried a little bit with the parameters "isDelivery", "isAuthorized" and "isEmergency".
Generally we noticed that by setting these parameters more routes could be calculated. However, we also had a few cases where setting the "isEmergency" parameter resulted in an incorrect calculation.

Now we have a route where setting the "isDelivery" parameter leads to an error.
We have also tried setting "<Maneuver considerTurningBans="false" uTurnCost="5000"/>" which did not help.

I put the route and the XMLProfileSnippet in the attachment.

Can you help us to fix the problem?

With kind regards
Lennart Kampshoff