To be clear, I do not claim to be authoritative in OSM. I merely do my best, perhaps "being a good example" as a high goal I do strive to achieve. I do so because I see other mappers strive to do their best, not be authoritative and "set a good example by being a good example." It works.

Thanks to all participants here, and I still have hope that some consensus can be achieved on these topics.

Quite a number of false allegations here by Adamant1 (again), is what I'll say about that. Though, maybe if I skate into "being generous territory" I give him the benefit of the doubt and say he has a misunderstanding or is offers us confusing language. I honestly don't understand much of his approach to mapping anyway, despite what might look like years of concerted efforts at large numbers of edits. Good luck to you, Adamant1, I wish you no ill will.

I thank Minh for pouring oil on these turbulent waters, hopefully calming them. (That's a metaphor for de-escalation, frequently necessary with one particular participant here). OSM is indeed a meritocracy (of mapping skills, sometimes of writing / communication skills); OSM is not "who you know."

<though it’s frustrating that “road” and “highway” are such overloaded terms.>

I agree that this is a crux of difficulty here. Keep up the excellent dialog, everyone, this is good stuff!

That's a fair observation!

Consensus can be difficult to achieve, but it isn't impossible. Again, I am cheered by seeing as much progress as I do.

Certainly, discussion is and will take place in Slack. I choose not to participate via that medium and am appreciative to learn of "California edition" momentum trickling to / being "cross-posted" (from Slack? OK) to talk-us. Maybe a talk-california mail-list could be born, but traffic (still) seems too low to fully justify that (now).

I applaud the momentum, discussion and serious movements towards good consensus (regarding trunk, et al re highway classification). This is difficult and good work, and exactly as Minh says, there remain some rough edges. That's to be expected and doesn't seem terribly contentious (nor does it need to be). Rome wasn't built in a day.

Hi Bradley and others: From his california/Draft HCG (linked by the US 2021 HCG) wiki, I understand Bradley to mean groupings of California as he describes them there (admittedly "arbitrarily," to use his word). Though I and my mapping do seem to fall "largely" into Bradley's "central" region of California, having deep roots in southern California and having travelled a great deal of Humboldt, Mendocino, Shasta, Trinity, Modoc and nearby "more farther northern" counties of northern California, I am quite familiar with Bradley's "northern" region as well. So, in short, I am very much a California-wide mapper, though I do focus on "my" various areas. These are broad strokes and our language use here can be difficult as we do that. No offense meant to anybody as they characterize somebody's statewide- (or "part-statewide'") mapping, and none taken.

However, I do defer to Adamant1's apparently deep familiarity with Shasta County, Redding and environs and leave mapping those areas to him and others, even as I might occasionally map in those areas (emphasis on occasionally) myself.

WRT the discussion-at-hand regarding "trunk," I am very much in "watching mode." Thank you to everybody for positive contributions to wiki, changeset comments and the map itself.

Thanks. We're getting there!

Well, OK. In my zeal to correct the map, I'll say my deletion was correct and your admonishment to do more research and find where it actually belonged is "more correct." Thank you for doing the leg-work on this.

Nice work!

Ah, thanks for the clarification.

If you say so. It's not too far from my house and I've driven it thousands of times, if there are new signs that "feather the edges" as you tag here, OK.

OK, I think I've got this (mostly?) correct: the segments of Blue which are shared by SDIY are now tagged railway=rail + usage=branch + railway:traffic_mode=mixed. Also, the Blue route=railway relation has a note tag of "SDIY is an operator only on segments tagged rail:traffic_mode=mixed."

ORM being VERY slow to render right now hinders my progress here; I'll take a look this weekend.

BTW, it's "trolley only" between Old Town and UCSD on the new Blue Line Extension, so that part for sure is properly tagged railway=rail. Are there specific segments (of Blue or Orange) you think should also be so tagged?

(I'm sure none of Green should be, it's "all trolley" too).

Taking a look over the next day or two. I believe you are correct: segments of Blue (and parts of Orange not currently so tagged?) between the Santa Fe Station and the new Mid-Coast addition (to UCSD, which are purely light_rail) likely ARE railway=rail, usage=branch. Thing is, I'm not sure where the split to "light_rail only" is. I think it is near the Green branch north of Old Town (station), but I'm not sure where.

What ZeLonewolf and I (and the rest of OSM) are saying is "go ahead and use boundary=protected_area to designate the boundary of the protected area," AND use natural=wood where it is wooded. These two tags truly should NOT be applied to the same polygon. It furthers confusion to do so by leaving the map a more difficult place to map with accurate natural=* tagging (because others would need to "make holes" in what they tag in the future). Keep them separate (tagged objects) because they ARE separate (things in the real world we wish OSM to represent in our map data).

There is also a proposal that ZeLonewolf and I have authored that goes a long distance to unsnarling what OSM means by boundary=protected_area.

Conflating a boundary with the entirety of "all of this is one particular natural area" isn't correct. It is understandable but it is distinctly incorrect and something OSM still struggles with.

However, about this, we are certain. ZeLonewolf's retagging was correct.

I ask platypil to read the docs pointed to be aware of the many issues here. In brief, it is "landcover is not landuse" but in this case it is about how it is incorrect to call "all wood" a wilderness area.

Hey, thanks a bunch for your additions to this route, Joel! "Many hands make light work."

Whoops, thank you for catching this error of mine! It was a "holding container" for the Great Allegheny Passage trail portion in Pennsylvania. But I made an error with this and you caught it.

I have corrected this by deleting the relation as some leftover elements during the creation and development of the route. Again, thank you for bringing this to my attention.

It is quite often much more complex than "all a leisure=park" and/or "all a protected_area" (or nature_reserve).

ZeLonewolf and I have proposed using boundary=protected_area (not necessarily with a protect_class=* tag) which would allow well-documented methodologies to assign "sub-areas" (like leisure=park) where they are warranted in the larger context of the protected area.

See osm.wiki/Proposed_features/Park_boundary to read that this proposal is rich, well-designed, has had over a year to absorb wide community consensus and has (to the best of my knowledge) no opposition to its basic tenets.

If you are looking to better develop "parks" in OSM, consider contributing to this proposal. Your comments are welcome on its Discussion page.