Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update for latest JuliaGeo/GDAL #48

Merged
merged 13 commits into from
Jul 10, 2018
Merged

Update for latest JuliaGeo/GDAL #48

merged 13 commits into from
Jul 10, 2018

Conversation

yeesian
Copy link
Owner

@yeesian yeesian commented Jun 30, 2018

No description provided.

people who test will want to keep them anyway, and people who don’t
won’t be bothered by the bloat
@yeesian yeesian requested a review from visr July 1, 2018 16:33
visr added 2 commits July 3, 2018 18:47
this will give aligned and more compact printing of test results
@visr
Copy link
Collaborator

visr commented Jul 5, 2018

Should your StringList be updated to match JuliaGeo/GDAL.jl@5069a75?

And supposedly some of your at-gdal lib calls can now be replaced with a GDAL.jl function call? Doesn't have to be part of it, but would be nice if you can drop workarounds :)

It curiously fails locally for me, but haven't found the problem yet.

ArchGDAL: Error During Test
  Got an exception of type LoadError outside of a @test
  LoadError: GDALError (CE_Failure, code 3):
        VSIFReadL(00000000360018E0,6*4) @ 86498296 failed in HFAEntry().
  No error

  Stacktrace:
   [1] gdaljl_errorhandler(::GDAL.CPLErr, ::Int32, ::Cstring) at C:\Users\visser_mn\.julia\v0.6\GDAL\src\error.jl:26
   [2] #unsafe_read#17(::ArchGDAL.GDALOpenFlag, ::Ptr{Ptr{UInt8}}, ::Ptr{Ptr{UInt8}}, ::Ptr{Ptr{UInt8}}, ::Function, ::String) at C:\Users\visser_mn\.julia\v0.6\ArchGDAL\src\dataset.jl:248
   [3] unsafe_read(::String) at C:\Users\visser_mn\.julia\v0.6\ArchGDAL\src\dataset.jl:248
   [4] #read#92(::Array{Any,1}, ::Function, ::##192#204, ::String, ::Vararg{String,N} where N) at C:\Users\visser_mn\.julia\v0.6\ArchGDAL\src\context.jl:81
   [5] #registerdrivers#39(::Array{Any,1}, ::Array{Any,1}, ::Function, ::##191#203) at C:\Users\visser_mn\.julia\v0.6\ArchGDAL\src\context.jl:21
   [6] registerdrivers(::Function) at C:\Users\visser_mn\.julia\v0.6\ArchGDAL\src\context.jl:5

visr added 3 commits July 8, 2018 15:37
This works on 0.6, on 0.7 it should be `use Dates`, but this is needed to get around this error in 0.7:
UndefVarError: Date not defined
Copy link
Collaborator

@visr visr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even though AppVeyor is green, it does fail this test, but it's just floating point fuzziness. Maybe good to replace it with something less sensitive? The result is different on different platforms.

Otherwise, LGTM!

@yeesian
Copy link
Owner Author

yeesian commented Jul 9, 2018

Even though AppVeyor is green, it does fail this test, but it's just floating point fuzziness. Maybe good to replace it with something less sensitive? The result is different on different platforms.

Which test are you referring to?

@visr
Copy link
Collaborator

visr commented Jul 9, 2018

Ah sorry I forgot the link:
https://ci.appveyor.com/project/NgYeeSian/archgdal-jl/build/job/vfuw912r0ke8xkx8#L59

@test AG.toJSON(poly) == "{ \"type\": \"Polygon\", \"coordinates\": [ [ [ 1179091.164690328761935, 712782.883845978067257 ], [ 1161053.021822647424415, 667456.268434881232679 ], [ 1214704.933941904921085, 641092.828859039116651 ], [ 1228580.428455505985767, 682719.312399842427112 ], [ 1218405.065812198445201, 721108.180554138729349 ], [ 1179091.164690328761935, 712782.883845978067257 ] ] ] }"

@visr
Copy link
Collaborator

visr commented Jul 9, 2018

I'm still getting the VSIFReadL error above. At first I thought it was unrelated, but on ArchGDAL master I'm not getting it. AppVeyor doesn't see it though. @evetion, do you get the same error locally on Windows?

@evetion
Copy link
Collaborator

evetion commented Jul 9, 2018

I'm getting the AG.toJSON failing test. But no VSIFReadL or any other errors.

@visr
Copy link
Collaborator

visr commented Jul 9, 2018

Ok thanks. So lets ignore VSIFReadL and attribute it to my pc being wonky for now. If it keeps popping up or I can reproduce elsewhere (or others reading this see it), we can make an issue.

@yeesian yeesian merged commit 74f2694 into master Jul 10, 2018
@yeesian
Copy link
Owner Author

yeesian commented Jul 10, 2018

Thanks for the review and fixes!

@yeesian yeesian deleted the juliageo-gdal branch July 10, 2018 02:09
@evetion evetion mentioned this pull request Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants