soap:2500

[KZsolt]

Hey guys!

I face a strange issue now that I can't fix for some reason:
With xRoute I try to plan a route with plenty of points (lets say 500+), and I receive a "cannot calculate route (concerning leg *number*)" error. If I'm right I get this because the mentioned point can't be handled for some reason by the component. (As I believe that happens if the point is on a segment which can't be reached with the profile and routing options I use. etc.)
That wouldn't be a problem at all, BUT if I take all the information of that problematic point (included the angle values) and I make a different routing query to plan between the problematic point and the following/previous one in the old query I get a normal result. In this case the component doesn't throw that issue.

In addition to that in some rare occasions if I simply throw out that problematic original point (because the points are fairly close in the chain), all the following points are getting indicated as bad points as well.

Do you have any idea what can cause that behavior?
Map data: EuroPremium 2015.1H + Truk Attributes - Routing options indicated in the XML

I've attached the 1st and 2nd query XML files with the answers I received from the server. (The last attachment includes the final, good answer.) After the 1st error I removed the problematic point and the 2nd query fails at the same leg (but with the upcoming point this time.)

[KZsolt]

Hey!

I found a solution: Every time I detect a problematic point, instead of throwing out only the problematic one I drop the previous one too. That solved the issue

Regards,
Zsolt

[Bernd Welter]

Hello Kszolt,

Ups - the big question is: why does your station list contain so many points? Sounds like the usecase you have is not really routing ... maybe you want to perform some MapMatching???

Best regards Bernd

[KZsolt]

Hey!

Yes originally I tried to fix that with MapMatching, but I had to use local matching and that caused some missbehaviour (like the one you posted Bernd in a different post). Currently I managed to find a fix for that so now it works correctly. The original aim was to calculate a really precise route for cost calculation based on GPS coordinates.

Regards,
Zsolt