Bivouac.com   Home     Help   Index   SignUp   Login
Prominence Editors Guide #3325
    Date first written: 2013.10.24   Review Date:2023.11.21

Table of Contents
1. Preface
2. Introduction
3. Reports and Tools
4. Rules for Tough cases
5. The Divide Method
6. Adding New Peaks
7. Summary of Rules
8. Summary of Tools and Techniques
9. Project Status (2014.04.06)

1. Preface
This is a summary guide mostly intended for the handful of people who are working to fix up the mountain database. Typical problems include missing line parents, peaks where saddle latlong is not filled in, missing height sources, wrong locations, missing peaks, etc. Many of these fixups are simple, but on some of them, you run into issues. My objective here is to make a list of the resources and methods for solving tough prominence cases. Many of those documents mentioned were previously written, but this puts them all in one place. For example, the document listing Prominence Theorems has been around for years, but is listed here in case you forgot about it. I keep updating these documents as people ask questions.

As of 2014, it has proven to be a bigger job than I thought to get all the data up to standards. We have about 5 people working on it. We'd like to get a couple more people working on this project. In order for someone to work on this stuff, someone has to spend quite an effort to explain things to the new person. So for this reason, it can't just be a free-for-all where every member is fixing things. However, if you've been a bivouac member for a couple of years, and have a pretty good understanding of prominence concepts, and want to invest countless hours of your time in working on this stuff, then we could sure use your help. Email Robin Tivy, and I'll come up with some fixup projects you might be interested in.

2. Introduction
In 2005 we updated most of the mountain records in bivouac so they had prominence data. However, since then new mapping features have been added to bivouac that allow us to spot errors. In particular, we can now plot the location of the key saddles of every peak, and these maps immediately bring to light numerous errors. To see this, go to any mountain page, and click "GMapForm". By default, this brings up a topo map which plots the peaks and the saddles. So you can immediately see errors.

Looking at maps is one way to find errors, but the system also has various reports that look through the mountain records for missing or non-standard data. These "exception" reports are launched by clicking the "AreaMgmt" (Area Management) link on any "area page". For example, look up "Vancouver Island", and then click on it's AreaMgmt link. This shows you an "Area Management Menu". Most of the links on this menu are problem reports. The one I always look at first is "Check Line Parents".

Fixing the problems is often pretty easy, but in some cases, can involve detailed analysis. This "Prominence Editors" guide is all about tools and methods for tackling the tough cases. I'm assuming you already know the basic concept of prominence.

3. Reports and Tools
Below is a list of various utilities and reports that you can use to fix up mountain data.

  1. AreaMgmt Link
     If you are a prominence editor, you will see a link on every "area page" called "AreaMgmt" (Area Management). For example, look up "Vancouver Island". This link has a menu with various utilities to report problems with the mountains within that area. For example, the "NullSaddles" report lists all the mountains in a given area that do not have the SaddleLatLong field filled in.

  2. LMap Form (and GMap Form)
     Use "GMap Form" and turn on the "Saddles" option, and turn off roads, etc. The saddles show up as small orange rectangles. Notice that the saddles are labelled with the names of the peaks to which they belong. This report is the quickest way to inspect data. Note: If you are fixing up heights of peaks, sometimes you can't see the spot height because the bivouac label blots it out. Eg: Duffys Peak in Washington. To get around this problem, use the regular GMap link when checking heights, since the labels on it have a transparent background.

  3. LMapForm MinHeight field
     Use this field when looking for distant line parents. Put in a height just below the height of the mountain you are checking. This allows you to find distant line parents from the maps. You just specify that the minimum height is the height of the peak you are investigating, and the map will only show higher peaks.

    For example, I used the feature to check the LineParent of Wedge Mountain. I went to Wedge Mountain, with height of 2892m. So I started up GMap Form, and filled in the radius=100 and MinHeight=2892, and I turned off the key saddles, to avoid clutter. Then I zoomed out to the 10 km radius. Right away I could see the distant candidates. I know it isn't Whitecap or Skihist, because both would involve crossing the Lillooet River. So as we know, the Line Parent must be in that group of peaks at the head of the Lillooet River. The prominence walk goes across the pass at Whistler, then across the pemberton Icefield, then across the pass at the head of the Elaho and then up onto the lillooet Icecap. Before today, the database had Stanley Peak as the parent. But with the new map, I'd say that isn't the parent. because before you get there, you go thru Dalgleish and Mount Lillooet and Tisiphone. Not only are they first, they are also more prominent than Stanley Peak. So I fixed the database. I picked Dalgleish as the line parent of Wedge, although Lillooet might be a more recognizable choice, since it is more prominent.

  4. Search by Mountain ID (in main search)
     You can now search directly for any mountain by typing its ID into the main search box on the front page. For example, type in "2122" and you see Lillooet Mountain. I use it every day, when someone sends me trouble tickets containing a mountain Id.

  5. Record Search
     Sometimes you come across a title of a record on a report or a map, but you can't display the record because it contains an error. For example, Glenn saw a peak on Gmap that had a title of "null". Normally, you could fix errors by going to the mountain page, then pushing the "Upd" link. But because of the error, the mountain page would not display. He can see the ID of the mountain,but he can't edit it.

    The record search function in the Index gives you a means of going directly to an update link without ever displaying the mountain page itself. Just type the ID into the "record search" function, and set the mode to "Title Only". This will bring up the name of the mountain and an update link:


      null [update]
    Once you have the update form, then you can fix the problem.

