id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
23869	By default, 'upload of changes in chunks of size' should be geographically close	merylstreet	team	"I use this feature to break big changesets into chunks but the upload seemed to pick modified objects at random for each batch. I tried to investigate the code that does this upload but I'm not a professional coder...didn't find answer to my question.
Is there a way to upload chunks by geographical proximity? 
I saw the upload order is ""all nodes first, then ways, then relations"", how does it pick the order of each modified node? By order of appearance in the .osm file or something else?
Sorry if this is not the right way to ask for this feature or if this already exists, I'm new here and didn't find the info in the docs."	enhancement	closed	normal		Core		wontfix	upload chunks	mmd