id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
12601	By default upload objects in chunks of 100	planemad	team	"Many of the mapping disasters I have come across in OSM are due to large JOSM changesets going bad. Examples:

* https://www.openstreetmap.org/user/PlaneMad/diary/35762
* http://tasks.openstreetmap.in/project/28

Both changesets were created with JOSM and was massive (>1000 objects). A network error or interruption during such an upload is a recipe for disaster. One will end up with unsynchronized data, conflicts, duplicates and a frustrated mapper can easily lose patience trying to force his changes as there is little help available on what to do in such a scenario.

I always upload in chunks of 100 objects as a default, so that recovery from a failed upload is less painful. This should be a default setting in JOSM and only advanced users should change it if they feel necessary.

Note: This is a bigger concern in developing countries where internet connectivity is not reliable and interruptions are common."	enhancement	closed	normal		Core		duplicate