Hello,
thank you for adding all these features.
Please note that confusingly, the correct tag for public things is access=yes, not access=public.
Don't worry, I already fixed it with the parking space at the library and also the two other parking spaces earlier, just please keep that in mind for future edits.

Thank you and happy mapping!
Jonas

Hello,
I think on way/225136415 there is a typo in the maxspeed value. What is the max speed there?

Thank you and happy mapping!
Jonas

Hello,
I think on way/160725219 there is a typo in the maxspeed value. What is the correct max speed?

Thank you and happy mapping!
Jonas

I reverted this edit as part of my cleanup of unexpected maxspeed values.
If this user regularly makes edits that are this bad and refuses to communicated with other mappers, I recommend contacting the data working group.

You should try out https://opengeofiction.net/. It is a clone of osm, but instead of the real world, you can make up a fantasy map there.

See previous comment

changeset/186423424

Hello,
please note that trees are only supposed to be mapped as nodes in osm. Individual trees mapped as ways will not get rendered on the map and do not have a place in the data structure. Please do not trace any trees as areas in the future.

changeset/186422353

Hello,
Thank you for adding all those details.

Please note that individual trees should only be mapped as single nodes. natural=tree on a way is not allowed. I fixed this 7 hours ago, sadly you deleted my correction and re-added a "wrong" tree, along with 16 others.

Hi,
Thanks for pointing that out! It's a bug with the function that lets you follow an existing path, I see you also already brought it up on the discord.

Hello stoney,
thank you for adding all those golf course details!
Plase note that you're drawing the center lines the wrong way around: In FairwayMapper, you have to start the lines at the tee boxes and finish them on the greens. FairwayMapper also automatically adds the pins to the end of the line, and yours appear in the tee boxes instead of the greens.
I will fix this right now for the holes you already mapped, so don't worry about them, but please keep that in mind for future edits.
Thanks and happy mapping!

Hello,
Thank you for adding details to this industrial area!
You tagged some streets with access=public. I changed that to access=yes because confusingly, that is the right tag for public places. However, are you sure that these are public? The whole area is private and then there are 6 smaller roads mixed in seemingly randomly that are supposedly public. It seems like that might be a mistake because people couldn't even get there without walking over private roads?

Thanks and happy mapping!

Hello again,
thank you for adding all those parking spaces!
Please note that confusingly, the correct tag for public features is access=yes, not access=public. I fixed that already, so don't worry, but it would be great if you could keep that in mind for future uploads.

Thank you!

Hi,
I am a real person. i think it is because your account is new. There has been some vandalism in the past so now new accounts can't change too much at once. I think it's currently set to 1000 edits per hour.

You can read more about that here if you want: https://heigit.org/analyzing-the-changesets-of-osm-newcomers/

So you just need to wait a bit before adding those bus routes.

Happy mapping!

Yes, the correct one to be used for public areas is just access=yes. This is mostly important for routing engines or other 3rd party services that automatically parse the data, so having standard values is especially important for those.
As with every openstreetmap tag value, you can make up any tags you like for cases which are not covered particularly well with the established standard values, but in this case, yes just does the job.
See access=* for more on those values.

Happy mapping!

Hello and thank you for adding all those camping grounds!
Please note that the correct tag for dog is dog, not dogs. I fixed this everywhere!

Thanks and happy mapping!

I apologize for the change set bbox size, I thought I had removed that one edit from the changeset.

The node and way id mixup also occured here. Please fix it before editing anything else on osm with that app

The same issue as in changeset/183732921 with mixed up node and way ids also happened here. I fixed it. Please make sure your app handles way IDs properly.

Hello,
It seems like there is an issue with your editor. Osm counts up ids for nodes and ways separately. You tried to edit way/115767704, which is the church in denmark, but you actually added the tags to node 115767704, which happens to be a random node of a street in Lousiana, Usa.
As far as I can see, the tags you added were all already on the church, too, so I just removed them from the wrong street node.
It would be great if you could further investigate how it came to this mixup (programming mistake vs user error for instance) to understand how to avoid it. A lot of newer editors are vibecoded and have this very mixup problem, unfortunately.

Thanks and happy mapping!
(An other) Jonas

My main argument for having it there is that the main purpose for having that tag in general is not for people to look up what a word means or who a certain person was if they don't know, which I guess is where usually etymology comes from. I think it is rather about having the data set for whatever social analysis people want to do. There are residential areas where every street is named after a species of tree, and an other one where every street is named after musical instruments, and all of that is very interesting in my opinion. The point of wikidata is to have this public knowledge structured in a way that allows for those analysis, and in some way, linking osm and wikidata is just an extentsion of that wealth of data.
A human looking at a map knows what a raspberry is, but the more of name:etyomlogy:wikidata tags exist, the more it will be possible to analyse how societies honor people, places or concepts by naming their streets.
I do understand where you're coming from though. I think I will keep it there, mostly for the aforementioned reason, but also because it's not wrong and although it might technically be unnecessary in some view, it doesn't hurt having it.