NC: US276 signed north-south

[yakra]

Checked around GMSV in several places. All of them had NC US276 signed as north-south.

[mapmikey]

order flipped and in the queue

[oscar]

Updated route is in the HB. But the old NC/SC point label should've been kept and hidden as an alternate label for SC/NC, to avoid breaking list files (my own included).

[mapmikey]

So the HB is able to use that even though the points are in the reverse order?

So my list file is this based on the original order:

NC US276 I-40 NC/SC

If i had the alternate label in there, my file listing would still work?

[oscar]

^ Your list file is broken too, per your error log:

Waypoint label NC/SC not found in line: NC US276 I-40 NC/SC

The list file parser doesn't care about the order of your waypoints in a list file line, but it does care when a line includes a waypoint label that doesn't exactly match any label in the HB. To the parser, "NC/SC" doesn't match "SC/NC".

Your list file would work fine if you just changed "NC/SC" to "SC/NC". But your file and other users' would work if your route file replaced "SC/NC" with "SC/NC +NC/SC", which lets the parser know that both labels refer to the same waypoint.

More broadly, for active systems we avoid if at all possible changing labels in use (check the "points in use" log), without keeping and hiding the old labels. There are situations where breakage is unavoidable (which should be reported in the Updates table), but this isn't one of them.

[mapmikey]

added the alt name in