climbing-nip.md

Climbing Wiki NIP-XX

Climbing related events for information and tracking climb

draft optional

This NIP describes a new set of events specifically for publishing climbing related content on NOSTR in order to create a fully decentralized knowledge base of all climbing information. Functionality is similar to Mountain Project or 8a.nu

The existing solutions own all user generated content, which is a vital piece of the climbing community. By bringing this information to NOSTR, we can ensure that all of the this info will be available for free forever.

Area

Areas will use kind 30820

Areas build on [[NIP-54]], adding some specific metadata that is relevant to climbing clients.

Areas MUST specify a tag ['g', '9xj5hm1qyjyj'] the geohash of the area with as much precision as necessary.

Areas must specify a d tag which will be the normalized version of the title as specified in [[NIP-54]], with the addition of the geohash.

{
	"kind": 30820,
	"content": "Markdown content with [[Wiki Links]]",
	"tags": [
		['title', 'Eldorado Canyon State Park'],
		['g', '9xj5hm1qyjyj']
		['d', 'eldorado-canyon-state-park-9xj5hm1qyjyj']
	]
}

Route

Routes will use kind 30821

Route are very similar to areas, however there is more metadata captured in tags

Routes must also include the geohash in their titles

Route Tags:

type: boulder, sport, trad, tr, ice, alpine (more than one can be present)
pitches: number
grade: '5.10, V0, 8a, etc...' # Clients will determine grade conversions
fa: string # Info about first ascensionist
length: number (in meters)

{
	"kind": 30821,
	"content": "Markdown content with [[Wiki Links]]",
	"tags": [
		['title', 'Not My Cross To Bear'],
		['g', '9wsrm893bx20'],
		['d', 'not-my-cross-to-bear-9wsrm893bx20']
	]
}

Curation Sets

It is often helpful to have a lot of routes grouped together in a specific order (e.g. L -> R) to help climbers navigate through areas. While Areas and Routes themselves have no specific relation, user can generate a curated set which can include both areas and routes.

Curation sets can be whatever the user the user wants to curate. e.g. it could be a curation set for an area (1 area -> many routes in left to right order), or it could be the best boulders to hit in Colorado (1 area (Colorado), many routes in order of best to worst)

{
	"kind": 30020,
	"content": "",
	"tags": [
	]
}

Tick Lists

Could just be curation sets?