Fri Sep 18, 2015 3:54 pm
Mon Sep 21, 2015 6:47 pm
DwarfLord wrote:I have struggled for nearly a year with the question of where junction nodes should be located.
So "how the TTS timing is set up in the app" really is the key question here. I hear conflicting driver experience and have no idea what to recommend.
Thu Sep 24, 2015 3:21 pm
top_gun_de wrote:For us, that means that we start freewayramps shortly after the beginning of the striped line, and that we start ramps on major highways late if we expect drivers to stop for more than a few seconds. The rest is somewhere in between.
Thu Sep 24, 2015 8:31 pm
top_gun_de wrote:These differences show why it's no possible to make global stAndards when there is no global standard for road construction, traffic rules and driver's habits.
Wed Sep 30, 2015 9:40 pm
Kayos_On_The_Road wrote:I believe the junction node where the solid line starts is by far the easiest and most consistent method of editing and should be applied across North America.
Thu Oct 01, 2015 9:58 pm
kentsmith9 wrote:At one time Sketch was doing a bunch of changes to JSG and there were many subpages created with works in progress last year. I lost track of where they went in their progress to get merged back together in a new page.
Is anyone currently spearheading the main JSG?
Fri Sep 04, 2015 9:41 pm
Fri Sep 04, 2015 10:55 pm
PesachZ wrote:Though I would argue that by our AGC rules in the US the two medians you set as MH, should really be mH. making them mh will have no detrimental on routing here.
PesachZ wrote:The issue will be that the guidelines fo this kind of thing varies by country. Perhaps it is better placed in the page for Median Uturns, and have that page expanded to cover all median typing in the USA.
Wiki wrote:Special rules are used to determine the road types of roundabouts and at-grade connectors.
Wed Jul 16, 2014 1:49 pm
Wed Jul 16, 2014 2:33 pm
PesachZ wrote:They do pose a real problem to routing, and should not be created as a one piece loop (for reasons you mentioned), or a two piece loops. When they are erroneously created that way they must be fixed, which is why the scripts detect and fix these errors.
I am mobile right now so can't elaborate in detail, but the short answer is the router has no issue with these 2 piece loops, but the client can't tell the two sides apart. So say you have a parking lot road connect to the same segment of highway on both ends, the app can't tell the difference between sending straight down the highway, or off the highway - through the PLR - and back on the highway. This can cause bad routing display when navigating and poor instructions as well.
This is because the app Identified segments based on which node they connect to at either end. If both segments share the same start and end node, they become interchangeable in the client app. Adding an extra nice to the lower priority side of the loop makes it so none of the segments share both the same start and end node.
Hope that was clear enough. If not I can explain better later