Author Topic: AB: AB-16 exit 400 issues  (Read 1199 times)

0 Members and 1 Guest are viewing this topic.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1829
  • Gender: Male
  • Last Login:Today at 06:11:34 am
AB: AB-16 exit 400 issues
« on: October 31, 2020, 08:01:08 am »
398 -> 400A, maybe fudge it as 400 to prevent list breakage?
400B -> delete (shouldn't it be counted as part of 'current' exit 400A since it's part of it ramp wise?  Plus, AB-216 doesn't have a separate '54' point for it's connecting ramps.)

NOTE: This will also affect AB TCHYel.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: AB: AB-16 exit 400 issues
« Reply #1 on: October 31, 2020, 12:15:06 pm »
Decade-old GMSV shows it was 398 in the past. Looks like ABMoT tweaked the exit numbers in here for some potential added confusion and little gain. In any case, it's 400A now, so relabeling accordingly. Luckily, 400A is not in use in either AB16 or TCHMai, so no need to worry about a label collision.
Agree re deleting current 400B.

https://github.com/TravelMapping/HighwayData/pull/4270
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca