4 ms·
Another option is EZCOD: all the features of Open Location Codes, plus error detection and correction using Reed-Solomon FEC (forward error correction), in C++
by pjkundert 11y ago
Another option is EZCOD: all the features of Open Location Codes, plus error detection and correction using Reed-Solomon FEC (forward error correction), in C++, Javascript or Python:
https://github.com/pjkundert/ezpwd-reed-solomon https://github.com/pjkundert/ezpwd-reed-solomon
A reference implementation is online at http://ezcod.com http://ezcod.com
More details at http://hardconsulting.com/products/13-reed-solomon http://hardconsulting.com/products/13-reed-solomon
TL;DR
Friends don't let friends use geolocation codes without error detection! You'll end up in the wrong hemisphere...
A code like "R3U 1JU QUY.0" gets you within +/- 3 meters of the coordinates 53.655832,-113.625433 -- with the ability to recover from 1 lost symbol, or a certainty of P(.969) that the presented code is correct.
Optionally, 15 symbols gets you within +/- 20 millimeters of any location on the planet with P(.99997) certainty of correctness, or recovery from up to 3 missing symbols, or 1 erroneous symbol while retaining P(.969) certainty of correctness!
- nulltype 11y agoYeah they list a lot of requirements on this page: https://github.com/google/open-location-code/blob/master/docs/comparison.adoc https://github.com/google/open-location-code/blob/master/doc... Oddly I don't see redundancy (error detection or better yet, error correction) in there but it seems to be an important part of human language. They do make an effort to reduce symbols that could easily be confused at least.
- jononor 11y agoSuprised they did not include error correction in the requirements list, at least in the canonical/long form.