Closed vlandau closed 4 years ago
Whats your version of ArchGDAL? You need the latest one. I think that is the problem here.
One structural problem with GeoData at the moment is that it uses Requires.jl. So it can't work out packages dependencies and get you the correct ArchGDAL. The option is that it depends on ArchGDAL, NCDatasets and HDF5, which starts to get pretty heavy and slow to load, when your're probably only using one of those.
Honestly I'm holding our for movement on this: https://github.com/JuliaLang/Pkg.jl/issues/1285
Otherwise we may need write glue packages like GeoDataGDAL.jl, but trying to avoid that because the maintenance will be a huge headache.
And if you scroll down here, it looks like a fix is on the way: https://github.com/JuliaLang/Pkg.jl/issues/2005
Let me know if it works when you have the latest version, otherwise it may be another problem with the Requires.jl setup.
I'm using ArchGDAL 0.4.1
Ok yeah there was a a lot of changes for 0.5 - mostly DiskArrays.jl backend (which is awesome). But you will need 0.5
Hopefully Pkg people will get this sorted for 1.6.
Ah good to know! Thanks! Going to verify that it works then I'll close this.
Maybe leave it open, it's going to be a common issue I think...
Should be fixed by #67 - close?
Here's the stack trace. It seems to trigger if I've run
using Circuitscape
prior tousing GeoData