I propose adding a bullet point on roads signed with “Toll”. Please provide feedback, as I have not driven on all the toll roads possible.
If the road is badged with, “Toll”, “Toll Bridge”, or “Toll Road”, include “Toll” after the road name in parenthesis. For example:
“Exit 19A: I-80 W (Toll) / San Francisco”,
“Exit 14: SR-520 W (Toll Bridge) / Seattle”,
“Exit 85A: SR-73 N (Toll Road) / Long Beach”
If the road name is not present, write “Toll” as a regular element: “to Surrey / Langley / Toll Bridge”.
^ The goal here is to set a consistent national standard of displaying these badges.
For the remaining items, the goal is to indicate/confirm with Wazers that by taking the next turn, they will be tolled.
If the road is closed-tolled and unsigned, follow the treatment above.
If the road toll is collected exactly once, but unsigned (i.e., a bridge toll), follow the treatment above for all entrances to the toll plaza, including the best continuation.
For roads that indicate tolls as a part of the road name (i.e., “[Indiana] Toll Road”, “Mass Pike”), and barrier toll systems, follow local guidance.
Similarly, if a specific pass is signed as required, add the requirements in parenthesis after the road name. “to SR-16 E (Good to Go only)” or “to SR-16 E (Good to Go or Pay by Mail)”. Consult with your state manager.
–
After this, perhaps it’s a good time to merge the Wayfinder naming article with the exit/entrance section, since the same rules apply.
I would make an exception for roads with “turnpike” in their name. That already implies toll, so it would be redundant to add toll. I also wonder if things in parentheses should be sentence case, as we have been doing for places. Also seems like toll should just be added in parentheses in all cases rather than distinguishing between signed and unsigned, but I don’t know. I don’t often drive toll roads. Is this proposal caused by the avoid toll setting failing? I know toll shows up in the route comparison view. And I think you are just talking about exit/entrance/wayfinder names with this, right, not normal freeway names?
Just a note: in my experience, there is no pause for parentheses so these names will run together and not sound as distinct as it’s displayed. For example, SR-73 W (Toll Road) would be heard as an ambiguous “SR-73 West Toll Road”
Would it be impossible to add to our TTS conversions that an open bracket adds a pause? I feel like beyond just tolls, having ( ) as a pause would be beneficial.
I would prefer that (toll) be lowercase. Also, I see no reason to distinguish between bridges and roads within the parenthetical. Keep it simple and short.
“Exit 19A: I-80 W (toll) / San Francisco”,
“Exit 14: SR-520 W (toll) / Seattle”,
“Exit 85A: SR-73 N (toll) / Long Beach”
When the road name is not present, just do it like a normal sign. In other words, I agree with your suggested guidance but I do not particularly care for the wording “write ‘Toll’ as a regular element”. I’m also not sure what the sign in your case actually says. If the sign actually reads “Surrey / Langley”, I would prefer
“to Surrey / Langley (toll)”
If the sign includes “TOLL BRIDGE” on it somewhere, it should be treated as any other sign element.
“to Surrey / Langley / Toll Bridge”, or
“to Toll Bridge / to Surrey / Langley”
The intent was simply match the signs, and stick into brackets after the road name. It was not to enforce common naming–It’s just that the jurisdictions that I edit in–have signs in any of those flavors.