You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When transferring cutouts, it is difficult to reason about the bounds and max_mips that will allow TransferTasks to be successful. I believe this is because the info file bounds are copied from the source image, and do not shrink to match the cutout. If we made a flag to allow create_transfer_tasks to update the dest info file to exactly match the bounds of the transferred image, this would allow the user to estimate the number of mips allowable based on the size of the cutout and the chunk size.
The text was updated successfully, but these errors were encountered:
When transferring cutouts, it is difficult to reason about the bounds and max_mips that will allow TransferTasks to be successful. I believe this is because the info file bounds are copied from the source image, and do not shrink to match the cutout. If we made a flag to allow create_transfer_tasks to update the dest info file to exactly match the bounds of the transferred image, this would allow the user to estimate the number of mips allowable based on the size of the cutout and the chunk size.
The text was updated successfully, but these errors were encountered: