Changes between Initial Version and Version 1 of Ticket #30933, comment 8


Ignore:
Timestamp:
Oct 31, 2019, 4:40:54 PM (5 years ago)
Author:
Adam Starrh

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #30933, comment 8

    initial v1  
    11Hello,
    22
    3 When following the instructions in the documentation, only the latest version of the gdal dll is placed in the /bin/ directory via the OSGeo4Win installer. There are no older versions available. 
     3When following the instructions in the documentation, only the latest version of the gdal dll is placed in the /bin/ directory via the OSGeo4Win installer. There are no older versions that are made available. 
    44
    55I don't have immediate access to the traces but the general result was that the utility that searches for the .dll was unable to find it, even when it was present. I should note that I identified two separate issues while setting this up.
    … …  
    1010
    1111In this case, `gdal204.dll` was missing from Django's `libgdal.py` file and I had to enter it manually. However, this time, it continued to return the same GDALexception as before,
    12 which led me to the second issue. I tried setting the GDAL_LIBRARY_PATH manually in the settings and when attempting to run the migrations, it reported: "this is not a valid win32 application". This tipped me off to the issue and I rolled python and OSGeo4Win back to the 32-bit versions, and that resolved it. This was the 4th or so time over the years that I have chosen 64-bit python in the installation process and had to go back and convert to the 32-bit. This is why I am suggesting an amendment to the instructions at this step in the process, as it creates hours of headaches each time.
     12which led me to the second issue. I tried setting the GDAL_LIBRARY_PATH manually in the settings and when attempting to run the migrations, it reported: "this is not a valid win32 application". This finally tipped me off to the issue. I rolled python and OSGeo4Win back to the 32-bit versions, and that resolved it. This was the 4th or so time over the years that I have chosen 64-bit python in the installation process and had to go back and convert to the 32-bit. This is why I am suggesting an amendment to the instructions at this step in the process, as it creates hours of headaches each time.
    1313
    1414Aside from these issues with GDAL, the instructions as-written work pretty well for getting casual coders like myself up and running quickly. The techs all work together nicely and having the process simple and straightforward is part of what I believe makes Django so accessible. The OSGeo4Win is certainly a convenient package that enables users to skip a lot of steps installing individual dependencies that they would have to endure otherwise. If a full revision is necessary, I'd hope that this is kept in mind.
Back to Top