As at the status quo, missing/wonky star sizes ended up heaved out the window.
Two specific cases (motivating this PR) I tripped over from the M1105 Travmap data (turned out they were the only ones in the M1105 data as at Nov 2023) are:
Wrenton 1901: G7 M4 V
Blaskon 2828: M5 IC
After checking with @inexorabletash , he agreed (presuming the QWERTY keyboard layout) that IC is most likely a typoed form of IV. For missing sizes, he agreed with my suggestion to play the odds and assume a star size of V.
The two motivating examples fall out after those changes as:
Wrenton 1901: G7 V M4 V
Blaskon 2828: M5 IV
These two particular cases have been fixed in Travmap, but I want to harden PyRoute against similar, undetected, cases, such as in other milieux, and future fat-fingers.
As such, I've also handled:
missing star size at end of stars line beyond actual, living star: G2 II G3 V M9 now unpacks as G2 II G3 V M9 V
multiple missing star sizes before end of line, between actual, living stars: M2 M5 M8 V gets unpacked as M2 V M5 V M8 V
As at the status quo, missing/wonky star sizes ended up heaved out the window.
Two specific cases (motivating this PR) I tripped over from the M1105 Travmap data (turned out they were the only ones in the M1105 data as at Nov 2023) are:
After checking with @inexorabletash , he agreed (presuming the QWERTY keyboard layout) that IC is most likely a typoed form of IV. For missing sizes, he agreed with my suggestion to play the odds and assume a star size of V.
The two motivating examples fall out after those changes as:
These two particular cases have been fixed in Travmap, but I want to harden PyRoute against similar, undetected, cases, such as in other milieux, and future fat-fingers.
As such, I've also handled:
G2 II G3 V M9now unpacks asG2 II G3 V M9 VM2 M5 M8 Vgets unpacked asM2 V M5 V M8 V