No problem. I should've worded this changeset comment a little better. Basically been combing through a bunch of unusual parking_space tags with only one use worldwide. Most of them were better of as a description=* tag, but a few were typos and syntax issues that got fixed, not "removed".

Excellent detailing work.
Just leaving a message to let you know for future edits that the parking_space=private tag has been recently phased out of use in favor of access=private for private parking spaces.

Don't see why not. Done.
changeset/149576618

Update: Ways have been reordered and PTv2 tags added.

Note to self: I spoke too soon. Not fully PTv2-compatible until ways are reordered in the relation.

Glad I'm not the only one who makes the typo natural=woof sometimes. WOOF! 🐶
Fixed the issue here.
changeset/148558332

I understand the relation isn't very usable in its current form. It's far from the finished product.

I'm laying the groundwork to transition bus routes to ptv2 in the long term by mapping the bus stops that'll be added to their relations.
node/11628003471

Also repurposing a lot of the retired "X" express bus routes into SIM routes.
changeset/140904155

Because the SIM1C route was very similar to its SIM1 counterpart, it was pretty quick and simple to duplicate that ptv1 route.

Once I reach a stage where all the stop nodes on a given route are created, I'll gladly take a stab at converting that route to ptv2 by following the path of the v1 route and adding each of its roadways into one (or both) of two directions.

The tl;dr is that ptv2 is the end goal, and making these ptv1 relations is a step toward that without creating TOO much double-work, since having a v1 relation with all the roadways I need in it makes the next step much quicker.

Ah, my bad. Ran quick query to fix the two times this happened.

changeset/147751522
changeset/147751629

Ah, thanks for catching that! Ran a quick query to see where else I made this error. Thankfully just one other instance.
changeset/147747564

parking_space=private has had de-facto status for a while, but there's been a campaign this past week to do away with the misplaced tag. In the coming update to iD, an Access tag picker has been approved for editing parking spaces moving forward.

https://github.com/openstreetmap/id-tagging-schema/pull/1123

Mxx, the validator tools and detailed presets are nice, but it's concerning that RapiD is still applying the crossing=marked tag, which has been systemically removed from Staten Island several months ago after its removal from vanilla iD presets. Will definitely throw a wrench in tagging consistency.

Hi again,

To help maintain consistency when adding crosswalks in Staten Island, please try to avoid "crossing=marked", which is deprecated in the latest version of iD. Also try to tag the roadway/crossing intersection's node with a crossing tag as well, to make the feature more apparent for vehicular navigation.

I'll routinely check and query and clean these up myself, but here is a before-and-after screenshot to help show the local standard (which is becoming increasingly prevalent throughout all of NYC). https://imgur.com/a/agFVMqE

Hi Yash, I see you requested someone to review this changeset. I don't think this would be a proper use case for "Primary Road". That tag is used for major artery streets.

Because the pavements ends, and people probably shouldn't be driving too close to the graves in this cemetery, I will change this to a Path.

Of course. I ran a query for any buildings with building=house and no height=* tag to make about 150 corrections overall.
The remaining cases are buildings that were mapped after the 2014 import and never had a height tag to begin with.

Fixed in changeset/141431167
---

Published using OSMCha: https://osmcha.org/changesets/139933865

My bad. This changeset predates iD's updated Townhouse preset, so tags had to be manipulated manually. Looks like a new line wasn't created and mixed the height and house tags together. Fixed in changeset/141430097. Luckily only impacted 72 buildings and not hundreds.
---

Published using OSMCha: https://osmcha.org/changesets/139853210

I've been looking into this as well, but the site only supports routes that are already in PTv2 format.

I'm still trying to figure out a way to efficiently split these route relations by direction (currently they're mapped as one full circuit). Once I do that, I should hopefully be able to use Relatify to link the stops to these routes.
---

Published using OSMCha: https://osmcha.org/changesets/140905787

I haven't been to this location since 2021, but I will confirm if this lot was ever reopened next time I pass through.

Ah, thanks for catching that. I'll tag that way moving forward (and run a query to fix the instances from this set).
---

Published using OSMCha: https://osmcha.org/changesets/139627951

Big changeset. Also I think "Love's Gluten Frew" may be a typo.