I’m happy to retag the specific portions that have had this occasional service. I thought I was merely acting on the note that was added in changeset/67040694.

It wasn’t clear to me from my research that this occasional service extends all the way from Santa Cruz to Capitola. In fact, the TAMC document I cited above states that there is indeed an isolated segment of active rail from Santa Cruz north, with the segment from Santa Cruz to Watsonville being unmaintained and out of service. However, that was 2020, and I’m happy to hear that there have been developments since.

Retagging the trackage all the way to Watsonville would raise some questions that hopefully you can shed more light on:

1. Is the old-school wigwag on Seabright Avenue still in operation? I have no idea how to tag it if so.

2. Does this tree still block the tracks south of the old county landfill? way/1074882241 It would be surprising to tag an impassable railway as anything but disused. By that logic, any railbanked trackage would be railway=rail.

3. What are the speed limits on this stretch? It had been mistagged maxspeed=40, which presumably meant 40 mph, for Class 3. But FRA records for crossings along this stretch give limits of 10 mph freight / 15 mph passenger, in line with Class 1 and consistent with the TAMC document.

Hi, are you sure this Costco has solar panels on its roof? All I see in aerial imagery is the skylights.

Separately, please try to provide more descriptive changeset comments when possible. It doesn’t have to be incredibly thorough, but for example here it would’ve been helpful to mention the giant solar panels. Thanks for understanding!

…added bridges, culverts; realigned roads, streams

Neat, mini runways! way/1060140555

The crossing had already been mapped; this changeset indicates that the crossing is uncontrolled.

More context in https://github.com/ZeLonewolf/openstreetmap-americana/issues/428#issuecomment-1159349224

Only the end of this street is a one-way street, as demonstrated by the stop sign and other signs facing in the other direction. Reverted in changeset/122640545.

Hi, should the speed limit on this bridge be 10 mph, as opposed to 10 km/h as it’s currently tagged?

Hi, thanks for adding these speed limits. Remember to add a space and “mph” to the end of the maxspeed tag value so that routers interpret it as miles per hour instead of kilometers per hour. Thanks!

Also adjusted the position of various POIs.

Undone in changeset/122300376.

Thanks!

I mostly agree and have been pretty active in promoting that tagging scheme. However, I figured it wouldn’t hurt to humor the mapper(s) who suggested the more standards-compliant en-fonipa code on the wiki. name:pronunciation=*#Possible_synonyms If history had played out differently and I knew about the fonipa language subtag a few years ago, I would’ve chosen it instead and we wouldn’t even be talking about the :pronunciation subkey that seems to be surprising to various editors. 🤷‍♂️ But I don’t really have plans to do much with this redundant syntax.

Reverted in changeset/121741937.

Hi, this sledding hill is 20 meters tall over the average ground elevation. By changing height=* to ele=*, this changeset implies that Chill Hill is only 20 meters above sea level, which would make it a pit more than 250 meters deep. You may want to review other peaks that you retagged in case they were similarly legitimate heights rather than elevations.

This changeset did the same thing to the route relation for California State Route 1, which ended up getting deleted as a tagging error in changeset/98079414. changeset/121350189 restored the relation and 121351794 reverted it to being a road route again.

This relation were somehow broken in changeset/93689318, but the correct fix would’ve been to revert that changeset rather than delete the relations, which represented California State Route 1. The relation has been restored in changeset/121350189 and was unrepurposed in changeset/121351794.

I reverted this change in changeset/121029361 because I saw the one-way restriction with my very eyes and mapped it the same day. It’s very recent, but you can read about it at https://bit.ly/quiet-zone-project

government=legislative is apparently for the main legislative meeting hall. (Don’t ask me how the State Capitol counts as a single office.)

https://taginfo.openstreetmap.org/tags/government=legislator was used three times until today, based on the discussion at https://osmus.slack.com/archives/C2VJAJCS0/p1608585986190800 osm.wiki/Talk:Tag:government%3Dlegislative#Legislative_offices I was going through retagging all the occurrences of office=political_party that weren’t party headquarters or field offices.

There’s an ongoing discussion about whether to use office=politician for any kind of office run by a politician, whether a campaign office or a constituent service office. https://lists.openstreetmap.org/pipermail/tagging/2022-May/thread.html#64575 I’m leaning towards retagging these offices as office=constituent_service for additional clarity, but in the meantime I moved them away from office=political_party, which is more incorrect.

Based on https://council.nyc.gov/district-30/ , I think node/9344579187 might’ve moved to a different neighborhood just after you mapped it. I’ve tagged it office=vacant for now, but perhaps you could double-check the new location?