The same idea applies with AltLabels. The same segments can be marked by another .list line via...
the same point's primary label,
another point farther along the same route, or
another concurrent route.
Low priority!
Implementation details TBD.
(Nota bene: beware hidden systems if they're ever implemented)
For what this would do, implementation would be complicated enough that it's probably not worth the hassle.
It could yield a small number of things to clean up, sure, but it's arguably only needed for cases like NC295 as in the forum topic above when we want to re-use a name for a new route. For the rare time this happens, we could just take it case-by-case and use shell commands to see who uses what as in the examples above.
Thanks for looking into this. I agree that it's low priority given that it's only really important if we need to reuse a name or label that was previously an alt.
https://forum.travelmapping.net/index.php?topic=5293.msg29822#msg29822 An in-use AltRouteName can be safely deleted if everyone using it marks the same segments via either...
usai;AR;I-49;;Tex;Texarkana, AR;ar.i049tex;AR549,I-130FutTex
usai;NY;I-99;;;;ny.i099;I-99FutCor,I-99FutMan
The same idea applies with AltLabels. The same segments can be marked by another .list line via...
Low priority!
Implementation details TBD. (Nota bene: beware hidden systems if they're ever implemented) For what this would do, implementation would be complicated enough that it's probably not worth the hassle. It could yield a small number of things to clean up, sure, but it's arguably only needed for cases like NC295 as in the forum topic above when we want to re-use a name for a new route. For the rare time this happens, we could just take it case-by-case and use shell commands to see who uses what as in the examples above.