yakra, if you think I am missing someone, please do your programming and edit the line above.
I took the labels of the
changed points that are
in use, plugged them into
whouses.sh, and came up with a shorter list:
yakra@BiggaTomato:~/ytm$ ./whouses.sh pa.us013 4THST_E 9THST_E 9THST_W KERST PA291 PA352 US322
All travelers with broken .lists:
capn dave1693 epzik8 extremebandman formulanone jpinyan lowenbrau osu_lsu RMA58 tbwillie tckma ua747sp verruckte_dan wphiii
Not sure how you're coming up with broken list files for all of those people. Many of them have clinched US 13, and the end point labels haven't changed.
This raises a good point -- whouses.sh was written with the MA exit renumberings in mind, and only reports, well,
who uses given waypoint labels. Cases like this where two "good" or "stable" points are in use on either side of a relocated section aren't detected. The .list line is unbroken in that it can still be parsed just fine, but broken in that it maps to something other than what the traveler originally intended, and may not be correct depending on that person's actual travels.
This does give me
an idea for a new shell script though!
There is a new solo portion of US 13 along Morton Ave between PA 291 and 9th St (the new north end of US 13 BUS, where US 13 previously turned from 9th St onto Morton Ave). This section is the only new TM mileage as a result of these changes.
Not sure what this has to do with existing .lists being affected by the relocation though. ...Other than something that can be incorrectly added to the maps/stats of those traveling over the entire relocated portion.
I also did not keep PA291 as an alternate for US13BusChe_S though I debatably could have.
Strongly recommend adding it back in. All 4 people using it only used it to mark off a section of the route that did not change.
This would unbreak .lists for capn, formulanone, osu_lsu & RMA58.
I guess my definition of broken here can also mean "list files affected".
It seems there can be "hard breaks" and "soft breaks" as I alluded to above in my reply to mapcat's post. There can sometimes be confusion about what's being spoken about.
Maybe we could say "invalidated .list lines" or something similarly specific for those cases, and use softer more vague phrasing like "list files affected" for cases that could be either.
Maybe "hard break" and "soft break" terminology could become a thing. Me, I'll be more conscious about the terms I use going forward, to avoid ambiguity.
