Page 33 of 35

Re: [Page Update] Junction Style Guide

PostPosted: Thu Oct 01, 2015 7:44 am
by kentsmith9
If it is different in different countries then yes. I was only speaking of the current page that has had all this material since I was working on it 2 years ago. If we need to split a US-centric version now, that is no problem.

Re: [Page Update] Junction Style Guide

PostPosted: Thu Oct 01, 2015 9:58 pm
by codgerd
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?


As far as I can tell, sketch's draft page for the JSG/Interchanges is here. I don't know if this represents the most recent version, but there are no apparent changes to the "Ramp geometry and complexity" section from the version currently in the wiki.

As it appears that the Canadian champs are more or less in agreement as to what the guidance should be for Canada, I'm going to lobby for us to make changes to our Canada wiki, as that appears to be easier than getting guidance from the global page.

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 5:54 pm
by jondrush
kentsmith9 wrote:
jondrush wrote:In my experience, having the junction at the mandatory split will yield a voice prompt that is too late. You would have to jerk the steering wheel to get over to the ramp if you waited for it.

I don't think I have the same experience. I get notifications a long distance in advance of the actual junction. Just like a turn at a corner. You get a 1/2 mile warning, then x feet, then y feet, then turn now. I get the same thing on the splits. I am pretty certain that is how we set up all the bay area freeways 3 years ago. I thought that was what we had in the guide for the US, unless I misunderstood back then or it has changed since then.

Are you on iOS or andoid? I'm on iOS and the exit notifications are spot-on. I've talked with some androids folks and they complain about early warnings.

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 6:14 pm
by kentsmith9
I am iOS.

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 6:27 pm
by jondrush
I don't get it then. How can we be having a different experience?

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 6:36 pm
by kentsmith9
Jon, are we talking about the same thing? I have multiple alerts in advance of the actual turn (or exit). Just like approaching a corner, I have alerts and voice prompts telling me a turn is coming. I have never had to do anything drastic to turn or exit when the junction point is placed at the legal solid while line divider for splits/exits, or at the actual corner junction of a road.

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 7:19 pm
by jondrush
I've never had notable issues at corners. But I have had the final exit right command (all I care about) come too late to safely start the maneuver to the ramp. All related to the position of the junction. It's also important when ramps are closely spaced. A too-late final command puts you on the wrong ramp on some interchanges.

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 8:10 pm
by kentsmith9
I will pay specific attention to it tonight on the way home just in case I have not been paying enough attention. ;)

Re: [Page Update] Junction Style Guide

PostPosted: Wed Oct 07, 2015 11:11 pm
by Kayos_On_The_Road
jondrush wrote:I've never had notable issues at corners. But I have had the final exit right command (all I care about) come too late to safely start the maneuver to the ramp. All related to the position of the junction. It's also important when ramps are closely spaced. A too-late final command puts you on the wrong ramp on some interchanges.

As I've stated before in this thread I believe the only reason for a late (or in fact no TTS instruction at all) is loss of gps location. For the late issues you have, are you certain that the node is not also incorrectly positioned late? I run Android and find the TTS fine (gps issues asside), but I have seen one UR recently complaining about late instructions but I didn't consider asking about which platform they were running.

EDIT: For closely spaced ramps you would have issues if the node is to early on the second ramp and wazers taking the first ramp incorrectly, so closely spaced ramps could be an issue regardless of the guidance on node location.

Kayos

Sent from my SGH-I747M using Tapatalk

Re: [Page Update] Junction Style Guide

PostPosted: Thu Oct 08, 2015 4:03 am
by qwaletee
I have sometimes experienced late instructions. This can happen:

1) if the phone is "pegged" (CPU running in overdrive, battery usually heating up)

2) if GPS signal is weak

3) if there are sequences including short segments, which seems to sometimes confuse Waze on timing... closely-spaced exits may be an example of this, or may be a fourth category, I can't tell for sure

BTW, these same factors affect me on the highway or on local streets.

Part of the difference in experience may be regional. East coast tends to have a lot of closely-spaced exits on older highways.