PROJ_LIB with relative paths

[sholl]

While working with a specialized EPSG-code-table we encountered the problem that the PROJ_LIB CONFIG-directive only accepts full paths to the folder containing the epsg-file.

Using relative paths are not possible.

It would be realy nice to make the PROJ_LIB-path relative, because mapfiles will be more transportable to other maschines/paths/...

Also the documentation under [1] states that MS_PROJ_LIB should be used to set the path to the epsg-file, which we never got working. Is this an osolete parameter? If so, please remove it from the mapfile-reference-documentation.

Thanks.

[1] http://mapserver.org/mapfile/map.html

[warmerdam]

I have removed MS_PROJ_LIB from the mapfile/map.txt doc as I cannot find any reference to it in the code (r9255).

I'm not terribly keen on making PROJ_LIB relative to the MAP file path, though I can see why it might be desirable.

[sholl]

Replying to warmerdam:

I have removed MS_PROJ_LIB from the mapfile/map.txt doc as I cannot find any reference to it in the code (r9255).

OK, great. this will reduce confusion.

I'm not terribly keen on making PROJ_LIB relative to the MAP file path, though I can see why it might be desirable.

Is it possible support both options, absolute and relative paths?

[warmerdam]

OK, I'm going to take a crack at this, if only to get the ticket closed.

[warmerdam]

Support for map relative proj_lib config variable implemented in trunk (r10376). Note that the way this works is that the proj_lib value passed via CONFIG in the map file is first checked relative to the map file to see if it points to a directory. If so, the relative path is used, otherwise it is used directly. Obviously absolute paths are not check for the relative location.

[bj]

Ping, is there any progress to get this feature it in MapServer 6.0?

We find this feature really useful.

Any comment from a dev would be helpful gain momentum here.

Best

bjoern

[warmerdam]

Bjoern,

r10376 introduced the feature intro trunk which means it will appear in Mapserver 6.0. It should be in the beta produced later today.

I'm not sure why I left this ticket open. Closing now.

[dmorissette]

FYI when I applied similar logic for MS_ERRORFILE in #2853 I realized that in addition to msSetConfigOption() we also need to apply the same logic in msApplyMapConfigOptions() which is called from a few places.

In the MS_ERRORFILE case, instead of duplicating the logic I moved it inside msSetErrorFile(). We may want to do the same for msSetPROJ_LIB().

Reopening ticket to review/test this. Too late for MS 6.0 beta1 but I'll take care of it after.

[bj]

Hej, any progress towards 6.0.0-beta3?

[dmorissette]

Looking into this now

[dmorissette]

I think I'll wait to do this after beta3 to not risk breaking something at the last minute

[dmorissette]

Fixed in r11376 (will be in 6.0.0-beta4).