Skip to content

Merge API recommendations and short code guidance into the specification#597

Merged
drinckes merged 2 commits intomainfrom
doc_merge_490
Dec 6, 2024
Merged

Merge API recommendations and short code guidance into the specification#597
drinckes merged 2 commits intomainfrom
doc_merge_490

Conversation

@drinckes
Copy link
Contributor

Fixes #490 and #432 .

This moves the API recommendations and short code guidance into the specifications document.

(Also a couple minor edits.)

* a method to determine if a string is a valid sequence of Open Location Code characters
* a method to determine if a string is a valid full Open Location Code
* decode and validation methods must not be case-sensitive
Being able to say _WF8Q+WF, Praia_ is significantly easier than remembering and using _796RWF8Q+WF_.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say it's compatible with postal addressing primarily.

Copy link
Contributor

@fulldecent fulldecent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to combine, a move in the right direction

@drinckes
Copy link
Contributor Author

drinckes commented Dec 6, 2024

Thanks all for the feedback!

@drinckes drinckes merged commit 6212a78 into main Dec 6, 2024
@drinckes drinckes deleted the doc_merge_490 branch December 6, 2024 10:15
YoshiRulz added a commit to YoshiRulz/open-location-code that referenced this pull request Jun 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Please move all wiki articles into the repository // MOVE SHORT CODE SPEC

4 participants