NIP-G0 for Geospatial Tagging Standardization #1642
Conversation
Introduction of NIP to standardize event geospatial tagging for location of event origin and location area of event relevance, with both being hierarchical, offering flexibility for users and systems to filter and improve content relevance to user interest when proximity, politics and geography matters.
swbratcher
changed the title
|
Yet to implement. Would love for a couple of press/news npubs to tag using the this approach and for utxo the webmaster 🧑💻 to build a customizable feed that uses it, where followers/subscribers could customize based on their geopolitical location interests. |
| ### 1. `geo_loc` [optional, repeatable] The geo-location of the event. | ||
| Represents the event’s origin location. Each tag specifies a geographic or political level. Multiple tags may be used to define a hierarchy. This structure may be quite flexible in eventual usage, but by predefining a base set, client usage benefits from establishing early consistency: | ||
| - `"location"`: (optional) Precise point as GPS long,lat coordinates. | ||
| - `"w3w"`: (optional) Precise point on earth using [what3words](https://en.wikipedia.org/wiki/What3words). |
There was a problem hiding this comment.
Closed source system. And we already have GPS coordinates, why have this?
There was a problem hiding this comment.
Optional usage within the NIP standardization. Not pushing it, just allowing it with the flexibility of the NIP-G0 standard. Some useful systems utilize w3w and this would accommodate that usage without impact to gps usage. Could even use in tandem to gps for compatibility.
| Represents the event’s origin location. Each tag specifies a geographic or political level. Multiple tags may be used to define a hierarchy. This structure may be quite flexible in eventual usage, but by predefining a base set, client usage benefits from establishing early consistency: | ||
| - `"location"`: (optional) Precise point as GPS long,lat coordinates. | ||
| - `"w3w"`: (optional) Precise point on earth using [what3words](https://en.wikipedia.org/wiki/What3words). | ||
| - `"g"`: (optional) Precise point as a [geohash](https://en.wikipedia.org/wiki/Geohash) as in [NIP-52](52.md). |
There was a problem hiding this comment.
Multiple ways of doing the same thing? Why?
There was a problem hiding this comment.
Optional and varied approaches depending on the systems posting and the systems consuming. Useful flexibility within the structured geographical association of content by the NIP-G0.
There was a problem hiding this comment.
Additional thought: The other way is to not allow for multiple systems to be compatible and restrict to GPS. Redundancy allowance seems more resiliant to allow for lack of government-controlled GPS access, or desire for only open source by a user, or proprietary system use for those users who find that more useful. Limiting to GPS may still allow w3w conversion by the w3w api and geohash generation on the client side, but open acceptance of any currently prominent method of location identification by the NIP-G0 standardization would potentially future-proof functionality in a freedom-tech environment.
| - `"dist"`: (optional,repeatable) Ward, Neighborhood or sub-municipal area. | ||
| - `"muni"`: (optional,repeatable) Specified municipality, city, town, etc. | ||
| - `"metro"`: (optional,repeatable) Metropolitan area that is multi-municipal in context. | ||
| - `"county"`: (optional,repeatable) County or similar administrative division of a state or province. | ||
| - `"reg"`: (optional,repeatable) Region named or general, non-state, non-province. | ||
| - `"canton"`: (optional,repeatable) Canton or similar administrative division of a nation. | ||
| - `"state"`: (optional,repeatable) State specified. | ||
| - `"prov"`: (optional,repeatable) Province specified. | ||
| - `"nat"`: (optional,repeatable) National context. | ||
| - `"cont"`: (optional,repeatable) Continental context. |
There was a problem hiding this comment.
Where's the standard for these naming schemes?
There was a problem hiding this comment.
Multiple references to arrive at a short, generic, type-comprehensive, global-friendly list in english:
https://en.wikipedia.org/wiki/Geographic_levels
https://en.wikipedia.org/wiki/Category:Types_of_geographical_division
https://en.wikipedia.org/wiki/List_of_administrative_divisions_by_country
https://en.wikipedia.org/wiki/List_of_political_and_geographic_subdivisions_by_total_area_(all)
https://wikitravel.org/en/Wikitravel:Geographical_hierarchy
Introduction of NIP to standardize event geospatial tagging for location of event origin and location area of event relevance, with both being hierarchical, offering flexibility for users and systems to filter and improve content relevance to user interest when proximity, politics and geography matters.