Open itati01 opened 5 years ago
Does the issue persist if you create an environment using only packages from defaults
? If so you will need to engage the conda-forge community for support.
Thanks for the suggestion. So, I created a new environment and installed only packages from defaults. Via Anaconda Navigator I then installed Spyder. Still the same problem, though: gdal output is ok if Spyder was started from the commandline, is erroneous if Spyder was started from the start menu.
I have a similar problem on Windows 10.
I created a new Python 3.7.3 environment because from mpl_toolkits.basemap import Basemap
wasn't working in the base environment anymore.
When I activate the new environment in the terminal and then start Spyder everything works fine, and doing
import os
print(os.environ['CONDA_DEFAULT_ENV'])
works as well.
When I use the shortcut for Spyder specifically for the new environment importing fails and the variable CONDA_DEFAULT_ENV
throws a KeyError.
Anaconda Navigator Version 1.9.7
The issue still persists even in newly created environments, both CONDA_DEFAULT_ENV
and PROJ_LIB
(which basemap uses) are not available when Spyder is started using the provided shortcut.
Actual Behavior
Hi, gdal-based libraries do not correctly identify the projection of geodata if Spyder is started via the Windows start menu (Win 10, Anaconda 2) because the required environment variables are missing. Starting Spyder from Anaconda Navigator or commandline works fine. This behaviour was confirmed with a clean environment. Thanks in advance for any help, Andreas
Expected Behavior
The attached file test.zip contains a GeoTiff with the CRS EPSG:25832.
gdal is expected to report
But I get
The environment after starting from Anaconda Navigator:
After starting via Start Menu:
Steps to Reproduce
Start Spyder from Start menu
Anaconda or Miniconda version:
Anaconda 2 64 bit
Operating System:
Windows 10 64 bit
conda info
conda list --show-channel-urls