Thanks for helping with the SDP project! Names should still usually follow OSM conventions, and be converted to title case: osm.wiki/Names#Uppercase_characters Also, as part of the MapRoulette task you're supposed to watch out for duplicates; in this case, an address node already existed nearby (though it's fine if you know there's more than one thing at this address).

Please use the changeset message to describe what you changed and why. For example, "Change construction_year tag to the documented tag year_of_construction". There are more examples here: osm.wiki/Good_changeset_comments

Traduzione automatica: Si prega di utilizzare il messaggio del changeset per descrivere cosa è stato modificato e perché. Ad esempio, "Modifica il tag construction_year nel tag documentato year_of_construction". Ci sono altri esempi qui: osm.wiki/IT:Good_changeset_comments

Please use a more descriptive changeset message. For example, "updated population". osm.wiki/Good_changeset_comments

If it's accurate. If the units really don't exist then they should be deleted, but there are plenty of churches that are just one unit in an office building, and there are plenty of churches that have multiple mailboxes.

I've reverted your change. "name=golf" is an invalid tag, and the areas are multipolygons, not boundaries. See osm.wiki/Tag:leisure%3Dgolf_course#Common_mapping_pitfalls for golf mapping guidance.

Why did you delete the cross-shaped building? I can still see it in recent aerial imagery. If both parts are actually one building it would be better to make them into "building:part"s.

Please remember to save your changes in one area before moving on to another, to keep changesets to a reasonable size.

This is not redundant. It included the unit number range, which could be added to the building, but ideally each unit should have its own address point at the correct location.

By removing that road, you've broken the connectivity of the service road, and also left a misleading foot crossing.

Welcome and thanks for contributing to OpenStreetMap! Please use the changeset description field to leave a message about what you changed and why—for example, "Improved building and address alignment." There's more information here: osm.wiki/Good_changeset_comments

"Privacy" isn't a valid reason to entirely remove verified objects from the map. In fact, emergency services have found OSM helpful specifically because it includes off-trail landmarks, paths, and houses that they can use for navigation. See here for more information: osm.wiki/Why_we_won%27t_delete_roads_on_private_property Or the 2nd-to-last bullet point here: osm.wiki/Limitations_on_mapping_private_information

Especially for such large a bounding box, I'd appreciate more details in the description as to what the tag fix was and why. Like, "Change all 'historic=petroglyph' to 'historic=archaeological_site'+'archaeological_site=petroglyph', a more established tag".

Welcome to OSM, and thanks for your contribution! Here's a tip: You can automatically make the corners of a building perfectly square by right-clicking it and selecting "square," or by selecting it and pressing "Q" on your keyboard.

Could you please use more descriptive changeset messages? For example, "Added a new dojo according to local knowledge." There are more tips here: osm.wiki/Good_changeset_comments

Why is access=no necessary? It's already implied from highway=motorway that mopeds, horses, bicycles, and pedestrians are not allowed. See osm.wiki/OSM_tags_for_routing/Access_restrictions . Adding access=no will tell many apps that don't support detailed access restrictions that the road is closed even to motor vehicles. If you're using an app that thinks highway=motorway is bicycle-accessible, that should be fixed in the app.

Fixed in changeset 130050657

If the buildings have finished being constructed, they should be re-tagged, not deleted.

I think lanes=1 would be better than either oneway=yes or narrow=yes

Welcome to OpenStreetMap and thanks for contributing! Some feedback: Please save your changes in one area before moving on to another, since that makes it easier to review. Second, you can press the "i" button on a field to read more about what each one is meant to be for. For example, "description" should be used to add additional, factual information about a feature, not your own notes or reviews—see osm.wiki/Key:description . That wiki has a lot of information in general about what features can be mapped and good practices for mapping them. Finally, the message when you save your changes should describe what you changed and why—see this page for tips: osm.wiki/Good_changeset_comments

The aerial imagery is offset here. Please use the building placement as reference rather than moving them.