Dear GRAB,
the organized editing guidelines is not something new. We placed the note on the wiki page to make it even obvious to the most ignorant. It simply emphasizes that there are guidelines.
And as others have already mentioned: We wand high quality edits. Those bad edits harm OSM. I have a tendency top use Google Maps in favor of OSM when driving unknown areas, as route guiding on OSM data too frequently leads to unsuitable roads. This is a direct effect of the aim to classify each and every bit of way which appears on aerial imagery.
This might be good bor some benchmark statistics, but it harms the overall quality.
The points of cmoffroad are very valid. Can you please go a bit into detail on how you plan to prevent such issues from happening in the future? currently you just stated that you follow rules and everything is fine from your perspective.
Obviously this estimation of your mapping quality is not in line with the estimation of the community.
We are all aiming to get the best data in OSM possible. This strive for quality is what was leading our mappers to get in touch with you. The simpler approach would be to ask DWG to block and revert your edits in Thailand.
So please work together with us to improve the quality of your edits.
What quality assurance procedures do you currently have in place? What further optimizations do you plan to implement?
When looking at your recent edits: Have you checked about Objects where your edit was reverted and analyzed what was leading to this? Did you use such feedback to optimize your internal processes? Did this lead to some additional training for your editors?
Have you added a review process to double check such kind of edits? Especially those where the exact tagging is not 100% clear?
The community appreciates companies improving the data. But notice the word “improving”. It is not about selling services to do as many data edits as possible. The resulting data after your edits has to be substantially better than before.
Thanks for your understanding and looking forward to get some details on how you plan to improve the mapping quality.
Stephan