PlotToSat export checker

[thelordfish]

I have been using PlotToSat extensively for my project and found it helpful to create a supporting script to double check where a PlotToSat export has stalled in the occasions that GEE slows or stops and needs to be restarted. The export ranges it produces can be used to pick up where the session left off. It uses Google Drive's API to look through the exports without having to download them and check locally.

Due to the recent changes made by GEE or google drive, where each file/chunk is exported in a separate folder, my script now needs to crawl through individual folders.

I have updated it and it is working in this new format, and checking multiple pages, but wondering if it's worth developing further to be helpful for other uses people may have (for instance this script only computes total unique covered indices (a count). It does not detect gaps, so the derived single restart range is only correct when coverage is contiguous from index 0. If there are gaps (or out-of-order exports), you’d need custom/multiple export ranges targeting the missing intervals.)?

I am aware that you could just check what the last chunk was in your exports without the need for any script, but it can be reassuring to check they have actually exported into your Google Drive, and to know how many have come as <2 bytes (if the satellite wasn't operational etc.). Do let me know if there's anything else I'm missing or any functionality that would be useful to add!
findwhereleftoff_drive_api_new.py

[Art-n-MathS]

Hi, Thank you for your message and your interest in contributing to PlotToSat. The contribution process is as follows:

1. Fork the repository.
2. Clone your fork locally:
   git clone https://github.com/your-username/repository-name.git
3. Create a new branch:
   git checkout -b feature/my-feature
4. Make your changes.
5. Add the new or modified files:
   git add new_file.py
6. Commit your changes:
   git commit -m "Add new feature"
7. Push the branch to your fork:
   git push origin feature/my-feature
8. Open a Pull Request on the original repository.

Once you open a pull request, I will be able to review and approve the code to be added to the official PlotToSat page. :)

Instructions also available at: https://github.com/Art-n-MathS/PlotToSat/blob/main/Contributing.md

[thelordfish]

Hi Milto, Thank you, I will try this out this week with the export checker script. While you can always check GEE's last export to find where you've left off, I think my script could be helpful to have the export progress printed as an export range that could be copied and pasted for the next run, and just to know that previous years/countries have exported properly. It also currently checks how many files have been exported as <2 bytes which may be helpful. Anyway you can review all this once I open the pull request. Excited to potentially contribute! Thanks, Ollie

…

On Tue, 10 Feb 2026, 17:09 Milto Miltiadou, ***@***.***> wrote: Hi, Thank you for your message and your interest in contributing to PlotToSat. The contribution process is as follows: 1. Fork the repository. 2. Clone your fork locally: git clone https://github.com/your-username/repository-name.git 3. Create a new branch: git checkout -b feature/my-feature 4. Make your changes. 5. Add the new or modified files: git add new_file.py 6. Commit your changes: git commit -m "Add new feature" 7. Push the branch to your fork: git push origin feature/my-feature 8. Open a Pull Request on the original repository. Once you open a pull request, I will be able to review and approve the code to be added to the official PlotToSat page. :) Instructions also available at: https://github.com/Art-n-MathS/PlotToSat/blob/main/Contributing.md — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIDIGDIHAP2NXP2MTPNHTHD4LIF5XAVCNFSM6AAAAACUQOQN2GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNZVHE2DGNA> . You are receiving this because you authored the thread.Message ID: ***@***.***>