nostr-geotags
v0.7.1
Published
Give an object of geodata, returns standardized nostr geotags
Downloads
128
Maintainers
Readme
nostr-geotags
ATTENTION: Use at your own risk, this is not a widely accepted standard, and there are chances a proposed standard will differ greatly or slightly from this pattern. See NIP-115
Summary
nostr-geotags
is a modern ESM-only package for generating nostr geo tags (['g', ...]
) based on various inputs like latitude, longitude, city, country, etc. It uses iso-3166
and ngeohash
to generate geodata. This package is alpha and the API and response formats will change.
This package was derived from needs in @nostrwatch
, an OpenSats Grant Recipient, and so was made possible by OpenSats.
Installation
The package is available on npm and can be installed using npm, yarn, or pnpm.
npm install nostr-geotags
yarn add nostr-geotags
pnpm add nostr-geotags
Usage
import ngeotags from 'nostr-geotags'
event = {}
event.kind = 1
//created_at, content etc...
event.tags = []
event.tags.push(['t', 'nostrworks'])
const inputData = {
lat: 52.5200,
lon: 13.4050,
city: 'Berlin',
countryCode: 'DE'
};
const options = {
geohash: true,
gps: true,
city: true,
iso31662: true
};
event.tags = [...event.tags, ...ngeotags(inputData, options)];
//sign and verify the event
console.log(event);
Input Reference
The inputData
object can contain:
- lat (number): Latitude
- lon (number): Longitude
- city (string)
- country (string)
- regionName (string)
- countryCode (string)
- Any other key-value pairs
Input Reference
The inputData
object can contain the following properties, used to generate geo-tags:
lat
(number): Latitude coordinate. No default value.lon
(number): Longitude coordinate. No default value.geohash
(string): Geohash coordinate. No default value. Will be ignored if lat & lon are also passed as input as they take precedence.city
(string): Name of the city. No default value.country
(string): Name of the country. No default value.regionName
(string): Name of the region or state. No default value.countryCode
(string):ISO-3166-1:alpha-2
country code. No default value.- Other properties (any): Additionally, key value pairs will be ignored but do not throw an error.
planetName
(string): Name of a planet.
Options Reference
The options
object specifies which types of tags to generate.
ISO options
iso31661
(boolean): Generate ISO 3166-1 tags. Default:true
.iso31662
(boolean): Generate ISO 3166-2 tags. Default:false
.iso31663
(boolean): Generate ISO 3166-3 tags. Default:true
. SeeISO-3166-3 Behaviors
Response Options
Please note: that these will only have an effect on the output if the input for their corresponding values were set. This is especially true for passthrough values. Some of these passthrough values may be deduped if they are not unique against ISO values.
geohash
(boolean): Includes geohash codes fromngeohash
, with diminishing resolution, based on latitude and longitude. Default:true
.city
orcityName
(boolean): Include a tag for the city in response if available. Default:true
.country
(boolean): Include a tag for thecountryCode
andcountryName
in response if available. Default:true
.countryCode
(boolean): Include a tag for thecountryCode
in response if available. Default:true
.countryName
(boolean): Include a tag for thecountryName
in response if available. Default:true
.region
(boolean): Include a tag for theregionCode
andregionName
in response if available. Default:true
.regionCode
(boolean): Include a tag for theregionCode
in response if available. Default:true
.regionName
(boolean): Include a tag for theregionName
in response if available. Default:true
.gps
(boolean): Include latitude and longitude as a 'dd' tag (de-factor GPS standards) and separate tags for lat and lon with diminishing resolution. Default:false
.planet
orplanetName
(boolean): Include a tag for theplanetName
in response if available. Default:false
.
Response Reference
The function returns an array of tuples, where each tuple represents a tag and its associated data. The format of the tuples is based on NIP-01
.
- The first element (
'g'
) is a constant indicating the type of tag. - The second element is the
value
of the tag, which can vary based on the input and options used. - The third element is the
key
of the tag. - The fourth element (optional) is the
standard
, which is serialized with a:
where when splitstandard[0]
is the the standard's identified andstandard[1]
is the standard's value. This field is only used for ISO.
Determining tag usage
Which tags you use depend on use-case. If your concerns are namely geospacial, using only geohashes likely suffice, if your concerns around around borders, languages or laws, ISO-3166-3
may suffice. If your concerns are mixed, a combination of standards will suffice. In most cases the defaults are good, and most likely won't need to be changed unless you are optimizing your tags array.
Tag Types and Their Descriptions
GPS:
[ 'g', '<latitude>, <longitude>', 'dd' ]
,[ 'g', '<latitude>', 'lat' ]
and[ l', '<longitude>', 'lon' ]
- Coordinates of diminishing resolution from the input latitude and longitude. One of each of these tags are passthrough, but the rest are progressively reduced in their precision until the final decimal point. If an integer is provided for one or both
lat
andlon
, an integer is returned.
- Coordinates of diminishing resolution from the input latitude and longitude. One of each of these tags are passthrough, but the rest are progressively reduced in their precision until the final decimal point. If an integer is provided for one or both
Geohash:
[ g', '<geohash>']
(NIP-52
)- Geohashes of diminishing resolution from the input latitude and longitude. These are not passthrough; they are computed using the
ngeohash
library.
- Geohashes of diminishing resolution from the input latitude and longitude. These are not passthrough; they are computed using the
ISO-3166-1 Codes:
- These tags represent country information derived from the
iso-3166
library and are based on the providedcountryCode
input value. They are not passthrough. - Examples
isoAsNamespace==false [default]
- Alpha-2 code:
[ 'l', 'HU', 'ISO-3166-1' ]
- Alpha-3 code:
[ 'l', 'HUN', 'ISO-3166-1']
- Numeric code:
[ 'l', '348', 'ISO-3166-1']
- Alpha-2 code:
- These tags represent country information derived from the
ISO-3166-2 Codes:
- These tags represent region information derived from the
iso-3166
library and are based on thecountryCode
andregionCode
input values. They are not passthrough values.
- These tags represent region information derived from the
ISO-3166-3 Codes:
- These tags also represent country information, but focus on historical changes in country codes. They are not passthrough.
- Examples mirror the ISO-3166-1 format but relate to updated country codes.
City:
[ 'g', 'Budapest', 'cityName' ]
- A passthrough from the input city name.
Planet:
[ 'g', 'Earth', 'planetName' ]
- A passthrough, assuming Earth as the default planet in the absence of specific planetary data.
ISO-3166-3 Behaviors
When iso31663
is enabled, it will affect the response contents. Any ISO-3166-3
code found for a given ISO-3166-1
countryCode
that is not a duplicate of it's ISO-3166-1
counterpart, will be appended to the tags array. Here's an example:
[ [ 'L', 'ISO-3166-1' ], [ 'g', 'AI', 'ISO-3166-1'], [ 'g', 'AIA', 'ISO-3166-1' ], [ 'g', '660', 'ISO-3166-1'], [ 'G', 'ISO-3166-3' ], [ 'g', 'DJ', 'ISO-3166-3' ], [ 'G', 'countryName' ], [ 'g', 'Anguilla', 'countryName' ] ]
Here two alpha2
codes are returned, the original ISO-3166-1
code, and the changed ISO-3166-3
code. Since the other ISO-3166-3
properties for AI
are the same as their ISO-3166-1
counter-parts, they are not included.
Example Response
Here is the default response when lat
, lon
, countryCode
, regionName
, and planet
are provided, with everything else default
[ 'l', 'u2mwdd8q4' ],
[ 'l', 'u2mwdd8q' ],
[ 'l', 'u2mwdd8' ],
[ 'l', 'u2mwdd' ],
[ 'l', 'u2mwd' ],
[ 'l', 'u2mw' ],
[ 'l', 'u2m' ],
[ 'l', 'u2' ],
[ 'l', 'u' ],
[ 'L', 'ISO-3166-1' ],
[ 'l', 'HU', 'ISO-3166-1' ],
[ 'l', 'HUN', 'ISO-3166-1' ],
[ 'l', '348', 'ISO-3166-1' ],
[ 'L', 'countryName' ],
[ 'l', 'Hungary', 'countryName' ],
[ 'L', 'cityName' ],
[ 'l', 'Budapest', 'cityName' ]
This is a response with all options enabled (deduped, dedupe: true
)
[ 'l', 'u2mwdd8q4' ],
[ 'l', 'u2mwdd8q' ],
[ 'l', 'u2mwdd8' ],
[ 'l', 'u2mwdd' ],
[ 'l', 'u2mwd' ],
[ 'l', 'u2mw' ],
[ 'l', 'u2m' ],
[ 'l', 'u2' ],
[ 'l', 'u' ],
[ 'l', '47.5636, 19.0947', 'dd' ],
[ 'L', 'geo.lat' ],
[ 'l', '47.5636', 'geo.lat' ],
[ 'l', '47.563', 'geo.lat' ],
[ 'l', '47.56', 'geo.lat' ],
[ 'l', '47.5', 'geo.lat' ],
[ 'L', 'geo.lon' ],
[ 'l', '19.0947', 'geo.lon' ],
[ 'l', '19.094', 'geo.lon' ],
[ 'l', '19.09', 'geo.lon' ],
[ 'l', '19', 'geo.lon' ],
[ 'L', 'ISO-3166-1' ],
[ 'l', 'HU', 'ISO-3166-1' ],
[ 'l', 'HUN', 'ISO-3166-1' ],
[ 'l', '348', 'ISO-3166-1' ],
[ 'L', 'countryName' ],
[ 'l', 'Hungary', 'countryName' ],
[ 'L', 'ISO-3166-2' ],
[ 'l', 'HU-BU', 'ISO-3166-2' ],
[ 'L', 'cityName' ],
[ 'l', 'Budapest', 'cityName' ],
[ 'L', 'planetName' ],
[ 'l', 'Earth', 'planetName' ]
Development
To build the package, run:
npm run build
To run tests:
npm test