Hello, this edit has broken the border. You have modified 7 ways, 16 relations, and 52 nodes. Calling it a "correction update" is not a reasonable explanation. Can you please state what you have changed and why.

Hello wambacher, I am trying to understand why you changed the boundary between India and China at this location. I am unable to access the source you specify. Can you explain?

Looks like greyim has moved it now: https://pewu.github.io/osm-history/#/node/7639755993

So no more discussion is needed here. Thanks greyim.

Hi greyim, I am sorry, neither of these sources has any information about where the clash took place. Nathan Russer, the only one who speculated about it, said it was adjoining the LAC: https://www.aspistrategist.org.au/satellite-images-show-positions-surrounding-deadly-china-india-clash/

He greyim, can you specify the actual source (news or analysis) that identified this location as the clash site? This looks too far back to me.

No, none of the satellite overlays available with OpenStreetMap show any permanent constructions anywhere in the Galwan Valley, except the Chinese Galwan Highway as currently marked.

Actually, this particular line is the boundary of Changthang WLS. But it is apparently sharing nodes with the LAC, which is represented by the "way" 201864296.

It is the Line of Actual Control between Ladakh and Aksai Chin. China called it its "traditional customary boundary" in 1960. Now it seems to have changed its mind.

Thank you, Kharbin. Nicely done!

Source: https://theprint.in/opinion/indias-fingers-have-come-under-chinese-boots-denial-wont-help-us/435145/

This border was supposed to represent that from the LSIB3 database. You cannot modify it as per the Chinese maps. It is an international line.

Hi PlaneMad, you seem to have fixed a lot of the problems introduced in the previous edit. Thanks a lot. But Uttarakhand boundary is still not closed at Kalapani:
osm.org/relation/9987086#map=10/30.1672/81.0297

It is being called "Mahakali River", also "Sarda River"/ "Sharda River".

I don't know what you mean. India didn't change any international boundaries. So there was nothing to reflect.

For Kalapani, the old line still shows. The new one will probably take a while to show up on normal display.

Hi Shressundar, all I did was to rename "Kalapani territory" to "Kalapani-Lympiadhura disputed area", since the area has now grown beyond the Kalapani area to include much larger territory. All the other names are still present. As for country borders, I don't even know how to change them, but I suspect that they are decided based on international maps, not merely by one country asserting claims.

Yeah, sorry, false alarm. After further investigation, I figured that your source for the river is quite right. It is on Wikipedia now.

Hi voidvector, I see a saddle point at
35.30137, 78.30896
So the river can't extend to the east of here.

I changed this to "headwater" rather than the main Tinkar Khola as per this map:
http://ai.stanford.edu/~latombe/mountain/photo/nepal-2016/nepal-2016.htm
But it is not yet updated correctly. Experts, please help!

I still don't understand. Wikipedia says, "Kalapani is a territory disputed between India and Nepal, but under Indian administration as part of Pithoragarh district in the Uttarakhand state". This is showing correctly up to map resolution 12, but at resolution 13, it is showing the Nepalese boundary as being correct, but the Indian boundary as being a claim line. This is the strangest thing, the kind of which I have never seen before.

Note also that Wikipedia is being flooded with loads of Nepalese editors trying to represent their national point of view. You shouldn't depend on Wikipedia. The LSIB database has always been correct. There was no need to change anything here.

I do not quite understand what has been done. But the border looks correct up to map resolution 12. For resolution 13 or higher, it shows the Nepalese claim line as the real border. Should there not be a way for the Nepalese claim line?