4 ms·
The larger the alphabet, the larger the risk of glyph confusion. Here's the alphabet they chose: // The character set used to encode the values. var CODE_
by tonyg 8y ago
The larger the alphabet, the larger the risk of glyph confusion.
Here's the alphabet they chose:
// The character set used to encode the values.
var CODE_ALPHABET_ = '23456789CFGHJMPQRVWX';
It omits easily-confused glyphs like "0oOD", "1lLI" etc.
- awirth 8y agoThis is an interesting alphabet, even Base58 (Bitcoin addresses) have "o" and "1". There's some information on how they generated it here in the spec[1]. The characters that are used in Open Location Codes were chosen by computing all possible 20 character combinations from 0-9A-Z and scoring them on how well they spell 10,000 words from over 30 languages. This was to avoid, as far as possible, Open Location Codes being generated that included recognisable words. The selected 20 character set is made up of "23456789CFGHJMPQRVWX". [1]: https://github.com/google/open-location-code/blob/master/docs/olc_definition.adoc#open-location-code https://github.com/google/open-location-code/blob/master/doc...