Bivouac.com Home Help Index SignUp Login
Master List of Peak Name Documents #3525
Date first written: 2022.01.03 Review Date:2022.01.03Table of Contents
1. List of Documents
2. Types of Document
3. Name Change Situations
1. List of Documents
Below is a master list of all the peak naming documents in bivouac. Every document should be linked to this document.
- Introduction to Mountain Naming Policy
- Naming Principles - Reference Dictionary
Reject self referential names, confusing names, - Properties of a Good Name
A list of properties of good names, as opposed to rules about when to override other websites. Eg: Short, phonetic, single word... - Ridge Names versus Peak Names
This is a specific document giving all the arguments in favor of avoiding using ridge names as peak names. - Guidelines For Geographic Names
Deals with Geographic names - Names of Peaks In the Selkirks - Policy Specification
Written when I was reconcilling bivouac with David Jones Guidebook. In particular, to address the issue of when to make "historical corrections". - Naming Rights
Some people have the idea that only the first ascent person has the right to name peaks. - Title Status Dictionary
- Mountain Naming Policy - Discussion #2
this is a discussion. - Mountain Names Cases
This uses my generalized system to relate Cases to Issues. - Inclusion Rules
This document just describes what peaks should be in the database.
Paste this into each document. See Master List of Peak Name Documents
2. Types of Document
Types of Issue:
Created Names
Desirable properties - Short, pronounceable, Geographic Semantics
(Ridges, Plurals, Ranges)Name Conflicts
With other websites3. Name Change Situations
What I want is a list of example sentences that could describe why something was renamed.
I use the term "good name" to refer to names that have good properties as labels. IE: short, unique, easy to pronounce. This is regardless of usage. Eg: Stair peak is a "good" name, but we wouldn't necessarily favor it over a longer name that was in general use.
- an "acceptable" name is one that meets our basic rules:
Prior Name exists
A guidebook, website or list has a good name that is more established than our name. Or we don't have a name. Or we have only a directional nameHybrid map has adopted bivouac directional name
The google hybrid map has adopted the bivouac directional name, and then a good name appears in some other website. The key question is: how established No Bivouac name
We would adopt the first "Good" name that comes available.Predated provisional name
This is the situation where bivouac has a provisional name, but then we learn that some other website has an acceptable name that is older than the Bivouac name. In this case, we adopt the established name. Retain anything with label on map
Our database should have a peak for any peak that is labelled on the map. (As long as it is
Inclusion rules.