Tao Peng

Thanks @GITNE! The logs you shared above didn't reproduce this HTTP 412 errors. However, I've reproduced it locally by switching on/off VPN during uploading. I think we should retry on...

@GITNE the offset reset is likely that when `mapillary_tools` resumes uploading from a different IP, it might upload to a different host, and the offset is **not** shared across hosts....

This is great news! I actually tweaked the param and didn't notice much improvement under a few network configuration. I will try again and make it more reasonable, or even...

I agree we should maximize the upload egress by default. Did some test under a good network in the PR, and it seems 16MB is a good default. I will...

This change **does not** affect video uploading though because the chunk size for video uploading is already 16MB by default.

v0.9.5 with the upload speed improvement is released https://github.com/mapillary/mapillary_tools/releases/tag/v0.9.5 Download binaries there, or run pip install: ``` pip install -U mapillary_tools ```

Yes, the [latest version](https://github.com/mapillary/mapillary_tools/releases/tag/v0.9.1) writes all processing metadata in a single JSON file "mapillary_image_description.json", including which images are duplicates.

It's built for intel arch, not for M1. Currently the build system (GitHub Action) does not support M1 arch https://github.com/actions/virtual-environments/issues/2187 We will build it from local machine for the next...

After downloading the binary, you need to run: ```shell unzip mapillary_tools-0.9.0-osx-x86_64.zip cd mapillary_tools-0.9.0-osx-x86_64 xattr -c mapillary_tools ``` then it should work

@DavidMetcalfe didn't it work after `xattr -c mapillary_tools` on your M1? What was the error? I own a M1 and it works.