-
Notifications
You must be signed in to change notification settings - Fork 0
Qgis 3.10.8+: CanFlood Import Error #46
Comments
Hi Pete, If you really want to dive down the rabbit hole, you could try to trouble shoot this further by with running the following in first OSGeo4W.bat and then in Qgis' builtin console:
However, you're probably better off just: 1) uninstalling ALL qgis versions; then 2) installing Qgis 3.10 from the OSGeo4W installer per the instructions here. Let me know how it goes |
Thanks for looking at this. I've already tried doing a full uninstall of QGIS and reinstalling following those instructions - it gave the same result and the error message posted above. |
Hi Pete, Is this how you managed your install? If so, please try running the following in first OSGeo4W.bat and then in Qgis' builtin console and sending me the error message: |
Scratch that. I just updated to 3.10.9 (which was released this week) and am getting the same error. Try installing LTR 3.10.8 (or some older version using the OSGeo4W installer) while I try and figure out what the brake is with 3.10.9. (note, CanFlood was developed/tested on 3.10.3 per in the install instructions). Sorry I didn't catch this sooner. |
I did some unsuccessful digging/testing and it sounds like the 3.10.9 has broken some backends for scipy. I've submitted a ticket to the Qgis project to hopefully get this fixed. In the meantime, you'll have to uninstall and then install an older version of Qgis. For this, it's probably easier to use the standalone installer (rather than the OSGeo4w network installer) by selecting the relevant 3.10.8 release listed here. (e.g. QGIS-OSGeo4W-3.10.8-1-Setup-x86_64.exe). Note this may make managing python package versions more difficult. |
Problem has been resolved in QGIS 3.10.12 |
Running QGIS 3.10 A Coruna. Installed all python plugins using OSGeo4W.bat and the latest CanFlood plugin (CanFlood_031_20200415.zip) within QGIS. CanFlood installs but then returns an error message and won't load.
The text was updated successfully, but these errors were encountered: