Refresh map download progress details more often

Andrew Heard shared this idea ago

Completed

I am currently downloading the 973MB Italy map over a "fairly slow" ADSL connection. It appears that progress details are updated only when the integer percentage changes, ie at 1%, 2%, 10%, 11% etc. which is each around 16MB "chunks" of data. Each percentage point of data is taking a few minutes so during this time there is no change to displayed progress such as #MB downloaded. Could you refresh map details more often, say every 15 seconds, as well as at each percentage point, so user is better informed that data connection is correctly working?

I also note that % calculation doesn't correspond to #MB downloaded / total size. For example currently displaying:

6% 116.82 MB/ 973.47 MB

but 116.82 / 973.47 = 12%? Is it 6% or 12%?

I like this idea 0

Replies (2)

Andrew Heard ●

40bc77b5f2f2eacb7f21f4532f34f27b

350/973 = 36%, what does 18% in screen capture refer to?

am fairly sure the percentage isn't correct because the transfer took a few hours to download ~600MB but then completed soon after

d76d73876e0db9ff6d6a530a71a15a72

URL

Menion ●

Good day Andrew,

in case of content that is also packed into "zip" file, progress counter is divided into two parts. 0 - 50% is downloading, 50 - 100% is extracting.

I firstly wanted to decline it anyway agree that it may be useful to refresh progress more often, so consider as implemented ( refresh will be once per 3 sec ).

URL

Andrew Heard ●

OK, understood. But the displayed percentage seems misleading. I experience very little time taken to extract the data, even for 1GB file. I was thinking the displayed percentage should just be #MB / total MB. Then once 100% downloaded, and extraction commenced, the progress bar could (briefly) become rotating marquee or restart from 0..100% with new text "extracting..."?

URL

Andrew Heard ●

Just a bit more info: on 450MB map download each 1% (4.5MB) was taking at least a few minutes, and while extracting the map each 1% was taking a second. So seems confusing to have download 50% = ~300 minutes (for example), and extraction 50% = ~1.5 minutes (for example), especially when the progress % is positioned next to the #MB downloaded, and user therefore thinks 100% is full download.

URL

Menion ●

Good day Andrew,

thanks for a feedback. Understand, anyway even after a while of thinking, I'm unable to find some easy-to-do & more logical solution. Running progress will be now more obvious, so I believe this will help. Thanks

URL