这条路是没问题的，lockdownguy的bad标记完全莫名其妙，@lockdownguy 应当注意自己在osmcha上的言行
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108333837

虽然绘图质量和精度确实不高，但这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108281889

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108280532

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108279677

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/107790529

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108176815

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/108176815

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---

Published using OSMCha: https://osmcha.org/changesets/108176538

这条路是确实存在的，只不过因为在沙漠中并不能很好的找到，同时名字会使人误认为这是历史上才有的道路。lockdownguy在osmcha的指控是不正确的
---

Published using OSMCha: https://osmcha.org/changesets/108176538

这条路从最高等级的卫星图上看依然是有痕迹的，因此我认为lockdownguy的bad标记是不正确的，这条路应当被保留
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/107789837

Hey guys! There are three item that have a odd key ```fixme:name:<lang>```, they are osm.org/way/219614364 , osm.org/node/2440289063 , and osm.org/node/7185830521

Using taginfo I only found 3 item have this tag, so I guess if they have a better way to describe.

Wish all the best！

你删了这么多路，可否给个明确的解释？以及当时我在软件园区添加了若干的人行道和斑马线，现在似乎全部被删除了，兄弟有什么头绪吗？

兄弟你好，建筑物需要保持building的标签

Don't use the key:construction=* in the planning area, which means that the construction has already started. If so, you can tag it like this, but I guess you mean "long-term planning", it just stays on the blueprint, so I think this should be tagged with Key:proposal=*

——LaoshuBaby 6.12.2021

规划中的地方就不要用construction了，这是代表已经开工了的意思。如果开工了可以这么标记，但是我看你意思是“远期规划”，就是仅仅停留在纸面上，这种应该使用proposal标签
——快乐的老鼠宝宝 2021.6.12

Hello, sir/madam, noticed that in your mapping, the ref H1 has been added to the entire ring road, but I didn't find the source. Could you please explain for this? Or I will delete this ref in 7 days.

------LaoshuBaby 6.12.2021

Hey guy! According to the multi language tagging guideline of China Mainland, you've made wrong edit with administrative-villlages' name.
Such as this, n7852000028
You can find more details in this osmwiki page.(osm.wiki/Multilingual_names#China)

Anyway, when OSM-Carto renders, it never considers our tags defined by the local community, right?
So even if we write down the real population data, whether it is the subkey of population, or a single china_population key, the final result is still that OSM will refer to the key of population to render.

So why just keep the de facto using method?

It is not appropriate to use population: cadc to describe population, an attribute belonging to an administrative entity, because cadc is already an attribute attached to the administrative entity, not an entity.

Cadc is just a control key for goverment to statistic people and govern more exactly.
And, china_population is for a more large range of admin_level, if the true population will lead a mistake in render.If you use a Key like population:cadc, it can't show the original purpose of using this new Key.
The point is the viliage/town/others, and it have a cadc(static or variable), it is itself!

Emmm……that's because cadc is just a code, not a exactly population number.
China government use a code to define a exist administrative entiries, like you use ```de``` to define Germany, or use ```us``` to define United States.
But we need a exact population number so we using this tag to contain it.