Colorado LiDAR Findings

Colorado peak questions, condition requests and other info.
Forum rules
  • This is a mountaineering forum, so please keep your posts on-topic. Posts do not all have to be related to the 14ers but should at least be mountaineering-related.
  • Personal attacks and confrontational behavior will result in removal from the forum at the discretion of the administrators.
  • Do not use this forum to advertise, sell photos or other products or promote a commercial website.
  • Posts will be removed at the discretion of the site administrator or moderator(s), including: Troll posts, posts pushing political views or religious beliefs, and posts with the purpose of instigating conflict within the forum.
    For more details, please see the Terms of Use you agreed to when joining the forum.
User avatar
bdloftin77
Posts: 1429
Joined: 9/23/2013
14ers: 58  1 
13ers: 99
Trip Reports (2)
 

Re: Colorado LiDAR Findings

Post by bdloftin77 »

Boggy B wrote: Wed Sep 20, 2023 12:15 pm TL;DR

How do we classify named summits where the highpoint and the named point are in different places?

Take ranked Middle Peak - the coordinates given on the BGN page match the point labeled "13261" (USGS) at the northwest end of the ridge, but the 14ers/LoJ pin is at the ranked highpoint further along the ridge towards the Dolores saddle.

Then we have unranked Thunder Mountain - the pin is at the same location as the officially named point. However, slightly upridge to the west there is a higher point--which if I recall though still unranked turned out to be fairly prominent--before the Greylock saddle is reached.

With unranked King Solomon, the map label appears to designate the entire ridge/massif, the pin is at the southernmost prominence, but the BGN page indicates the northernmost (despite that the southern one was known to be higher then).

I believe The Sawtooth is an unranked/named example where 14ers, LoJ, and the BGN disagree.

This seems like an inconsistency. Do we usually try to use the map labeled (BGN/USGS?) point if it's unranked and otherwise the ranked point?
Are there any examples of named+ranked peaks that contradict this scheme?
If the point west of Thunder had turned out to be ranked, would we have moved that summit?

I'm not arguing for more peaks (since the only alternative that comes to mind where the named and ranked points differ would be to keep the named point as an unranked summit and add a UN at the ranked point, which would yield a bunch of extra named points with almost no prominence). Just curious if there's an actual methodology in these cases.
John said, "Generally, I'd say benchmarks are fixed points whereas summit names can be applied to the highest point if nearby and no other name nearby exists. "Hawk Peak" exists on a sky terrain map with an ISBN." He also said, "For unranked peaks, the name should probably stay where the mapmakers intended."

Given all that, it seems like if there is a ranked point somewhat near a named point, the name could possibly apply, depending on how close it is. It would be a lot of extra points to add an unranked exactly where the name is, and then a ranked point at the actual HP.

Ranked Middle Peak is ranked, so the LoJ point is at the HP, and gets the name from nearby Middle Peak.

For unranked, Thunder Mountain, Sheep Mountain, and Lone Eagle Peak, John chose to keep the LoJ point closest to the name on the caltopo map. (Though Ryan did show an old map where the name was more ambiguous).

For unranked King Solomon, since the name on the map vaguely indicates the entire ridge, the actual HP makes since to pinpoint (even though BGN has the northern spot).

And yes, for Hawk Peak, LoJ depicts the HP as shown in the guidebook instead of the BM location.

Hopefully that makes some sense. He tries to put a big emphasis on where the USGS map shows the name (which the BGN coordinates often correspond to), especially if the peak is unranked. Sometimes the placement is ambiguous/subjective as to where exactly it refers to. If there's a ranked summit and if there's no name, it'll be unnamed; if there's a nearby name, sometimes LoJ takes that name and applies it to the ranked summit if it seems reasonable to do so.
User avatar
Scott P
Posts: 9876
Joined: 5/4/2005
14ers: 58  16 
13ers: 57 14
Trip Reports (16)
 

Re: Colorado LiDAR Findings

Post by Scott P »

bdloftin77 wrote: Wed Sep 20, 2023 4:34 pmJohn said, "Generally, I'd say benchmarks are fixed points whereas summit names can be applied to the highest point if nearby and no other name nearby exists. "Hawk Peak" exists on a sky terrain map with an ISBN." He also said, "For unranked peaks, the name should probably stay where the mapmakers intended."

Given all that, it seems like if there is a ranked point somewhat near a named point, the name could possibly apply, depending on how close it is. It would be a lot of extra points to add an unranked exactly where the name is, and then a ranked point at the actual HP.

