Post Reply

[Page Update] Junction Style Guide

Post by PesachZ
In regards to a misunderstanding brought up elsewhere, I have made a small calrification edit to the section for Two-Segment Loops on this page. I also removed some extra spaces in the section.

Finally, I updated the forum link in the mbox at the top of the page to point to this new thread, since it was still linking to the legacy thread from years ago, and there is no existing USA thread specific for the main JSG page that I could find.

Here is the before and after text, or if you prefer a link to the change delta in the page history:
[quote=original]Two-segment loops create a situation called "same endpoint drivable segments" or "same connection segments". There are two or more ways to get from one junction node to another without going through any other nodes. They can cause a problem for the Waze app because the routing server gives your mobile app a list of node ids, but the app needs to tell you which segments to drive on. If there are two ways to get from one node to the next without going through any other nodes, then the Waze app might just have to guess. It might guess a detour off the highway through a service road or scenic overlook. Please save Waze from this silliness. Correct two-segment loops.[/quote]

[quote=update]Two-segment loops create a situation called "same endpoint drivable segments" or "same connection segments". There are two or more ways to get from one junction node to another without going through any other nodes. They can cause a problem for the Waze app regardless of the direction, or other attributes of the segments. This is because the routing server gives your mobile app a list of node IDs only, but the app needs to tell you which segments to drive on. If there are two ways to get from one node to the next without going through any other nodes, then the Waze app might just have to guess. It might guess a detour off the highway through a service road or scenic overlook. Please save Waze from this silliness. Correct two-segment loops.[/quote]
PesachZ
Wiki Master
Wiki Master
Posts: 4513
Has thanked: 1381 times
Been thanked: 1618 times
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

Post by SolSash7
In addition to trying to update images in the article, I also created a draft in my user space that includes several minor changes to the formatting as well as some of the content. My main goals were:
* Provide more up-to-date imagery
* Condense and utilize a-lot of the white space
* Include some of the summary information from other pages to help the reader ascertain whether they wanted additional reading by following the link
* Caption all of the imagery to help the reader connect the images with the content

Since there were a lot of minor changes, I'm not entirely sure whether it'd be helpful to itemize each one; however, I'm open to porting over only some of the changes to the main article as consensus allows.

Here is a link to my draft of the Junction Style Guide:
https://wazeopedia.waze.com/wiki/USA/Us ... tyle_Guide
Please provide any and all feedback as I'd like to tailor my editing style to the audience as well as improve the wiki - Thank you.
SolSash7
Area Manager
Area Manager
Posts: 17
Has thanked: 54 times
Been thanked: 18 times
With regards,
SolSash7, "Sol"

I entered ten puns into a pun contest, as for what won? No pun in ten did.

Post by Kartografer
Thanks for doing this! The draft looks good. While we're at it, we might as well apply the WP MoS (which we have agreed to use) and change all the section headings, bulleted lists and image captions to sentence case, where they are not already, and use italics rather than all caps for emphasis. There is also a link to the validator script that could use a |.
Kartografer
Wiki Master
Wiki Master
Posts: 1244
Has thanked: 462 times
Been thanked: 671 times
Galaxy S20 FE on Mint
Retired SM Ohio
Then you will know the truth, and the truth will set you free.
-John 8:32

Post by SolSash7
I believe I have brought my draft up to WP MoS
Now, when I first read this article a couple of weeks ago, I was confused by these sections:
Make sure that there is a junction indicator (the small blue dot, not just a geometry node) at the very end of the segment. While this one segment does not actually constitute a junction, the small blue dot is a visual indicator to the editor that the end of this segment is properly set up. This is necessary to ensure proper routing out of the segment. See the cul-de-sac section below on when and how to fix this.
Be sure the free end of the final road segment has small blue dot displayed at the tip (when not editing or selecting the segment). If there is no blue dot, please correct it by following the steps for fixing dead ends.
Where the second quote ends with a link to the creating and editing road segments with a reference to a section that no longer exists: Fix the end-node on cul-de-sacs and dead-ends.

Following information from here: map editing quick-start guide
As of July 2014, U-turns at dead ends or cul-de-sacs, no longer need to be adjusted in a particular way. WME no longer provides a link to adjust it.
I assume that the two quoted sections in the junction style guide can be nuked?
SolSash7
Area Manager
Area Manager
Posts: 17
Has thanked: 54 times
Been thanked: 18 times
With regards,
SolSash7, "Sol"

I entered ten puns into a pun contest, as for what won? No pun in ten did.