That's clear. However, environmental means SET in one environment, and
EXPORT in the other.
Sorry for the pun, but I expect Windows and Linux settings/exports for GDAL
should be fairly similar.
So the environments might be the next step to communicate, if I'm not
mistaken at root.
On Sun, Sep 24,
This applies to *all* shapefiles for that user. There are about 10 in
the sample and they're from a diverse range of UK organisations. Mostly
27700 (British National Grid), but likely one or two WGS84. Hence
thinking it may be environmental, but I don't have any real *nix
knowledge to use to di
Sorry to break in, but surely, we would like to see the .prj file in
question for a simple try at reproducing?
On Sun, Sep 24, 2023 at 11:37 PM Jonathan Moules via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Thanks Even. I don't have access to the machine either as the colleague
> is moving to
Thanks Even. I don't have access to the machine either as the colleague
is moving to another project. I'll have to see if it fails for another
*nix user.
On 2023-09-24 22:35, Even Rouault wrote:
Le 24/09/2023 à 23:22, Jonathan Moules via gdal-dev a écrit :
> Also check if the environment is
Le 24/09/2023 à 23:22, Jonathan Moules via gdal-dev a écrit :
> Also check if the environment isn't messed up regarding PROJ and the
PROJ_LIB/PROJ_DATA environment variable
Thanks Even; sorry, what does this line mean? I'm guessing you're
referring to: https://proj.org/en/9.3/usage/environm
> Also check if the environment isn't messed up regarding PROJ and the
PROJ_LIB/PROJ_DATA environment variable
Thanks Even; sorry, what does this line mean? I'm guessing you're
referring to: https://proj.org/en/9.3/usage/environmentvars.html - what
would a "messed up" one look like?
Thanks,
