While running the custom croptype map notebook, I am getting the following response while running Step 4 codeblock -
Could you share a bit more information?
What happens when you start map production, is that in the subfolder “runs” a new folder is created with the custom name you provided and the timestamp when you started production.
You can simply retry map production by manually changing the “output_dir” to this previously created folder and restart production. The process will resume where it left off. If this still returns no results, we’ll need to investigate further…
Within that folder, you’ll see a “job_tracking.csv” file and a “production_grid.gpkg” file. Can you verify whether these files are there and that the production_grid indeed matches your drawn area of interest? The job tracking csv contains an overview of all the processing jobs involved along with their status. Could you check and share the status of these jobs? Based on the id of your processing jobs, we can further investigate…
The “runs” folder is not created and the above message appears when I run the codeblock. I am running this code locally.
its working fine on Terrascope but not working on local
If you are running this locally, feel free to define another output_dir, somewhere you are sure you have the necessary permissions to create new directories.
This “runs” folder should be created automatically upon running the “start_production_process” function.
But the folders for bbox as well as extractions etc are getting created. I also tried changing the name from ‘runs’ to ‘bbox’ to just test out weather it works in existing folder. I still get the same error.
Maybe, it might be an issue with the ‘start_production_process’ function
Since you are running this locally, could you try to run this in a normal Python script (not in a notebook) and debug the start_production_process function to find out where things are going wrong?