Hi again,
I'm using xRoute to calculate a route from
50.87596, 4.05801
to
50.87267, 4.01837
with the storedProfile set to "van".
I've calculated it in three ways:
1) With speed patterns enabled (Current time)
2) Without speed patterns enabled
3) With speed patterns enabled (optimistic)
From ...
Search found 5 matches
- Wed Apr 15, 2020 1:41 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Slower speed when not using speed patterns layer?
- Replies: 1
- Views: 2894
- Thu Apr 09, 2020 12:21 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Road used inaccessible by truck
- Replies: 7
- Views: 5508
Re: Road used inaccessible by truck
no signs, but physically it'll be impossible to go through, but I guess that truck attributes works based on signs/indications that certain roads are off limit? (Not too important, just found it weird that it would send a truck that way, trying to understand if my request/layers were correctly setup)
- Thu Apr 09, 2020 11:53 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Road used inaccessible by truck
- Replies: 7
- Views: 5508
Re: Road used inaccessible by truck
Ok thanks, but in your first example it will still use a road that should be inaccessible by a truck due to its attributes, should I check this with our local support then?
- Thu Apr 09, 2020 9:37 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Road used inaccessible by truck
- Replies: 7
- Views: 5508
Re: Road used inaccessible by truck
ah hmm, that changed about 6 months ago (I live in the area), but still, the right turn before that forbidden sign would have been the route you take
- Thu Apr 09, 2020 8:35 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: Road used inaccessible by truck
- Replies: 7
- Views: 5508
Road used inaccessible by truck
Hello,
This might be a nitpicky question but I'm investigating the API & was testing the calculateRoute with some data and received some strange results. I'm wondering if this is a request issue, or missing data on your provider side.
(Doing a simple REST call with start location lat: 50.890830 lon ...
This might be a nitpicky question but I'm investigating the API & was testing the calculateRoute with some data and received some strange results. I'm wondering if this is a request issue, or missing data on your provider side.
(Doing a simple REST call with start location lat: 50.890830 lon ...