4. Rules for Tough cases
In this chapter, I'm assuming you have already used the TRIM and GMapForm maps and have fixed some easy ones. But now you have run into some of the tough cases.

See the later document Prominence Walk Rules

  1. Prominence Theorems
     The first document to look at is Prominence Theorems. For example, a really common error you may find is where there are two mountains trying to share the same key saddle. The theorems tell you that one of them is wrong.

  2. Changing the line parent
     There are many cases where the line parent should be a closer peak. Eg: The line parent is some large distant peak, but now there are several closer peaks in the database. This happens because more peaks were added to the database since the original line parents were designated. Such situations should be corrected.

  3. New peaks for Line Parents
     There are cases where the sensible thing is to add a couple of new peaks, to make things simpler. The "line parent" concept exists to make it easy to verify key saddles. It should be the first significant "higher ground" on the far side of the key saddle. There are some definite cases where you MUST add an intermediate peak, because without it, the distant line parent is not correct. This is the case if there is a saddle lower than the key saddle between a peak and the designated line parent. In other words, you must add the bump if there is a saddle beyond it that is lower than the key saddle of a peak. This case and others are dealt with in When to Add Peaks.

  4. Duplicate Heights (Designated Heights)
     Another problem we've run into is cases where there are several peaks or saddles all the same nominal height. This happened in a couple of cases in Alberta, where the heights were estimated from contour lines, because there are no spot heights. In this case it is desirable to artificially tweak some of the heights so we get one consistent database. See Handing Peaks and Saddles of Similar Heights.

  5. Two Possible Line Parents
     Once you get on the far side of the key saddle, there are sometimes cases where you could pick either of two peaks as the line parent. In general, we pick the one with the highest route AFTER the key saddle. In other words, the one with the highest "subsequent saddle".

    Eg: Near Mount Priesley there is a peak called Fugora Peak at 55.179603,-128.927135. It's key saddle is just north, at 55.189551,-128.928938, but beyond there either Priesley itself could be the Line Parent, or Priesley W4. We pick Priesley W4 because it is closest. This rule has the advantage that if Priesley W4 ever was named, then Fugora would take it as a namesake, rather than the more distant Priesley.

    If the "subsequent" saddles were also identical heights, then we would choose the closest peak.

5. The Divide Method
The most effective way to solve distant prominences is to chart the long ridge (the divide) that leads to the suspected line parent. In the Yukon, the suspected line parent may be several hundred km away.

The method I've been using for these is to first of all use GMap Form to find the possible line parents that are already in the system. (Put in a minimum height of the target peak). Once you've picked the direction you are going to go with your "prominence walk", then use the GMap "Draw and Save" feature to plot the ridge line between the peaks. At first, you plot it at an overview scale, just making sure you go around the big rivers. Then you zoom in on your existing line to look for saddle heights.

When you zoom, you usually have to add dozens of new points to your line to make it go around the detailed streams. To see good contour labels, I use the "t5 - Canada Topo display. You need to zoom in to 200m to see the detailed contours. Zoom in till 200m shows in the scale bar in the lower right corner.

Sometimes there are dozens of high prominence, uncharted peaks on the way to the original line parent. In this case, I stick them into the database, give them temporary names, and thus take care of the original peak. But then you have to repeat the process for the new peak you just added.

Note: In the above method, you add as few peaks as possible. The only one essential to add is the first one higher than the original peak, and of sufficient prominence, so you are sure it is not just a low prominence bump on the way to a higher peak. In other words, at least a P500.

6. Adding New Peaks
Sometimes it is necessary to add new peaks, just to solve the prominence of an existing peak. Other times, your goal is to fill in an entire area. Before adding peaks be sure and check Inclusion Rules for Mountains.

In which case, give the new peaks a "temporary" name. Interpolate the height from the contours if there is no spot height. Our standard is to always interpolate half way between the contour interval. Eg: If the contour interval is 100 foot, we interpolate to the nearest 50 foot.Same thing with saddles.

