Feel free to change that back. I just am concerned (perhaps unnecessarily) that editors may see a list and jump to action, find a ramp which can be considered to meet one of the criteria (most ramp names are long enough to get truncated on screen), then point here demanding it be made unnamed "because the wiki says it has to be". I was trying to strengthen the "may", in relation to the statement at the end to use good editorial judgement. Not every ramp will need this treatment just because it could be considered to meet a criteria.codgerd wrote:Thanks for the edits; they help with readability. My only comment is that putting the word "may" in italics (twice) rather weakens the statements. It's already written in the conditional, is it necessary to emphasize it further? The impetus for the edit was to flesh out those circumstances in which it can be advisable to use an unnamed segment; the may appears to give more equivocation room rather than less.
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Again I would prefer replacing the word text with content so that it also covers shields which are a big part of sign naming.qwaletee wrote:Paragraph "In the general case..." - I think this one should be pared down.
Despite all the forgoing - the syntax is ambiguous until you read the last couple of phrases.
Suggested wording (general case):
Usually, the exit ramp name should match the text on the exit sign very closely, but using the formatting instructions above. There are exceptions where the ramp should either not be named at all, or should be named differently than the signs. Some examples appear below.
The remainder of the paragraph really should be together with the bullets below it, and a cross-reference to the unnamed segment article instead of trying to summarize it all into a single sentence.
Despite all the forgoing - suggested text:
Despite all the examples, there are other exceptions, and there are cases where the foregoing exceptions may not apply. A good editor will always analyze the situation, adjust for its context and expected user experience, and use good judgement, editing experience, and collaboration to arrive at the best name. Remember, the overriding principle is to help drivers navigate the route Waze provides. This means providing simple, practical guidance on the approach and transit of an intersection or interchange. Any exit name that fails to do so, despite following rules and exceptions perfectly, is itself a failure.
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Again I would prefer replacing the word text with content so that it also covers shields which are a big part of sign naming.qwaletee wrote:Paragraph "In the general case..." - I think this one should be pared down.
Despite all the forgoing - the syntax is ambiguous until you read the last couple of phrases.
Suggested wording (general case):
Usually, the exit ramp name should match the text on the exit sign very closely, but using the formatting instructions above. There are exceptions where the ramp should either not be named at all, or should be named differently than the signs. Some examples appear below.
The remainder of the paragraph really should be together with the bullets below it, and a cross-reference to the unnamed segment article instead of trying to summarize it all into a single sentence.
Despite all the forgoing - suggested text:
Despite all the examples, there are other exceptions, and there are cases where the foregoing exceptions may not apply. A good editor will always analyze the situation, adjust for its context and expected user experience, and use good judgement, editing experience, and collaboration to arrive at the best name. Remember, the overriding principle is to help drivers navigate the route Waze provides. This means providing simple, practical guidance on the approach and transit of an intersection or interchange. Any exit name that fails to do so, despite following rules and exceptions perfectly, is itself a failure.
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Just a quick thought about the transition you mentioned where the highway simply changes designations with no decision by the driver or lane drops etc. Even if the guidance were to include the "exit" in the map, the guidance does not say we need to make it a Wayfinder and 'force' a prompt. We could be aligned with the guidance by adding a short ramp segment with the exit name, whoch would never be announced as a prompt since the ramp is the Best Continuation, and does not meet the criteria for a Wayfinder.
Sent from Android using Tapatalk
Sent from Android using Tapatalk
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum
We might have a few jughandles on undivided roads in Jersey, but I wouldn't go changing the wiki over that. NJ jughandles typically appear on divided roads, which if split, don't cause any BDP problems. So, I'm pretty sure that situation is trivial enough that we can handle it on a case-by-case basis when we find ones with a problem.
https://images2.imgbox.com/6b/db/BSSGdrWs_o.pnghttps://s.waze.tools/coor.pnghttps://s.waze.tools/lcus.pnghttps://s.waze.tools/mntr.pnghttps://s.waze.tools/betc.png
https://s.waze.tools/c6.png
Waze Editing Manual | USA Road Types | USA Forum
Mint Mobile (T-Mobile) iPhone 15 Pro / iOS (latest) / Waze (latest/beta)
https://s.waze.tools/c6.png
Waze Editing Manual | USA Road Types | USA Forum
Mint Mobile (T-Mobile) iPhone 15 Pro / iOS (latest) / Waze (latest/beta)
Moving the word Exit to the end would sound less awkward, though not as consistent with numbered exits. Building on Sketch's note, "Exit right to Kindergarten Ct Exit" has the verb/noun pairing.
IIRC, TTS ignores parentheticals, so we might look into that.
An alternative for freeways that avoids using the word Exit twice might be "Exit right to Kindergarten Ct ramp."
IIRC, TTS ignores parentheticals, so we might look into that.
An alternative for freeways that avoids using the word Exit twice might be "Exit right to Kindergarten Ct ramp."
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
Didn't you just do one in Queens recently?PesachZ wrote:I can't say for certain that there are, but I figured it can't hurt to cover it if you're redoing the guideline anyways. I'm sure there's a few somewhere. And that may be a valid use for naming the ramp based on where it leadsCBenson wrote:PesachZ wrote:But you also have to cover exits which have a BGS.
I'm intending to cover exits which have a BGS. Are there exits as we are defining them (i.e. ramps that are part of a grade seperated interchange) that do not have BGSs?
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
But, to his point, if the BGS doesn't already include too much verbiage, it might be OK to add "/ local name." I don't see much downside, so long as it doesn't result in CONFLICT with the BGS, reads the BGS FIRST, and is based on LOCAL KNOWLEDGE that the exit is called something else locally. I do see an upside in case the driver has received some sort of instructions from a local but is using Waze as a failsafe, and could otherwise become confused/concerned at the mismatch.sketch wrote:No. We follow the order things are on the BGS because it's simple, uniform, easy to edit, and doesn't require any arbitrary decisionmaking. Even if no one knows or cares that Claiborne Ave is LA-39, the sign has the LA-39 shield first, so we say it first.KB_Steveo wrote:Another question:
If you have an exit where the local convention uses the street name when providing verbal exits, would it be OK to list the street first instead of last?
For example, no one in Green Bay would say to take the Highway 54 exit, we would just tell someone to take the Mason St exit.
(I will note the one exception you spoke of recently in the JSG thread, which I am a fan of and have used myself – moving anything prefaced with "TO" on the actual sign to the end of the string.)
If the BGS is already long, then I would avoid the addition.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
I thought we were abandoning SH, using only SR for consistency, regardless of TTS. I don't care either way, I'd personally go with local convention.
For directional suffix, I know I read somewhere that Waze used to need the suffix on split roadways because otherwise there would be some kind of routing problem, but that has been resolved, so no need for it. That doesn't mean we can't have a convention that requires it for the benefit of the driver (and editors sticking forks in the spaghetti!).
For directional suffix, I know I read somewhere that Waze used to need the suffix on split roadways because otherwise there would be some kind of routing problem, but that has been resolved, so no need for it. That doesn't mean we can't have a convention that requires it for the benefit of the driver (and editors sticking forks in the spaghetti!).
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
Looks OK, but we should probably look towards simplifying it a bit and cleaning up language. We can probably explain unsigned/numbered/signed but unnumbered in half the verbiage.
The "in other words stuff" is just awkward -- I know you did not put that in, I'm just pointing out things that need fixing.
IIRC, there was a recent discussion about appending the common-usage local name even if it did not appear on BGS, so long as the ramp name did not become excessively long, but I don't see that present. For example, if SR-1234 is locally known as McManus Road, but the BGS says
...then it would be OK to use a name of: SR-1234 / Goodness City / McManus Rd
But..
...might be a little too much with the appendage: SR-1234 N / Goodness City / to SR-1234 S / Graciousville / McManus Road
And in any event, if the local name was added, it was to always be appended, never added anywhere else, and if the local name was actually in the BGS, then the order listed on the BGS should be respected.
The "in other words stuff" is just awkward -- I know you did not put that in, I'm just pointing out things that need fixing.
IIRC, there was a recent discussion about appending the common-usage local name even if it did not appear on BGS, so long as the ramp name did not become excessively long, but I don't see that present. For example, if SR-1234 is locally known as McManus Road, but the BGS says
Code: Select all
[1234]
Goodness City
But..
Code: Select all
[1234] N to [1234] S
Goodness City Graciousville
And in any event, if the local name was added, it was to always be appended, never added anywhere else, and if the local name was actually in the BGS, then the order listed on the BGS should be respected.
US Champ / Country Manager | State Manager NY, NJ, PA, CT, MA, RI, VT, ME, NH | Northeast ARC | Mentor | Responding to Map Issues
Re: [Update] Road Name/USA