NIP-3166: Geo-location tag #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft NIP for introducing a new geo-location tag that can be added to any event. The tag makes use of the ISO-3166 standard country codes and would allow easier filtering and indexing of events based on their geographic location.
It differs from the current
gtag presented in NIP-52 in that it is much less granular than a geohash, which is not ideal for indexing.The same difference is true for the proposed Geospatial Types NIP-44.
Possibly a third parameter could be added (eg:
["g", "<ISO-3166 code>", "country"]), in conjunction to the existinggtag, as presented in NIP-66 to support multiplegtag types. But I'm not sure that's preferable for indexing.Open to feedback!