shawndoc wrote:How to do this is covered on the Wiki in the Junction Guide.
shawndoc wrote:Yes. Adding a short ramp segment on the continuing road seems best. The Wiki explains the pros/cons of doing it via two ramps vs using exits.
AlanOfTheBerg wrote:shawndoc wrote:Yes. Adding a short ramp segment on the continuing road seems best. The Wiki explains the pros/cons of doing it via two ramps vs using exits.
A ramp segment isn't necessary though, and IMO, looks very ugly. At a Y split, if all 3 segments connected to the junction are freeway, name the left and right split differently, as you'd see in the on-road signage, and make sure there's a slight angle to both sides of the split. This is shown in the first example of the freeway split in the junction style guide. I use that type, whether it is freeway or highway types, and it is effective and the least obnoxious looking, IMO.
Jpere wrote:Let me ask you, though, will that also create a new set of directions that will appear on the top banner on the app screen? What I mean is, using my same example, when I was 200 miles away from the end of I-75 S, the directions I was being shown on the screen were to exit onto "NW 42nd Ave," which is an exit on SR-924 E. If I implement the fix you and Shawn have suggested, will the app now first indicate to stay left onto SR-924 E and once I get there it will update with the exit onto NW 42nd Ave directions? Or will the change only affect the voice guidance?
Users browsing this forum: PopCulturePhD