-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Processing interpolation crash #55138
Comments
I should include the full traceback:
|
Hi @arnige, thanks for reporting. |
Can confirm that I have had the same issue when trying to open the Tin interpolation processing tool. QGIS version Active Python plugins |
Same problem with TIN and IDW interpolations. Versión de QGIS Complementos activos de Python |
I, too, am experiencing this same issue and it is critical to my project. I am dead in the water until this issue is resolved. |
@robricks86, you can use QGIS 3.28 LTR. |
Thanks, I will!
…On Tue, Nov 7, 2023, 12:35 PM Andrea Giudiceandrea ***@***.***> wrote:
@robricks86 <https://github.com/robricks86>, you can use QGIS 3.28 LTR.
—
Reply to this email directly, view it on GitHub
<#55138 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACVG33CYDETNN3GPJ2YXBUTYDJ5PZAVCNFSM6AAAAAA63SC5KOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJZGQ4TIOBZGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
What is the bug or the crash?
When attempting to run interpolation algorithms in the processing toolbox, python crashes before opening the dialog with the following error:
File "C:\OSGeo4W/apps/qgis/./python/plugins\processing\algs\qgis\ui\InterpolationWidgets.py", line 305, in pixelSizeChanged
rows = max(round(self.extent.height() / cell_size) + 1, 1)
OverflowError: cannot convert float infinity to integer
Steps to reproduce the issue
Open the processing toolbox and try to run "TIN interpolation" or "IDW interpolation".
Versions
3.34.0-Prizren
Happens both in Windows and Ubuntu
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: