It is almost always useful to add "added", "changed", or in this case "removed" to your changeset description.
When changing and especially when removing tags, it can be useful to mention the reason why you removed a tag. I'll assume here it is because it is redundant.
This will make it easier for users to understand your changes.

Suggested changeset description:
"Removed is_in tag (redundant)"
(Or simply
"Removed redundant is_in tag")

If it was on an object it shouldn't be on, you could also specify this;
"Changed is_in tag on building to addr tag (incorrect)"
Or,
"Removed is_in tag from building (incorrect, redundant)"

Also, it may be useful to discuss with your community if it is a good idea to create a MapRoulette task to remove this tag from all objects in the area. This way you may get community consensus and if accepted, it would be more efficiently removed.
( See also
osm.wiki/Automated_Edits_code_of_conduct )

It is good practice to use the same changeset description, regardless of where or when it was made. If it's related to a notable place, you can add it. Otherwise, you can leave the place out.

Just fyi; consider
1) Is it relevant?
Users can click your changeset and see what coordinates it has, simply by briefly closing the changeset and looking at the url bar, or right clicking the map and asking for the location -to some extent-.
2) Does it help identify your changeset?
Users can query for changesets near certain coordinates using the history page, or the monitoring tools listed on wiki.osm.org .
Most users don't associate coordinates with a place.
Changesets adding the same thing in a large bounding box are not tied to places or coordinates. It is well possible that (nearly) none of those changes are anywhere near those coordinates. To identify a changeset, the following are much more useful - most are already available from your changeset by default:
- the changeset number (unique id), on which the user's changes can be seen.
- the user profile on which the user's history can be found.
- the changeset description to describe what was changed and if needed, why it was changed (ie. if there's a new building being constructed).
- hashtags to group changes into projects -or organizations-.
Coordinates or numbers mostly add clutter to changeset descriptions. They don't convey any useful information which can not be found out otherwise -without looking at the contents of the changeset itself-.
As such, it can be considered as spam.

website should preferably be brand:website or operator:website instead, since it belongs to the chain, not the store itself.

Congratulations on creating
node/9876543210
node/9876543210

Unfortunately I do not have time to give feedback on all your contributions. From a quick look at your manual changesets, they look ok.

Congratulations on the 'symmetrical' changeset number 123454321 :-)

Without streets no OpenStreeertsMap. Or OpenStreetMap. The first one doesn't exist by my knowledge.

Regards,

Daniel

Hey d1sr4n,

Congratulations on changeset/123456789.

Unfortunately I can't review all your contributions.

Feedback;
Changeset comments which are just "tree", or adding numbers ("1", "2", ...) or coordinates, is not very useful for other contributors reviewing your changesets. Use good changeset comments, please
osm.wiki/Good_changeset_comments

Regards,

Daniel

I have sent you a private welcome message with useful information :)

I unfortunately can't give feedback on all your contributions. At a glance the Fremantle ones look ok.

Hey and welcome,

I have sent you a private welcome message with useful information :)

Feedback;

node/6687593708
You can seperate values (ie. artists' names) with a semi-colon (";").

(Sidenote: If the artists or the artwork have a wikidata or wikipedia page, you can add a tag ie. artist:wikidata)

Bicycle parkings:
You don't need to add indoor=no (or most tags *=no) to everything, this is redundant information, unless there exists a risk for others to think it is indoor (when it's mapped really close to a wall). covered=yes or covered=no and indoor=yes if true suffices here. With AEDs, they are usually mapped on a wall, so there adding indoor=no is useful.

Guidepost:
Looks ok

See the wiki for information on tags
osm.wiki/wiki/

Regards,

Daniel

node/9878239217
Name is the name only, so don't add the name "guidepost" on a guidepost, please (unless that is its actual -signed- name)
osm.wiki/Names#Name_is_the_name_only

Zoek zonder de post code, dan werkt het. Dit is (gerelateerd aan)
https://github.com/osm-search/Nominatim/issues/1452

Kanttekening: Als je de post code zelf zoekt krijg je een resultaat, maar geen OSM object, de postcode staat namelijk niet in OSM, maar is wel bij de zoekmachine bekend (vanuit bestaande adressen)

