-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watford City ND bypass #127
Conversation
sync yakra/master with upstream master 2015-10-06
Removed from US 85 Business and relocated onto the southwestern Watford City bypass.
Removed from ND 23 Business between US 85 Business and the southeastern Watford City bypass, and relocated onto the southeastern Watford City bypass between US 85 and ND 23 Business.
Removed from US 85 Business and relocated onto the southwestern Watford City bypass.
I'd appreciate your adding OldUS85_N and _S points to the US85 and US85BusWat files, where both peel away from the old US 85 alignment. The junctions between the mainline and business routes leaves more than usual stranded old pavement, and the extra points would best reflect that. Also, suggest the north endpoint be renamed from ND/Can to either ND/SK or USA/Can, to be consistent with other international border points. |
Thanks, Jim -- my close was indeed by mistake, while I was removing a duplicate comment. Looking again at US85BusWat, it looks like ND23_E is where an OldUS85_S point would go, so no new point needed there. Still needs an OldUS85_N point, to reflect my travels on former US 85 through Watford City, |
Holding off on this one for tonight. Let me know if all is set and I should merge. |
If I update the files in my local branch, will merging his request pull in my newest revisions of the files, or just the earlier commits listed above? |
@yakra You can add commits to an open pull request, or if it's easier, just open a new one with either all of the changes or just the additional ones. |
Unsure immediately how to add new commits. How about we merge this one in, and then I add in the *OldUS85 points in in a future pull request? Oscar, WRT US85BusWat and the usual amount of stranded old pavement: |
Sure. Merging this one in. |
The first (oldUS85) seems better to me than the second (*OldUS85), The second is slightly more perfect, but the first is close enough for me, and that it's at an actual intersection makes it better. Oscar ----- Original Message ----- From: "Eric Bryant" [email protected] Unsure immediately how to add new commits. How about we merge this one in, and then I add in the *OldUS85 points in in a future pull request? Oscar, WRT US85BusWat and the usual amount of stranded old pavement: — |
I've added OldUS85 to US85BusWat in my repository. US85 proper: |
All of these are fine with me, including using 130thSt instead of the northern OldUS85 point. Oscar ----- Original Message ----- From: "Eric Bryant" [email protected] I've added OldUS85 to US85BusWat in my repository. For US85 proper: — |
I'll use 130thAve, then. Heck, it's what I did with the US54/400 Cunningham KS bypass. |
Just to let you know, the concurrency between ND 200 and US 85 is now broken. I think the points need to be added to ND 200's file as well. |
Derp! Thanks. |
Nice. No, not for the reason you think.
go on confusing the soul hold my breath
15-10-06;(USA) North Dakota;US 85;nd.us085;Removed from US 85 Business and relocated onto the southwestern Watford City bypass.
15-10-06;(USA) North Dakota;US 85 Business (Watford City);nd.us085buswat;Added route.
15-10-06;(USA) North Dakota;ND 23;nd.nd023;Removed from ND 23 Business between US 85 Business and the southeastern Watford City bypass, and relocated onto the southeastern Watford City bypass between US 85 and ND 23 Business.
15-10-06;(USA) North Dakota;ND 23 Business (Watford City);nd.nd023buswat;Added route.
15-10-06;(USA) North Dakota;ND 200;nd.nd200;Removed from US 85 Business and relocated onto the southwestern Watford City bypass.