Author Topic: CO: US6 concurrency with I-70 possibly wrong  (Read 3091 times)

0 Members and 1 Guest are viewing this topic.

Offline Spinoza

  • Jr. Member
  • **
  • Posts: 85
  • Last Login:April 17, 2024, 08:47:39 am
CO: US6 concurrency with I-70 possibly wrong
« on: October 05, 2016, 10:45:14 am »
Hi, I see that US6 in Colorado, between waypoints I-70(169) and I-70(171), east of Eagle-Vail, has been set to concurrency with I-70. I drove there some months ago and I remember US6 to run parallel to it, until it becomes US24 leading to Minturn and ultimately Leadville. Google Maps and Openstreetmaps seem to agree on that.

Offline the_spui_ninja

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 734
  • Last Login:Yesterday at 10:42:49 am
  • THE Western SD Highway Nut
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #1 on: October 05, 2016, 09:52:44 pm »
There isn't a concurrency there; I've clinched that part of I-70 (just have I-70 in my list file) and the concurrency checker didn't autoclinch that segment of US 6.

If that makes any sense.
An adventure is only an inconvenience rightly considered. An inconvenience is only an adventure wrongly considered. - G.K. Chesterton

Online si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1975
  • Last Login:Today at 11:49:56 am
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #2 on: October 06, 2016, 07:56:36 am »
The US6 point for I-70 exit 169 is slightly off to deliberately break the concurrency (http://www.openstreetmap.org/?lat=39.622648&lon=-106.484428 rather than I-70's http://www.openstreetmap.org/?lat=39.622648&lon=-106.484427). It's hard to tell on mapview though, especially if (like you have) you've clinched both (you can just about see the difference between I-70 and US6 concurrent, and I-70 and US6 not concurrent on the_spui_ninja's)

the_spui_ninja hasn't clinched 169-171 on US6, but has on I-70.

Offline Spinoza

  • Jr. Member
  • **
  • Posts: 85
  • Last Login:April 17, 2024, 08:47:39 am
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #3 on: October 06, 2016, 12:53:51 pm »
Ok, I see now. Sorry for bothering.

Maybe the two roads could be drawn more distant in that segment, for instance with curves? It's really hard to tell them apart just by looking at the map.

Thanks for clearing this up.

Offline Bickendan

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 543
  • Last Login:April 16, 2024, 10:17:30 pm
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #4 on: October 06, 2016, 01:46:41 pm »
I'd say that's a spot where shape points would clear up the ambiguity.

Online si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1975
  • Last Login:Today at 11:49:56 am
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #5 on: October 06, 2016, 04:20:30 pm »
Ok, I see now. Sorry for bothering.
It's no bother.
I'd say that's a spot where shape points would clear up the ambiguity.
Done.

Offline oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1528
  • Last Login:Today at 10:40:32 am
    • Hot Springs and Highways pages
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #6 on: October 06, 2016, 09:00:28 pm »
Maybe the two roads could be drawn more distant in that segment, for instance with curves? It's really hard to tell them apart just by looking at the map.
You'll still have situations where two routes share exactly the same centerline, but are not concurrent. Like I-65  and US 31 in Indiana just north of Louisville KY (I-65 is the mainline, US 31 is on the frontage roads) or Interstate H-1 and HI 92 passing the airport (H-1 is on the upper level, HI 92 is on ground leve).

Offline Spinoza

  • Jr. Member
  • **
  • Posts: 85
  • Last Login:April 17, 2024, 08:47:39 am
Re: CO: US6 concurrency with I-70 possibly wrong
« Reply #7 on: October 07, 2016, 04:32:02 am »
Thanks, much better now.