1) If something, ie. a runway, is visible on aerial imagery, someone will map it, regardless of what function it serves or what status it has. A status given only by a single (local) government is not verifiable on the ground.
It is true that (cartographic) representation of certain sites, ie. military sites may be deemed illegal by a country's government and therefore may not be mapped by inhabitants of said country, but can be mapped by those not under said country's laws, unless otherwise agreed by the OSM community (see the Ukraine case, where mapping a country in war would likely do more harm to the country than good)
2) To indicate the type of aerodrome, ie. consists of small runways with little to no infrastructure and is usually used by small planes and not used by public transport, the aerodrome is mapped as a seperate node, unless the extent is verifiable, ie. there's physical barriers around the whole site, in which case it is (additionally) mapped as an area
The same goes for the runway, which can be mapped as a way and to which length and width can be specified, though additionally mapping as area is ok.
3) If you have the local knowledge, a compatible source, or done a survey yourself which shows that
- a certain object, i.e. an aerodrome, is private you can add an access=private tag to further specify this
- a certain physical object or i.e. construction work is temporary (ie. yearly construction work, cable-laying), e.g. less than 6 months (what is considered temporary varies..) then -and only then- you can indicate that by instead leaving it unmapped or (may be better in some cases) instead mapping a node or area with a "note" tag to indicate to other mappers the area is only temporary.

1) osm.wiki/Good_practice#Map_what's_on_the_ground

osm.wiki/Verifiability#Subjective_opinions

osm.wiki/Military

osm.wiki/Russian%E2%80%93Ukrainian_war

2) osm.wiki/One_feature,_one_OSM_element

aeroway=aerodrome

3) osm.wiki/Good_practice#Don't_map_temporary_events_and_temporary_features

The node is synonymous to aeroway=aerodrome + aerodrome=airstrip
(to indicate further details of the landing site as a whole)
"For small or very small aerodromes, aeroway=airstrip can be used; this is preferred in certain countries."
I'm fine with either.
aeroway=aerodrome

The runway which was mapped as an area elsewhere -I did not map this runway- should be mapped as a way aeroway=runway and can additionally be mapped with an area area:aeroway=runway to indicate the area. My focus was purely on adding runways which weren't added yet.

The abandoned: lifecycle prefix is to signify to other mappers that something is visible in some imagery (Bing), but has been abandoned since, which is only visible in Maxar (and regular Esri) imagery in this area. That way the object isn't constantly removed, mapped again, removed, etc.

*to the west

Hey algastroller,

Do not create duplicate or non-existent POIs, please. Only add names with :en/:nl/etc. if different names exist for the same object in different languages. And, in the Netherlands, always add POI tags on the existing address node when possible. Another restaurant with proper name and website already exists
node/2722889418

This changeset has been reverted by
changeset/123147623

Regards,

Daniel

@H4N5-antw iniedergeval is deze verwijdert als foutje;
node/9788922775

Er lijkt "iets" op AIV Vlaanderen meest recente luchtfotografie te staan, maar wat precies en wanneer het er precies gestaan heeft weet ik niet. Het kan perongeluk als picnic gezien zijn (er zijn mappers die vanaf de luchtfoto mappen met MapComplete).

@H4N5-antw allen of specifiek een?

node/6068474211/history
has since been likely duplicated by
node/9142685792/history

Feel free to (re)move/place where the node should be. I don't think keeping them split would be needed.

Welcome (back) to OpenStreetMap!

Please use good changeset comments
osm.wiki/Good_changeset_comments

It would be appreciated if you reply to this comment, so other contributors know you are reading it.

Regards,

Daniel

Hey again,

Looks like you made a small typo in the "capacity" field ("22" instead of "2"). Don't worry, it can happen. I've fixed it for you here;
changeset/122799284

Regards,

Daniel

Hey Laurens,

Welcome (back) to OpenStreetMap!

Building data in The Netherlands comes from the BAG dataset. Any building updates are imported from the BAG manually. The building update you are reporting is not present in the BAG yet. Please report this building update to the BAG using their website (Dutch):
https://bagviewer.kadaster.nl/

Click on the building. In the right menu, next to "Pand", click on the pencil icon "Terugmelden". Be sure to use formal, complete sentences.

Regards,

Daniel

--

This changeset was reverted in
changeset/122798524
(PS: The building was intersecting itself; this makes it no longer display on the map.)