Skip to content
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

Raster flood on raster people fails #5091

Open
timlinux opened this issue Jun 21, 2021 · 1 comment
Open

Raster flood on raster people fails #5091

timlinux opened this issue Jun 21, 2021 · 1 comment

Comments

@timlinux
Copy link
Contributor

Problem

QGIS version 3.19.0-Master QGIS code revision a038a79997
Qt version 5.14.2
Python version 3.8.6
GDAL/OGR version 3.1.3
PROJ version 7.1.0
EPSG Registry database version v9.8.12 (2020-06-19)
GEOS version 3.8.1-CAPI-1.13.3
SQLite version 3.33.0
PostgreSQL client version 12.5 (Ubuntu 12.5-0ubuntu0.20.10.1)
SpatiaLite version 5.0.0
QWT version 6.1.4
QScintilla2 version 2.11.2
OS version Pop!_OS 20.10
Problem
The following problem(s) were encountered whilst running the analysis.

QgsProcessingException
Suggestion
You can try the following to resolve the issue:

Check that you have the latest version of InaSAFE installed - you may have encountered a bug that is fixed in a subsequent release.
Check the InaSAFE documentation to see if you are trying to do something unsupported.
Report the problem using the issue tracker at https://github.com/inasafe/inasafe/issues. Reporting an issue requires that you first create a free account at http://github.com. When you report the issue, please copy and paste the complete contents of this panel into the issue to ensure the best possible chance of getting your issue resolved.
Try contacting one of the InaSAFE development team by sending an email to info@inasafe.org. Please ensure that you copy and paste the complete contents of this panel into the email.
Details
These additional details were reported when the problem occurred.

GEOS geoprocessing error: intersection failed.
Diagnostics

In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/impact_function/impact_function.py", line 1449, in run self._run()
In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/utilities/profiling.py", line 126, in with_profiling ret = fn(*args, **kwargs)
In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/impact_function/impact_function.py", line 1653, in _run self.hazard_preparation()
In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/utilities/profiling.py", line 126, in with_profiling ret = fn(*args, **kwargs)
In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/impact_function/impact_function.py", line 2179, in hazard_preparation self.hazard = clip(self.hazard, self._analysis_impacted)
In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/utilities/profiling.py", line 126, in with_profiling ret = fn(*args, **kwargs)
In file "/home/timlinux/.local/share/QGIS/QGIS3/profiles/InaSAFE Develop/python/plugins/inasafe/safe/gis/vector/clip.py", line 53, in clip result = processing.run('native:clip', parameters, context=context)
In file "/home/timlinux/dev/cpp/QGIS-Debug-Build/output/python/plugins/processing/tools/general.py", line 108, in run return Processing.runAlgorithm(algOrName, parameters, onFinish, feedback, context)
In file "/home/timlinux/dev/cpp/QGIS-Debug-Build/output/python/plugins/processing/core/Processing.py", line 174, in runAlgorithm ret, results = execute(alg, parameters, context, feedback, catch_exceptions=False)
In file "/home/timlinux/dev/cpp/QGIS-Debug-Build/output/python/plugins/processing/gui/AlgorithmExecutor.py", line 71, in execute results, ok = alg.run(parameters, context, feedback, {}, False)
@lucernae
Copy link
Collaborator

I used the test layers and can't seem to replicate this, but I found entirely different issues #5092

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants