Hi Belmemes,
I've been looking at your recent editing of the trails in St. Joseph's Hill. Your changeset says the trails were "unmaintained track roads", and I guess that's why you consider them paths rather than tracks. But the wiki characterizes paths as " not intended for motorized vehicles" and tracks as " that are suitable for two-track vehicles, such as tractors or jeeps. If the way is not wide enough for a two-track vehicle, it should be tagged as highway=path. ". For general multipurpose trails in wild lands, this distinction is followed by all just about all mapping around California (and elsewhere AFAIK).
Most of the trails in St.Joseph's Hill are in fact wide enough for vehicles, and are definitely used by Open Space District Ranger truck patrols, and if necessary by emergency vehicles. So I would maintain that the existing definition of these trails was correct. The only trails that are truly paths (ie, too narrow for vehicles) that I can think of off the top of my head would be the Brother's Bypass, the Flume, and the Serpentine Trails. I'm pretty familiar with the SJH Preserve because I volunteer with the MidPeninsula Open Space District, and do trail patrol there (on foot and riding in District trucks on occasion) frequently.
What do you think? Would you buy the above point of view?? I want to change the trail designations back to the way they were, but didn't want to do so without discussing with you first.

Hi Anthony, you just renamed Hwy 9 between Saratoga and Hwy 35. This road has two names in local current use - "Congress Springs Road", and "Big Basin Way". Now both name= and name_1= tags are set to "Congress Springs Road".
Certainly both names should be tagged (for what it's worth, both Google and Bing maps show both names, though I'm not relying on them). What was your source for removing "Big Basin Way"?

Hello user_5359. Thanks for the welcome, but I've been doing this since around 2013 :)
Check the wiki at osm.wiki/Addresses
Note that "tags can be added to.... polygons representing the perimeter of the site". However, I'll change the Zerowaste building address because that's obviously the main building.

Thanks for the fast reply. And kudos for cleaning up the geometry, and the import of the Marine Protected Areas. I hear what you're saying but, with respect, I'm not convinced that lots of little relations beats beats simple ways sharing nodes in terms of complexity of mapping - and particularly of maintenance. I'm not familiar with the reltoolbox plugin, but will take a look. Do you know other mappers who use this approach? Certainly it renders OK, and I don't know of any explicit rules being broken.
But it seems unusual to me, and I think it's likely that no-one else has noticed, that I may throw the question out onto talk_US or OSM-Talk to see if other people think it's "best practice". At least I'd like to know if the rest of us should be mapping stuff this way.
Cheers

Hi glebius,
I was wondering why you went to such a lot of work to "properly multipolygonize" a lot of the Monterey waterfront? Is there an advantage to having building footprints, pedestrian areas, etc, all defined as multipolygons? Multiple closed ways (areas) are allowed to share nodes in OSM (JOSM makes it quite simple) but all these multipolygons seem unecessarily complicated.
Thanks!

Hi hwescott,
I wondered why you're using leisure=park on the Smith River NRA and the Six Rivers National Forest? This is usually reserved for small, mainly grassy, maintained urban spaces. See the wiki definition, and how the Klamath NF is tagged.

The description of this changeset should have read: "Update Skyline Ridge Open Space Preserve.... etc".

You are correct. The road is "Bridgers Close", and the unnecessary recreation and the temporary "fixme" was a bit of editing clumsiness on my part. I have corrected the road name.