Update on this thread:
Thanks for being patient while we work on this. I’ve done some investigating on previous successful uploads up Shawn’s data. One thing that stood out to me, is that the images are extremely large- some upwards of 30MB.
This uploader does most of it’s work in the user’s browser before sending off the data to Wildbook. A very large upload could time out the recaptcha, and the uploader itself.
I downloaded and tested some of Shawn’s existing image data and saw the uploader seem to take longer than usual, but the encounters were still created. Based on this, it seems like the uploader is doing it’s first job but then failing to let the user’s computer know it is finished. Depending on Shawn’s internet speed his upload times may differ from mine also.
The test(s) that I performed all included at least 11 images, as that was the minimum described as encountering this problem. This came in at 293MB, exceeding the recommended 250MB for a single upload due to the image sizes- even though the number of images was few.
The images I downloaded are all around 6000x4000px and JPG quality 99, almost the maximum archival quality possible with JPG. Wildbook does not need anything close to this size of image for good quality display and effective spot mapping. We strongly suggest saving smaller images and reducing the JPG quality if possible. Quality levels over 90 in JPG tend to increase file size quickly, and 90 is still quite good. 6000x4000 could easily be reduced to 1600x1200 or thereabout. In fact, the images you see in the Wildbook software are in almost all cases processed smaller versions of the original. If the images are reduced to 1-5MB the multiple encounter submission process should proceed much more quickly.
This will not just reduce upload size and therefore upload time, it will save space on the server. Server space can be extended, but it add to cost for us.
In the mean time, I’m going to extend timeout lengths throughout the server and continue testing with these images. I’ve begun this process and will keep you updated as it continues.
Thanks for continuing to be patient while we work on this.