Author Topic: CA 23/US 101 broken concurrency  (Read 2788 times)

0 Members and 1 Guest are viewing this topic.

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1018
  • Last Login:Yesterday at 11:50:45 am
CA 23/US 101 broken concurrency
« on: January 10, 2023, 12:43:56 am »
CA 23 is missing the 43A point that US 101 has. This... makes sense on the face of it since one cannot directly access exit 43A from CA 23, but as mapped it breaks the concurrency with US 101 north of exit 41 because the point for the split at 43B is after 43A.

Cleanest way to fix this may be to consolidate 43A and 43B under 1PPI. 

« Last Edit: January 11, 2023, 08:05:29 pm by Duke87 »

Offline oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1584
  • Last Login:Yesterday at 09:05:00 pm
    • Hot Springs and Highways pages
Re: CA 23/US 101 broken concurrency
« Reply #1 on: January 11, 2023, 07:35:16 am »
^ That could work. It helps that nobody is using 43A, just the 43 and CA23_N alt names for 43B. And 43A and 43B are just 0.12 mile apart, which makes 43A dispensable, and 43B => 43 is desirable for waypoint simplification.

Comments? My only GitHub client is on an old laptop on the verge of failure (though still usable for now), and I'm not ready to install a GitHub client on my new laptop. So I'm trying to be careful here.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4422
  • Last Login:November 11, 2024, 12:50:03 pm
  • I like C++
Re: CA 23/US 101 broken concurrency
« Reply #2 on: January 11, 2023, 08:38:12 am »
There's always the web interface,
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1584
  • Last Login:Yesterday at 09:05:00 pm
    • Hot Springs and Highways pages
Re: CA 23/US 101 broken concurrency
« Reply #3 on: January 19, 2023, 09:55:03 am »
I just attempted to pull in a fix, using a new GitHub install on my new laptop. Not working so far. Will retry.

UPDATE: My attempted fix was pulled in earlier today. Only I forgot to delete unused US 101 point 43A, which was the cause of the broken concurrency problem discussed above. I'll try again in my next pull request.
« Last Edit: January 19, 2023, 10:29:25 pm by oscar »

Offline oscar

  • TM Collaborator
  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1584
  • Last Login:Yesterday at 09:05:00 pm
    • Hot Springs and Highways pages
Re: CA 23/US 101 broken concurrency
« Reply #4 on: January 21, 2023, 10:19:47 pm »
Fix is finally in the HB. Marking as solved.