Ranked Middle Peak is ranked, so the LoJ point is at the HP, and gets the name from nearby Middle Peak.

For unranked, Thunder Mountain, Sheep Mountain, and Lone Eagle Peak, John chose to keep the LoJ point closest to the name on the caltopo map. (Though Ryan did show an old map where the name was more ambiguous).

For unranked King Solomon, since the name on the map vaguely indicates the entire ridge, the actual HP makes since to pinpoint (even though BGN has the northern spot).

And yes, for Hawk Peak, LoJ depicts the HP as shown in the guidebook instead of the BM location.

Hopefully that makes some sense. He tries to put a big emphasis on where the USGS map shows the name (which the BGN coordinates often correspond to), especially if the peak is unranked. Sometimes the placement is ambiguous/subjective as to where exactly it refers to. If there's a ranked summit and if there's no name, it'll be unnamed; if there's a nearby name, sometimes LoJ takes that name and applies it to the ranked summit if it seems reasonable to do so.
Often the above are true, but I have noticed a lot of inconsistencies. North Star Mountain, for example is a weird one on LoJ. The USGS maps say the middle summit is North Star Mountain, but the ranked summit is quite a distance from the name on the topo map.

https://www.listsofjohn.com/mobile/peak/229

LoJ calls the ranked summit North Star and the Middle Summit "The Butterknife" from a guidebook name.

North Star is a weird one for sure.
I'm old, slow and fat. Unfortunately, those are my good qualities.
User avatar
bdloftin77
Posts: 1429
Joined: 9/23/2013
14ers: 58  1 
13ers: 99
Trip Reports (2)
 

Re: Colorado LiDAR Findings

Post by bdloftin77 »

Scott P wrote: Wed Sep 20, 2023 5:14 pm Often the above are true, but I have noticed a lot of inconsistencies. North Star Mountain, for example is a weird one on LoJ. The USGS maps say the middle summit is North Star Mountain, but the ranked summit is quite a distance from the name on the topo map.

https://www.listsofjohn.com/mobile/peak/229

LoJ calls the ranked summit North Star and the Middle Summit "The Butterknife" from a guidebook name.

North Star is a weird one for sure.
Yeah. It must have been close enough to still call the ranked peak North Star vs having an unnamed ranked peak as the HP, and then unranked North Star as a subsummit. 14ers.com has the same location as LoJ for North Star. I wonder if some of these have historical precedents as well. I don't have any 13er books nearby at the moment, but maybe people have always considered the HP as listed in LoJ and in 14ers.com as North Star, even though it's along the ridge a bit from the map location.
User avatar
Bigfoot
Posts: 71
Joined: 6/25/2008
14ers: 58  1 
13ers: 22
Trip Reports (0)
 

Re: Colorado LiDAR Findings

Post by Bigfoot »

I was thinking similar thoughts this weekend as I was climbing Mt. Buckskin. The new LiDAR high point is now on what some maps labeled as West Buckskin. So what is proper? Renaming West Buckskin to Mt. Buckskin and the current Mt. Buckskin to East Buckskin? Or changing the highpoint from Mt. Buckskin to West Buckskin?
User avatar
Scott P
Posts: 9876
Joined: 5/4/2005
14ers: 58  16 
13ers: 57 14
Trip Reports (16)
 

Re: Colorado LiDAR Findings

Post by Scott P »

Bigfoot wrote: Wed Sep 20, 2023 10:19 pm I was thinking similar thoughts this weekend as I was climbing Mt. Buckskin. The new LiDAR high point is now on what some maps labeled as West Buckskin. So what is proper? Renaming West Buckskin to Mt. Buckskin and the current Mt. Buckskin to East Buckskin? Or changing the highpoint from Mt. Buckskin to West Buckskin?
The USGS maps list the highest point as Buckskin so it won't matter much. The two summits are pretty close together and there isn't much separation in elevation between the two.
I'm old, slow and fat. Unfortunately, those are my good qualities.
John Prater
Posts: 221
Joined: 2/4/2007
14ers: 58  58 
13ers: 368 2
Trip Reports (0)
 

Re: Colorado LiDAR Findings

Post by John Prater »

bdloftin77 wrote: Wed Sep 20, 2023 5:36 pm I wonder if some of these have historical precedents as well. I don't have any 13er books nearby at the moment, but maybe people have always considered the HP as listed in LoJ and in 14ers.com as North Star, even though it's along the ridge a bit from the map location.
I suspect historical precedents may have played into it.

