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

0 Members and 1 Guest are viewing this topic.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2820
  • Last Login:Today at 05:18:18 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.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2849
  • Last Login:Today at 12:55:55 pm
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.