#462 <https://github.com/google/open-location-code/issues/462> should then be closed.
Semi-related, there are lots of other issues and PR that need to be dealt with one way or the other (for example, there has been a PR for this exact issue open for more than half a year by now). It would be great to see some activity in that space. On Monday, June 27, 2022 at 8:43:32 PM UTC+2 phi...@google.com wrote: > Hi Plus Codes Community, > > We updated our documentation to clarify an inconsistency on Plus Code > shortening (issue > <https://github.com/google/open-location-code/issues/462>). API.txt > previously stated that up to a maximum of eight digits could be removed > resulting in a valid plus code, but this should actually be six. This has > been updated as of PR #489 > <https://github.com/google/open-location-code/pull/489>. > > As a sidenote, shorting codes to four digits before the plus and two-four > digits after is the most common choice by addressing authorities around the > world and by consumer products when shorting Plus Codes with locality. > > Sorry for the confusion on this. > > Thanks, > > Phebe > > -- Public site: http://www.openlocationcode.com/ Github project: https://github.com/google/open-location-code Demo site: http://plus.codes/ --- You received this message because you are subscribed to the Google Groups "Plus Codes Community Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-location-code+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/open-location-code/df4cafaf-45bf-4cf1-9dcf-bfd971cfdc88n%40googlegroups.com.
