New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple data directories in PROJ_LIB env variable #1150
Comments
This is a good idea! I'm happy to accept a pull request implementing this. |
Looking more into proj API, it is actually possible to use multiple paths by setting own "finder" with If they are going to stay, it is probably easier for apps like QGIS to use |
If they are useful to you we can move them into the proj_ namespace. So far we have tried to keep it to a minimum to find out which functions are in use out there. |
I think we need a means to specify multiple paths for proj resource files, but I do not have a strong opinion how exactly that should work. If I could choose, I would probably go with something like this:
This should give enough flexibility and it should simplify the search logic (which is currently 1. try pj_finder, 2. try PROJ_LIB, 3. try search paths) to just simple traversal of search paths. |
…colon on Windows (fixes OSGeo#1150)
…colon on Windows (fixes OSGeo#1150)
When working with 3rd party datum shift grid files, they need to be copied to the directory recognized by proj library which can be set by PROJ_LIB environment variable. The problem is that typically this directory (e.g. /usr/share/proj) is read-only for ordinary users. As a result, it is difficult for users to use such grid files.
If we had support for multiple directories in PROJ_LIB, we could also take into account some directory in the user's home folder and so it would lower the barrier for users to install extra grid files (e.g. there could be QGIS plugin to download them - or even built-in functionality in QGIS).
The text was updated successfully, but these errors were encountered: