The frustration with both of these approaches is that viewing the map doesn't show the pass. A mountain pass is roughly as important as the peaks that surround it. Those have a "natural=peak" tag, but somewhat frustratingly there isn't even a proposal for a "natural=pass".

I'll have to figure out how to make a formal proposal, but for the time being I've added that tag to the "name=Muir Pass" node preemptively.

Had to look up "lit" -- makes sense, but anyone camping had better bring a flashlight/torch, eh?

And for public restrooms in the U.S., "fee=no" is pretty universal. Last time I heard of a toilet that charged a fee was back in the 1970s. Folks really hated the idea, and it went away as far as I'm aware.

Finally, open hours for any of the toilets I'm adding here will universally be 24 hours a day. I can't remember the last time I saw a public toilet that wasn't, at least out of the big cities where curfews and vandalism might change that.

Interesting. Are these factors a frequent issue in the northern U.K.?

Well, I think I can resist that. Last September when I did the Rae Lakes loop I included some serious side trips in to the 60 Lakes Basin, Charlotte Lake and Lake Reflection. But I want to concentrate on the hikes others might be more likely to do, especially "named" hikes. On the other hand, I think I've *done* most of those...

Also, I'm tending to push my less-traveled hikes towards where there aren't any trails at all (e.g., the 60 Lakes Basin). So I'll be mostly mapping based on memory and some old GPS traces.

That being said, I'm s'posed to be starting the JMT in less than a month, so I guess I still haven't done all the "common" stuff.

Okay, reverted to that standard practice.

BTW, SK53, the value of searching for how tags are used and combined is nice, but is there a way of seeing *what* node has the attached "trailhead" tag? There appears to only be one, which is amusing, but I also would like to see examples of other combinations, such as trying to find if anyone is using "amenity=parking" plus "trail=yes" or something similar.

I'm also amused that while "kayak=yes" is apparently used 171 times, "kayak=no" is used 3 times. Seems a curious prohibition to specify. And when is the tag "hikingshoes" appropriately set to "high_heels"?!?

Ah, very clever. Of course, that's assuming the original is also a three-dimensional measurement. I'm just going to assume exactly that... :-)

Excellent — relationship is continuous.

http://ra.osmsurround.org/analyze.jsp?relationId=1709551
Relation length ca.: 10.6 KM
Hmm, that's only 6.6 miles, but the race website claims 7.4 miles. That loss of 0.8 miles is very disconcerting.

Oh, well I didn't mean to imply there were abbreviations — "JMT" is just short for "John Muir Trail", and likewise PCT is as you've noticed Pacific Crest Trail.

The tiny segment in question is osm.org/browse/way/125842182

If I understand correctly: when I split the previous way into three pieces, all of them inherited the relationship to longer paths; changing the name of this small segment doesn't affect that. Which attribute will show up as displayed text once a user zooms in far enough? (I'm guessing "name" :-)

That seems to make sense.