Unset PROJ_LIB environment variable in dea-env

[omad]

The error below happened when trying to run an old script in the current dea environment. This is due to the PROJ_LIB environment variable not being set.

The dea-env module is based on a conda environment, which usually sets environment variables specified in etc/conda/activate.d shell scripts. We have manually copied the environment variables for udunits and gdal into the module files, but PROJ_LIB and a whole bunch of other environment variables are being ignored. Mostly this has been fine, but has reared it's head with this issue.

See /g/data/v10/public/modules/dea-env/20190329/etc/conda/activate.d for the current set of shell scripts which aren't being run.

This issue can be fixed by simply adding PROJ_LIB beside GDAL_DIR, and replacing gdal with proj in the module files for new environments.

In future we could consider running activate scripts when loading a module, but this could have wider reaching repercussions.