The loaded PROJ version could not be determined from library name 'proj_e.dll

[Eyal]

Hello,

Has anyone encountered the error below when using las2las64 with the -proj_epsg option?

 

"The loaded PROJ version could not be determined from library name 'proj_e.dll'"

Thanks

[Jochen Rapidlasso]

Hi Eyal,

some users experienced issues at the beginning, so we've improved the API integration much;
in particular, we now log exactly what happens and where the API is being called.
Please check the log output with verbose commands to see exactly what went wrong.
It is absolutely necessary to have read our documentation on this topic
first: 
https://downloads.rapidlasso.de/html/proj_README.html

Cheers,

Jochen @rapidlasso

[Eyal]

Hi Jochen,

Thanks for that, my mistake was that I assumed that proj was already installed.

Anyway I installed proj. and ran the command line again (in Python subprocess)

I got the following error:

"WARNING: PROJ Library 'C:\\OSGeo4W\\bin\\proj_9.dll' was found but could not be loaded. Please check that all dependencies are present and the library is compatible with your system.",
 'ERROR: PROJ Installation not found. For more information see proj_README.md.',

             ''

Which my guess refers to missing the other dependencies.

• libcrypto

• libcurl

• libssl

• sqlite3

• tiff

• zlib

Can you please provide further guidance about installing these other dependencies?

Thank you

--
Download LAStools at
https://rapidlasso.de
Manage your settings at
https://groups.google.com/g/lastools/membership
---
You received this message because you are subscribed to the Google Groups "LAStools - efficient tools for LiDAR processing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lastools+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lastools/f00a63fb-d8d7-4ddf-b4f0-f9fcd115252cn%40googlegroups.com.

--

Eyal Saiet

Airborne and spatial data specialist

Remote sensing and in-situ measurements

Geophysical Institute 

University of Alaska Fairbanks

Fairbanks, AK 99775

(907) 750 6555 (cell)

The mind is not a vessel to be filled, but a fire to be kindled. Plutarch

[LAStools - efficient tools for LiDAR processing]

Hi Eyal,

once the OSGeo4W installation is found — as is the case for you — it should run without any issues. If not, it’s 

likely a problem with the OSGeo4W installation. Nevertheless, we’ll try to help you here.

Some of the libraries you mentioned appear under different package names in OSGeo4W. The DLLs libssl and
libcrypto are provided through the package openssl, and libcurl is included in the package curl. For
TIFF support, the correct package is libtiff (not the TIFF tools). These packages contain the runtime
libraries that PROJ depends on. OSGeo4W installs them into the correct directory automatically, and they
should not be installed manually, as manual installation can easily lead to version mismatches or
incompatible builds.

Your system correctly finds the PROJ library at C:\OSGeo4W\bin\proj_9.dll. All of its dependent DLLs are
also located in the same directory, typically including: libcrypto*.dll, libcurl*.dll, libssl*.dll,
sqlite3.dll, tiff.dll, and zlib1.dll. If any of these cannot be loaded, Windows will refuse to load
proj_9.dll, even though the file itself exists.

To verify that all dependencies are present and compatible, we recommend using the tool Dependencies
(https://github.com/lucasg/Dependencies/releases). You can simply drag and drop proj_9.dll into the
application window. Missing or incompatible DLLs will be highlighted immediately.

If all dependencies are present but the library still cannot be loaded, the issue may be related to the
environment from which the program is started. Since your Python script launches our tool through a
command-line call, it is possible that the Python process provides a different runtime environment than
a normal Windows command prompt. To check whether this is the case, please try running the exact same
command manually in a standard Windows CMD or via laslook. If the PROJ library loads correctly there,
the issue is caused by the environment in which Python starts the process.

In addition, please make sure that your PROJ installation matches the architecture of your LAStools
installation. Due you are using the 64-bit version of LAStools the proj_9.dll and all of its dependent
libraries must also be 64-bit.
Installing PROJ or OSGeo4W is more a IT challenge, not a LAStools task. If you can not handle to solve 

this by your own it is best to ask your local IT support for assistance.

Cheers,

Jochen @rapidlasso