Welcome to OSM. Your newly created roads do not follow the reality. They are away from the real geometry of up to 200m. Please also make use of the other imagery providers available. In this case Digital Globe imagery is available and allows you to draw roads without guessing. Be aware that sometimes the imagery provided is not exactly aligned. So best is to check imagery alignment against GPS tracks first. As a rule of caution: If you are not certain regarding correct placement do not re-align existing things. In this change the situation is clear. I have aligned your geometry. Plese check the exact location of the POI you have added against the Digital Globe imagery and correct them as well. Especially these located away from the main road.

These are the unconnected ones. Are you in the process of adding a separate highway lane for 24 or shall I connect the to the existing road? I didn't want to interfere with ongoing mapping...

node 5345965541
node 5345963620
node 5345965527
node 5345965565
node 5345965705
node 5345965544

You created a lot of unconnected roads to highway 24, eg node 5345963620.
I hope it is due to you being in the process of making it separated by direction. Please check all the road connections to have a routable network. Thanks

You might be really knowledgeable, but hundreds of them including exact elevation? Your source statement sounds a bit strange. Can you please document this import including the source of the data?

I guess you did with best intentions, but your mapping needs a massive rework. Micro-Mapping mostly not justified by landuse pattern. Geometries uneven and partially overlapping/duplicating other features.
Guess your teacher is to blame. Can you please give details who directed you here and failed to do a proper review?

Let me guess: You had been mapping for a class, right? Please give details who directed you.

I guess you (and others) did with the best intentions, but unfortunately your edits lack in many ways.

That tagging is broken. Had you been there at all? "unknown" or "house" are not names.

"not sure" is certainly not the name of way 501292972.

Are you going to revert your things?

A Volcano? No further details and wrong tagging?

I am very tempted to count this as vandalism. Please give some details regarding this.

This is not a playground. It is a live database used by people...

I recommend to move the discussion to the forum thread mentioned above. That way we can document the decision better.

Might be an interesting decision whether to go for addr:*. is_in:* or completely remove those where admin boundaries are available.

I am not too keen on investing time to do a proper revert of something which also took you time to do.

I am personally undecided whether is_in is better or worse than addr tags in this situation. I always considered them only being a mid-term solution on the way to admin boundaries.

The thing to worry about is that some details are lost due to the tag change.

So please let's bring all those details to the forum.

Thanks for responding to the comment.

Doing a mass change of tags is considered a mechanical edit. Whether you are using JOSM or other tools is not relevant in this context.

It seems this change was not discussed with the community. Or was it somewhere?

I see the problem that some details had not been migrated when you changed the tagging.

For example here:
osm.org/node/1684727085/history

you have removed other details, eg:
addr:district หนองสองห้อง

So you could argue that this can be derived from the admin polygones. But same is true for the is_in structure you had added.

Would be great if you could respond in the forum: https://forum.openstreetmap.org/viewtopic.php?id=60482
Opinions are mixed, so certainly something which should be discussed. There is also the option to first revert and then to re-apply the change and this time preventing the loss of details. Or maybe only reverting it partially based on criteria we can define.

this is clearly a mechanical edit. I do not see any documented prior discussion. Please give some details, as I am not convinced that replacing addr:* with is_in:* is the current standard.

Thanks for trying to contribute. Unfortunately your edits need much improvement. Please seek out for some guiding on how to correctly add things to OSM. For example you created some artificial boundaries to the woos which clearly not exist in this way. Also your road classification needs improvement.

Why are you tagging ways which are at best agricultural track as highway=tertiary?
I see you are participating in organized mapping. Please contact your organizer for some training

This is a Buddhist graveyard? As you changed it from cemetery you indicate it belongs to the temple next to it. I know this concept mostly from Europe where a graveyard is next to the church.

The aerial looks much more like the Chinese cemeteries I have seen before...

Right. But locals seem to consider it so important that they print it on the limited space available on the signs.

Typically in OSM we avoid abbreviations in the data. So we add Street instead of St.

If a data consumer wants to generally avoid it then it can be filtered at nearly no cost. See the osm2pgsql Lua script for example. Adding something missing is nearly impossible.

So at least where local people explicitly write something I think we should then add it as well.

You did not create the tagging, but should have noticed that for most of the ways the highway=tertiary is absolutely not reasonable. eg way 274228028
and way 274228023. In tsuch cases please change to something more appropriate.

For example at node 997415485 you did not add the "Ban" to the village name, despite it being written like this on their village sign. Any specific reason for not doing so? I think it should be ບ້ານຫ້ວຍຊຽງ

why is for example way 516234777 not connected to the rest of the network?

way 529811317
way 529811311
way 529811338

and others in that area are clearly residential roads in a newly constructed residential area. Should be tagged as such, not service.