Please save your changes before moving on to another area, and please keep HOT project changes within the area of the task.

Hello and thank you for contributing to OSM! In the future, please save your changes in one area before moving on to another; this keeps the total changeset size small and therefore easier to review.

If you use JOSM, the Java OpenStreetMap editor, you can download data, edit it, and save it to a file, then open this file in your program.

Yes, that kind of description is good! Even though I can click through to see what objects you changed, it's not always obvious what you changed about them, and it's helpful when reading through long lists of changesets to know what each of them changed without actually clicking through (otherwise, the changeset description would be useless!). The wiki page I linked goes through these and many other reasons why descriptive changeset comments are useful.

Make sure you're looking around for duplicates before you add something! The building was already tagged with the shop information.

In this changeset you removed one lane from turn:lanes and vehicle:lanes on Berryessa Road, but did not remove the lane from bicycle:lanes. Please make sure that ALL values with key ending in :lanes have a consistent number of lanes. Also consider if by removing a lane you are removing information. Here, you removed the bike lane, removing the information that it is to the left of the turn lane.

Could you please try to be a little more descriptive about what you changed any why? Like if it was road realignment, lane tagging, new building traces, something else, or some combination. Here are some more suggestions: osm.wiki/Good_changeset_comments Thanks!

Please save your changes in one area before moving on to another, to keep the changeset size down. Also, please use the changeset description to describe what you changed and why; for example, "Added parking lots and service roads". More examples here: osm.wiki/Good_changeset_comments

Please remember to save your changes in one area before moving on to another, to keep the changeset bounding box small.

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 leisure=golf_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