What happened here? A (service?) road leading to the temple tagged as tertiary, nearby highway=road. eg way/568301907

Are you going to revisit that tagging?

why is nearly everything tagged as highway=tertiary? Most of them are clearly not...

While I agree, that way/384629995 is not necessarily an agricultural track, it is certainly no major highway of the arterial network. So highway=tertiary is absolutely unjustified. I'm changing it to a highway=service as it seems the only thing it serves is the cemetery.
In case the area nearby the railway crossing is residential, a highway=residential might be an option as well.

you deleted a lot of highway=* classifications when adding the durface. Did you replace/rename existing tags instead of adding a new one? I fixed some, bout would be nice if you could review the other edits you did during this time to ensure that others got their tags back as well

you repaired some, but for example residential way/559328577 is still tagged as secondary

residential roads are no major highways. please use appropriate tagging

I repaired your bad tagging before. Why are you breaking it again? Are you trying to destroy data? a residential road is no tertiary highway.

Will you fix it yourself?

Do not use highway=tertiary for residential roads. The key "maxspeed" is for tagging signed speed limits. So there has to be an official speed limit sign. It is not used to tag the typical/recommended speed. Please double-check this.

In English there are spaces between words. Use Thai script in "name" and English/RTGS in "name:en"

Hello and welcome to OSM.
Thank you for your contributions around ซอย 3 หมู่ 9 ตำบล นครปฐม. Please double-check the tags you choose. Here you selected highway=tertiary for residential roads. This will lead to problems when the map is rendered. Also make certain that crossing ways are having a node at the crossing point. Without this a routing engine can not understand that it is possible to get from one way to the other. So it would not allow you to turn there. I fixed the issues for you already. You still might to go back to the area to add street names. Use the "name" for names in Thai script. "name:en" for English/RTGS.

Please do not use abbreviations for names. It is impossible for an algorithm to expand these in all conditions while it is simple to shorten them by software. So write "Road" instead of "Rd."

Please also avoid using the tag highway=unclassified. This does not mean that you don't know the classification. It is actually a way to mark roads which for example connect villages to the main highway network but have not yet received a classification (from DRR, like the 4 digit numbers)

As mentioned in another comment, please make sure to use correct tags. Otherwise data consumers can't make sense of your contributions. Worst case it won't be considered at all. I fixed residential roads tagged as highway=road instead of highway=residential. Also parking isles also have their own tagging.

Welcome to OSM.
The way you added is a typical residential way. So please tag it as highway=residential. It is important that we use the correct tags in OSM as the data will be used for many purposes extending the simple display of a map. way/559992740

Please feel free to check out the forum in case you have questions regarding how to best tag things in OSM.

way/555897421:
is tagged as footway. But has additional tags to allow cars/motorbikes. Could it be simply a very narrow road? Maybe highway=service together with service=alley. Or is it a one-lane residential just wide enough people can get their car in&out? would be lanes=1. There is a note mentioning a free public parking. Is this still there? Would then be worth tagging and marking the note as resolved. note/810618

what are you doing? First you deleted hundreds of way, and now adding them from scratch?

A nice first edit. Check out the different imagery layers you can use. You will notice that some offer details others don't. Also take note that sometimes the roads look shifted on different layers. Best is to compare the imagery position with GPS traces available and choose the best fitting one. Just as a hint: don't re-align existing roads unless you are absolutely certain about the better alignment. (don't worry, you didn't do).

With your mapping I have a question: You added a highway=residential with an angle. There is another road continuing to the east. I added this now. Could it be, that the north-south section is a different soi? Maybe it even has a name? You could re-visit your addition and add a name to it. We tag the name in Thai script in "name". The RTGS with Latin characters would be in "name:en".

Hello,
welcome to OSM.
You added a short way leading to administrative buildings (way/556677629). The road classification in OSM is quite important. unfortunately "secondary" is the wrong type for such a way. I changed it to "service" which matches much better the function of it. I recommend to reach out to other mappers to get some support in case questions come up about how to exactly add something to OSM. You can send me a message via OSM if you need support.

what happened here? node/4990576441

a huge gap in a major highway. I have re-connected the ways based on aerial imagery to have a routable network again...

Hello and welcome to OSM Thailand.

way/555900975: Please explain what you mean with oneway=reversible. I know that sometimes entry to a road from one side gets blocked, eg during busy hours. But infrequently reversind the one-way? With this being in Bangkok nothing is impossible, but please clarify. Same for way/402310959
and way/555900974

way/555900976: In Thailand we don't have the legal concept of a living_street. It's a highway=residential. Also adding all those special sub-tags like horse, etc is not necessary and is typically only added if it differs from the norm. Same for way/555900977.

In general, please make sure that your ways are connected to each other, otherwise routing is not possible. Also keep roads with are not needed to be separated for mapping reasons connected together. Gap at node/3585868101.