Perfect.
One last question: Is there a way to get also the duration/distance after the penalty?
So in your example:
111475m and 6446s for the inner route.
Ideal would be the "real" distance/duration and the one after the penalty.
Search found 4 matches
- Tue Nov 24, 2020 9:42 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: xRoute distanceTimeWeighting Problem
- Replies: 10
- Views: 8231
- Mon Nov 23, 2020 3:02 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: xRoute distanceTimeWeighting Problem
- Replies: 10
- Views: 8231
Re: xRoute distanceTimeWeighting Problem
Yes thanks, that makes sense. Are the set of penalties in the profiles trustworthy or just an idea what could happen in the worst case? It makes sense to use them and leave them like in the profile? There is no possiblity to get a final distance + duration with the punishment of each route segment? ...
- Thu Nov 19, 2020 2:00 pm
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: xRoute distanceTimeWeighting Problem
- Replies: 10
- Views: 8231
Re: xRoute distanceTimeWeighting Problem
Thx Joost and Bernd for your quick answers. Yes, I understand that the speed values have a lot of influences. It makes sense that if the route is calculated for a car that the quicker route is via A7. For the speed values I take the default values in 'truck11_99t'. I also use 'PTV_TruckAttributes' a...
- Thu Nov 19, 2020 10:19 am
- Forum: PTV xRouteServer / DEV.Routing API
- Topic: xRoute distanceTimeWeighting Problem
- Replies: 10
- Views: 8231
xRoute distanceTimeWeighting Problem
Hi, we've got following problem: We would like to calculate the fastest and the shortest route between two coordinates. To do that we are using the parameter "distanceTimeWeighting" (100 = fastest; 0 = shortest). We are using following penalties: "penalties": [0, 20, 30, 35, 40, ...