I don't think you can. If you dig into the arcpy source you'll find that arcpy.Describe essentially returns a wrapper around a non-python binary object (see line 369 in <install dir>\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py) which doesn't have a class you can inherit from.
However, you could fake a subclass, by creating a stand-alone ...
If you are using the ArcMap application rather than the ArcGIS Pro application of the ArcGIS Desktop product then I believe you will need to use the ArcPy that installs with ArcMap and that requires you to use Python 2.x.
The normal way to use conda is to activate an environment where proj is installed, which sets PROJ_LIB to the correct path.
However, it's not always possible to run "activate", for instance from PyCharm or Spyder IDEs. Here is my workaround that works for a few scenarios:
# workaround if activate is not called
conda_prefix = os.environ.get('...
I just struggled through this. ArcGIS Pro (v2.5) doesn't seem to support all of the dependencies for fiona v1.8.6, even though that is the recommended install version. If you downgrade fiona to 1.8.4, all of the other dependent modules will subsequently downgrade. After the downgrade, everything imported fine for me.
Got this error too when all my GIS related packages (geopandas, gdal, fiona) that all seem to rely on that libfontconfig randomnly broke.
In terminal, I had to first install the fontconfig package using brew
brew install fontconfig
Navigate to your python install path, which is in your error:
Rename the libfontconfig to a ...
If those steps are exactly what you did the problem may be that you installed the package in the wrong environment.
Prior to installing qgis (step 2) you have not activated the environment which means qgis is installed in you base environment. You are then trying to add the path to a library outside of the environment which can be tricky for an application ...
The EE Python API has been updated, breaking backwards compatibility. This is the way you get the tile URL these days:
map_id = ee.Image(ee_image_object).getMapId()
tile_fetcher = map_id['tile_fetcher']
To return to this question, I ended up giving up and configuring the users' computers myself so the script could run on double-click as a .py. As Vince said, it's a stubborn licensing issue with arcpy.
For passersby who may be interested in accomplishing what I could not, this may be a helpful resource: https://community.esri.com/t5/python-questions/using-...
Pyinstaller should be able to do this for you as long it was installed in the same environment as the dependencies (modules/libraries) for your script. Pyinstaller finds all import statements in your script and can compile everything into a single .exe file.
Since you're on Windows 10, search for "Python Command Prompt". This will open a window with the current default ArcGIS Pro python environment activated. Pip and other python modules should work normally, as well as conda.
The environmental variable PROJ_LIB needed to be set to the location of the files used by the proj library. In my case that was in the following directory:
Editing the build configuration in PyCharm allows for modification of environmental variables. See this tutorial.
Add these commands to your code at the beginning. Your issue will be solved.
os.environ['PROJ_LIB'] = 'C:\\Users\\Sai kiran\\anaconda3\\envs\\sai\\Library\\share\\proj'
os.environ['GDAL_DATA'] = 'C:\\Users\\Sai kiran\\anaconda3\\envs\sai\\Library\\share'
Search for the location of your proj.db file in your anaconda directory and replace the same ...
To use GDAL and/or PROJ from conda, you need to activate the environment, which sets the necessary environment variables (including GDAL_DATA and PROJ_LIB).
If you have conda on your path, it's simply conda activate base (or other environment).
If you don't have conda on your path, you can activate this a bit differently. For example, to activate the "base"...
Hopefully somebody who understands the internal processes better than me can provide an answer.
You can add GDAL to your Anaconda installation, and use it this way for example:
import ogr # it should also be available if gdal is present
And then use these packages in your standalone script, which reproduces the internal processing of QGIS. ...
Only QGIS 2.18 is available for Linux via conda-forge and it requires Python 2.7.
conda create -c conda-forge -n qgisenv qgis
You won't be able to install matplotlib though. I'm not sure where the fault is.
If you restrict packages to the conda-forge channel (conda create/install -c conda-forge --override-channels etc...) then QGIS 2 conflicts ...
Treat conda envs as disposable. If you have trouble installing gdal into an existing environment, ignore it and create a new env conda create -n mynew env gdal other packages etc...
Never install stuff into your default ("root") environment. Don't have 2 root conda installs (miniconda2 and miniconda3), just install one and use it to create separate ...
I think the problem is in the Anaconda version that you are using. You should install Anaconda 2 (32 bit) not Anaconda 3 (32 bit). ArcGIS 10.4 works with python 2 which is 2.7 which is included in Anaconda 2. ArcGIS 10.4 does not work with Python 3.6 which is included in Anaconda 3 which you already use and stated in your question.
I am using Anaconda 2 (...
I've found that the dependency versions are a bit messed up. GDAL is relying on there being older versions of certain libraries, but newer ones are installed by default. I've managed to get it working by forcing older versions of some of the dependencies. A minimal working environment.yml looks like this: