Newer
Older
## Similarity or Random Forest causes QGIS to crash
This crash is due to a bug during `geopandas` reading of a shapefile, only when it has allready read a shapefile. It is probably linked to `fiona` as well. If you have any idea on how to solve this, please do participate in the [corresponding issue](https://github.com/umr-amap/iamap/issues/28).
Meanwhile, if QGIS crashes and your file were not saved, you can still find them in the temp files like `/tmp/iamap_features` for instance.
## QGIS crashes at the start of encoding
This issue should be solved but the solution has not been tested on all OSes. This is an issue with `rtree` during the creation of the dataset that will be used by the plugin.
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
Indeed, depending on the installation, `rtree` and QGIS may have conflicting `libspatialindex`. Currently, there is several solutions:
### 1. Uninstall `rtree` installed via pip and reinstall via package manager
in the QGIS python console:
(following code has not been tested, based on this [SE answer](https://gis.stackexchange.com/questions/418274/installing-python-module-using-pip-via-python-console-in-qgis-3-22))
```
import subprocess
import sys
if sys.platform == 'win32':
subprocess.call([sys.exec_prefix + '/python', "-m", 'pip', 'unininstall', 'rtree'])
else:
subprocess.call([sys.executable, '-m', 'pip', 'uninstall', 'rtree'])
```
then in a terminal (for a debian based linux)
```
sudo apt-get install python3-rtree
```
### 2. Uninstall `rtree` installed via pip and reinstall `rtree` at an older version (<1.0.0)
in the QGIS python console:
(following code has not been tested, based on this [SE answer](https://gis.stackexchange.com/questions/418274/installing-python-module-using-pip-via-python-console-in-qgis-3-22))
```
import subprocess
import sys
if sys.platform == 'win32':
subprocess.call([sys.exec_prefix + '/python', "-m", 'pip', 'unininstall', 'rtree'])
subprocess.call([sys.exec_prefix + '/python', "-m", 'pip', 'install', 'rtree==0.9'])
else:
subprocess.call([sys.executable, '-m', 'pip', 'uninstall', 'rtree'])
subprocess.call([sys.executable, "-m", 'pip', 'install', 'rtree==0.9'])
```
### 3. Use a conda environement.
This way, rtree and qgis will automatically share the same libspatialindex.
If you have any idea on how to solve this issue properly, do participate in the [corresponding issue](https://github.com/umr-amap/iamap/issues/13).
## UMAP crashes
If you're using Windows, the use of UMAP may cause the plug-in to crash QGIS when using it.
If this issue happens we recommend to go in the algo.py file of this plug in and comment the line :²
```
import umap
```
Then save the change, reload the plug-in and try again.
## Major tilling efects
After encoding, it is common to see tilling effect, however, sometimes, these effects are overwhelming (for instance if you can only see a color gradient on every tile and no local features).
The issue might be a normalization issue, with every tile fed to the network being wrongfully normalized.
The root of the problem may be the meta-data of your raster, check that the `STATISTICS_MEAN` and `STATISTICS_STDDEV` are correct, because these are the ones used by the plugin if they exist.
The following command could potentially solve meta-data issues.
```
gdal_edit.py -stats your_file.tif
```
## Conflicting requirements for UMAP
`umap` has `numba` as a dependdencie, which may require `numpy < 2.0` and conflict with other librairies depending on how you installed them. According to `numba` developpers, this
(should be resolved in comming numba releases)[https://github.com/numba/numba/issues/9708].
In the mean time, you can use a conda environement or uninstall and reinstall numpy at a previous version.