Hi Jon, thanks for requesting a review and leaving a detailed, helpful changeset comment!

it looks like this changeset entirely deleted the driveway and its nodes, instead of splitting the way and tagging it appropriately, as you've properly done in your other changesets. Therefore, I've restored it and tagged it appropriate in changeset/180037317 : changeset/180037317

See the wiki for some more background on why this is avoided on OSM: osm.wiki/Why_we_won%27t_delete_roads_on_private_property

Thanks, and happy mapping!

Maybe should be scrubbed entirely given the stated source of Google Maps, per OSM policy?

Maybe it should be deleted entirely, though, given the stated source of Google Maps in violation of OSM policy...

Fixed remaining SEO spam and mistagging in changeset changeset/180030861

Cleaned up the SEO spam and fixed the mess of address tagging as best I was able (given that none of the many POIs around this had proper address tags, I could not easily determine local OSM addressing convention): changeset/180024249

Removed this now-duplicate node in changeset/179869733 as you added the same tags to the building, and in any case it is missing a top-level tag meaning it won't actually display as anything on the map regardless. Moved the phone number to the building way (that was only on the node for some reason) in changeset changeset/179869861

> The osm-revert has some problems.

Just FYI, I've previously had it not work due to the overpass-api.de server that is unfortunately used by default most places being extremely overloaded and underresourced to the point of being almost unusuable; using another Overpass server e.g. https://maps.mail.ru/osm/tools/overpass/api/interpreter with more resources and much less load has worked like a charm for me.

> I designed the bot with the goal of not reverting an entire changeset, but instead trying to keep any "good" tags from a changeset. However, doing a full revert would definitely be much simpler for such spammy edits ... 🙂

Yeah, that definitely makes sense especially for a bot like this that doesn't require human effort. That was also the approach I've taken in the past with SEO spam changesets, trying to manually preserve what I could and fix or remove what I couldn't. On the other hand, on the advice of the DWG members I've worked with lately helping deal with hundreds of SEO spam changesets/accounts I've also done more full reverts in situations where the SEO spam was more egregious, complex, or there wasn't much of value to preserve (like in this case, where it was just a node with no top-level tags and just a name and website), and to avoid rewarding SEO spammers by doing what they should be doing for them.

Of course! Thanks for the quick fix!

Awww, you're too kind, but you're most welcome Pascal! Your fantastic tools really help motivate me (and surely thousands of other mappers) to keep mapping as well, especially HDYC!

Speaking of which, your own kind words gave me the motivation to finally get around to typing up and sending you (via OSM user message) that feedback on HDYC that I messaged you about on Insta, both the original two inter-related issues and a few others I'd found. Cheers!

Just for reference, that final changesets was: changeset/179664487

Hi Pascal, see my reply to your other comment for full details: changeset/179664298#c1566980 but TL;DR for anyone else reading, I had to revert the SEO spammer's changesets one by one due to OSM-Revert not letting my new-ish dedicated `_Revert` account revert them all three cleanly at once, so some SEO spam text remains until the third revert changeset/179664487 changeset/179664487

Hi Pascal, sorry if I wasn't totally clear here--the "artificial limitations" mentioned above refer to OSM-Revert, nothing to do with the NeisBot bug (which would have only been a potential factor given the issue with the former, and of course you fixed now in any case).

Namely, since I was using my new dedicated "_Revert" account (which I created recently to avoid polluting my main account with these revert changesets), it thought I was a "new user" (defined by it as less than 100 changesets, albeit by the time my main account had 100 changesets I'd sunk well over 100 hours into OSM).

As such, OSM-Revert would not let me revert more than one commit at a time, so I had to revert the user's three SEO spam commits one by one in separate changesets instead of cleanly in one, waiting in between them for Overpass to update (if JOSM didn't make it a pain to switch accounts, I'd just have done it manually). Therefore, this changeset and the other one (reverting the third and second SEO spam changesets) still contains some of the SEO spam added in the first changeset, which was then removed by the final changeset in the revert sequence.

Again, sorry for any confusion and hope that clears things up!

Thanks Pascal! Yep, I figured the issue had something to do with the SEO account making a revised version that still triggered the bot again, which then automatically reverted back to the previous revision, but that version also had (more egregious) spam. Thanks for fixing that corner case!

Of course! Thank you for NeisBot!

Great, thanks Pascal!

Thanks Pascal! By the way, thanks SO MUCH for the NeisBot suite--you are truly doing a hero's work helping eliminate SEO spam on OSM (never mind all your other OSM tools and activities). I don't know what we'd do without you!

(Hopefully the bot doesn't add back the reverted SEO spam text as it did in another changeset)

Hello, if you're going to use OpenStreetMap to promote your business/client, at the very least please take the minimum care to not add invalid tag values. "W" (West) is part of the street name ( addr:street=* ), not the house number ( addr:housenumber=* ), while the suite number is not part of the street name but rather is the unit number ( addr:unit=* ). And as you can clearly see, the name of the street is "West Atlantic Avenue"--everything should be written out in full on OpenStreetMap, so "West" not "W", "Avenue" not "Ave" and "Suite" not "STE". Same applies to your other changesets. Also, the standard format for phone=* in the US is +1-NNN-NNN-NNNN` (although spaces is at least a lot better than the spurious parenthesis in your other changesets).

Blatant SEO spam description removed in changeset/179665276 changeset/179665276