Garratt and Martin (Third Edition) says, "The second ridge point, at 13,500 feet, is near the name "North Star Mountain" on the 1987 photo revised Breckenridge topographic map, however, we elect to apply the name to the entire high ridge and consider the 13,614-foot high point to be the summit of North Star Mountain."

Also interesting to note that Ormes Sixth Edition (1970) has "North Star Mountain, 13,350'" and the Seventh Edition (1979) has "North Star Mountain, 13,614'". It seems that Ormes may have "moved" the summit to the western summit between those editions. I'm not clear on which summit the Sixth Edition with 13,350' was referring to, though. I think that was most likely based off of older maps - perhaps the "Hist. 1945+" map that LoJ has? On that map, I can't clearly tell what the western and middle summit elevations would have been. It almost looks like the highest contour on both of those summits could have been 13,350.
User avatar
bdloftin77
Posts: 1429
Joined: 9/23/2013
14ers: 58  1 
13ers: 99
Trip Reports (2)
 

Re: Colorado LiDAR Findings

Post by bdloftin77 »

John Prater wrote: Wed Sep 20, 2023 11:04 pm
bdloftin77 wrote: Wed Sep 20, 2023 5:36 pm I wonder if some of these have historical precedents as well. I don't have any 13er books nearby at the moment, but maybe people have always considered the HP as listed in LoJ and in 14ers.com as North Star, even though it's along the ridge a bit from the map location.
I suspect historical precedents may have played into it.

Garratt and Martin (Third Edition) says, "The second ridge point, at 13,500 feet, is near the name "North Star Mountain" on the 1987 photo revised Breckenridge topographic map, however, we elect to apply the name to the entire high ridge and consider the 13,614-foot high point to be the summit of North Star Mountain."

Also interesting to note that Ormes Sixth Edition (1970) has "North Star Mountain, 13,350'" and the Seventh Edition (1979) has "North Star Mountain, 13,614'". It seems that Ormes may have "moved" the summit to the western summit between those editions. I'm not clear on which summit the Sixth Edition with 13,350' was referring to, though. I think that was most likely based off of older maps - perhaps the "Hist. 1945+" map that LoJ has? On that map, I can't clearly tell what the western and middle summit elevations would have been. It almost looks like the highest contour on both of those summits could have been 13,350.
Thanks John! Cool to know that there's a precedent for this.
User avatar
RyanSchilling
Posts: 212
Joined: 1/18/2005
14ers: 58 
13ers: 266
Trip Reports (1)
 

Re: Colorado LiDAR Findings

Post by RyanSchilling »

bdloftin77 wrote: Wed Sep 20, 2023 12:30 pm Good thoughts. Do you have any more examples that could be looked at and possibly changed? I'll let John know you're curious and we'll see what he thinks.
One that's always driven me nuts is Epaulet Mountain / Epaulie. Given what epaulets are, the name clearly was intended to refer to the pair of summits -- the mountain looks like a pair of shoulders -- but for whatever reason, mapmakers slapped the label on the lower, northwestern summit.

Other inconsistencies...

Gravel Mountain's summit isn't 13,702', and Jones Peak's summit isn't 13,712', but we're fine with Mount Mamma's summit shifting south?

A different scenario, but how is this the summit of Twin Sisters Mountain? Inconsistent with, say, how Brown Mountain is defined.
Last edited by RyanSchilling on Fri Sep 22, 2023 3:03 pm, edited 1 time in total.
User avatar
supranihilest
Posts: 960
Joined: 6/29/2015
14ers: 58  45 
13ers: 752 2 8
Trip Reports (122)
 

Re: Colorado LiDAR Findings

Post by supranihilest »

RyanSchilling wrote: Fri Sep 22, 2023 10:23 am
bdloftin77 wrote: Wed Sep 20, 2023 12:30 pm Good thoughts. Do you have any more examples that could be looked at and possibly changed? I'll let John know you're curious and we'll see what he thinks.
One that's always driven me nuts is Epaulet Mountain / Epaulie. Given what epaulets are, the name clearly was intended to refer to the pair of summits -- the mountain looks like a pair of shoulders -- but for whatever reason, mapmakers slapped the label on the lower, northwestern summit.

Other inconsistencies...

Gravel Mountain's summit isn't 13,702', and Jones Peak's summit isn't 13,712', but we're fine with Mount Mamma's summit shifting south?

