[Page Update] Junction Style Guide
Posted: Thu May 23, 2019 2:26 pm
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]
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]