id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22947	Download along gpx feature request	mrgenie	team	"I sometimes have larger areas to download or areas with high node/way/polygon intensity..

Selecting 1sq km as ""Maximum area per request"" takes ages especially due to the large distance to the servers in Amsterdam the latency is quite high. Selecting 25sq km reduces the amount of requests, and thus the stacked latency issue - and works for rural but getting closer to the city you get errors... data size to big.

So what I do to minimize the download time:
first download in ""maximum area per request"" of 25 sq km (5000m for download everything within...)
manually click away the notification of errors
download in ""maximum area per request"" of 16 sq km (4000m)
manually click away the notification of errors
download in ""maximum area per request of 9 sq km (3000m)
manually click away the notification of errors
download in maximum area per request of 4 sq km (2000m)
manually click away the notification of errors
download in maximum area per request of 1 sq km (1000m)

at this point I never had an error anywhere 


This could be automated .. so my request is adding some setting for the user to choose this way of downloading - automatic adaptive downloading 

if the user selects this - then the plugin will automatically try this concept itself to download first the largest possible download area - and for the missing parts due to errors - skip notification and automatically adept to a smaller max download area in a step by step approach to always use the max possible area that makes sense and the few areas where density of data is too high and thus can't be downloaded ni a single download - reduce that automatic download area.

I found the
5000m, 4000m, 3000m, 2000m, 1000m the optimal approach for me but I suggest to cover any possible future density increase 500m and 100m could be added as well to ensure this automatic adapative download is capable of catching literally anything.

error notification should then only be enabled for the final step - if that's still too big an area to download.

in case of 100m as final step I strongly doubt that, but hey the feature would at least cover every possible scenario then."	enhancement	closed	normal		Core	tested	wontfix	download along gpx