Travel Mapping

Highway Data Discussion => Updates to Highway Data => Topic started by: michih on December 31, 2019, 04:21:55 am

Title: MN+VT: LONG_UNDERSCORE data errors
Post by: michih 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.

Title: Re: MN+VT: LONG_UNDERSCORE data errors
Post by: yakra 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. (http://travelmapping.net/devel/manual/wayptlabels.php#differentnames)
ChuSt & nothing, declaring the Barton one to b part of the VT16_S junction & deleting it.

Title: Re: MN+VT: LONG_UNDERSCORE data errors
Post by: michih on November 14, 2021, 03:45:31 am

@froggie Do you agree that the two labels are worth being changed?