reverted

I've fixed the road deleted here

I've fixed the road deleted here

I've fixed the road deleted here

I've fixed the road deleted here

I've re-added the road deleted here.

I restored a part of SH236 that was deleted here

I re-added two roads in Faridabad that were deleted in this changesets

fixed road deleted here

road deleted here was restored

road deleted here was restored

restored the road deleted here

This changeset deleted an unclassified road. Restored here
changeset/68915596

fixed

Hi Favas007, you deleted a road here. I've restored it now.

Hi Halloween123, you deleted a road here. I've fixed it.

Hi LiJuThomas, you deleted a road here. I've restored it now.

Hi, thanks for fixing it. At the moment I really don't know how this error can happen (I never doubted it was non-intentional). The curious thing is it only seems to happen to a somewhat defined group of paid mappers who map roads from gps traces. Your changeset is the only exception to that that I found. I also took some samples in other random countries (Iran and Turkey) and there I didn't find any orphaned nodes resulting from deletions.

FYI I've uploaded a list of deletions I found here changeset/60215392.

I think an error like that could occur if the data is somehow downloaded so that there is a hard cutoff at the edge of the bounding box of the download. Do you use the regular "download map data" button in JOSM? Do you then use the tabs "Download from OSM" and "slippy map"? These are the default active tabs. There are number of other options to download data here, but I never looked into these.

Thank you for answer! I never realized there was an extra delete mode in JOSM. And you're right: alt+clicking on the way deletes the way but not nodes. But that still doesn't explain how one can accidentally split the way. Moreover, these deletions always occur at the edges of the bounding box. For example, in this changeset changeset/66150424 three roads were cut at the top edge of the bounding box.