As showed it in the global meetup last month - Toll penalty based on toll price - now available on Live map - and your feedback will be much appreciated!
How does it work?
On the live map you can now do the following:
See the toll prices per route
Adjust the toll penalty to reflect the toll price
:arrow: To see the toll price you should add in the url the following string: &rp_options=USE_TOLL_PRICES:t
:arrow: To adjust the toll penalty to reflect the toll price, you should add to the url the following 2 params: &rp_options=USE_TOLL_PRICES:t&rp_tollPriceUserVector=USD,1,120,3,240,5,420
The values of the rp_tollPriceUserVector should include the following:
Currency of the toll road that is being tested
Toll price diff between routes in the currency from #1
Number of seconds of penalty for the difference in #2
***#2 and #3 can continue as you wish, as in the example above.
Required feedback:
To start with, we would like to set this param per country / state and experiment it with the users. We would love to get your feedback on how this parameter should be set in your country / state, given the local toll prices and possible roads.
I can’t get this to work, trying either routing server. The prices do not display, and the penalty is not evident. Can you give an example Live Map URL where this can be seen?
OK, now I see it, and I got the penalties working too. I had tried rp_id=beta before but maybe didn’t notice the price inside parentheses in the route description
I’ll just leave my feedback about the penalty applied to toll/non toll segments transition. Not about this way to check it.
Waze has always considered “What is the fastest way to get from A to B”. It doesn’t consider if you have to drive 10 more miles, go up a hill, etc. What matters is the fact that it is the fastest. That’s also why you don’t have an option to choose the shortest drive.
We have already the option to choose if we are willing or not to pay tolls. So if I don’t care to pay extra, waze should present me with the fastest way to get there. One good featureis already implemented: If there is a cheaper alternative, the app presents me with that info “Drive x more minutes, and pay y amount in toll”.
I don’t agree with a hidden penalty of the transitions. If a toll booth represents a delay in the route, this will be already considered in the statistics of the segments they are in. And in many cases they don’t even represent a real delay (electronic tolls, without stops for instance).
If the penalty persists, I would suggest that each country could decide to switch them off and on.
In Portugal, we had significant change in routing since implementing the tolls. The solution to this routing “abnormality” may require to alter lots of roads in the country, to bypass it.
Hi everyone. I totally agree with @Hugo_Moreira. We are getting a log of complains already concerning the Waze routing choices by not driving them through the fastest way.
Please consider to turn the tolls penalties ON or OFF for each Country, according to each local community decision.
In general any time you are adding parameters to a URL the very first parameter is preceded by a “?”, and each additional parameter is preceded by an “&”.
It is not necessary to share the drive first and then adjust the URL, you can start with the adjusted URL and then choose routes as long as the URL is adjusted properly (with a “?” for the first parameter).
In this example I started with the following URL and then just tapped the map to choose start and end points. It is choosing a longer route (additional 7 minutes, and 0.7 miles) since it will be a savings of $9.50.
This is great, but I still have a couple of questions:
how are the penalties computed exactly?
If I have 2 routes with a 5,50€ difference and I set:
0,10€ -> 5s of penalty
0,50€ -> 60s of penalty
5€ -> 600s of penalty
5.60€ -> 700s of penalty
What penalty would the second route get?
Only the larger one that is below it? (5€ = 600s)
Or 5€ + 0,50€ (660s?) - (If it would have been 5,40: 5€ + 4x0,10€ = 600s + 20s?)
The closest one? (700s)
This doesn’t seem to work, anymore (even with rp_id=beta). It actually looks like the livemap does not return beta routes anymore, even if that parameter is provided.
None of the parameters shared with us before seem to work anymore. My only hope is that they will add some sort of UI for it in the Livemap to replace the fact we just lost this ability.
I see, but in this case, they can’t blame it on confidentiality if this is posted by a staff member on a public forum.
The live map was a very useful tool to check and debug this functionality.
After some deeper checks, the livemap still sends all given parameters to the routing server, which seems to ignore them. So it’s a Routing Server issue / terrible WAD.