Height units should match source
 The units in the underlying database for peak heights should match the units of the map. For example, if a height was obtained by interpolating imperial contour lines, such as 11,050 feet, then we enter the height as "11050 feet", and let the mountain page translate it to meters. The reason for this is so you immediately know that the source of the height was one of the imperial maps.

If your goal is to chart missing peaks, as opposed to solving the prominence for a distant peak, then it is good to have a rough idea of how many peaks you are going to put in.

In remote areas such as the Yukon, just pick the highest peak in each cluster, and at least 10 km apart. This means that a convenient "group" size with 9 peaks would be 30 km by 30 km, or 900 sq km. Therefore something like the Whitemantle range is a good size.

7. Summary of Rules
Below is a description of the ideal rules that would be followed for any data you are correcting.

  1. Use the standard map
     In BC, all mountain heights and locations come from the BC Basemap TRIM maps, not the older 1:50K maps. In all other Canadian provinces, there is no equivalent of TRIM data, so we use the NTS maps. Where possible, we use the imperial version of the 1:50K map. In the USA, the rule is to use the spot height printed on USGS maps, except in very special cases like Mount McKinley where a newer official height is available.

  2. Use Source Units
     In order to quickly verify peak heights and saddle heights on the map, you should input the units in the same units as the map that was the source. For example, if the source map was in feet, then put the number in as feet. For example, if you go into the mountain record for Mount Willingdon, you will see the height string is "11066 feet", matching the spot height off the old imperial map. Note it is not in meters, although the primary display on the mountain page is translated to meters.

    At present, the majority of heights do NOT use the source units, but instead were translated to meters. We don't currently have any project to systematically change all of these, but if you are working on a given mountain for any other reason, then you should upgrade to following the new standard. Eg: If you are adjusting the prominence, quote the height of the saddle in the units of the map used as its source.

  3. Always Interpolate heights
     For all peak and saddle heights estimated from contour lines, we interpolate by adding 1/2 of the contour interval to the highest contour. For example, on a typical peak on a 100 foot contour map, whose highest contour is 11,100 feet, we would say the height is 11,150 feet.

  4. Fill Saddle Lat-Long
     Always fill in the saddle lat-long, but usually there is no name for the saddle. See help notes on this field.

8. Summary of Tools and Techniques
When working on prominences use GMap Form, and turn on saddles. The saddles then show up as orange rectangles with the heights.

Often with a new peak on a ridge, you need to figure out which direction to go. Eg: Imagine a new peak of elevation 2500m, and with the only higher peaks 20 km away, one to the north and one to the south. To determine which direction the "prominence walk" goes, you need to find the lowest saddle in each direction. (Use a piece of paper). Eg: Suppose you find the lowest saddle is 10 km south at 2000m, and the lowest to the north is 2100m. So the prominence goes north, with the key saddle being the 2100m saddle.

Often it is not obvious where the lowest saddle is. So you go south and make notes as to the elevation of each possible saddle. Eg: you start out finding a 2300m saddle, but then as you continue further south, you find a lower one at 2200m. From then on you are only interested if you find a saddle lower than 2200m.

What I do in really long cases is use a piece of paper.

When tackling a new area, I often put in the peaks in clusters of 8 or 10 peaks without figuring out the prominences, just to get the markers onto Gmap. Then I fill in the prominence info in the easiest peaks first.

9. Project Status (2014.04.06)
This is an inventory report. It lists the situation, province by province as of 2014.04.03. My status reports are based partially on random investigations of the maps, and partially on the "Area Management" reports (AreaMgmt link on the area page). First, I'll give an overview, and then discuss each area.

What we want are people to work on the most important problems. As opposed to picking some obscure area, and putting in hundreds of low prominence peaks. The problem is that all data needs to be checked and maintained, so right now, I think we should concentrate all available effort on fixing the important areas.

BC and Alberta are the most important areas of all. Fortunately, they are also the most complete areas of the entire database. Next most important are Yukon, and bordering US states like Alaska and Washington. And then the Maritimes and Newfoundland. In all other areas, such as California, Arizona, etc. all we want are the high prominence peaks.

How complete are we? In BC and Alberta, I'd say we have charted almost every P1000 peak. I'd be surprised if anybody could find any more than 2 or 3 new P1000 peaks in BC/Alberta, even working for months. Furthermore, I'd say we have 99% of the P500 peaks charted, and I'd be surprised if anybody could find more than a couple dozen, lurking in remote areas. Both BC and Alberta have thousands of minor peaks (below 500m prominence) charted, and in most populated areas, every peak over P300 is charted.

The Yukon and Alaska, are less complete. In the Yukon, there are vast areas where no peaks are charted. In working on a couple of these areas, I easily came up with 3 or 4 missing P1000 peaks, and could find dozens of missing P500 peaks.

