Seems to have been a breakdown of the copy buffer - haven't seen that before. Fixed now.

Thank you! Not my intention. I am seeing more residuals in changesets that aren't closing properly and have yet to trace down the source.

Touché

I am very sorry to have caused you trouble, but you are the first person in many years to express value in the tag semi-mindlessly imported a decade and a half back that most US contributors consider irrelevant. The number one thing I have worked on for more than a decade on is aligning routes with alignment errors per Ian Dees' JOSM overlay using the best available imagery I can find for an area (WV lacks good ortho imagery). As the wiki says, there is no agreement amongst editors as to the fate of the Tiger:reviewed tags. I am in the camp that at this point considers them "dross". My apologies if you have found them otherwise.

Good to see you tackling my 7 year old note. Just do be aware of the copyright marked at the bottom of the webpage you have referenced. Kindly reference this page of the OSM wiki: osm.wiki/Copyright

I'm calling shenanigans on this changeset. There's no lake at or anywhere near where this created one. Instead, there are six buildings and a half dozen trees on this grass covered block. Vandalism deleted.

I have moved the text of your edit to a note tag on the building. As others have pointed out, your text misuses the purpose of the building name field. Pls see our basic best practices guidance at: osm.wiki/Good_practice#Don.27t_use_name_tag_to_describe_things

Fortunately, the note you had created and closed showing where your house is was still fresh enough I could find it. In the future, so similar needs, notes are the way to go. Commenting on a changeset only tells us the thing that needs to be changed is somewhere in a pretty large area. All the best.

I am actually on record as of 2015 raising objection to unguided imports of SF addresses - see osm.org/user/Alan/diary/35341 Working essentially alone as I am, it may be slow going but I can't create the large scale havoc of an import. I have spent an hour or more a day for nine years cleaning up the Tiger import mess. If one were to mix the errors in the SF Enterprise Address DB with the errors in the Mapbox building placements, it would leave an enormous mess. I would truly need convincing to believe it would be otherwise.

Thank you for your QC contribution. I've entered more than 30,000 addresses in SF by hand and doubtlessly there are errors. Since the city's Enterprise Address system is often incorrect outside of residential areas, I field survey business districts using Vespucci, but rely on it in residential areas. I obtained permission (and support) from SF Planning to reference their website at https://sfplanninggis.org/pim/, which is tied to the Enterprise Address database. I have also found and reported errors it for incorporation in the Enterprise DB. The area of your contribution is made doubly difficult because the Mapbox imported Lidar building outlines in the hilly areas of the city are often mispositioned by 15-20 m or more, and are often missing whole buildings as a result. I do my best to correct these as I go but the task is almost overwhelming in scope. I would caution that you reference Google Streetview. While the wiki is unsettled on this, the consensus in the forums is to rely strictly on Mapillary, Openstreetcam and Bing's Streetside as these entities provide for unrestricted use in OSM. In SF, you will find my contributions to Mapillary second only to those of Mapbox. All the best and thanks again.

Thank you for the fix - as I recall the imagery available at the time was as a dark as the interior of a cave. Hope you are well sir!

I neglected to properly respond with a thank you Steve for all your contributions. I would love to clean up the mountain edges of SC more but am challenged by the imagery as we all are. I continue to edit around where I am in town and hope you will continue to also.
AS

Welcome to OSM - you seem like a fairly new contributor. None of my 2.2M+ changes have been performed using imports, a term which has a specific meaning in OSM. Instead, in the last few months when I edit in Maproulette, I switch from JOSM to Facebook's new RapidID editor (see link in changeset above). There's a number of useful things you can do in that editor not currently possible in JOSM, including manually selecting MS bldg outlines one at a time as part of the of editing session. Not all the the MS detections are useful - I talk about this in the OSM Slack session dedicated to AI assisted editing, but much of what's there is useful, some of it with rotation required. In some cases, extensive follow up in JOSM is required for precision, which I usually reserve for large civic buildings like schools, universities and hospitals. That said, you should check it out.

I'm going to move this reference to a place Steve once lived from Name to Note as consistent with our rules, we "map what's on the ground" and this is not a Name for this structure. In addition, like almost all houses in the Sunset District, it's not detached (see Wiki: osm.wiki/Tag:building=detached) but attached on two sides, and thus should be tagged simply as building=house.

Pls be careful to avoid unintentionally moving nodes when editing. This changeset moved Tart-to-Tart 1-1/2 blocks from it's actual location into the middle of a parking lot.

I have some serious concerns whether the this import was sufficiently accurate to add value to the map. As a cyclist in SF, I get no benefit from knowing a lockup is in the general area as most of these imports wound up 75 feet from where the actual parking location is and, since the Mapbox building import, generally are depicted now as deep inside a building interior. As an OSM'er - I am spending a lot of time using Vespucci in the field, and Mapillary and common sense in JOSM trying to clean these up.

Welcome to OSM. Thank you for your recent edits. It's great to see new contributors!

Can I ask you to please re-review the edits made in this changeset with respect to the OSM wiki standards for housenumbers: osm.wiki/Addresses

It appears you are using Chinese characters in lieu of Arabic numbers, which is inconsistent with the regional address system and creating QA flags such as this one: http://tools.geofabrik.de/osmi/?view=addresses&lon=-122.48864&lat=37.75353&zoom=18&overlays=buildings,buildings_with_addresses,postal_code,entrances_deprecated,entrances,no_addr_street,street_not_found,place_not_found,misformatted_housenumber,nodes_with_addresses_defined,nodes_with_addresses_interpolated,interpolation,interpolation_errors,connection_lines,nearest_points,nearest_roads,nearest_areas,addrx_on_nonclosed_way

Thank you in advance.