« previous next »
Pages: [1]

Author Topic: WI: US12BusBar label issues  (Read 668 times)

0 Members and 1 Guest are viewing this topic.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1844
  • Gender: Male
  • Last Login:April 24, 2024, 10:38:14 pm
WI: US12BusBar label issues
« on: July 11, 2023, 11:50:11 pm »
US12 -> US12_W
US12/CRW -> US12_E

If a business route starts/ends on both ends at it's parent, it the only route that should be mentioned.
Logged

Offline Highway63

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 532
  • Gender: Female
  • Last Login:April 17, 2024, 11:00:05 pm
Re: WI: US12BusBar label issues
« Reply #1 on: July 13, 2023, 12:39:36 am »
There is a problem with this suggestion: The point US12_W already exists. It was at the end of the business route before US 12 was realigned and the business route extended. It's an alt label for WI33/136.

If you want me to break that point I can, but there will be a consequence.
Logged

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1844
  • Gender: Male
  • Last Login:April 24, 2024, 10:38:14 pm
Re: WI: US12BusBar label issues
« Reply #2 on: July 14, 2023, 01:32:41 am »
Quote from: Highway63 on July 13, 2023, 12:39:36 am
There is a problem with this suggestion: The point US12_W already exists. It was at the end of the business route before US 12 was realigned and the business route extended. It's an alt label for WI33/136.

If you want me to break that point I can, but there will be a consequence.

Route probably should have been broken when the reroute/extension happened sadly.  However, I've come up with a possible compromise for this.  See the new 'rule' change in the private area.  If it's approved, then it will be a perfect solution to this.
Logged
Pages: [1]
« previous next »