Our goal in the remote areas is just to be reasonably complete as far as P500 peaks. We don't want to chart thousands of unnamed peaks with prominences less than 300m.

  1. Province of British Columbia
     As I outlined above, I'd say most of the peaks in BC are charted. The source of heights is the TRIM data, not the NTS. The big job now is to correct mistakes, and fix null saddles. There were initially several thousand problems and several of us worked away at it. Currently you can see in "New Infrastructure" that Glenn Woodsworth is working away on BC every day. As of today, the list of null saddles has been whittled down to 414 peaks, and probably if you look right now, that number is even smaller.

    540 Peaks with non-precise positions
      593 Peaks with null height source
      693 Peaks with height not trim

    414 Null Saddles

  2. Alberta
     Alberta is probably the most complete of all. I'd say every P1000 peak is charted, and probably almost every P500. Furthermore, there are no null saddles, thanks to Walker McBride. However in random samples, I've definitely run into really well used areas where the prominence data is not correct. Wrong line parents, and a few missing peaks.

  3. Yukon
     As of 2014 April, the Yukon is only partially charted. There are hundreds of missing P500 peaks and we are probably yet to discover several dozen P1000 peaks. The AreaMgmt utilities show there are currently 9999 peaks with no line parent, prominence or saddles. In 2014 March, I picked several peaks at random to try and fix them. Each one turned out to be a multi-day fixup job, since the line parent was often hundreds of kilometers away.

    The method I was using to find the saddles is to chart the divide toward what looked like a distant line parent, and then refine the divide and make notes of the likely lowest points on the ridge. The length of these "prominence walks" were often several hundred kilometers. In the process I'd find dozens of P500 peaks and usually a few P1000 peaks, all unnamed and uncharted. Unfortunately, the best map for this is the GMap Topo Canada display, but it is very slow to refresh at the detail level, often taking 50-60 seconds to update the tiles on the map. It took too long, so temporarily, I quit working on Yukon. I hope the government server improves its response time, or we find some other method.

  4. Alaska
     The AreaMgmt report shows 27 peaks that have missing or wrong line parents. And 26 peaks that have null saddles. However, I suspect that there are parts of Alaska where we are missing hundreds of P500 peaks, similar to the Yukon.

  5. Maritimes
     (Nova Scotia, New Brunswick, PEI) As you can see from New Infrastructure, Fred Touche has been working away on these areas. The peaks in the Maritimes are very low. Nova Scotia has only one P500 peak! Our goal in Nova Scotia is to chart peaks down to P100, especially ones that are hiking destinations. There are a huge number of sub 100 peaks charted, these were done for convenience in solving some of the more important peaks. I was reading about a hike in Cape Breton the other day, and discovered the peak is not in the database. New Brunswick still has 3 or 4 wrong line parents.

  6. Newfoundland
     A quick inspection using AreaMgmt shows there are 101 missing line parents and 97 null saddles. So Newfoundland is a sizable fixup project.

  7. Labrador
     There are 10 line parent problems, and 11 null saddles. Several years ago Fred Touche did quite a job charting these peaks, and I would guess most are charted. I did a random sample of fixing one of the peaks on the null saddle list "Gnat Peak". It was easy to find the line parent and saddle using GMap. So I filled those in. I found that the position was a bit off, there was no height source given, etc, which I fixed. So based on that one example, I'd say that someone could probably bring Labrador up to standards just by working away at it. Around Gnat Peak, I did a quick scan of the map looking for uncharted peaks. I easily found an 1120 foot peak, with a probable prominence of 300 meters. But that isn't big enough to worry about in a remote area like Labrador. In Labrador, all we want are the P500 peaks.

  8. Washington
     Washington state is important because it borders on BC, and hundreds of Bivouac members do trips down there. I'd say we've got most of the major peaks charted, but very few saddle lat-longs are charted. Also the heights should be in feet to match the available USGS maps, not meters. I find the USGS maps are more difficult to work with than the Canadian 1:50K. When I run AreaMgmt reports, I see 30 line parent problems and 138 null saddles. In March, I talked to Wayne Weber and he said he'd work away at them. However, I think it will be a big job.

  9. Colorado Rockies
     (This includes peaks in Colorado, Wyoming, New Mexico, Utah) As of 2014.04.06, this area is almost completely fixed up by Richard Wilson. Null saddles is now 0, line parent mistakes=0, Height sources are all done. He must have stayed up all night, because only 2 days before, there were 42 line parent mistakes and 116 null saddles. I think all the major peaks are charted. In May 2012, I did quite a bit of work with Peter Chinigo reconciling some of the Colorado peaks. That was the project that inspired the database change where we could record peak heights in native units. (So you could work in feet).

  10. Arizona, California
     These are under control for now. We have the high prominence peaks charted, and it is more important to fix areas like Washington or Alaska than to fill in hundreds of low prominence peaks in these areas.