Internal Proj Error: proj_create: no database context specified

[abashishvili]

Hello Everyone,

Its already been a long time since I have had this error when executing the code, and I was not able to find a solution on the internet.

So the problem is the following, I created the new conda environment and installed geopandas. When I import geopandas, I get this warning:

UserWarning: pyproj unable to set database path. _pyproj_global_context_initialize()

Whenever I want to do a simple operation, for example, import shape file and change crs, I get the following error:

Invalid projection: EPSG:4326: (Internal Proj Error: proj_create: no database context specified)

I searched for the problem, and it seems pyproj database is mixed, and that's causes the error. There is something mentioned on pyproj FAQ about the database directories, but it was difficult for me to fully understand how to solve it. Any suggestion?

Thanks for your help!

[snowman2]

This is likely due to installation issues. Mind providing this information?

Installation method/steps

• Installation method (conda, pip wheel, from source, etc...)
• How did you install PROJ? Where is it installed?
• Please provide all commands/steps you used to install pyproj and PROJ.

Environment Information

• pyproj version you are attempting to install
• PROJ version (Execute proj command and give version here.)
• Python version (python -c "import sys; print(sys.version.replace('\n', ' '))")
• Operation System Information (python -c "import platform; print(platform.platform())")

[snowman2]

This looks correct:

'PROJ_DATA': 'C:\\Users\\Win7ADM\\anaconda3\\envs\\ox_test\\Library\\share\\proj'

[abashishvili]

Could be this problem related to the error mentioned in FAQ on pyproj website?

[snowman2]

Not exactly, it is not finding a PROJ database. What is the output of: pyproj.datadir.get_data_dir?

[abashishvili]

It is C:\Users\Win7ADM\anaconda3\envs\ox_test\Library\share\proj

[snowman2]

What are the contents of that directory?

[avriiil]

I'm running into the same issue.

I've installed via mamba install pyproj.

Here are the contents of my proj_dir/share/proj directory:

CH				deformation_model.schema.json	proj.db
GL27				nad.lst				proj.ini
ITRF2000			nad27				projjson.schema.json
ITRF2008			nad83				triangulation.schema.json
ITRF2014			other.extra			world

[snowman2]

#1262 (comment)

[avriiil]

python version: 3.12
OS: MacOS 14.3.1
proj: Rel. 9.5.0, September 15th, 2024
PROJ not installed explicitly, just via mamba install pyproj AFAIK

trying to install latest pyproj

[snowman2]

Did you call mamba activate to activate your virtual environment?

[avriiil]

Yes

…

On Tue, 5 Nov 2024 at 15:21, Alan D. Snow ***@***.***> wrote: Did you call mamba activate to activate your virtual environment? — Reply to this email directly, view it on GitHub <#1262 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQLWMSQFT6AWK5S74NA4DZ3Z7DO7JAVCNFSM6AAAAABRGVMFB2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJVGYZDIMQ> . You are receiving this because you commented.Message ID: ***@***.***>

[snowman2]

Are all of the packages from conda-forge?

[sheilasaia]

Hi all, I recently ran into this same issue trying to run on Windows in VS Code. I found that when I activated my environment in the Anaconda Powershell Prompt using conda activate myenv and then checked the environment using dir env:, my PROJ_DATA and PROJ_LIB paths were not pointing to the proj directory within the environment. The correct path should look something like C:Users/yourname/AppData/Local/anaconda3/envs/myenv/Library/shared/proj for both the PROJ_DATA and PROJ_LIB variables. If you're also finding that the paths are not pointing to the correct place, you can fix them permanently within your environment using conda env config vars set PROJ_DATA =C:Users/yourname/AppData/Local/anaconda3/envs/myenv/Library/shared/proj. You can also set the PROJ_LIB variable as well, but I think the PROJ_DATA is more important for newer versions of pyproj. You will then need to deactivate your conda environment (use conda deactivate) and then reactivate using conda activate myenv again for the changes to the environmental variables to save. Then you should be able to open VS code from this terminal window using code and it will automatically be set to your environment and use the environmental variables you just set. If you want to make 100% sure it's set up ok, you can import pyproj (import pyproj) and then run pyproj.show_versions(). There is a similar show versions command for rasterio too.

I also found that there was something weird going on with the order in which you import pyproj and rasterio, but it sounds like that's still an open issue here. TLDR; an ad-hoc fix for this is to import osgeo before you import either pyproj or rasterio.

I hope that helps!
`

[djhoese]

This discussion is very old and many things have likely changed. It is important to include what versions of the software you are installing and from where. These environment variables are set in the PROJ (proj) package from conda-forge and are configured as part of the activate scripts here:

https://github.com/conda-forge/proj.4-feedstock/tree/main/recipe/scripts

If these settings in these scripts are not correct or not complete then please file an issue there so it can get fixed.

[sheilasaia]

@djhoese, thanks very much for sharing that link. I hadn't come across this resource. It's also good to know that PROJ_DATA is the variable for setting the PROJ location now. I'm similar to the original poster here in that I'm fairly new to using python geopspatial packages (and conda). I've found that the documentation can sometimes be difficult to decipher so I wanted to post what worked for me in case someone came across this GitHub page in a similar manner as I had.

Are these scripts in the repo you shared typically installed automatically when PROJ is installed with conda? If not, where do you recommend implementing the scripts in the link you provided or if are they designed to sit in a directory in my environment and run when the conda activate <your env>? Do you have any recommended pyproj or other documentation on this set up/where they are typically added? I'm looking here, but don't see anything about these files. Thanks very much for your help and thanks for your patience with my questions! If there's a better place to post these than on this GitHub thread, please let me know.

[djhoese]

So conda-forge is one channel that provides conda packages. I assumed that that is where your packages were being installed from. Anaconda (the curated selection of conda packages) may have a different version and likely older than what is available from conda-forge due to the amount of testing and curating they do. I highly recommend using conda-forge packages since they are much more up to date.

The activation scripts should installed as part of the package installation and are meant to be automatically executed when you load (activate) your environment. You shouldn't need to do anything. If you're running an older version of these packages though, these scripts may have not been implemented or properly configured.

As for the documentation you're looking at, that URL is for proj-tmp which...I have no idea what that is. You may want:

https://proj.readthedocs.io/en/latest/index.html

It is not guaranteed that a software's official documentation will mention these activation scripts as:

1. conda package building is a completely separate process and repository outside of the main package distribution.
2. Users usually don't need to know or worry about these files.

Bottom line: With modern versions of packages this is just meant to work.

[sheilasaia]

Thanks very much, @djhoese!