Transform can not find proj.db
See original GitHub issueI can no longer perform transformations. The minimum (platform independent) example code is:
docker run -it python bash -c "pip install pyproj && python"
>>> import pyproj
>>> pyproj.transform(pyproj.Proj(init='epsg:4326'), pyproj.Proj(init='epsg:3857'), 0, 0)
This returns: proj_create_operation_factory_context: Cannot find proj.db pj_obj_create: Cannot find proj.db
running with pip install pyproj==1.9.6
works fine though.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:13 (5 by maintainers)
Top Results From Across the Web
GDAL, ogr2ogr "Cannot find proj.db" Error - Stack Overflow
Your issue will be solved. Search for the location of your proj. db file in your anaconda directory and replace the same location...
Read more >"Cannot find proj.db" in PostgreSQL+PostGIS logs
Proj tries to find an SQLite database "proj. db" where all the transformation parameters are stored.
Read more >FAQ — PROJ 9.1.1 documentation
Why am I getting the error “Cannot find proj.db”? ... PROJ supports transformations between most coordinate reference systems registered in the EPSG ......
Read more >Several proj.db and io_gdal related issues - SourceForge
When using "coordinate transformation" functions, I get this error: pj_obj_create: Cannot find proj.db and Error: Dataset creation failed: ...
Read more >#4372 (PROJ 6: 4x slowdown over points) – PostGIS
I tried this test case and didn't see a substantial difference in ... jun 14 12:31:13 Mordor postgres[27104]: proj_create: Cannot find proj.db jun...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ESPECIALLY when used in a containerized environment. Unless its pip installable, no one will use it.
I believe that’s where proj.db would live if you installed a binary wheel with pip, or using conda