William Entriken

Can you please verify one of the code length 15 examples by hand. Using a calculator with sufficient digit precision.

Recommended tag: implementation request (but actually recommending to close as out-of-scope in #434)

Yes. That file is normative and it should be merged into the specification file. Or at a minimum it needs to be linked. --- --- P.S. Here is an example...

Recommended tag: specification

Also, the specification in https://github.com/google/open-location-code/blob/master/API.txt conflicts with the specification at https://github.com/google/open-location-code/blob/master/docs/specification.md The former states that every function "should" be implemented and the latter states that some "must" and others "should"...

This is fixed at https://github.com/google/open-location-code/pull/463 All normative notes about function names are moved into the new Open Location Code API Specification.

Regarding tone. Very insulting! And ambiguous!!! > in the voice of an expert who cares more about all the things you are implementing than you do This is meant to...

This issue is fixed (actually, obviated) at https://github.com/google/open-location-code/pull/463

Recommended tag: implementation // specification

I am considering to add to the OLC specification that longitude normalization MUST run in O(1) time. I consider this a security issue.