MysticCobra wrote:You mixed me up with another poster. My issue was I495/DC beltway Exit 39 / RT 190 / Potomac MD headed south into NOVA. There was another user reporting this issue in Severn MD.
As bigbear notes the "continue on" state does not trigger an instruction in the client.jhfrontz wrote:Is the "Continue on..." relatively new?
jhfrontz wrote:There are several intersections in Ohio where the main route peels off on what seems like an exit, leaving some smaller route continuing on the straight-away. I've always heard that we should vary the spelling/spacing on the peel-away segment to induce a proper TTS instruction to "stay right" -- but I thought if the straight-through didn't have any discernible angle that there would be no instruction.
jhfrontz wrote:Ugh, that's hard on the eyes (though I thought the same thing about bow-tie intersections when I first saw them, so maybe the crossed-exits trick will grow on me). Ignoring that, I'm still at a loss as to why there would be routing through that intersection (vs. the freeway). The average speeds seem to favor the freeway. Were there lots of complaints at this intersection or was it by chance a one-off wayward GPS that confused the routing server into thinking that the driver was actually going down the ramp?
jhfrontz wrote:So, should I take the silence here as being consensus on toning down the "Be sure to restrict the straight through" on the wiki page?
Perhaps to something likeIn some cases, editors have found it necessary to restrict straight-through motion. If you are encountering inappropriate routing that seems inexplicable, please post details of it on the forums so that other editors can help identify what might be causing the problem -- and get support form waze developers if needed.
I don't want to make any gung-ho edits...
BlazeTool wrote:skbun wrote:By the way...are we all in agreement that the correct name for interstates now is "I-XXX", with no space, and we should make a project of seek and destroy wherever found?
Has the problem with shields only being displayed if the space is included been fixed?
Users browsing this forum: deeploz