Wikidata:Property proposal/PeakVisor ID

PeakVisor peak ID

Originally proposed at Wikidata:Property proposal/Place

   Done: PeakVisor peak ID (P9568) (Talk and documentation)

Description	identifier for a mountain or hill in PeakVisor
Represents	PeakVisor (Q106303028)
Data type	External identifier
Domain	item; mountain (Q8502), stratovolcano (Q169358), or hill (Q54050)
Allowed values	[a-z0-9\-]+
Example 1	Mount Rainier (Q194057) → mount-rainier
Example 2	Haute Cime (Q3128532) → haute-cime
Example 3	K2 (Q43512) → k2
Example 4	Mount Kilimanjaro (Q7296) → kilimanjaro
Example 5	Oregon Hill (Q34828319) → oregon-hill-united-states
Example 6	Balmhorn (Q15294) → balmhorn
Example 7	Mont Blanc (Q583) → mont-blanc-monte-bianco
Example 8	Königstein (Q1796472) → koenigstein
Source	https://peakvisor.com/panorama.html
Planned use	will add to items for peaks in the Pacific Northwest
Expected completeness	eventually complete (Q21873974)
Formatter URL	https://peakvisor.com/peak/$1.html
See also	Peakbagger mountain ID (P3109), Bivouac.com mountain ID (P3507), SummitPost ID (P3309), peakware mountain ID (P3513), crdb peak ID (P3770), LoJ peak ID (P3907), proposals PeakVisor range ID, PeakVisor area ID, PeakVisor park ID
Applicable "stated in"-value	PeakVisor (Q106303028)

Motivation

PeakVisor is another website that provides information about the mountains (and hills) of the world. Entries include information about elevation, coordinates, nearest higher neighbor, jurisdiction located in, mountain range located in, park located in, photographs, and a digital terrain model which labels all the peaks around. It also links to Wikipedia articles for mountains that have entries in Wikipedia. UWashPrincipalCataloger (talk) 19:41, 31 March 2021 (UTC)

Discussion

•  Question Is there a specific reason you proposed four different PeakVisor properties? Could we use just one? --Emu (talk) 23:26, 31 March 2021 (UTC)
•  Question I have the same question as Emu. I see that the formatter URL's are different, as are the domains. Is there a way to consolidate these four properties despite those differences? --Crystal Clements, University of Washington Libraries (talk) 00:45, 1 April 2021 (UTC)
• @Emu, Clements.UWLib: I modeled these proposals on what was done with Peakbagger, which has Peakbagger mountain ID (P3109), Peakbagger area ID (P3635), Peakbagger climber ID (P7278), and Peakbagger key col ID (P7279), all of which have numeric identifiers and different formatter URLs. It would be possible to have one PeakVisor ID by using just https://peakvisor.com/$1.html as the formatter, and then having IDs like peak/mount-rainier, range/cascade-range, adm/pierce-county-washington, and park/mount-rainier-national-park, but then the specific entity would not be part of the property itself. If the community thinks this is better, I can revise one proposal and withdraw the others. UWashPrincipalCataloger (talk) 02:05, 1 April 2021 (UTC)
•  Support. I guess we can have only one property for all things considered. Thierry Caro (talk) 01:18, 2 April 2021 (UTC)
•  Support, an important property for peaks.--Arbnos (talk) 15:14, 13 April 2021 (UTC)

@UWashPrincipalCataloger, Emu, Clements.UWLib, Thierry Caro, Arbnos:  Done Now PeakVisor peak ID (P9568). --Lymantria (talk) 20:42, 14 May 2021 (UTC)