A different scenario, but how is this the summit of Twin Sisters Mountain? Inconsistent with, say, how Browns Mountain is defined.
In the case of Mount Mamma there's a note saying "Notes: Garratt & Martin: USGS confirms that name refers to entire massif rather than spot elevtion where name appears on printed map." I don't know how G&M got the USGS to confirm that and there's no further proof of them doing so, but in that case it makes sense assuming the note is true. That note is absent on the other two similar examples, which also make sense considering the original names and thus BGN and mapmakers don't care at all about prominence or rank, as the concept of a peak ranking almost certainly didn't exist then and they were most likely naming points and not massifs, at least in those cases.
User avatar
Chicago Transplant
Posts: 4112
Joined: 9/7/2004
14ers: 58  12  24 
13ers: 701 46 36
Trip Reports (66)
 

Re: Colorado LiDAR Findings

Post by Chicago Transplant »

supranihilest wrote: Fri Sep 22, 2023 10:41 am
RyanSchilling wrote: Fri Sep 22, 2023 10:23 am
bdloftin77 wrote: Wed Sep 20, 2023 12:30 pm Good thoughts. Do you have any more examples that could be looked at and possibly changed? I'll let John know you're curious and we'll see what he thinks.
One that's always driven me nuts is Epaulet Mountain / Epaulie. Given what epaulets are, the name clearly was intended to refer to the pair of summits -- the mountain looks like a pair of shoulders -- but for whatever reason, mapmakers slapped the label on the lower, northwestern summit.

Other inconsistencies...

Gravel Mountain's summit isn't 13,702', and Jones Peak's summit isn't 13,712', but we're fine with Mount Mamma's summit shifting south?

A different scenario, but how is this the summit of Twin Sisters Mountain? Inconsistent with, say, how Browns Mountain is defined.
In the case of Mount Mamma there's a note saying "Notes: Garratt & Martin: USGS confirms that name refers to entire massif rather than spot elevtion where name appears on printed map." I don't know how G&M got the USGS to confirm that and there's no further proof of them doing so, but in that case it makes sense assuming the note is true. That note is absent on the other two similar examples, which also make sense considering the original names and thus BGN and mapmakers don't care at all about prominence or rank, as the concept of a peak ranking almost certainly didn't exist then and they were most likely naming points and not massifs, at least in those cases.
A lot of mountains get named from being visible from the valley below. I don't think it's unusual for a named unranked peak (i.e. Gravel or Jones) to block an unnamed higher summit that wasn't visible from a distance.

I saw the same note about Mamma that Ben references, so it makes more sense to call the high point Mamma and not the map point if that is USGS' intent.
"We want the unpopular challenge. We want to test our intellect!" - Snapcase
"You are not what you own" - Fugazi
"Life's a mountain not a beach" - Fortune Cookie I got at lunch the other day
User avatar
Boggy B
Posts: 956
Joined: 10/14/2009
14ers: 58  7 
13ers: 784 76
Trip Reports (57)
 

Re: Colorado LiDAR Findings

Post by Boggy B »

Great examples.

Brown Mountain (Duco BM) matches the coordinates on the BGN page, despite a map label sprawled across the whole ridge.
This is inconsistent with King Solomon, which despite the same style of map label does not match the coordinates on the BGN page.
In this scenario I'd vote to move King Solomon to the USGS-designated, lower northern prominence.

Mamma is consistent with Middle Peak (Dolores), though I don't know if there's a published justification in the case of Middle.
As noted above this is inconsistent with Epaulet (odd case since Roach named "Epaulie"), Gravel, and Jones.
EDIT - a similar case is Green Mountain and unnamed (Roach nicked) Stony Pass Peak.

Like Ben said, I'm not sure how the USGS would have confirmed naming for a massif instead of a highpoint, and the BGN feature type for all seven of the above is "Summit."
User avatar
RyanSchilling
Posts: 212
Joined: 1/18/2005
14ers: 58 
13ers: 266
Trip Reports (1)
 

Re: Colorado LiDAR Findings

Post by RyanSchilling »

supranihilest wrote: Fri Sep 22, 2023 10:41 am In the case of Mount Mamma there's a note saying "Notes: Garratt & Martin: USGS confirms that name refers to entire massif rather than spot elevtion where name appears on printed map." I don't know how G&M got the USGS to confirm that and there's no further proof of them doing so, but in that case it makes sense assuming the note is true. That note is absent on the other two similar examples, which also make sense considering the original names and thus BGN and mapmakers don't care at all about prominence or rank, as the concept of a peak ranking almost certainly didn't exist then and they were most likely naming points and not massifs, at least in those cases.
Thanks, I hadn't noticed that Mamma note before