Polygonize progress the KeyboardInterrupt() error

[mayong1556]

Hi AROSICS developers,

Thank you for creating and developing the useful open-source tool。I'm currently using the latest version of arosics, version 1.13.2, but I'm still encountering the KeyboardInterrupt() error. The screenshot of the error is below. So far, I haven't been able to figure out how to solve this problem. Previous posts suggest it might be related to nodata or nodatamask, but I'm unsure how to modify these parameters. I've also included my parameters below.

Calculating footprint polygon and actual data corner coordinates for reference image...
Polygonize progress |======================----------------------------| 43.0% Complete => 0:00:14Traceback (most recent call last):
File "E:\soft\conda\envs\arosics_gdal310\lib\site-packages\py_tools_ds\processing\progress_mon.py", line 160, in call
self.print_progress(percent01 * 100)
File "E:\soft\conda\envs\arosics_gdal310\lib\site-packages\py_tools_ds\processing\progress_mon.py", line 117, in print_progress
raise KeyboardInterrupt()
KeyboardInterrupt
Bounding box of calculated footprint for reference image:
(413374.57061741856, 4287791.51396406, 520428.57061741856, 4347199.51396406)
Calculating footprint polygon and actual data corner coordinates for image to be shifted...
Polygonize progress |=====================-----------------------------| 41.0% Complete => 0:00:14Traceback (most recent call last):
File "E:\soft\conda\envs\arosics_gdal310\lib\site-packages\py_tools_ds\processing\progress_mon.py", line 160, in call
self.print_progress(percent01 * 100)
File "E:\soft\conda\envs\arosics_gdal310\lib\site-packages\py_tools_ds\processing\progress_mon.py", line 117, in print_progress
raise KeyboardInterrupt()
KeyboardInterrupt
Bounding box of calculated footprint for image to be shifted:
(413374.57061741856, 4287791.51396406, 520428.57061741856, 4347199.51396406)
Matching window position (X,Y): 466901.57061741856/4317495.51396406
Initializing tie points grid...

The parameters used are as follows: kwargs_local = {
'grid_res':400,
'window_size' : (220,220),
"CPUs":10,
"max_shift":150,
'nodata':(0,0),
'fmt_out':'GTiff',
}

[danschef]

Hi,
this is due to the implementation of the progress bar for the polygonization progress. Seems like it needs to be improved as it sometimes raises a KeyboardInterrupt, mainly in case of complex footprints of the input images. As a workaround, you may either disable progress printing (progress=False), or disable the computation of the footprint polygons (calc_corners=False). Also make sure that your input images have the correct no-data value in the metadata, a wrong value there, or a value that not only appears at the image background, can also cause the issue.

[mayong1556]

Thank you very much for your prompt reply, and I look forward to the improved version being updated soon. Currently, the footprints of my image to be registered and the reference image are not complex; their outer rectangular boundaries are identical, but some parts of the image to be registered are missing. The nodata value for both images is 0, and this has already been set. You can see that the nodata value is 0 through gdalinfo.