Proposal of Standard: G2B Notation #3
Description
I propose we establish a standard of notation equivalent to DMS (Degrees-Minutes-Seconds) that is called GLCTB, short for Gate-Line-Color-Tone-Base, or G2B for short. (Gate-to-Base.)
This standard would allow for a number of basic conversion methods such as:
dmsToG2B(degrees, minutes, seconds) {
// perform translation
return { gate: g, line: l, color: c, tone: t, base: b };
}
And,
g2bToDMS(gate, line, color, tone, base) {
// perform translation
return { degrees: d, minutes: m, seconds: s };
}
There would also be string notation, as with DMS, e.g. 10º20'30". The equivalent in G2B would be using dots as separators, e.g. 10.1.2.3.4. That would be equivalent to Gate 10, Line 1, Color 2, Tone 3, Base 4.
Thus,
dmsToG2BString(degrees, minutes, seconds) {
// perform translation
return g2bString; // e.g. '10.1.2.3.4'
}
And,
g2bToDMSString(gate, line, color, tone, base) {
// perform translation
return dmsString; // e.g. '10º20'30"'
}
There will certainly be more useful methods, but as a start, I am proposing the standardization of the naming convention G2B to refer to Gate-to-Base notation, with the long form GLCTB, or Gate-Line-Color-Tone-Base.
I am also proposing that we accept helper methods to translate between Exact Base notation and G2B, along with DMS and other useful systems. These are all isomorphic to each other and should be able to be losslessly converted, with the exception of the fact that DMS is more precise, having 1.296m specific positions, while G2B and Exact Base only have 69,120 positions.
Thus, you can losslessly translate from any G2B position to a DMS position, but not from all DMS positions to G2B or Exact Base positions.
Exact Base would be a system of notation using the exact Base position relative to Gate 3, Line 1, Color 1, Tone 1, Base 1, or 3.1.1.1.1 in G2B notation. That is, the position 3.1.1.1.1 is Base 0, and each Base increments by 1 up to Base 69,119 which is the final Base before returning to Base 0 again at 3.1.1.1.1 on the wheel.