Your changeset make this forest to a deprecated tag “landuse=wood”
www.openstreetmap.org/way/756287734

Dear local editor:
This fix is to make those points have a more wildly used tag value.
You'd better use lowercase character and underline to create a value or key.

Thanks.

同学你好，感谢你对良乡校区的完善做出的贡献，良乡这边六月以后就没再去过，文教楼也是，所以形状上都把握的不是很到位。如果有兴趣可以试试加上高度标签做成三维的

BTW, thanks you for your contribution!

If you noticed this comment, that is because you are confused by "Hengqin Dao" added in this changeset(changeset/107833965)

Dear Apple mapper HindmarshSquare:

According to the multilingual name guideline for Mainland of China(osm.wiki/Multilingual_names#China), you should use Simplified Chinese as "name=*", and "Hengqin Island" should be put in "name:en=*"

But don't worry, we will fix those tiny problem. Next time you can try some translator, and if we noticed a place with non-Chinese name, we will help you refined it manually.

Dear Apple mapper HindmarshSquare:

According to the multilingual name guideline for Mainland of China(osm.wiki/Multilingual_names#China), you should use Simplified Chinese as "name=*", and "Hengqin Island" should be put in "name:en=*"

But don't worry, we will fix those tiny problem. Next time you can try some translator, and if we noticed a place with non-Chinese name, we will help you refined it manually.

关于这次修复的Tag总计：

cuisine=中餐
cuisine=饺子␣(jiaozi)
cuisine=烤肉
cuisine=中餐，酒，饮料
cuisine=中餐;早餐
cuisine=炒菜，干锅，面条，米饭
cuisine=北京味道;炸酱面;饺子;炒饼
cuisine=热干面;包子;饺子;炒河粉

一共是这些，全都非常傻逼

I make this change because of the inspire of this Pull Request in NSI on github:(https://github.com/osmlab/name-suggestion-index/pull/5283)

I think you want to type "kebab" so I do this changes, If not suitable, just revert this changeset and meke "kebap" again.

I make this change because of the inspire of this Pull Request in NSI on github:(https://github.com/osmlab/name-suggestion-index/pull/5283)

I think you want to type "kebab" so I do this changes, If not suitable, just revert this changeset and meke "kebap" again.

I make this change because of the inspire of this Pull Request in NSI on github:(https://github.com/osmlab/name-suggestion-index/pull/5283)

I think you want to type "kebab" so I do this changes, If not suitable, just revert this changeset and meke "kebap" again.

I make this change because of the inspire of this Pull Request in NSI on github:(https://github.com/osmlab/name-suggestion-index/pull/5283)

I think you want to type "kebab" so I do this changes, If not suitable, just revert this changeset and meke "kebap" again.

We will pause deleting population for a while, but I think you can ask DWG for those china_population problem.(The solver should be familiar with China problem)（Here are votes for this new tag：osm.wiki/Proposed_features/china_population）

Maybe call DWG will be ultimate and put an end to this problem, because we didn’t want to be enemies of world editors at first

If we fight with render developer, I hope that those comment in this changesets can be evidences for edit render way.
(And wish someone "fixing population"can help to improve render)

You should judge what level of place it is based on adminlevel, not based on population.
Population is inaccurate. China’s population is completely different from that of the West. The accusation of china_population is based on the stereotype of the Western model’s global promotion.
This is data tyranny. So will you face the true problem we faced? You helped? You only removed!

Here is a question usually talked.
A is a county level town with 2000K people, B is a prefecture level city with 300K people, which should be prefered?

> this is not a valid reason to remove correct tags, such as population tags

Do you still think this is correct? What is correct?
The correct way is to face the complexity of China's administrative level and significantly larger population than a western town, to use more region defined tag to render correct, instead of accusing others of "your tag is wrong"

Using this way to tag is to solve problem, not create problem

This changeset will be revert immediately as the same way you revert it.

Deat Mateusz Konieczny:
Please stop your singal revert.
This tag is to preserve exact population data not removed by other mapper, because they will think osmcarto do wrong render by population.
If render is not suitable and you find they are hard to communite (not say issue, you can't know how stubborn those people are), the only way is change a tag to describe, utill one day they use correct way to render.

If you still think "do not tag for render" is strict and can't violate by anyway, at any situation,
We only can say that correct render of administrive is strict to us too, and to satisfy your request for "correct tag way"
And, at that time, population and china_population all will be removed, so render is OK, your "guideline" is OK, leave data-completeness to be the victim, will that world you dream?

Hey brother, it looks like you are not malicious, but maybe you really don't understand China's administrative divisions, which are more complicated than what Key:place in OSM can provide, so we use the Key:china_class to improve administrative divisions. If you have paid attention to the guide in Key:admin_level, it will also remind you to refer to the Chinese document first.
In order to better repair the previous data, please suspend the modification of administrative jurisdiction in Western China. Thank you very much for your understanding, and thanks for your knowledge in local language.