From Wazeopedia


2,634 bytes added, 5 months ago
More infos
#* This also means that given two route options the routing server will choose the one with the fewest number of toll segments, regardless of if they are consecutive or not.
'''Note:''' The penalty for "avoid toll roads" is very high, and the definition here of reasonable may seem extreme. The routing server will prefer a significant detour to avoid a toll, but not one it considers to be insane or impossible. The exact amounts of both penalties are proprietary information and are not published by Waze.
In addition, if a toll road is given in the first route option, Waze tries to provide a free route as the second option, even if this route takes much longer than alternative routes that include toll roads. It even gives cards in the route summary to inform users how much more time would be required for them to use a free or cheaper alternative.
== Editing ==
If any of these IDs or their order are changed through cutting, merging, disconnection or deletion, the toll price file will not work. It must be updated with new IDs and re-uploaded onto the server. {{As of|August 2019}} the editor gives no indication that segments have any associated pricing information, and the toll tool gives no indication that a file contains broken segments, apart from manually testing routes through specific segments. Therefore, '''editors must be very careful not to inadvertently break price files when working with tolls'''. While building price files, some editors have added map comments or higher locks on segments that they use, in order to provide some level of protection, but this has not been done universally. Each section can also be associated with a venue ID of a toll booth or other place. {{As of|August 2019}} the venue ID is not used in the app, and only static pricing is supported. The segment, node and venue IDs are the only common elements between the toll price tool and WME.
==== Pay-per-section Pay_per_section ====
This is the most common rule used for toll roads. Drivers pay fixed amounts at each collection point along a toll road. The amounts collected do not depend on how far the driver has driven on the road. In the toll tool, the pay-per-section rule is used, sections are defined for every toll collection area, whether a mainline toll plaza or a pair of exit and entrance ramps. Prices are added to each section. Multiple prices can be added per section, depending on passes, vehicle types, and valid times, days or dates. If one section has a pass-specific price, all sections must have this price added in. So, for example, if a road collects tolls through both cash and E-ZPass transponders, a section that contains E-ZPass-only segments must have a cash price (nothing in the permit field) defined, along with an E-ZPass price (ezpass-us or a variant in the permit field), even if only E-ZPass holders will be routed through it.
==== Entry/exit price Entry_exit_price ====When traffic is charged different amounts at an exit depending on where they entered, toll prices must use this rule. Prices should not be entered in the sections, and if they are, they will not be used. Instead, prices must be entered using one of two ways, entry/exit matrices or entry/exit rules.  ===== Entry_exit_rules =====In the early versions of the toll tool, only entry/exit rules were available. An entry section and exit section, and optionally an intermediate section, are filled in for each price in the system. The number of rules increases quadratically with the number of sections (entrances and exits, and this becomes cumbersome very quickly. Some files have become so large that they have caused browsers to crash.
===== Entry_exit_matrix =====
More recently the entry/exit matrix was developed. Instead of making a new line for each individual entry/exit price, a square matrix is generated based on the number and order of sections in the file. Note that the sections listed above the matrix in the tool are the "from" sections, the sections listed to the left of the matrix are the "to" sections, and the rows of prices in the JSON data are transposed as columns in the tool. So if a file has 20 entries and 20 exits defined individually, a 40x40 matrix is generated, with 1600 individual prices. If the entry sections are listed sequentially before the exit sections in the file, this would mean that the lower left quadrant of the matrix (as displayed in the tool) is where the prices should go, because this represents the prices from the entry sections to the exit sections. Multiple price matrices can be added to a toll, dependent upon which permit, time or vehicle type they apply to.
==== Pay_per_section_count ====
This is used in the uncommon situation that a toll road charges a discrete amount for passing through a certain number of collection points. Permit_prices are defined for any applicable permits and section counts.
=== FAQ ===
==== Can the toll tool handle prices for different vehicle types, passes and times? ====
Yes, prices can be defined by vehicle type, toll/HOV pass, hours and minutes of the day, days of the week and dates in the year. Pass interoperability and subsets are supported. Enter the pass display name or code name in the permit_id field. ==== Can the toll tool handle prices with multiple currencies? ====At this point, each toll file must use one currency, so uploading a toll price in multiple currencies would require multiple files. However, the existence of multiple files for the same segment and direction creates a conflict, so multi-currency prices have not been seen to work successfully. ==== Can the toll tool handle prices for different numbers of passengers? ====Not at this time, but it is a planned improvement. HOV discounts are not supported, nor are prices that increase with multiple passengers, such as certain ferry fares. When mapping ferry tolls, it's best to give a price that applies to solo drivers.
==== What do I do if I see a UR about a toll price problem? ====
==== How does uploading work? ====
When a file is ready to be used in the app, its builder can request an upload through a form linked under the Welcome tab of the toll tool. If a file has been submitted for upload, but a correction needs to be made, the form should be filled out again to request uploading a new version of the existing file. Staff generally uploads new files and corrections every two weeks, after checking for problems with the files and conflicts between different files over the same segment and direction. If someone has saved a public file for the same toll road that you are working on, try to coordinate with them, and check the list of uploaded files to make sure that uploading your work won't create a conflict. The mere existence of multiple public files for the same road that ''have not'' been uploaded is not a problem; sometimes people collaborate and copy work from one person's file to their own. ==== Can the toll tool handle prices with multiple currencies? ====At this point, each toll file must use one currency, so uploading a toll price in multiple currencies would require multiple files. However, the existence of multiple files for the same segment and direction creates a conflict, so multi-currency prices have not been seen to work successfully.
==== How do I log into the tool? ====
==== Do I need to fill in every field? ====
Under tolls, the toll_id, road_local_name and currency fields must be filled in, and one rule must be chosen (if more than one is chosen, only one will work). At least one section must be added. Under sections, the section_id, road_local_name, section_local_name and location must be filled in. At least one segment must be added. Under segments, the id, fromNode and toNode fields must be filled in, but the tool can extract these from segments marked with toll, by filled in the permalink field and clicking Populate (if the segment from the Permalink permalink does not have a toll flag or toll free restriction in the most recent tile build, the tool will only extract the segment ID).  The polyline field only provides a visual indicator of the toll road in the playground; this can be left blank if not planning to test the file in the playground. The venue_id field is not currently used and can also be left blank, but it's good to fill in if a Waze place exists for the toll booth in the section.
==== What do I put for the section/road_local_name and section_id fields? ====
==== What happens if I don't select any vehicle types or days of the week? ====
The price applies to all vehicle types or on all days of the week. There's no need to select everything, and in the case of vehicle types, this would exclude any new vehicle types that are not included in the tool but may be enabled in the app in the future, so if a toll is not specific to certain vehicle types, it's recommended to select no vehicle types for the prices.
==== How do I handle time-based or date-based prices? ====
There For prices that vary by times of the day or days of the week, simply adjust the valid_minutes field or select valid_days. Multiple ranges of valid minutes can be entered in the same price, separated by a comma. For prices that vary by dates, there must be a default price that is valid for a whole day all dates of the week and/or datesyear, and it must be listed first. Then other prices can be added with valid_dates in them. It doesn't matter whether the default price is higher or lower than the time-based valid_date price. So for example, if a toll price is scheduled to increase on January 1of next year, 2020the new price for next year can be entered as the default price, and the current price can be entered under it with valid_dates ranging from the current date to December 31 of the current year. ==== What is a trip_charge? ====This is a base fee that applies once to all trips through the toll. It is added to any individual section-based or matrix-based prices. One example use is with ferries that charge money individually for passengers and vehicles. The passenger fare can be added as a trip_charge (since we do not yet have multi-passenger support), and the vehicle-based prices can be added as normal prices in the section. ==== What is a special_price? ====It is used for special cases, such as an additional amount added to the trip charge if traveling over a certain section.
==== Is there an easier way Has anyone come up with a script to do make thiseasier? ====Of course! The Portuguese community have developed another tool in Google Sheets that automates some of the price file generation process. It is presented [ here].