-
Notifications
You must be signed in to change notification settings - Fork 29
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
proj error on recent master image #822
Comments
@geographika indicates it may be related to moving from proj_lib env to proj_data env, based on version of proj see https://proj.org/en/9.4/usage/environmentvars.html I added an env param PROJ_DATA, but it has no effect
|
Ok, we found the problem, I'm used to starting my mapfiles with
With the new version of proj this is problematic, and causes above error. |
I can recreate the error by setting the following in a Mapfile in the master Docker image (before any PROJECTION blocks):
I get If I set it to the following it runs fine:
The base image at https://github.com/OSGeo/gdal/blob/master/docker/ubuntu-small/Dockerfile builds PROJ so I'm not sure why there is a difference. (Probably unrelated) - I don't fully understand the symlink here: Line 17 in 1445ddc
|
@sbrunner @geographika I closed as completed, but maybe we should reopen to facilitate more research or documentation |
The GDAL base image builds the master version of PROJ from whenever it is tagged ( I'm not sure, but I'm guessing another version of PROJ is installed onto the image. |
Shouldn't we simply add the environment variable ENV PROJ_DATA=/usr/share/proj/ |
I tried a env param proj_data, no effect, either gets overwritten by the config in mapfile or there is a problem with the path; usr/share/proj vs usr/local/share/proj |
This is just to make the build work |
Assuming the PROJ install in pkg-versions.yaml is required, then I think updating the sample in mapserver.conf is enough (note the working value is @pvgenuchten - a PROJ_DATA setting in a Mapfile will always take precedence over any environment setting or setting in mapserver.conf - I'd suggest removing these and if a custom path is needed setting it in mapserver.conf. Note, from MapServer/MapServer#6573 on the deprecation plan for PROJ_LIB:
|
No, the version in this file is not required, this file is just used to trigger a rebuild when a package is updated. |
I just tried to reproduce the issue and I didn't succeed, can you share the files you used to reproduce it? |
@sbrunner - the following setup should trigger the error. The data isn't required - just setting the
Mapfile:
|
I can reproduced also on my side. The fix looks good (remove CONFIG PROJ_LIB). |
the latest master image gives me problems with projections, something changed in image build (or mapserver)?
msProcessProjection(): Projection library error. proj error "Invalid PROJ string syntax" for "EPSG:4326"
also tried init=epsg:4326
the master image of last month works fine...
The text was updated successfully, but these errors were encountered: