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 ...
Search found 3 matches
- Tue Mar 23, 2021 8:10 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Cannot caluclate route concerning leg *number*
- Replies: 20
- Views: 50648
- Wed Jul 08, 2020 7:13 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: XRoute 2: "tourReport" not present in response
- Replies: 1
- Views: 2331
XRoute 2: "tourReport" not present in response
Hello,
we have the problem, that the parameter "tourReport" in the "resultFields" Section does not affect the response.
This is the (shortened) part of the "resultFields" from the request:
{
"resultFields": {
"tourReport": true,
"tourReportSpecified": true,
}
}
But the "tourReport" field in ...
we have the problem, that the parameter "tourReport" in the "resultFields" Section does not affect the response.
This is the (shortened) part of the "resultFields" from the request:
{
"resultFields": {
"tourReport": true,
"tourReportSpecified": true,
}
}
But the "tourReport" field in ...
- Fri Mar 06, 2020 1:19 pm
- Forum: PTV xLocateServer / Developer: Geocoding and Places
- Topic: Performance issues with XLocate 2
- Replies: 2
- Views: 7857
Performance issues with XLocate 2
Hello,
we have a performance problem with the XLocate 2 API
We have a list of ~1000 addresses that we are geocoding for testing, and PTV2 performs significantly worse than PTV1.
The average time needed for an address is ~200ms for version 1 and 1 second (970ms) for version 2.
We noticed that ...
we have a performance problem with the XLocate 2 API
We have a list of ~1000 addresses that we are geocoding for testing, and PTV2 performs significantly worse than PTV1.
The average time needed for an address is ~200ms for version 1 and 1 second (970ms) for version 2.
We noticed that ...