« previous next »
Pages: [1]

Author Topic: MN+VT: LONG_UNDERSCORE data errors  (Read 8911 times)

0 Members and 1 Guest are viewing this topic.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 5197
  • Last Login:Yesterday at 01:57:29 pm
MN+VT: LONG_UNDERSCORE data errors
« on: December 31, 2019, 04:21:55 am »
http://travelmapping.net/devel/datacheck.php?show=LONG_UNDERSCORE

MN US75: CR1_Kent -> CR1_Ken
VT US5: ChuSt_Bart -> ChuSt_Bar

Originally, it flagged files with an underscored suffix of 5+ characters. But yakra tweaked it a while back to only allow 4-character ones if they end with a capital letter.
Logged

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4475
  • Last Login:May 02, 2025, 03:12:41 pm
  • I like C++
Re: MN+VT: LONG_UNDERSCORE data errors
« Reply #1 on: March 01, 2020, 07:54:10 pm »
ChuSt_Bar is already taken in Barnet.
Could do...
ChuSt_S & ChuSt_N
ChuSt & ChrSt, ChuSt & ChurSt, etc.
ChuSt & nothing, declaring the Barton one to b part of the VT16_S junction & deleting it.
Logged
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 5197
  • Last Login:Yesterday at 01:57:29 pm
Re: MN+VT: LONG_UNDERSCORE data errors
« Reply #2 on: November 14, 2021, 03:45:31 am »
@froggie Do you agree that the two labels are worth being changed?
Logged

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 878
  • Last Login:Yesterday at 04:07:58 pm
Re: MN+VT: LONG_UNDERSCORE data errors
« Reply #3 on: June 11, 2025, 04:50:35 pm »
https://github.com/TravelMapping/HighwayData/pull/8425

For Barton, I opted for "Option 3".  VTrans officially has VT 16 intersecting at US 5 at Church St anyway so that was an easy label change.
Logged
Pages: [1]
« previous next »